Event red-amber-green status definitions that mean something
Every workstream reports green until the week it suddenly turns red, and nobody can say what green was supposed to mean.
The short answer
Red, amber and green only help when each colour has a written test that two different people would apply the same way. Add a fourth status, grey for not reported or not known, so that missing data is visible and never counted as green.
Write the definitions once, by dimension (schedule, budget, scope and decisions, suppliers), and have the committee approve them before the first report.
Why green drifts
Owners report green because it is the comfortable answer, and because nothing in the definition stops them. Without a test, green means 'I am not worried yet'.
The fix is evidence: a status of green must point to something that can be checked, and a status with no evidence is grey.
A four-status scheme
| Dimension | Green | Amber | Red | Grey |
|---|---|---|---|---|
| Schedule | Milestone met or on its dated plan, with evidence. | Slipped but recovery date agreed, and no later milestone is affected. | Slipped with a later milestone or the event date affected, or no recovery date. | No update, or no dated plan. |
| Budget | Forecast within approved, with committed and paid shown separately. See variance. | Forecast above approved, within what the budget owner can approve. | Forecast above what anyone present can approve, or an uncosted item above an agreed size. | No forecast, or major lines not yet quoted and not flagged. |
| Decisions | No decision overdue. | A decision is overdue but nothing is blocked. | An overdue decision is blocking work. | Decision log not updated. |
| Suppliers | Contract and requirements confirmed in writing. | Confirmation promised with a date. | Confirmation overdue and the work depends on it. | Supplier has not replied. |
Rules for using the statuses
- Assign status by the written test, not by how the owner feels.
- Attach evidence for green and a reason for amber and red.
- Treat grey as not good: a rolled-up summary counts grey items separately and never merges them with green.
- Allow the compiler to downgrade a status when evidence is missing, and tell the owner.
- Review the definitions after the first two reports and adjust where two people read them differently.
What each colour asks of the reader
- Green: no action. The reader can skim.
- Amber: owner has a plan. The reader asks whether the plan has a date.
- Red: a decision or help is needed. The report must say what and from whom.
- Grey: ask why. A grey that lasts two cycles goes to the chair.
Using the same scheme for readiness
The same rule applies to a readiness check: an unknown critical item must never produce an all-clear. The planning readiness diagnostic groups unknowns by workstream for this reason.
Worked example · Fictional example
Two owners, one dispute about green
Fictional organisation and figures, written to show the level of detail that is useful.
A fictional trade association had both its sponsor-materials owner and its AV owner reporting green three weeks out. The compiler applied the written test: the AV supplier had not replied in 12 days, so that status was changed to grey and the owner was told why.
The materials owner showed a signed artwork approval and stayed green. The AV owner then chased the supplier, found the quote had expired, and reported amber with a new confirmation date. The chair saw the change the same week.
Use this yourself
Status definitions worksheet
Complete one row per dimension you will report on. Have the committee approve it before the first report.
- Dimensions we will report on:
- Green test and the evidence it must point to:
- Amber test and who owns the plan:
- Red test and who is asked for the decision:
- Grey rule: what counts as not reported or not known, and who is told:
- Rule for downgrading a status when evidence is missing:
- How grey and unknown items appear in any roll-up (shown separately):
- Who approves the definitions and the date they were approved:
- Date of the first review of the definitions:
Handle it in-house, or bring in help?
Your team can usually handle this when
- The committee can agree on thresholds in one meeting.
- One person can apply the definitions consistently.
- Statuses are checked against evidence by the compiler.
Outside planning help earns its fee when
- Owners argue about colours, or each owner reads them differently.
- Status has drifted to green while problems came as surprises.
- Budget and supplier statuses need someone neutral to check them.
Want status definitions that hold up?
A conference project lead can draft the definitions with your committee, apply them each week against the evidence, and show grey and red items plainly in the report. Approval of the definitions and of any decision stays with you. Send the status colours you use now.
Questions organisers ask
Why add grey?
Because a missing update is information. Without grey, the options are to leave it blank, which gets overlooked, or to carry the last status forward, which hides a problem.
Who decides if something is amber or red?
The written test decides. The compiler checks the evidence, and any dispute goes to the chair.
Can an item be amber and green at the same time?
No. If a part is amber, report that part separately, or rate the whole item at the worst status.
Where do the statuses appear?
On the status dashboard and in the weekly status report, where grey items are listed separately.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.