Business Messages

This chapter moves through the planning, drafting, and revising phases of business writing. You will learn how to select a channel, organize positive and neutral messages directly, make requests, respond to inquiries, and write usable instructions. Leo’s case develops from a vague first sentence into a patient text and a staff email designed for different needs.

Professional writers aim to make messages clear, concise, complete, correct, courteous, and easy to use. Writers do not create those qualities in one pass. They develop them through three overlapping phases: planning, drafting, and revising.

During planning, the writer defines the purpose, studies the audience, gathers facts, chooses a channel, and selects an organizational pattern. During drafting, the writer puts the main point and supporting details into sentences suited to the audience. During revising, the writer checks meaning, structure, tone, accuracy, mechanics, format, and delivery.

The phases overlap because new information may send a writer back to planning. A draft may reveal that the purpose is too broad. A revision may reveal a missing fact. Skilled writing is not a march from left to right; it is a controlled cycle that continues until the message serves its purpose.

Leo pauses before drafting. His patient message should explain the delay, tell the reader whether any action is needed, and set an update time. His staff message should coordinate a consistent response and provide an internal contact. The facts overlap, but the purposes differ.

Did You Know? A short message can require more planning than a long one. When space is limited, every detail competes for attention, so purpose and priority must be especially clear.

Analyze the Audience

Useful audience questions include:

• Who is the primary reader, and who else may see the message?
• What does the reader already know?
• What question will the reader ask first?
• What action, if any, can the reader take?
• What terms need explanation?
• What emotion or concern is likely?
• Does the message contain private, sensitive, or regulated information?

Audience analysis does not mean guessing stereotypes about a group. It means using relevant information about this communication situation. For patients, Leo should use plain language and avoid internal software terms. For clinic staff, he can use established process terms, but he still needs to explain any temporary procedure.

Digital communication also creates a durable impression of the writer and organization. Research on email politeness shows that electronic messages carry relationship signals as well as information.1 Research on social network sites likewise illustrates that digital platforms are spaces where people learn communication practices, not neutral containers for words.2 A greeting, specific request, acknowledgment, and courteous close can help readers interpret intent, especially when voice and facial expression are absent.

Define Purpose and Select a Channel

A specific purpose guides every later choice. “Send an update” is broad. “Tell affected patients that confirmation may take one business day longer and that no action is needed” is usable. A purpose statement should name what the reader should know or do.

Channel selection depends on urgency, complexity, privacy, need for interaction, need for a record, and audience access. Email supports detail, attachments, and an accessible record. Text supports a short, timely notice. Chat works for quick coordination when the organization permits it. A phone or video conversation supports immediate questions and sensitive discussion. A letter may suit formal external communication or a reader’s access needs.

Convenience for the sender is not the only factor. A channel should fit the message and the audience. Sensitive information should travel only through approved systems. If a matter is emotionally charged or likely to create questions, a live conversation followed by a written confirmation may work better than a long email. Channel choice is part of the message, not a final delivery detail.

Professional Tip: If readers are likely to forward or save a message, write it so the purpose and context remain understandable outside the first screen where it appeared.

A brief business message should let the reader find the central point quickly. Use a descriptive subject line, lead with the purpose when the situation is routine or neutral, place supporting details in a logical order, and end with the next action or goodwill close.

Paragraphs should usually carry one main idea. Lists help when items are parallel, readers will scan, or steps must happen in order. Headings help longer messages but can make a two-paragraph email feel overbuilt. Format should reduce effort, not decorate the page.

Conciseness removes unnecessary words without removing needed meaning. “At this point in time” can become “now.” “Due to the fact that” can become “because.” Yet “Appointment processing is delayed” may be too concise if it omits the size of the delay and what readers should do. The correct question is not “Can this be shorter?” but “Can the reader understand and act with less effort?”

Positive and Neutral Messages

Positive and neutral messages often use a direct pattern:

1. open with the main point;
2. provide relevant details or explanation;
3. identify any action, deadline, or contact; and
4. close with a specific, courteous statement.

Use this pattern for confirmations, routine requests, answers, announcements, acknowledgments, and instructions when the reader is unlikely to resist the message. A direct opening respects the reader’s time.

Consider a confirmation:

Your orientation is confirmed for Tuesday, August 11, at 9:00 a.m. at the Westview clinic. Please arrive ten minutes early and bring photo identification. Use the visitor entrance on Pine Street; staff at the desk will direct you to Conference Room B. If you need an access accommodation, contact Jordan Lee at 555-0148.

The message answers likely questions in the order the reader will use the information. It avoids a long opening about how pleased the organization is to provide details.

Goodwill is more credible when it is specific. “Thank you for sending the updated form by noon” connects courtesy to the reader’s action. A generic phrase such as “Have a great day” may be friendly, but it cannot repair an unclear request or dismissive tone.

A routine request should make the requested action visible. State the request early, explain only the context the reader needs, include relevant dates or specifications, and make the response path clear.

Weak request: “I was wondering if maybe you had time to look into the issue we discussed because it is becoming a concern.”

Stronger request: “Please confirm by 2:00 p.m. whether the three pending referrals reached the specialist’s queue. I need the status to update the patients before the office closes.”

The stronger version names the action, scope, deadline, and reason. It remains courteous without hiding behind hesitant wording. A request should also respect authority. Asking a coworker to provide information is different from directing that person to change a process.

A response to an inquiry should answer the actual question near the beginning. If the answer is unknown, say what is known, what will be checked, who owns the follow-up, and when the reader can expect it. Do not fill space with unrelated background to avoid saying “I do not know yet.”

When several questions arrive together, mirror their order or use a short labeled list. This helps the reader verify that each item was addressed. If the request contains an incorrect assumption, correct it neutrally: “The visit is scheduled at Northside, not Westview. The date and time remain unchanged.”

Think About It: Which is more respectful: a very warm message that hides the requested action, or a direct message that explains the action and reason? How could you combine clarity and warmth?

Instructions translate a process into observable actions. Before writing them, perform or verify the actual process. Identify the starting condition, required materials or access, steps, decision points, expected result, and recovery path if something goes wrong.

Use numbered steps when sequence matters. Begin each step with an action verb. Keep one main action per step. Place warnings before the risky action, not after it. Define what success looks like. If the process branches, state the condition clearly: “If the status reads Pending Review, go to Step 5. If it reads Returned, contact the referral coordinator.”

Good instructions also respect role boundaries. In allied healthcare, an administrative employee should not turn a process message into clinical guidance. Privacy and approved-system rules still apply. Examples should use fictional or de-identified details.

Example: confirming a contact preference

1. Open the patient’s contact page in the approved system.
2. Ask the patient to confirm the phone number using the organization’s identity-verification procedure.
3. Record the preferred contact method in the designated field.
4. Read the preference back to the patient.
5. Save the record and confirm that the update appears.
6. If the system does not save, follow the downtime procedure and notify the designated support contact.

The final step matters. Without a recovery path, instructions work only under ideal conditions.

Editing and proofreading are related but different. Editing improves meaning, organization, tone, and usefulness. Proofreading checks the final surface: spelling, grammar, punctuation, names, dates, links, numbering, and layout. Proofread after major editing so you do not polish sentences that will be removed.

Read important messages in more than one way. Review once for purpose, once for facts and action, and once for mechanics and format. For high-consequence communication, use a second qualified reviewer when policy permits. Never paste private information into an unapproved writing tool.