Memos, Letters and Short Reports

Most of the writing that actually moves an organization is short. A half-page memo reroutes a supply chain. A one-paragraph letter closes or reopens a relationship with a vendor. A two-page report funds a position, kills a project, or changes how a unit staffs its evening shift. These documents are small enough that people write them carelessly and consequential enough that carelessness shows. They also outlive the moment: the memo you send Tuesday afternoon can be pulled from a shared drive four years later by an auditor, a surveyor, or an attorney who was not in the room and will not ask you what you meant. This chapter treats the three short forms as craft objects with parts, patterns, and testable standards. You will write openings that land in thirty words, refusals that stay humane, and findings that a stranger can act on without calling you.

Section 1Pick the Form Before You Write the Sentence

What each form is actually for

A memo is an internal document. It assumes shared context, skips the courtesies that strangers need, and exists to make something happen inside the organization: a policy changes, a deadline moves, a decision gets recorded. Because everyone in the distribution already knows what a par level is and where 4 West is, a memo can start at full speed. That efficiency is exactly why memos go wrong — writers assume more shared context than the reader has, especially when the memo reaches a float nurse, a new hire, or a night-shift manager three weeks later.

A letter is an external document. It crosses the boundary of the organization, and the moment it does, it stops being your voice and becomes the institution’s. Letters carry letterhead, a signature, and an implied warrant that someone with authority stands behind the words. They also assume no shared context: the recipient may not know your title, your department, or why you are writing. Everything a memo can leave out, a letter has to supply.

A short report is defined by its content, not its audience. A report answers a question with evidence. It can go up the chain, down the chain, or out to a regulator, and it can be delivered in memo format or letter format — those are wrappers. What makes it a report is that it contains findings the reader did not already possess, gathered by a method the reader can evaluate. If you are only requesting or announcing, you have a memo. If you are telling the reader what you found out, you have a report.

The channel is not the genre

Confusing the two is the most common structural error in workplace writing. The channel is how the document travels: email, a printed page, an intranet post, a signed PDF, a message in the electronic health record. The genre is what the document is: memo, letter, report, procedure. A single genre can ride any channel. A formal letter of complaint to a supplier can be emailed as a signed PDF and lose nothing. An informal memo posted on a break-room corkboard is still a memo.

Choose in this order. First, decide what the reader needs (genre). Second, decide how it should travel (channel). Third, decide how formal to sound (register). Writers who reverse this order end up with the wrong document: a legally significant refusal typed casually into an email body, or a two-line schedule change dressed up as a letter with an inside address and a complimentary close, which reads as either sarcastic or alarming.

One practical consequence: the channel usually determines the record. A memo posted to a shared drive is findable in five years. The same memo sent as a chat message may be purged in ninety days. If the content matters to the organization’s memory — a policy change, an approval, a documented refusal — choose a channel that preserves it, and say inside the document where it will live.

A thirty-second selection test

Ask four questions. Is the primary reader inside or outside my organization? Does anyone need a signature, letterhead, or institutional voice? Am I asking for action, or reporting what I found? Will a stranger read this a year from now with no one available to explain it? The last question is the one people skip, and it is the one that decides how much context you have to write down.

Below, one situation is written three ways. A hospital unit has been running out of glucometer test strips. Same facts, three readers, three forms. Notice that the opening sentence changes completely while the underlying truth does not.

Section 2The Memo: Header, Headline, Action

The header block does real work

Four lines: TO, FROM, DATE, SUBJECT. Each one is functional, not decorative. The TO line is a promise about responsibility — the people named there are expected to act. A copy notation (cc) means informed, not responsible, and that distinction should be stated in the body if there is any chance of confusion. Writing “Charge nurses on 4 West and 4 East” on the TO line and “cc: N. Okafor, Nurse Manager” underneath tells the reader instantly who owns the task.

The DATE line is the anchor for the record. Write it out: August 3, 2026, not 8/3/26, which reads as March 8 to a large share of the world and to plenty of software. In printed memos, writers traditionally place their handwritten initials beside their typed name on the FROM line; the initials signal that the writer read the final version and stands behind it. That convention has migrated into electronic form as a verified sender or an electronic signature block, and it still carries the same meaning.

The SUBJECT line is the part people write last and the part readers use first. A subject line must name the topic and the reader’s stake in it. “Update” is not a subject. “Policy” is not a subject. A subject line does its job when a reader scrolling a full inbox can decide, without opening anything, whether this concerns them today.

