All posts
November 18, 2026
Figures checked November 2026

Write Clearly at Work — Professional Development #012

Writing clearly at work means saying one thing per sentence, putting the important news first, and writing so the reader knows what to do next. This guide covers reports, proposals, and memos — the documents where muddy writing costs real time — and gives you five steps you can run this week. Most work writing is read once, fast, by someone with ten other things waiting. The fix is not a bigger vocabulary. It is a shorter sentence, a clearer first line, and a second read before you send.

An open notebook with blank pages and a pencil beside a stack of report pages, under a large ember-orange arc.
An open notebook, a pencil, and a stack of pages under an ember sun. Clear writing starts before the first sentence.

Difficulty: Beginner · Time: About 90 minutes: 30 to draft, 30 to cut and rebuild, 30 to read aloud and get a second read · You need: One report, proposal, or memo you are about to send, a pen, and one colleague willing to read it.

Disclosure: some links on this page are affiliate links. As an Amazon Associate, Changenaire earns from qualifying purchases made through links on this page, at no extra cost to you.

Key takeaways

  • Put the point and the ask in the first sentence; the details follow.
  • One sentence, one job — cut extra words and never say the same thing twice.
  • Set the tone on purpose: confident, courteous, and sincere, with the reader's benefit in view.
  • Give busy readers short, specific headings and lists; a memo runs a page or two with the summary up front.
  • Read every draft out loud, then have one other person read it before it goes out.

Who this is for: owners who write reports, proposals, and memos and watch them come back with questions the document already answered — and anyone whose writing gets skimmed instead of read. No training is needed; the practice is the training. Who should adjust: if a document carries legal or safety consequences, write it the same clear way, but have someone qualified check the facts before it goes out — clear writing is not a substitute for counsel.

Here is the honest version. Most work writing fails in the same three places: the point shows up in paragraph three, one sentence tries to do three jobs, and the tone blames the reader for a problem they did not cause. None of that is a talent problem. It is a habit problem, and habits change one document at a time. This guide is part of the Professional Development hub, and it travels with Pitch Your Idea in 3 Minutes — a pitch is the same skill spoken aloud, and a clear page makes a clear pitch easier.

Go deeper (affiliate link — we may earn a commission): the five steps below are the whole method, and you need nothing to buy to run them. If you want the longer study — the classic guide to writing nonfiction, built on one idea, simplicity: a stripped-down style, strong and clear — On Writing Well, 30th Anniversary Edition, by William Zinsser is the book this guide leans on. Skip it if you only want this week's practice — the steps below are enough to start.

Write the one sentence first

Before you type the document, write one sentence: what you want the reader to know, and what you want them to do. That sentence goes at the top of the page. Everything after it earns its place by supporting it — background, numbers, options, next steps. If you cannot write the sentence, you do not know what the document is for yet, and no amount of drafting will fix that.

Purdue OWL puts it as a rule: the most important information in a piece of business writing comes first — the dates, the times, the actions the reader must take — and less important detail is subordinated behind it (checked November 2026). A reader who stops after the first paragraph should still leave with the point. A reader who keeps going gets the proof. Pitch Your Idea in 3 Minutes works the same way — one sentence holding the problem, the fix, and who it helps — and a pitch that starts clear is easier to write down than one that starts tangled.

Do it like this: take the document you are about to write and fill in this line first: "I am writing to tell you [the point], so that you will [the action]." Put that line at the top of your draft. If the line has two points in it, pick one and save the other for a second document.

Give every sentence one job

Read the draft and split any sentence doing two or three jobs into separate sentences, then cut the extra words. A sentence that says what happened, why it matters, and what to do next is three sentences wearing one coat — take the coat off. Short sentences are not simple thinking; they are thinking the reader can follow without rereading.

Purdue OWL calls this concision: saying things in as few words as possible, without dropping the details that matter. Its rules are plain — do not use several words where one will do, and do not repeat information, because a reader who hears the same thing twice stops trusting that the next line is new (checked November 2026). The one exception OWL allows is repeating a date or deadline at the end of a message, so the reader can find it again without hunting.

Do it like this: take one paragraph from your draft, count the words, and cut ten. Not by deleting facts — by deleting filler: "in spite of the fact that" becomes "although," "due to the fact that" becomes "because," "at this point in time" becomes "now." Read the paragraph again. If nothing is missing, the ten words were never doing any work.

Set the tone on purpose

Before you send anything, read the draft as the reader would: does it blame them or help them? Tone is the writer's attitude toward the reader, and the reader feels it before they finish the first line. A confident, courteous, and sincere tone — one that puts the reader's benefit in view — gets a document read. A blaming tone gets it filed away unread, even when the facts are right.

Purdue OWL advises writing from the reader's side of the desk: instead of writing what the reader can do for you, write what you can do for the reader (checked November 2026). Its example is worth copying word for word. Weak: "You didn't read the instructions carefully; thus your system has shut down." Better: "Your system has currently shut down. The instructions may contain information to help you restart it." Same facts, no blame — and the reader can act on the second version. The same care applies when the news is bad: stay gracious, thank the reader, state plainly that you cannot do what they asked, and explain why. Have the Hard Conversation covers the talks where honesty is the point; the tone you set on the page is what makes those talks possible.

Do it like this: find one sentence in your draft that points at the reader — "you failed to," "you didn't," "as I already told you" — and rewrite it as a fact plus a fix: what happened, and what happens next. If the sentence cannot be rewritten that way, it does not belong in the document.

