Editing, Review and Quality Control

A first draft is a hypothesis. Editing is the experiment that tests it. Most writing that damages a career or a patient is not badly conceived — it is simply unfinished: a discharge instruction with a stray decimal point, a policy memo whose second paragraph contradicts its fourth, an email that reads as hostile because one word never got changed. This chapter treats editing as a craft with named moves and a fixed sequence, not a vague instruction to “look it over.” You will learn to separate revising from editing from proofreading, to cut a paragraph by a fifth without losing a single fact, to ask for review in a way that produces usable answers instead of “looks good,” to verify the handful of details that carry nearly all the risk, and to build a small quality system — a style sheet, a short checklist, a sign-off trail — that keeps catching errors on the days you are too tired to catch them yourself.

Section 1Three Passes, Not One

The single-pass trap

Watch most people “edit” and you will see them start at the top of page one and crawl to the end, fixing whatever they notice: a comma here, a weak transition there, a whole missing section noticed on page four and patched with an apology. That approach feels efficient and is not. Your attention is finite. If you spend it on a comma in paragraph two, you have less of it for the discovery on page four that paragraph two should not exist.

Skilled editors split the work by altitude. One pass at 30,000 feet: does this document do its job for this reader? One pass at 500 feet: does each sentence carry its weight? One pass at ground level: is anything misspelled, mispunctuated or broken? Each pass asks one question and deliberately ignores the others. That ignoring is the hard part and the whole point.

A 1976 NASA Jet Propulsion Laboratory handbook, The Levels of Edit, formalized this idea by naming nine distinct types of edit and grouping them into five levels, so a project could specify how much editing a document would receive rather than pretending all documents get “edited.” You do not need nine types. You need the habit underneath: decide the level of edit before you start, based on stakes, audience and shelf life.

Pass one — revising: does the document work?

Revising means re-seeing. You are allowed to delete paragraphs, reorder sections, change the opening, and discover that your real recommendation is buried in the last line. Read the draft once, straight through, without touching anything. Then write one sentence at the top: What do I want this reader to know, decide or do? Now check whether the document delivers that in the first ten seconds of reading.

Three revising tests catch most structural failures. The headline test: if the reader read only the subject line, the first sentence and the headings, would they get the message? The so-what test: for every paragraph, can you say why the reader needs it? If the honest answer is “because I did the work,” cut it. The order test: does the document move from what the reader cares about most to least, or from what you did first to last? Chronology is almost always the wrong order for a workplace document.

Expect this pass to be violent. On a first draft of a two-page report, deleting 30 percent and moving two sections is a normal outcome, not a failure. You are not throwing work away; you are declining to make the reader pay for it.

Pass two — editing: does the sentence work?

Once the shape is settled, edit line by line for clarity, tone and accuracy of expression. Now you tighten, replace jargon, split tangled sentences, fix a paragraph that opens on its weakest sentence, and repair a tone that reads colder than you intended. Section 2 gives you the specific moves.

Editing has one prerequisite: the structure must be stable. If you are still arguing with yourself about whether the recommendation goes first or last, you are revising, not editing, and every sentence you polish is a sentence you may delete. Finish the argument first.

Pass three — proofreading: is it clean?

Proofreading is surface work: spelling, punctuation, capitalization, numbering, spacing, headings that say “Section 4” twice, a table that ends mid-row, a link that goes nowhere, the attachment you promised and did not attach. It is the last pass because everything you change in earlier passes creates new surface errors. It also demands a different mental mode — you are no longer reading for meaning, you are inspecting marks.

Proofreading your own writing is genuinely hard, because your brain supplies the text you meant. The standard explanation is familiarity: you are reading intention, not ink. Whatever the mechanism, the remedy is to break the familiarity — time away from the draft, a change of medium, machine narration, or another human being. Section 5 covers the techniques.

Section 2Editing the Sentence

Cut the run-up

Most workplace sentences begin with a runway before takeoff: It is important to note that…, Please be advised that…, The purpose of this memo is to inform you that…. These are warm-up phrases. They belong to drafting, where they help you get moving, and they should not survive editing. Delete the run-up and start with the noun that matters.

The same logic applies to phrases that do the work of a single word. Due to the fact that is because. In the event that is if. At this point in time is now. In order to is almost always to. Has the ability to is can. None of this is about elegance. Every extra word is a small tax on a reader who is charting between patients or reading on a phone in a stairwell.

