Writing an event leadership status summary
Your chair or director has two minutes before a meeting and wants to know whether the event is on track.
The short answer
A leadership status summary is one page with five blocks: overall position, what changed since last time, what is at risk, decisions needed from the reader, and the next two weeks. Every status word on it points to evidence, and every decision has a name and a date.
It is not a copy of the full tracker. It is the part of the tracker that a senior reader can act on.
What leadership actually reads
Senior readers tend to look for three things: is anything about to go wrong, is anything needed from me, and has anything changed since last time. A summary that answers those in the first half page gets read.
Put decisions near the top, not at the end. A request buried under progress notes is the one most likely to be missed.
The five blocks
| Block | What to write | Evidence to attach or cite |
|---|---|---|
| 1. Overall position | One sentence and one status word using the team's agreed status definitions. | The tracker rows behind the word. |
| 2. Changes since last report | Three to five lines: completed, slipped, newly raised. | Dates and names from the tracker or decision log. |
| 3. Risks and issues | Only items that could move the date, cost or scope. One line each with owner. | Link to the issue record and its age. |
| 4. Decisions needed | The question, the options, the date it must be decided by and who decides. | A decision-needed summary when there are several. |
| 5. Next two weeks | The few milestones that matter, with owners. | The milestone list. |
Rules that keep it honest
- A status word needs evidence. If the supplier has not replied, the line says awaiting reply since a date, not green.
- Missing data is shown as missing. Do not turn an unknown into a positive status to keep the page tidy.
- Use the same labels every week so readers can compare reports without re-learning them.
- Keep detail in the tracker. If a line needs a paragraph of explanation, link to it.
Who writes it and how often
The project lead, or the secretariat head if no lead is appointed, writes it. Workstream owners supply their lines by an agreed cut-off, for example the day before the report goes out.
Weekly is common while many items are moving, and fortnightly can be enough early on. The weekly status report builder gives you an editable layout that keeps urgent decisions in the export.
Common mistakes
- Reporting activity, such as emails sent, instead of position.
- Showing every workstream as an equal row, so the one that matters is lost.
- Asking for a decision with no deadline or consequence stated.
- Changing the report layout every week.
Worked example · Fictional example
A fictional association's summary before the committee meeting
Fictional organisation and figures, written to show the level of detail that is useful.
Persatuan Fiktif Pengurusan Fasiliti is preparing a one-day forum. Its week-six summary opens: Position: amber. Venue contract is signed; the programme is waiting on two speaker confirmations.
Changes: AV quotation received; registration page approved. Risk: one keynote has not replied since the second request, now 9 days old. Decision needed from the chair by Friday: approve a reserve keynote to be approached, or wait another week. Next two weeks: confirm both speakers, send partner promotion pack, close catering numbers range.
Use this yourself
One-page leadership status summary template
Copy this into your report document. Delete nothing; write Not known where information is missing.
- Report date, reporting period and author:
- Overall position (status word per agreed definitions) and one-sentence reason:
- Evidence for the status (tracker rows, documents, dates):
- Completed since last report:
- Slipped or newly raised since last report:
- Top risks and issues (item, owner, age, next step):
- Decisions needed from leadership (question, options, decider, deadline, what it blocks):
- Budget position in one line, with source and date of the figure:
- Next two weeks: milestones and owners:
- Items marked Not known and who is finding out:
Handle it in-house, or bring in help?
Your team can usually handle this when
- One person owns the tracker and can collect lines from workstream owners.
- Leadership reads one report and already agrees what the status words mean.
- Few decisions are outstanding at any time.
Outside planning help earns its fee when
- Several committees or departments each give a different version of progress.
- Leadership keeps asking for more detail because the report is not trusted.
- Decisions stall and nobody is chasing owners and suppliers for evidence.
Need someone to run the reporting and chase the evidence?
A conference project lead can collect workstream updates, check each status against evidence, and send leadership a one-page summary with decisions up front. The programme and the decisions remain with your committee. Send your current tracker or last report and say who reads it.
Questions organisers ask
Should the summary include the whole risk register?
No. Include only the items that could move the date, cost or scope, and link to the full register. The page should be readable in a couple of minutes.
What if the news is bad?
Say it plainly in the first block, with what is known, what is not known and what is being done. Leadership can only help with problems it can see.
Do we need a status word at all?
A word helps readers scan, as long as it is defined and backed by evidence. If your team cannot agree definitions, write the position in a sentence until you can.
Who signs off the summary before it goes out?
Agree this at the start. Often the project lead or secretariat head approves, and the chair sees it only once it is sent.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.