Every piece of writing is a request for someone's time. A reader who opens your email, report or letter is lending you attention they could spend elsewhere, and clear writing is how a writer repays that loan. This course treats writing as a practical skill that anyone can improve, not a gift a few people are born with. It begins where every good piece of writing begins: before the first sentence, with two questions. Why am I writing, and who will read it?

Writing is for the reader

Speech comes with a safety net. If a listener looks puzzled, you can stop, back up and try again. Writing has no such net. The reader cannot interrupt to ask what you meant, so the page has to answer their questions before they think to ask them. This is why a sentence that seems perfectly clear to its author can baffle everyone else. The author already knows what the sentence is supposed to say and quietly fills the gaps. The reader has only the words.

The French mathematician and philosopher Blaise Pascal, in one of his Provincial Letters of 1656, apologized to his reader for the letter's length: he had made it longer than usual, he explained, only because he had not had the time to make it shorter. The joke holds a serious point. Clear, short writing usually takes more effort than long, muddy writing, because the writer has done the sorting and cutting so the reader does not have to.

Purpose: what should change?

Most writing exists to change something: what a reader knows, believes or does. A useful habit is to write a purpose statement: one or two sentences on what you want the reader to know or do after reading. "I want the city council to know that the crosswalk on Elm Street has had three near misses this month, and to schedule a safety review" is a purpose statement. "I want to write about traffic" is not. It names a topic, not a goal.

Purposes come in a few broad families. Some writing informs (a lab report, a set of directions), some persuades (an op-ed, a grant proposal), and some records or expresses (a diary, a memoir, a thank-you note). Many documents mix them, but one purpose usually leads, and knowing which one leads tells you what to put first.

Audience: who is reading, and what do they know?

The same facts need different writing for different readers. A doctor explaining a diagnosis to a colleague can use technical terms and skip the basics. Explaining it to a frightened patient, she must define terms, slow down and address worry. Before drafting, ask: What does this reader already know? What do they need? What might they object to? How much time will they give me?

A common mistake is to write for an imagined reader who is just like you. Experts are especially prone to it, because once you know something well, it is hard to remember what it was like not to know it, and steps that feel obvious get skipped. A good default for public writing is the intelligent outsider: a reader who is bright and willing but does not share your background or vocabulary. Writing for that reader rarely insults experts, and it keeps everyone else from getting lost.

Putting the point first

Busy readers, which means most readers, want to know early what a document is about and what it asks of them. Military and business writers call this principle "bottom line up front": state the main point or request at the start, then give the support. A reflective essay can build slowly toward its conclusion, and that suits some purposes. But a memo that hides its request in the last paragraph risks never being acted on, because the reader stopped before reaching it.

Register and tone

Register is the level of formality a piece of writing uses. A text to a friend, a cover letter and a court brief sit at different points on that scale. The right register is the one your reader expects for the situation, not the fanciest one you can manage. Respectful, direct and warm is a safe tone for nearly all public writing. Treating readers as intelligent adults whose time matters is not only good manners. It is a small, daily way of recognizing that every person counts.

Worked example: the broken heater

Maria rents an apartment, and her heater has failed in January. Her first draft to the building manager reads: "Hi, I'm writing because things have been kind of rough lately with the apartment and I wanted to reach out about some issues, mainly the heating situation, which hasn't been great."

She asks the two questions. Purpose: she wants the heater repaired within a few days. Audience: a manager who handles dozens of requests and needs the unit number, the problem and the urgency. Her revision: "The heater in unit 4B stopped working on January 9. The indoor temperature is now about 55 degrees. Could a technician come by Friday, January 12? I am home after 3 p.m. and can also leave a key at the front desk."

The second version is shorter, puts the request in the opening lines and gives the manager everything needed to act. The register is polite and businesslike, which is what a manager expects from a tenant. Nothing about it is rude. It is simply written for the person who will read it.