Set yourself a numeric target and the cuts become mechanical rather than emotional. Take any paragraph you have written, count the words, and rewrite it 20 percent shorter with no loss of information. The first time, it feels impossible. By the fifth paragraph it feels like tidying.

Put the action in the verb

A nominalization is a verb wearing a noun costume: conduct a review instead of review, provide assistance instead of help, make a determination instead of decide, perform an assessment instead of assess. Nominalizations bloat the sentence and drain its energy, because the real action gets stashed in a noun while a limp verb (conduct, provide, make, perform) takes the stage.

Closely related is the expletive construction — a sentence that opens with There is, There are or It is followed by a clause. There are three factors that contribute to the delay hides both the subject and the verb. Three things caused the delay puts them back. When you delete there are, you are usually forced to name the actor, which is exactly the improvement you wanted.

Passive voice: a tool, not a sin

The advice to “avoid the passive” is over-applied, and professionals genuinely disagree about it. Plain-language guidance and most style handbooks favor the active voice as a default because it names the actor and is usually shorter. But experienced editors and linguists have pushed back hard on treating the passive as an error — it is a normal, useful English construction, and much of what people call “passive” in casual complaint is actually vagueness or nominalization.

The workable rule is a question, not a ban: Does the reader need to know who did this? In an incident report, The medication was administered at 0900 is a problem, because accountability is the point. In a lab methods section, Samples were centrifuged for ten minutes is fine and standard, because the actor is irrelevant and the procedure is the subject. In a patient handout, Your dressing should be changed daily is worse than Change your dressing every day, because the reader is the actor and needs to know it.

So: use passive voice when the actor is unknown, unimportant, or obvious; when the receiver of the action is the true topic of the sentence; or when naming the actor would be gratuitously accusatory in a document meant to fix a system rather than blame a person. Use active voice everywhere else, which in ordinary workplace writing is most places.

One sentence, one job

Long sentences are not automatically bad, but a sentence carrying three ideas, two qualifiers and a parenthetical is a comprehension test the reader did not sign up for. The repair is rarely subtle: find the second idea, put a period in front of it, and delete the connective tissue that was holding the pile together.

Vary the result. A page of six-word sentences reads like a fire alarm. Aim for a mix — a short sentence lands hardest when it follows a long one. Read the passage aloud and listen for the place where you run out of breath or lose the thread; that is where the sentence broke, regardless of what a readability score says.

On that point, be careful with readability formulas. Tools that report a grade level are counting sentence length and syllables; they cannot tell whether your terminology is familiar to your audience or whether your instructions are in the right order. They are a rough smoke detector, not a measure of comprehension, and writing to hit a target score can produce choppy, disconnected prose that scores well and teaches nothing. Use them to flag a paragraph for a second look, not to certify it.

Section 3Review That Actually Helps

Ask a better question

“Any thoughts?” is the most common review request in professional life and one of the least productive. It gives the reviewer no idea what stage the draft is at, what you have already decided, or what you are worried about — so you get comma corrections on a draft whose structure is still wrong, or a philosophical objection to the whole project on the day it is due.

A directed review request takes three lines and changes everything. Name the stage, name the ask, name the deadline. For example: Attached is a structural draft of the fall-prevention policy — content is not final and I have not proofread it. What I need from you: does the escalation path in Section 3 match what actually happens on nights? Please ignore wording. I need this by Thursday noon.

Match the ask to the reviewer. Your manager reviews for risk and politics. Your subject-matter expert reviews for technical accuracy. Your target reader — a new hire, a patient’s family member, a night-shift tech — reviews for whether the instructions can be followed. Sending all three the same request wastes two of them. Send each a different question and you get three non-overlapping sets of findings.

Comment so someone can act

A useful comment has three parts: the location, the problem and, when you can manage it, a possible fix. “Awkward” has one part and puts all the diagnostic work on the writer. “Sentence 4 packs three clauses — try splitting after ‘discharge’” has all three, and takes ten seconds longer to write.

Separate the categories of problem so the writer can triage. Mark blocking issues (the policy contradicts the union contract) differently from preferences (I would use a bulleted list here). If you do not label them, writers either treat every comment as mandatory and produce a Frankenstein document, or treat them all as optional and miss the one that mattered.

Praise specifically or not at all. “Love it!” tells the writer nothing they can repeat. “The first line states the ask in one sentence — do that in the cover note too” identifies a move worth reusing. Specific praise is not politeness; it is instruction.