Build the document so a busy reader can scan it

Give the document short, specific headings and turn any paragraph holding three facts into a list. A busy reader does not read a memo the way you wrote it — top to bottom, slowly. They scan for the part that concerns them, read that part, and move on. Headings and lists are how you make sure the part they need is the part they find.

Purdue OWL sets out the shape for a memo: usually a page or two, single spaced and left justified, with a line skipped between paragraphs instead of indenting (checked November 2026). Headings should name the content, not the section — "New Advertising Recommendations" tells the reader more than "Summary" ever will — and the sections run roughly like this: the header takes about an eighth, the opening and context about a quarter, the summary and discussion about half, and the closing and attachments about an eighth. The same shape fits a report or a proposal: heading, summary, detail, next step — in that order, every time.

Do it like this: add a heading every three or four paragraphs, and make each heading name what is under it. Then find any paragraph with three facts in it and turn it into a list of three short lines. If a heading could sit on any document in your company, it is too vague — rewrite it until it only fits this one.

Read it out loud, then have one person read it

Read the whole draft out loud once and mark every sentence you stumble on, then fix those first. Your eyes skip over tangled sentences because they already know what you meant. Your ears do not. A sentence that is hard to say out loud is hard to read silently, and the stumble is the sentence telling you where it breaks.

Purdue OWL advises revising and editing carefully before sharing anything — when you reread what you wrote, you will be surprised by how much can be changed — and asking a colleague or friend to look at a piece before it goes out, especially in a new or unfamiliar format (checked November 2026). One outside reader catches what a hundred self-reads miss. Ask for Feedback That Helps covers how to ask for that read so you get something useful back: one question, one piece of work, and no arguing with the answer.

Do it like this: read the draft aloud, pen in hand, and circle every sentence you stumble on. Fix those first. Then hand it to one person with one question: "What do you think I am asking you to do?" If they cannot answer in one sentence, rewrite the first paragraph — the point is still buried.

At a glance

At a glance: Write Clearly at Work
StepThe short version
One sentence firstThe point + the ask, at the top of the page, before anything else
One job per sentenceSplit overloaded sentences; cut ten words from one paragraph
Tone on purposeConfident, courteous, sincere — a fact plus a fix, never blame
Built to scanSpecific headings and lists; a memo runs a page or two
Read it twiceAloud once, then one colleague reads it and says back the ask

Common mistakes

Burying the point at the end. The reader stops after paragraph two and never reaches the ask in paragraph five. Fix: put the point and the action in the first sentence, and let the details follow.

One sentence doing three jobs. What happened, why it matters, and what to do next, all in a single sentence nobody can follow. Fix: split it into three sentences and cut the filler words — "in spite of the fact that" becomes "although," "due to the fact that" becomes "because."

Blaming the reader when something went wrong. "You didn't read the instructions" ends the conversation before it starts. Fix: state the fact and offer the fix — "Your system has shut down. The instructions may contain information to help you restart it."

Sending the first draft. The version you wrote is the version you meant, not the version the reader will understand. Fix: read it aloud once, fix the sentences you stumble on, and have one colleague read it before it goes out.

Can't do it this week?

Do the 20-minute version: take one memo you are about to send, move the point and the ask into the first sentence, cut ten words, and read it aloud once. The missed-week rule is simple: let the week go, and run the five steps on the next document you have to write. What counts as enough: one document rewritten with the point first, one sentence cut in half, and one read-aloud before it goes out.

Questions people ask

How do I make a report easier to read?

Put the point and the ask in the first sentence, then let the details follow. Purdue OWL advises giving the most important information — dates, times, and actions the reader must take — at the beginning, and using short, specific headings and lists so a busy reader can find each point. A report built that way can be read in order or skimmed, and either way the reader leaves with the point.

How do I sound confident without sounding rude?

Write with a confident, courteous, and sincere tone, and put the reader's benefit in view. Purdue OWL advises writing what you can do for the reader rather than what the reader can do for you, and keeping the language plain and respectful. When the news is bad, stay gracious: thank the reader, state plainly that you cannot do what they asked, and explain why — without blaming anyone.

How long should a memo be?

Purdue OWL says a memo is usually a page or two, single spaced and left justified, with a line skipped between paragraphs instead of indenting. The sections run roughly like this: the header takes about an eighth, the opening and context about a quarter, the summary and discussion about half, and the closing and attachments about an eighth. Different workplaces have their own formats, so match the house style where one exists.

How do I know if my writing is clear enough?

Read it out loud, then ask one person to read it. Purdue OWL advises revising and editing carefully before sharing anything, and asking a colleague to look at a document before it goes out — especially in a new or unfamiliar format. Hand your reader one question: "What do you think I am asking you to do?" If they cannot answer in one sentence, rewrite the first paragraph.

What comes next

Keep the habit small: one document a week through the five steps, starting with the next thing you have to send. And give the clear writing somewhere to go — Build a Network From Zero shows how a network is built one real conversation at a time, and every follow-up note you send after meeting someone is a short piece of business writing. One sentence first. One job per sentence. Read it aloud.

Sources

Every fact in this post was checked against the sources below in November 2026.

The Changenaire Newsletter

Subscribe for more free step-by-step how-to guides to help you get more things done to grow your business or project everyday.

Email required. Unsubscribe anytime.

Read our Privacy Policy.