Event asynchronous status updates, written so they get read
Your workstream owners are tired of the weekly status call, but nobody trusts a chat thread to tell them what is really happening.
The short answer
An asynchronous status update is a short written report from each workstream owner, sent by a fixed cut-off, in the same five fields every week. It replaces the round-robin part of a meeting, so meeting time goes to decisions only.
It works when silence is treated as information. An owner who has not reported is shown as not reported, never as fine.
What an update must contain
Keep every update to five fields so the compiler can read twenty of them in ten minutes. Free-form prose hides the one line that matters.
| Field | What the owner writes | Rule |
|---|---|---|
| 1. Done since last update | Completed items, each with the evidence (a signed quote, a confirmed email, an uploaded file). | No evidence, no tick. See milestone completion evidence. |
| 2. Next, with dates | What will be done before the next update, with a date for each item. | Dates, not 'soon' or 'ongoing'. |
| 3. Blocked or at risk | Anything waiting on a person, supplier or decision, and since when. | Name the person being waited on. |
| 4. Decision needed | The decision, the options, who decides and by when. | Use the decision request format. |
| 5. Self-rated status | Red, amber, green or not known, with one line of reason. | Use the agreed definitions. Not known is allowed. |
Set the rhythm before the first update
- Choose one cut-off day and time that suits the owners, for example Thursday noon, and one compile-and-send time, for example Friday morning.
- Choose one place for updates, such as one shared document or one email thread. Updates scattered across chats and calls cannot be compiled.
- Name the compiler, usually the secretariat or the project lead, and one backup.
- Agree what happens when an update is late: the compiler marks the workstream as not reported and asks once.
- Agree which items still need a live conversation, such as any red item or any decision with a deadline inside the week.
What to do about silence
The weakness of written updates is that a missing one looks the same as a quiet week. Decide in advance that it is not the same.
A workstream with no update is listed as not reported in the compiled summary, and the committee chair sees that line. After two missed cut-offs in a row, the compiler asks the chair to speak to the owner, since the cause is often workload, not neglect.
What still needs a meeting
- Decisions where the options affect more than one workstream.
- Disagreements that two written replies have not settled; use a disagreement resolution record.
- Any item that has been red for two cycles.
- Introductions, such as a new supplier or a new committee member.
Worked example · Fictional example
A forum secretariat drops its Monday call
Fictional organisation and figures, written to show the level of detail that is useful.
The secretariat of a fictional logistics industry forum ran a 75-minute Monday call with six workstream owners. Most of it was each owner reading out their own list.
It moved to written updates with a Thursday noon cut-off and a Friday summary. In the first week, five of six updates arrived; the sixth, for exhibitor logistics, did not, and the summary showed it as not reported. The chair rang the owner, who had been waiting on a supplier reply and had not wanted to report a delay. The call was kept at 30 minutes, for decisions only.
Use this yourself
Weekly asynchronous update template
Each owner copies this block, fills it in and sends it before the cut-off. The compiler pastes the blocks into one summary.
- Workstream and owner:
- Update date and period covered:
- Done since last update (item, date, evidence link or attachment):
- Next before the following update (item, owner, date):
- Blocked or at risk (what, waiting on whom, since when):
- Decision needed (decision, options, who decides, decide by):
- Self-rated status: Red / Amber / Green / Not known, with one line of reason:
- Anything the chair should hear about live:
Handle it in-house, or bring in help?
Your team can usually handle this when
- One person can compile and chase for 30 minutes a week.
- Owners are used to writing short updates and the committee reads them.
- The event has fewer than about six active workstreams.
Outside planning help earns its fee when
- Updates arrive in different formats and nobody has time to reconcile them.
- Owners are volunteers or staff with other jobs who need someone to follow up each week.
- The chair wants one reliable view across committees, suppliers and the venue.
Need someone to compile and chase the updates?
A conference project lead can run the weekly update cycle: set the cut-off, chase late owners, compile the summary and take the decisions to the committee. You keep the decisions; the lead keeps the cycle running. Send what your current update format looks like, even if it is a chat group.
Questions organisers ask
How long should one update be?
One screen for most workstreams. If an owner needs more, the extra detail belongs in an attachment, with the five fields still answered at the top.
Is a chat group good enough for updates?
Only if someone copies the answers into one place each week. A chat holds the conversation well but cannot show who has not reported.
What if owners say they have nothing to report?
Ask them to send the update anyway with 'no change' and the next dated step. A short update still proves the owner looked.
Where do the updates feed into?
They feed the weekly status report and the decision log, so each decision needed appears once, with an owner and a date.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.