Write a Two-Line Delegation Status Note for Busy Executives

A status note is not a progress report

Executives delegate work because they trust someone else to carry it. What they still need is a reliable signal about whether the work is moving, stuck, or waiting on them. A long progress report buries that signal under context they already know. A two-line note gives them the smallest useful update and leaves the detail available if they ask for it.

The format is not a substitute for a project plan or a decision log. It is a communication habit for the space between formal updates. The assistant or project owner still keeps the full record, the risks, and the next actions. The note simply translates that record into something an executive can read in ten seconds between meetings and still understand.

Use the first line for the current state

The first line should say where the work stands right now, in plain language. Write that the vendor contract is with legal for redline review, rather than saying the team is continuing to move it forward. The first version names an owner, a stage, and a concrete object. The second version sounds busy but leaves the reader unsure whether anything has actually happened. A reader should be able to repeat the state to a colleague without adding interpretation.

Keep the state line factual and free of defensiveness. If the work is late, say it is late and give the new date. If the work is blocked, name the blocker and the person who can remove it. The executive does not need a explanation of every step that led to the current position. They need to know whether their attention is required and what decision would change the outcome.

Use the second line for the next commitment

The second line should name the next concrete action and the date it will happen. "I will send the revised scope to Priya on Thursday" is a commitment that can be checked. "I will keep pushing this along" is not. The action should belong to a named person, even when that person is the assistant. The date should be a real working day, not "soon" or "next week" unless the team has agreed on what those words mean.

The second line also gives the executive a natural place to intervene. If the date is too late, they can say so immediately. If the action is wrong, they can redirect before more work is done. A status note that only describes the past removes that opportunity. A note that commits to the future turns the update into a small, low-friction decision point.

Add a third line only when a decision is needed

Some updates genuinely need the executive to choose between options. In that case, add a single question line and keep the options short. "Decision needed: approve the higher retainer or move the start date to January" is enough. Do not attach a long analysis unless the executive asks for it. The goal is to make the decision visible, not to prove how much work went into preparing it.

If no decision is needed, leave the third line out. A status note that always asks for something trains the executive to expect a request and may make them avoid the updates altogether. The two-line format works because it is predictable. When the reader sees a third line, they know it is there for a reason. That contrast is what makes a decision request stand out instead of blending into routine noise.

Standardize verbs and dates

A small vocabulary makes the notes faster to read and harder to misinterpret. Use a short list of states: on track, waiting, blocked, and complete. Use a short list of actions: send, review, approve, schedule, and confirm. Avoid words that sound active but have no clear finish line, such as coordinate, align, or follow up, unless they are paired with a specific output. The smaller the vocabulary, the easier it is to scan a week of notes and spot the work that has stopped moving.

Dates should follow one format throughout the team. Write the day of the week when the date is close and the full date when it is farther away. If a deadline depends on another person, say whose deadline it is. "Waiting on finance to approve by Friday" is clearer than "waiting on approval." The plain-language guidance from plainlanguage.gov is a useful reference for keeping these notes short and direct.

Route updates by exception

Not every piece of work needs a note every day. Define which changes trigger an update and which can wait for the weekly review. A missed milestone, a new cost, a customer escalation, or a decision that has slipped should trigger a note. Routine progress on a stable project should not. This exception rule protects the executive's attention and makes each note worth reading.

The assistant can own the routing rule and keep it visible in the project tracker. When a trigger occurs, the owner sends the two-line note to the executive and records it in the same place. When nothing triggers, the work stays quiet. The executive inbox escalation protocol uses the same principle for incoming messages, and the two systems reinforce each other.

Keep the note where the work lives

A status note that exists only in a chat thread disappears when the thread scrolls away. Store the latest note with the project record, the decision log, or the task in the team's work management tool. The assistant should be able to pull the current state and next commitment without reconstructing the history from memory. That record also makes handover easier when someone takes time off.

The note does not need to duplicate the full project file. A single line in the project record with the date and the two sentences is enough. If the work is sensitive, keep the note in the restricted location and share only the summary the executive needs. The document naming standard can help the team find the right record later.

Review the habit after a month

After four weeks, look at the notes that were sent and ask which ones led to a useful action. A note that consistently produces no response may be too detailed, too vague, or unnecessary. A note that consistently produces a fast decision is working. Adjust the trigger list and the vocabulary based on that evidence rather than on how the notes feel to write.

The review should also check whether the second line is being kept. A team that writes confident next steps but misses the dates has turned the format into decoration. When a commitment slips, the next note should say so and give the new date. That honesty is what makes the two-line note trustworthy, and trust is the only reason an executive will keep reading it.

For help setting up delegation routines that fit an executive's real attention span, talk to our team. The best status system is the one the team will actually maintain on a busy Friday afternoon. Start with the two lines, test them for a month, and keep the version that produces decisions. A format that survives a normal week is worth more than a perfect template that nobody uses.