Bottom line up front

Bottom line up front, usually abbreviated BLUF, is the practice of putting the decision, the change, or the request in the first sentence and the reasoning after it. It came into wide civilian use from military staff writing, and it survives because it matches how busy people actually read: they triage on a phone, decide in seconds whether a message is theirs, and read the rest only if the answer is yes. Save the background for paragraph two, where the readers who need it will find it.

Here is a memo opening written the way most people write a first draft, with the reasoning in front and the point buried at the bottom:

Weak. “As many of you may recall, at the March staff meeting several members of the unit council raised concerns about the process by which certain point-of-care supplies are ordered and restocked. Since that time, a workgroup has met three times and reviewed data from the past two quarters, in consultation with Materials Management and with input from the evening charge nurses. After considerable discussion of the various options available to us, and taking into account the constraints identified by Finance, a decision has now been reached regarding ordering.”

Better. “Starting Monday, August 3, all glucometer test strips will be ordered through Central Supply rather than the unit stockroom. Charge nurses need to do one thing: send your unit’s par level to Materials Management by Friday, July 31. Background follows.”

The second version is not merely shorter. It reorders the information so that the reader’s question — what do I have to do? — is answered before anything else. Notice too that the weak version never actually names the decision. It announces that a decision exists. That is a common failure, and it usually means the writer has not decided how to say the hard part.

Body architecture and the action line

Below the opening, a memo should be built in chunks a reader can scan. One idea per paragraph. Three to five sentences per paragraph, not eleven. If the memo runs longer than a single screen, add short bold headings — What is changing, Why, What you need to do, Who to ask — because a heading lets a reader who only needs one section skip straight to it without missing the parts that apply to them.

Every memo that asks for anything ends with an action line: a single sentence naming who does what by when, plus how you will know it happened. “Charge nurses: email your par level to [email protected] by 1700 on Friday, July 31; I will confirm receipt the same day.” If a non-response would be acceptable, say so explicitly with a default clause — “If I do not hear from you by Friday, I will carry forward your current par level unchanged.” Defaults prevent the ambiguity that produces a second memo two weeks later.

One underused move is negative space: telling readers what you are not asking for. “No change to how you document blood glucose in the chart. No change to the meter itself.” Two sentences of that kind prevent a dozen questions and stop people from inventing work that does not exist.

Section 3Letters: Speaking as the Institution

The parts, and why each one survives

A standard business letter runs in a fixed order: letterhead, date, inside address (the recipient’s full name, title, organization, and mailing address), salutation, body, complimentary close, signature, typed name and title, then optional enclosure notation and copy notation. The dominant modern layout is block format: every element flush left, no paragraph indents, a blank line between blocks. Modified block, which starts the date and the closing block at the horizontal center of the page rather than at the left margin, is still used in law and in some traditional institutions; both are correct, but pick one and hold it for the whole letter.

The inside address is not redundant with the envelope. It travels with the letter into a file, so that a reader in 2031 knows who received this and in what role. Titles matter for the same reason: “Ms. Dana Ortiz, Director of Materials Management” documents the authority of the person addressed. In United States business practice a formal salutation takes a colon (“Dear Ms. Ortiz:”); a comma reads as personal correspondence and is standard in British usage, which is a genuine transatlantic difference rather than an error.

When you do not know the recipient’s name, address the role: “Dear Credentialing Committee:” or “Dear Claims Review Team:”. Whether “To Whom It May Concern” is acceptable is genuinely contested — several style guides still permit it for letters of reference and other documents with no known reader, while most hiring and business-writing guidance now treats it as a signal that the writer did not do thirty seconds of research. The safe practice is simple: use a role when you can find one, reserve the generic phrase for documents that truly have no addressee.

Direct, indirect, and the honest disagreement about buffers

The direct approach puts the main message first: approvals, routine requests, order confirmations, good news, most claims. The indirect approach delays the main message behind a buffer — a neutral or appreciative opening — then gives reasons, then the refusal, then an alternative. It is the traditional pattern for bad news, and it is taught in nearly every business-communication textbook.

The evidence for buffering is mixed. Studies of reader response have found that recipients often perceive delayed bad news as evasive, and that a buffer which sounds warm before a refusal can read as manipulative once the reader reaches paragraph three. Practitioners in healthcare, safety, and regulatory contexts increasingly favor a direct refusal delivered with respect. A workable synthesis: keep the buffer to one sentence, make the refusal unmistakable, give the real reason, and spend most of your space on what the reader can do next. Never let the reader finish the letter unsure whether the answer was yes.

