Purpose in line one: how to write to a CEO

01

What the first line must carry

The opening sentence carries three facts: the choice you are asking the CEO to make, your deadline and your advice. It is not a greeting, a thank you or a history of the problem. It is a request with a date on it.

Army Regulation 25-50, the US Army's rulebook for letters and memos, says two things are essential in good writing: the main point goes at the start, and the writer uses the active voice. The Army calls the first of these the bottom line up front. Active voice simply means the actor comes before the verb. "I need your approval" is active. "Approval is sought" hides who wants what.

Digital.gov, the US government's plain language guide, gives the same advice for any document. Digital.gov says to put the most important information at the beginning and to move background, when it is needed at all, toward the end.

A good first line reads like this: "Decision needed by Thursday: approve a second Arabic interpreter from 1 November. I recommend yes." A CEO who reads only that line knows what to do. Line two gives the reason in one plain sentence. Everything after it is support the reader can take or skip.

02

Why a buried request costs patients time

Notes often open with history because the writer wants the effort to be seen first. I understand the pull. But the CEO pays for that history with attention, and attention is short between meetings. A message that makes its reader hunt gets parked. Parked can mean next week.

In international patient work, delay has a direct cost. A patient in another country is waiting for a firm date. Flights, a companion's leave from work and a place to stay all wait on that date. An interpreter booking waits on a budget line. When the approval sits unread, the patient abroad waits too, and draws a conclusion about India.

There is a second cost. A puzzled chief executive tends to call a meeting, and diaries can push that meeting back by days. The traveller never sees any of this. They see a slow reply, and slowness looks like doubt.

India earns the trust of patients abroad through answers they can check and dates that hold. Prompt internal decisions belong to that standard, even though no patient will ever read the memo behind them.

03

How I would build the note

I would build every note in the same order: request, reason, options, owner, the cost of no answer, then background. Each part earns its place or comes out.

The subject line compresses the opening into fewer words. It starts with the kind of reply I need, such as "Decision", "Approval" or "For information". Anyone scanning an inbox can then sort it unopened.

Options come next. I give two or three, each with its price and its main hazard. I mark my preferred route and justify it in a single sentence. Offering one path only asks for a signature, and experienced leaders notice.

Then the owner. The note names whoever acts the day the CEO says yes, plus their first step. A decision with no owner is a wish.

Then the price of silence. This line is often missing, and I find it the most useful one. "If there is no decision by Thursday, the desk will stop offering November dates to new enquiries." The CEO now sees that silence is also a choice.

Background goes last, under a plain heading, for the reader who wants it. Army Regulation 25-50 also asks for sentences of about 15 words on average, paragraphs of no more than 10 lines and one-page letters and memos for most correspondence. I would hold every CEO note to that page limit. Detail goes into an attachment, which Army Regulation 25-50 calls an enclosure.

Write the one line you would want read aloud if nothing else were read.

04

A note from the international desk

Here is how such a note might look for the interpreter example. Its subject line reads: "Decision by Thursday: extra Arabic cover for November".

Line one asks for approval and says I support it. The second states the cause: next month's bookings put more Arabic-speaking patients in consultation and discharge on the same days than one interpreter can cover.

Three options follow. Option A hires a contract interpreter for three months, with a cost the finance team has checked. Option B moves some admission dates, which costs nothing but asks patients to change their travel. Option C uses phone interpretation for some meetings, which is cheaper but needs the clinical team's view first. Whether a phone interpreter is suitable for a clinical conversation is a question for clinicians, and the note says so rather than guessing.

The owner line names the desk lead, who will sign the contract on Friday. The no-answer line says new November bookings pause until there is a decision. The background, with booking counts by week, sits in the attachment.

05

The trade-off in a short note

Short notes carry a real risk. A one-line recommendation can sound more certain than the evidence allows. A CEO may approve quickly because the note reads as settled. So I would add one line near the options: how sure I am, and the single fact that would change my mind. That keeps the note brief without hiding doubt.

Some messages should not start as a note at all. A serious matter affecting a patient goes to the CEO by phone first, then in writing the same day. The written record still opens with its purpose.

Writing short also takes longer. A long note is quick to write and slow to read. A short one reverses that, and the writer carries the cost. I think that is the right person to carry it.