Progress monitoring and management reporting
Event project status dashboard: what goes on one page
The committee asks for a dashboard, and what you have is a spreadsheet of forty rows that nobody reads past the first screen.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
An event project status dashboard is one page with five blocks: milestones, risks and issues, budget position, decisions needed and next steps. Every line has an owner, an evidence link and a status from agreed definitions.
The dashboard exists to prompt decisions, so the decisions-needed block goes first. Anything with missing data is shown as not reported, never as green.
The five blocks
| Block | What it shows | Evidence behind it |
|---|---|---|
| 1. Decisions needed | Open decisions with owner, options and the date by which they must be made. | Decision log entries. |
| 2. Milestones | Next five to eight milestones with date, owner, status and what 'done' will look like. | See milestone completion evidence. |
| 3. Risks and issues | Top five only, each with an owner, a next action and how long it has been open. | Risk register or issue list. |
| 4. Budget position | Approved, committed and paid, kept separate, with forecast and what is not yet quoted. See budget variance. | Finance record or supplier quotes. |
| 5. Next steps | What will happen before the next report, by whom and by when. | Workstream updates. |
Rules that keep it honest
- Each status is Red, Amber, Green or Grey (not reported), using the written definitions.
- Every green has a piece of evidence, such as a signed document, a dated confirmation or a completed deliverable.
- A line with no update since the last cycle turns Grey. It does not stay green by default.
- Show the date the data was last updated next to each block.
- Keep the page to one printed side. Detail sits in linked documents.
Who owns the dashboard
One person compiles it, usually the secretariat or the project lead. Workstream owners supply their own lines by a set cut-off.
The committee chair reads it before every meeting. The first agenda item is the decisions-needed block, not a discussion of each row.
Build it in four steps
- List the workstreams and name an owner for each.
- Agree the status definitions and the cut-off day.
- Draft the page with the five blocks and fill it for the current week, marking blanks as Grey.
- Review it with the chair after two cycles and remove any line nobody used.
What to leave off
Skip percentages of completion that cannot be traced to counted items, and charts that look precise but have no source. A single honest list of what is not known is more useful than a coloured chart.
If you do show a completion figure, state the denominator and any items excluded, as the readiness diagnostic does.
Worked example · Fictional example
A dashboard for a 400-person annual dinner and forum
Fictional organisation and figures, written to show the level of detail that is useful.
A fictional professional institute is eleven weeks from its annual forum. Its dashboard shows two decisions needed: whether to extend the venue hold by one week, and who approves the printed programme.
Of seven milestones, four are Green with evidence links, two are Amber, and the AV brief shows Grey because the supplier has not replied for two weeks. The budget block lists approved, committed and paid separately and notes two items not yet quoted. The chair opens the meeting with the two decisions, and both are closed in ten minutes.
Use this yourself
One-page status dashboard layout
Copy this structure into a document or spreadsheet. Keep each block to a handful of lines.
- Event, report date, compiled by, data as at:
- Decisions needed (decision, options, decider, decide by):
- Milestones (milestone, date, owner, status R/A/G/Grey, evidence link):
- Risks and issues, top five (item, owner, next action, days open, status):
- Budget position (approved / committed / paid / forecast / not yet quoted):
- Next steps before the next report (action, owner, date):
- Items shown Grey and why no data was supplied:
- Changes since the previous dashboard:
Handle it in-house, or bring in help?
Your team can usually handle this when
- One person can collect updates and keep the page to one side.
- Workstream owners already update their own lines.
- The committee wants a short read, not a project database.
Outside planning help earns its fee when
- Updates arrive late or in different forms, and the page is rebuilt each time.
- The committee reads the colours but not the evidence.
- Several suppliers and committees feed the page and nobody owns the compile.
Need the dashboard built and kept current?
A conference project lead can set up the dashboard, agree the definitions with your committee, collect the updates each cycle and put the decisions needed at the top. The status and decisions remain your committee's. Send the spreadsheet or tracker you use today.
Questions organisers ask
How many rows should a dashboard have?
As few as the committee will read: five to eight milestones and five risks is typical. Put detail in linked documents.
Should a dashboard show percentage complete?
Only if it can be traced to counted items, with the denominator shown. Otherwise list milestones and their evidence.
Can the dashboard be live?
A live sheet works if someone is accountable for updates and the date of last update is visible. A static weekly page is easier to read in a meeting.
What links to the weekly report?
The weekly status report builder turns the same five blocks into a written report with an editable next-decision section.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.