The Five Emails You Send Every Week

Look at your sent folder from last week. Most people find the same five emails again and again: the request, the update, the follow-up, the thank-you, and the polite no. Everything else is rare. Once you accept that, writing gets much faster. You are not composing something new each time; you are filling in a shape you already know.

The request is the one people get wrong most often. Bury the ask in paragraph three and you will wait three days for an answer. Put it in the first line instead: "Could you approve the vendor contract by Thursday?" Then give the context underneath. Add a deadline every time — an email without a date quietly moves to the bottom of everyone's list.

The update costs you five minutes and buys you a week of quiet. Send it before anyone asks. Three lines will do: what moved, what is next, what worries you. Managers do not chase people who keep them informed. The trick is to send an update even when nothing good happened; silence is what makes stakeholders nervous, not bad news.

The follow-up feels rude, so most people never send it. It is not rude; it is the job. Wait three working days, then reply inside your own thread so the history is visible: "Just bumping this up — do you still need the numbers from me?" Keep it to one sentence. Never open with "As per my last email", which reads as an accusation.

The thank-you is the cheapest email you will ever send and the one people remember. Be specific about what the person actually did: "Thanks for staying late to fix the export — it saved our demo." Vague gratitude sounds automatic. And copy their manager when the help was real. Two extra names in the CC field can shape someone's whole quarter.

The polite no protects the other four. Turn down the work in one line, without a story: "I can't take this on this month — the migration has all my time. Ask me again in October." Notice there is no apology tour and no fake maybe. A clear no today is far kinder than a slow yes that quietly collapses in three weeks.

All five live or die by the subject line. Write it last, and write it as a headline your reader could act on: "Approval needed: vendor contract, by Thu". Nobody opens "Quick question". Then read your draft once and delete the first sentence — it is almost always throat-clearing that says nothing your reader needs. Your reader is standing on a train, deciding in two seconds whether to open it.

Build the five into a habit and email stops being a swamp. Draft the update on Friday morning. Chase your open requests on Tuesday. Send one thank-you a week. None of this is clever writing — it is maintenance, like clearing a gutter. Do it badly and one afternoon a month disappears into apologies you could have avoided.