Revise one thing

Pick something small, real and yours

The temptation at the end of a module like this is to write a plan for improving everything your unit sends. Do not. Pick one thing that is currently in use, that you can change without anyone's permission, and that reaches people outside your team: the standing email, the page you maintain, the memo template, the deck you present twice a year. One finished revision creates something colleagues can copy. A plan creates a document.

Run the pass in order. Purpose first, because a message with an unclear purpose cannot be fixed by better sentences. Words and framing next. Then structure and format, because moving content into real text often changes the wording again. Then language access and timing, which are calendar decisions more than writing decisions. Finish by writing down what changed, so the next person inherits the reasoning rather than repeating the discovery.

Here is the pass applied to one line. Before: “Impacted parties requiring accommodations should notify the undersigned at their earliest convenience.” After: “Tell us what you need to take part — an interpreter, captioning, large print, a translated copy, or something else. Email Dana Olsen or call the number below by the Friday before the meeting, and we will arrange it.” Same offer, named person, real deadline, examples that tell the reader what is actually available.

A communication revision checklist

One page you can copy into your own work and run on a single email, web page, memo or slide deck.

What this is and who it is for Name the piece, its audience, and the one thing a reader should be able to do after reading it. If you cannot write that sentence, the revision starts there. Example: standing email announcing a moved public meeting; anyone who planned to attend; the reader should know the new date and how to arrange what they need to take part.

Words and framing First read, plain meaning: what changes, for whom, when, what to do. Program terms defined at first use, acronyms spelled out or removed. No euphemisms, no functioning labels, no sentences that put a person on trial for a process problem. A named contact, not “the undersigned.”

Structure and format Real headings in order; genuine lists; tables for data with header rows marked; link text that names its destination; alternative text on images that carry meaning; nothing essential trapped in a screenshot, a scanned page or color alone; readable contrast; captions and a transcript for anything recorded.

Language access and timing Short sentences and no idioms so the text can be translated accurately. Translated versions and formats planned on the calendar, not requested at the end. Interpreters and captioners sent the agenda, names and terms in advance. The message sent early enough that a reader can still arrange what they need.

What changed and who needs to know Two or three lines naming what you changed and why, sent with the revised version to the people who use it. List anything outside your control — a system-generated notice, a locked template, a page another office owns — with the exact sentence, where it appears and the wording you suggest, routed to that office.

Copy the five fields into a blank page, fill them in against one real piece of your own work this week, make the changes you own, and send the last field to whoever owns the rest.

Browse and download only. Staff notes are not typed or saved on this page.

Revisions that need nobody's permission

Move the essentials out of an attachment and into the message itself.
Replace “click here” with link text that names the destination.
Apply real heading styles to a document you already maintain.
Replace a screenshot of a table with the table as real text.
Name a person and a real deadline instead of “at your earliest convenience.”
Add one line inviting people to say what they need to take part, with examples of what is available.
Send the meeting materials two working days early instead of the morning of.
Write a short plain-language summary at the top of a technical document.

Ship the revision, then hand off the rest

What you can change

You control the pieces you write and maintain, and you control how precisely you describe the pieces you do not.

What to watch for

Do not stall the revision you can make while waiting on a decision about the system-generated notice. And do not send a general concern upward; a vague message about accessibility lands nowhere and comes back as a question.

Your next step

Make your changes, send the revised version with two lines saying what changed, and route each remaining finding as a specific sentence with suggested wording to the office that owns it.

You have revised your unit's standing notice and found that the automated confirmation message, owned by another office, is unreadable. Which handoff is most likely to result in a fix?

A message asking the other office to review their automated notices for accessibility.

A message naming the exact notice, quoting the sentence and where it appears, describing what a reader cannot do with it, offering suggested replacement wording, and asking who owns the change.

Adding a line to your own notice warning people that the confirmation message may be hard to read.

Raising it at the next all-staff meeting so everyone is aware of the problem.

Try a situation

An administrative staff member maintains the standard email their unit sends when a scheduled public meeting moves. It reads: “Per the attached notice, the previously scheduled stakeholder engagement session referenced below has been rescheduled due to unforeseen circumstances. Impacted parties requiring accommodations should notify the undersigned at their earliest convenience.” The attachment is a scanned memo, and the email goes out two days before the new date.

How should the revision start?

Rewrite the wording into plain English and keep the rest as it is, since the format and timing were set by someone else.

Start with what this message is for and who receives it, then fix the wording, then move the essentials out of the scanned attachment into the email itself, then set a sending time that leaves people room to arrange what they need — and note who owns each change.

Add a standard accessibility statement to the bottom of the template and leave the message as it is.

Carry this forward

One revision done well teaches more than a policy about revisions. Pick something real, currently in use, and yours to change.
The pass runs in a fixed order — purpose, words and framing, structure and format, language access and timing, then what changed — because fixing wording inside the wrong format wastes the effort.
Say what changed and why when you send the revised version. That is what turns a personal edit into a template other people reuse.
Some findings are not yours to fix. Route those to the office that owns them with the specific sentence, the page and what you would change, rather than a general concern.

A worked before-and-after revision, a checklist to copy into your own work, and a knowledge check on a complete revision note.

Run the pass on one thing this week. Send the revised version, tell the people who use the original what changed, and hand anything outside your control to the office that owns it with your suggested wording attached.

What you’ll be able to do

Pick something small, real and yours

A communication revision checklist

Revisions that need nobody's permission

Ship the revision, then hand off the rest

What you can change

What to watch for

Your next step

Try a situation

Carry this forward

Your next step

Revise one thing

What you’ll be able to do

Pick something small, real and yours

A communication revision checklist

Revisions that need nobody's permission

Ship the revision, then hand off the rest

What you can change

What to watch for

Your next step

Try a situation

Carry this forward

Your next step