Compare these two refusals of the same request.

Weak. “Thank you for your recent inquiry regarding educational funding. We value the professional development of all our team members and appreciate your interest in advancing your practice. Unfortunately, due to circumstances beyond our control, and in light of current budgetary considerations, we regret to inform you that your request cannot be accommodated at this time. We hope you will consider reapplying in the future.”

Better. “Thank you for the detailed application. We cannot approve tuition reimbursement for the CCRN review course. The fund is limited by policy to coursework that leads to a degree or an initial license, and the CCRN is a specialty certification. Two things are still available to you. The department can pay the certification exam fee directly under the certification line, and the review course qualifies for eight hours of paid education time. Send me a note if you want me to start either of those.”

The second letter refuses more clearly and treats the reader better. It gives a real reason instead of an atmospheric one, it does not blame “circumstances,” and it leaves the reader with two usable next steps rather than a vague invitation to try again someday.

Goodwill without gush

You-attitude means writing from the reader’s side of the transaction. “We require three business days to process refunds” becomes “Your refund will post within three business days.” Same fact, but the second version answers the question the reader actually has. Positive framing works the same way: “The clinic is closed after 4:00” becomes “The clinic is open until 4:00, and the nurse line answers until 8:00.” Neither move requires you to soften a fact or hide a limit; both require you to state the fact in terms of what the reader gets.

Delete the dead phrases. Please be advised that adds nothing to the sentence that follows it. Pursuant to your request means “you asked.” Enclosed please find is a fossil; write “I have enclosed the corrected invoice.” At your earliest convenience is not a deadline and should be replaced with a date. These phrases feel professional because they sound unlike speech, but readers hear them as filler and skim past exactly the sentences you most wanted them to read.

Apology deserves particular care, especially in clinical settings. There is a real and useful distinction between expressing regret for a person’s experience and admitting fault for an outcome you have not investigated. “I am sorry this happened to you, and I want to find out why” is human and honest. “We were negligent” is a legal conclusion that is not yours to reach in a letter. Many United States jurisdictions have enacted apology or benevolent-gesture statutes that limit the admissibility of expressions of sympathy, but those statutes vary widely in scope, and some protect sympathy while explicitly excluding admissions of fault. Say the true, kind thing; route the fault question to the people whose job it is.

Section 4Short Reports: Findings a Stranger Can Use

Four workhorses

Most short reports are one of four kinds. An informational or periodic report tells the reader what happened during a defined window — monthly volumes, quarterly compliance rates, an annual education summary. A progress report tracks work against a plan: what was completed, what slipped, what is now at risk, and whether the end date has moved. An incident report records a single deviation from expected care or operations. A recommendation or feasibility report evaluates options against criteria and argues for one.

These are not interchangeable, and mixing them is a frequent failure. A progress report that omits the schedule impact is a status update, not a progress report; the whole reason the reader asked is to learn whether the date still holds. A recommendation report that presents options without stating criteria leaves the reader unable to check your reasoning, so all they can do is trust or distrust you.

Findings, conclusions, and recommendations are three different things

A finding is something you observed or measured. A conclusion is what the finding means when judged against a standard. A recommendation is what someone should now do. Writers collapse these constantly, usually by jumping from a number straight to an action, and the report loses its power because the reader cannot see where judgment entered.

Watch the same evidence pass through all three. Finding: “Median call-light response time on 4 West was 6 minutes 40 seconds across 2,240 calls in June; the 90th percentile was 14 minutes 10 seconds.” Conclusion: “Response time exceeds the unit’s 4-minute internal standard, and the gap is concentrated between 1900 and 2300, when one patient care technician covers 28 beds.” Recommendation: “Move one PCT shift from 0700–1500 to 1500–2300 for a 60-day trial and re-measure when the trial ends.”

Keeping them separate does something useful: it lets a reader disagree with you precisely. A director might accept the finding, accept the conclusion, and reject the recommendation because a different unit needs that position more. That is a productive disagreement. If you had written only “we need another PCT at night,” the same director could only accept or refuse, and the measurement work you did would vanish.

Short reports usually do not need a formal executive summary — that convention belongs to the longer documents in Chapter 6 — but they do need the headline finding in the first three sentences. If a busy reader stops after the opening paragraph, they should still leave with the single most important thing you learned.

