Skip to content
ConsultEvo

How to Write a Business Letter: A Practical Format Guide

To write a business letter, define the outcome, identify the right recipient, state the purpose early, include only relevant facts, specify the next step, and review the finished document before sending. For example, a delivery-date request should identify the order, state the current date, and ask the recipient to confirm a specific next step.

A business letter is professional written communication with a clear business purpose. The appropriate structure depends on the recipient, organization, document type, and delivery channel. If a short email meets the need and no formal document is required, do not add letter formatting simply for appearance.

A useful drafting prompt is: I am writing to [request, inform, propose, or confirm] [specific outcome] by [date or next step]. Use it to clarify the message, not as a formula that must appear in the final letter.

How do you write a business letter?

Start by answering three questions: What should the reader know or do? Why is this person or group the right recipient? Is there a deadline, reference number, or other fact the reader needs to act?

If you cannot describe the intended outcome in one sentence, clarify the request before drafting. A letter may be printed, attached as a PDF, or delivered through another channel. A printed letter commonly includes a return address and recipient block. A digital letter may not need every postal detail, but it should still identify the sender and provide enough information for the recipient to respond.

Follow the recipient’s or organization’s required format first. If no house style applies, block format is a practical default.

Start with the purpose and recipient

Confirm the recipient before writing the salutation. Use an approved company directory, the organization’s website, or a current CRM record to verify a person’s name, preferred title, and contact details. Do not guess a title or gender. When a person’s identity is unknown, use a verified department, committee, or organization name where appropriate.

If several contacts could be suitable, ask a person to resolve the choice rather than letting an AI system select one silently. If a contact-data provider is used, check its accuracy, permissions, terms of use, and applicable privacy requirements.

For a formal letter, Dear Jordan Lee: is a supported salutation convention. Open punctuation is also used in some organizations. Use the recipient’s preferred title or organizational protocol when known. To whom it may concern is not categorically incorrect, but a verified person, department, or committee is usually more specific.

Use a clear business-letter structure

Common elements include a sender heading or letterhead, date, recipient details where appropriate, salutation, body, complimentary close, signature and typed name, and an enclosure notation when documents are actually included. Follow a required organizational template if one exists.

For a letter with supporting detail, organize the body around three jobs: state the purpose first, provide relevant facts next, and finish with the requested action or next step. A short acknowledgment may need only a few sentences.

Sender name and contact details
Date
Recipient name and title
Organization and address, if needed

Dear Jordan Lee:

I am writing to request confirmation of the revised delivery date for PO-1048.
Our current record lists 14 May as the expected date.

Please confirm the date by 8 May.

Sincerely,

Morgan Patel
Account Manager
Enclosures, if documents are actually included

This is an illustrative block-format skeleton, not a mandatory form. A generic title such as Business Letter is usually unnecessary unless the document type or house style calls for one.

Choose a layout that follows the recipient’s requirements

Purdue OWL’s business-letter format guidance describes three common layouts:

  • Block: Text is left-aligned, paragraphs have no first-line indent, and a blank line separates paragraphs. It is a straightforward default when no house style is specified.
  • Modified block: The body and addresses remain left-aligned, while the date and closing move toward the center or right. Exact positioning depends on the template.
  • Semi-block: Paragraphs use first-line indents. Purdue describes this as less frequently used than block and modified block.

Use single-spaced paragraphs with a blank line between them unless the template says otherwise. Readable 11- or 12-point type and margins of approximately one inch are common conservative choices, not universal requirements. Do not force a letter onto one page when supporting detail is necessary.

For a digital letter, include the sender information and recipient details that help the reader identify the message and act on it. A PDF may not require every mailing-address element used for a printed letter. The organization’s template and the purpose of the document take priority.

Write the body, close, and enclosure line accurately

Put the main point early and keep each paragraph focused on one useful idea. Include facts that help the reader understand or respond, but remove background that does not advance the purpose. End with a proportionate, specific action such as confirming a date, replying to a question, reviewing a proposal, or attending a meeting.

Use a stated deadline only when the date is known and appropriate. Do not invent a deadline merely to make the request sound definite. For a formal letter, Sincerely, is conventional, although the relationship and house style may call for another sign-off.

Use an enclosure line only when the referenced documents are actually included. If the letter says Please find enclosed, verify that the file or paper document exists and is correctly identified. If an automated workflow creates the letter, make the enclosure claim depend on a validated attachment record rather than generated prose alone.

Decision point

Treat the enclosure statement as a deterministic field check: an enclosure claim requires an actual attachment or enclosure record, and an attachment requires an accurate description when the selected format uses one.

Review the letter before sending

Read the letter once for meaning and once for mechanics. Check the recipient name and title, sender identity, dates, amounts, deadlines, reference numbers, requested action, and attachment references against their source information. A grammar checker can flag possible issues, but it cannot approve the writer’s intent or establish that a commitment is correct.

Keep routine correspondence concise without treating one page as a rule. Use additional pages when the purpose requires supporting detail. For a digital letter, confirm that the final file renders correctly in the intended format and follows the organization’s document process.

Final check before sending
  • Recipient identity, title, and destination are verified.
  • Purpose and requested action are clear and consistent.
  • Dates, amounts, reference numbers, and commitments match approved source information.
  • Sender identity and contact details are correct.
  • Every enclosure or attachment mentioned is present and correctly identified.
  • The final file renders correctly and has the required approval status.