Take feedback like a professional

The rule that saves the most time: the reader’s reaction is data; the reader’s proposed fix is a suggestion. If three reviewers stumble in the same paragraph, that paragraph has a problem, even if all three misdiagnosed it and even if you can prove the sentence is grammatically fine. You do not get to argue a reader out of confusion. You do get to solve it your own way.

Resist two reflexes. The first is explaining — “what I meant there was…” If you have to explain it in the meeting, the document has failed, because the document will be read without you in the room. The second is silent capitulation: accepting every edit including the ones that introduce errors. If a reviewer’s change is factually wrong, decline it and say why in one sentence.

Finally, close the loop. Tell each reviewer, briefly, what you did with their comments and what you did not, and why. It takes two lines, it makes people willing to review your next draft, and it prevents the awkward meeting where someone assumes their objection was quietly ignored.

Track changes, comments and reconciling versions

Learn your tool properly. In word processors, track changes records insertions and deletions as a reviewable redline; comments hold questions and reasoning that should not become part of the text. Keep them distinct: never write a comment that is actually an edit, and never make a silent edit that is actually an argument. Before sending any document outward, accept or reject all changes, delete all comments, and check the document’s properties — hidden tracked changes and stale comments leave your organization more often than anyone admits.

When several people review at once, you own the merge. The safest pattern is a single source of truth: one master file, one owner, reviewers commenting in a shared copy or returning marked copies you consolidate yourself. Parallel editing of separate downloaded copies is how a paragraph you deleted returns from the dead in the final version.

Set an end point. Reviews expand to fill available time, and a document that has been through nine rounds is not nine times better. Announce a close date in the request, and treat silence as silence — not approval. If you need someone’s sign-off, ask for the word “approved,” in writing, from the person whose name will be on it.

Section 4Verify Before You Send

The few things that carry all the risk

Not all errors are equal. A missing comma embarrasses you. A transposed digit in a dose, a wrong effective date on a policy, or a misspelled surname on a legal notice can cause real harm and real liability. Quality control means spending your verification effort where the consequences live, which in most professional documents is a short and predictable list: numbers, names, dates, money, links and attachments, quotations and citations, and identifiers.

Handle those items differently from prose. Prose you read; high-risk elements you check against a source. Reading a figure and thinking “that looks right” is not verification — it is recognition, and recognition is exactly what fails when you have typed the number four times already. Open the source document, put it beside the draft, and compare character by character.

Numbers deserve particular paranoia because they fail silently. Percentages that do not total 100, a table whose column sum does not match the text, a “30 percent increase” that the underlying data shows as 30 percentage points, a date that falls on a Sunday when the memo says Monday. Recompute rather than re-read; do the arithmetic independently and see whether you land on the printed figure.

Independent verification and read-back

Healthcare has spent decades engineering around the fact that competent, careful people misread things. Two of its habits transfer directly to writing. The first is independent double-checking: a second qualified person verifies against the original order or source, without being told what the first person concluded. Priming destroys the check — if you hand someone a draft and say “I think it’s 250 milligrams, can you confirm?” you have just told them what to see.

The second is read-back: the receiver repeats the critical information aloud, and the sender confirms it. In accredited hospitals, read-back of verbal orders and critical test results is standard practice for exactly this reason. Apply it to writing whenever a number is transferred by phone or hallway conversation into a document: repeat it back, digit by digit, and read the units too.

Formatting itself is a safety control. The Institute for Safe Medication Practices maintains a widely used list of error-prone abbreviations and dose expressions, because certain written forms are reliably misread. A trailing zero — 1.0 mg — has been read as 10 mg. A naked decimal — .5 mg — has been read as 5 mg. Write 1 mg and 0.5 mg. Spell out units rather than writing U, which can look like a zero or a four. Avoid abbreviations that are ambiguous between two drugs. These are not style preferences; they are the written form of a known failure mode.

Checking your claims and your sources

Verify the claim, not just the citation. It is common, and professionally serious, to cite a real source that does not actually say what you attribute to it — usually because the claim traveled through a summary, a slide deck or a colleague before it reached you. Open the original. Read the sentence you are relying on. If you cannot find it, either the claim changes or the citation goes.