Evidence, and the line between observation and inference

Every number in a report needs three attachments: a denominator, a date range, and a source. “Falls are up” is unusable. “Six falls in June across 750 patient days, up from two in May across 780; the rate rose from 2.6 to 8.0 per 1,000 patient days; source: unit quality dashboard pulled July 6” can be checked, argued with, and acted on. Include the pull date, because dashboards backfill and your numbers will not match someone else’s if they query a week later.

The observation-versus-inference line matters most in incident reports, where writing what you concluded instead of what you saw can create a record that is both inaccurate and damaging. Consider an unwitnessed event.

Weak. “Patient fell in the bathroom because the night aide did not answer the call light in time. Patient was confused and clearly should have had a sitter. Bed alarm was probably not on.”

Better. “At 0215 this writer entered room 412 and found the patient sitting on the floor beside the toilet. The patient stated, ‘I slipped getting up.’ No one witnessed the event. The call light was within reach and not activated per the console log. The bed alarm was found in the off position. Vital signs at 0218: BP 138/82, HR 92. No obvious deformity or laceration; a 2 cm reddened area was noted on the right hip. Dr. Ellison notified at 0224; portable hip film ordered. Family notified at 0250.”

Three things changed. Inference became observation — “fell” became “found on the floor,” which is what the writer actually knows. Blame disappeared, because assigning cause is the investigation’s job, not the reporter’s. Hedges like “probably” were replaced by verifiable states. The second version is also longer, and that is the correct trade: precision costs words.

Section 5Making It Land: Persuasion, Revision, and the Record

Problem, cost, options, ask

Most short documents that fail were not badly written; they simply never asked for anything specific. A persuasive memo or report has four moves. Name the problem in one measurable sentence. Quantify the cost of leaving it alone. Lay out two or three options, including the cheapest and the do-nothing case. Then make one ask, in one sentence, with a decision date.

A worked skeleton, using the call-light data from the previous section: Problem — “Between 1900 and 2300, one PCT covers 28 beds on 4 West; median call-light response in that window is 11 minutes against a 4-minute standard.” Cost — “Four of the six June falls occurred in that window. Medicare does not pay the added cost of a fall with injury that was not present on admission, and commonly cited estimates put that added cost near 14,000 dollars per fall, so two avoided falls would fund the more expensive option below for a year.” Options — “A: move one existing PCT shift to 1500–2300, no new FTE. B: add 0.5 FTE evening PCT, roughly 26,000 dollars annually. C: no change and continue monitoring.” Ask — “I am requesting approval of Option A as a 60-day trial beginning September 1; I need a decision by August 14 to build the September schedule.”

Two disciplines make this work. First, use the reader’s own criteria, not yours — if your director is evaluated on overtime and length of stay, connect your evidence to overtime and length of stay. Second, present the do-nothing option honestly. Readers trust a writer who names the case against their own proposal, and they discount one who pretends there is only one reasonable path.

A rubric you can run in ten minutes

Revision is not rereading. Rereading confirms what you meant; revision tests what the document does. Run the following checks in order on a printed copy or a full-screen preview, not in the editing window where you wrote it, because your eye has already memorized that view. Each check has a test you can perform in under a minute and a specific fix.

Routing, transmittal, and the record

When a short document accompanies something larger — a contract, a data set, a full report — it becomes a transmittal document. A transmittal memo or letter does four things in about a hundred words: states what is enclosed, says why it is being sent, points to the one or two things the reader should look at first, and names the next step. Readers use transmittals as a map, so a transmittal that only says “attached please find the report” wastes the most-read paragraph in the package.

Routing decisions deserve deliberate thought. Put decision-makers on the TO line and everyone else on cc. Use a named distribution list rather than twenty individual addresses so the record shows who received it. Put a version and a date in both the filename and the document footer — 4West_calllight_report_2026-07-14_v2 — because a year from now, two undated copies with different numbers are worse than no copy at all. And resist reply-all: a thread of thirty people watching two of them negotiate is a small daily tax on an entire department.

Finally, remember that these documents are records, and records generally are not yours to delete. Retention schedules, litigation holds, and public-records laws apply to memos and reports the same way they apply to contracts, and in regulated settings the deletion itself can be a more serious problem than anything the document said. The productive way to hold this is not fear but habit: write documents you would be comfortable reading aloud, with the facts you actually have, in language that says what you mean. That standard makes writing faster, not slower, because it removes the effort of hedging.

Words worth knowing