Letters involving employment, legal matters, financial commitments, discipline, sensitive personal information, or other consequential content need appropriate human review and approval. A proofreading tool is not an approval authority.

Use AI or document automation only for a bounded job

Keep fixed facts in validated fields: recipient and sender details, dates, amounts, addresses, reference numbers, commitments, letter type, and attachment metadata. AI can help turn approved information into clear prose, but it should not invent or change those facts. Use deterministic rules for required fields, date formats, allowed letter types, template versions, and enclosure presence.

A spreadsheet-to-document workflow can support draft production, but it is a proposed implementation pattern rather than a ready-made business-letter recipe. Zapier documents a Google Sheets New Spreadsheet Row trigger and a Google Docs Create Document From Template action that replaces placeholders in a user-created template available to the connected account. Test the template, placeholder formatting, permissions, and connected account before using the workflow.

The Google Docs copy link supplied by Zapier should not be treated as a verified standalone template. Independent access may require Google authentication, so confirm its contents and permissions before recommending it for production use. Zapier’s general tutorial for populating a Google Docs template from spreadsheet data is useful implementation evidence, but it is not a complete business-letter template or approval-and-delivery system.

Use one source row for one intended generation event

Define the source row’s grain before building the workflow. One row should represent one intended letter-generation event, not one paragraph, citation, attachment, or email attempt. If one submission can legitimately produce several letters, add an explicit event or revision ID.

{
  "submission_id": "form-7842",
  "letter_event_id": "form-7842-rev-01",
  "recipient_full_name": "Jordan Lee",
  "purpose_summary": "Confirm a revised delivery date",
  "approved_facts": ["PO-1048", "Expected date: 14 May"],
  "requested_action": "Confirm by 8 May",
  "template_version": "delivery-letter-v3",
  "review_status": "Needs review"
}

The values are illustrative. Preserve the source record, source snapshot, template version, and document ID used to create the draft. For AI-assisted prose, supply the approved facts, purpose, and requested action, then compare names, dates, amounts, commitments, and attachment references in the output with those inputs.

Use a review-gated implementation sequence

01Intake and validateCollect one event record with a stable ID, recipient, sender, purpose, approved facts, requested action, template version, and attachment metadata. Stop missing or ambiguous records and assign an operator to resolve them.
02Draft and createUse AI only for optional prose based on approved fields. Create the Google Doc from the accessible, tested template, check required placeholders, and save the document ID and source event ID.
03Review and approveSet the draft to Needs review. A designated reviewer checks facts, tone, recipient, enclosures, and risk, then records approval or rejection with a reason and timestamp.
04Deliver and recordOnly after approval, use a separately configured and tested PDF or email step if needed. Record the final document, reviewer, approval time, delivery result, and any error code. Inspect failed runs before replay.

Filters can stop records that do not meet specified conditions, and Paths can route records to different outcomes. Availability and task behavior depend on the Zapier plan. PDF conversion, attachment handling, delivery, permissions, and approval must be configured and verified separately. For implementation support, see Zapier automation services.

Prevent duplicates at the correct grain

Use an idempotency key that identifies one letter-generation event, such as letter type + source submission ID + template version + content revision. Do not use recipient email alone, because one recipient may receive several legitimate letters. Zapier trigger deduplication applies within the scope documented for a Zap and does not guarantee that downstream actions will not create duplicates. Replaying a full run can also repeat successful actions.

Where concurrent processing matters, enforce uniqueness at the destination with a database unique constraint or transactional upsert. A spreadsheet lookup followed by a create is not a concurrency-safe uniqueness control. If the destination cannot enforce uniqueness, route collisions to an operator and preserve both the source event and attempted output for investigation.

Choose the right kind of signature

A typed name, an image of handwriting, drawn ink, an eSignature request, and a certificate-based digital signature are different things. Microsoft Word supports inserting a signature image and, in supported versions, inking, signature lines, and certificate-based digital signatures. A picture of handwriting is not certificate-based authentication, which requires a current digital certificate.

Google Docs supports eSignature requests for eligible Workspace accounts and PDFs, subject to edition and administrator settings. Check Google’s eSignature eligibility guidance before choosing that option. The document type, jurisdiction, identity assurance, consent, and organizational policy determine which method is appropriate. A feature description alone does not establish legal sufficiency.

Common questions about business letters

Is block format required?

No. It is a useful default when the recipient or organization has not specified another layout.

Does a business letter have to fit on one page?

No. Keep it concise, but use additional pages when the purpose requires supporting detail.

What should I do if I do not know the recipient’s name?

Verify whether a department, committee, or organization-level recipient is appropriate. Do not guess a person’s identity, title, or gender. If several contacts could be right, ask a person to resolve the choice.

Does a digital letter need the recipient’s postal address?

Not always. Follow the purpose, recipient expectations, and house style, and include enough sender information for the reader to identify and respond to you.

Can AI write the whole letter?

AI can draft prose from supplied information. Keep names, dates, amounts, addresses, commitments, and attachment claims in validated fields, compare the output with those inputs, and obtain appropriate approval before delivering consequential content.