Check quotations against the original wording, including capitalization and any ellipsis, and check that the ellipsis has not reversed the author’s meaning. Check that a statistic still applies — a 2016 figure describing staffing ratios may be true and useless. And check every hyperlink by clicking it in a fresh browser session, not by looking at it. A link that works because you are already logged in will fail for the reader who is not.

Finally, verify the boring things, because they are the ones that get you. Is the attachment attached? Is the recipient list correct? Does the file name match the document title? Is last quarter’s header still sitting on this quarter’s report? Are all the placeholders gone — the bracketed name, the highlighted “TBD,” the sentence you left yourself in yellow?

Section 5Build a Quality System

The style sheet

A style sheet is a one-page record of the decisions your organization has already made, so nobody re-litigates them at 4:45 on a Friday. It is not a grammar textbook. It answers the small recurring questions: do we write health care or healthcare, use the serial comma, spell out numbers under ten, capitalize job titles, say patient or client, write 0900 or 9:00 a.m.?

Build it by accretion. Every time you or a reviewer makes a call, add a row. Include an example, not just a rule — people copy examples and misread rules. Where your field has a governing standard (a journal style, an agency manual, an accreditation requirement), name it at the top and let the style sheet cover only the local deviations and gaps.

The value is not consistency for its own sake. Inconsistency makes a document look unreviewed, and a reader who notices that Sect. 3, Section 3 and §3 all appear on one page starts wondering what else nobody checked. Surface care is read as evidence of substantive care, fairly or not.

A checklist short enough to use

Long checklists do not get used; they get signed. Keep a pre-send checklist to seven to ten items, all binary (done or not done), all covering things that have actually gone wrong. Put your killer items — the failures with the worst consequences — at the top, where attention is highest.

Write it for the moment it will be used, which is the last two minutes before sending, on a day when you are behind. That means no items requiring judgment (“is the tone appropriate?”) and no items you cannot check in ten seconds. Judgment belongs in the editing pass; the checklist is for the surface pass.

A serviceable generic version: attachment attached; recipient list correct and blind-copied where required; all placeholders removed; every number matches its source; every link opens in a private window; names and credentials spelled correctly; dates and weekdays agree; tracked changes accepted and comments deleted; file name follows the convention; the ask appears in the first three lines. Then add the two or three items your own last three mistakes would have caught — a personal checklist beats a generic one.

Proofreading techniques that beat your own eye

The core problem is familiarity, so every effective technique is a way of making the text unfamiliar. Incubation is the cheapest: put the draft down for a few hours, overnight if the deadline allows. Errors that were invisible at 11 p.m. are obvious at 7 a.m., not because you got smarter but because you stopped remembering what you meant.

Change the medium. Print it, or change the font, column width or zoom level. The idea is that new line breaks force genuine reading rather than pattern recognition. Some studies have found an advantage for proofreading on paper and others have found little or no difference on modern screens, so treat this as a useful trick rather than a proven law — the reliable part is the disruption of familiarity, not the paper itself.

Use text-to-speech. Have the computer read the draft aloud while you follow along. The machine reads what is on the page rather than what you meant, so omitted words, doubled words and mangled clauses become audible. Reading aloud yourself works too and is better for rhythm and tone, though you will unconsciously repair errors as you speak.

Read backwards for spelling — last sentence first, or word by word from the end. Reversing the order strips away meaning and leaves only the marks. It is slow, so reserve it for short high-stakes text: titles, headings, executive summaries, anything that will be printed or displayed large. Headings and titles are where embarrassing typos survive longest, precisely because nobody proofreads the part they think of as decoration.

Version control and sign-off

A quality system fails at the last step more often than at any other: the wrong file gets sent, or nobody can prove which version was approved. Adopt a naming convention and never depart from it. Put the date first in year-month-day form so files sort chronologically, then the document name, then the version, then the status. 2026-03-05_FallPrevention_v6_DRAFT.docx tells you everything; fall policy FINAL final (2) REAL.docx tells you that a team lost control of its own document.

Record sign-off in writing: who approved, what version, on what date, and what their approval covers. Approval of the clinical content is not approval of the legal language. In regulated environments this is not optional — controlled documents typically require an owner, an approver, an effective date and a review date, and an auditor will ask for exactly those four things.

Keep one single source of truth and make everything else obviously a copy. When a document is superseded, mark it superseded rather than deleting it; the old version is evidence of what staff were told at the time, which matters enormously if anyone later asks why a decision was made. Archive, do not erase.

Words worth knowing