How to Replace a Status Meeting With a Written Update

The weekly status meeting is the most common meeting in office life and one of the least loved. Eight people, forty-five minutes, each person reading out what they did while everyone else waits for their turn. Most of the information could be read in two minutes. The few things that need discussion get squeezed into the last five.

Replacing it with a written update is simple in principle. Doing it so that people actually read the updates, and so that problems still surface, takes a little structure.

Why Written Updates Work Better

• Reading is faster than listening. Most people read three or four times faster than people speak.
• People can read when it suits them, which matters across time zones.
• Updates become a record you can search later.
• Writing forces clarity. It is hard to be vague in a short written update.

The trade is that you lose the quick back-and-forth. The fix is to keep a short live conversation for the items that genuinely need it, rather than for everything.

A Format That Works

Ask everyone to post in the same place, at the same time each week, using the same headings:

1. Done: what finished this week, with links.
2. Next: what you will do next week.
3. Blocked or at risk: anything that needs help or a decision, and from whom.

Three headings, a few bullets each. The third is the one that matters. See how to write an async standup update for a daily variant.

Write For The Skim Reader

Before:

This week I mostly worked on the onboarding project, had a few meetings with the design team about the flows, still waiting on legal for the terms, also helped Sam with the reporting issue. Next week more onboarding stuff hopefully.

After:

Done: Onboarding flow designs agreed with Design (link). Fixed the reporting export bug with Sam. Next: Build the first two onboarding screens. Blocked: Terms of service text is with Legal since 22 September. I need it by 17 October to keep the November launch. @Maria, can you chase?

The second version separates finished work from intentions, and the blocker has a date, a consequence and a named person. That is what gets action.

A Wrivio Context for weekly updates could say:

Rewrite this as a weekly written status update with three headings: Done, Next, Blocked. Short bullets, plain language, put any blocker’s date, impact and owner in the Blocked section. Keep every name, date, link and task exactly as written. Do not add progress, tasks or risks that are not in the original.

Press Ctrl+Shift+Space, paste your rough notes, and make sure the blocker is still as specific as you meant.

Make Sure People Read Them

Written updates fail when nobody reads them. A few habits help:

• The manager replies to each update, even with a short acknowledgement or question. If nobody responds, people stop writing carefully.
• Blockers get answered within a day. The fastest way to kill the format is for a blocker to sit unanswered.
• Summarise upward. The team lead writes one combined update for their own manager. See how to write a status update executives read.

Keep A Shorter Live Slot

Most teams still benefit from some live time. Replace the 45-minute status round with:

• A 15-minute slot that only covers blockers and decisions raised in the written updates, or
• A fortnightly or monthly team meeting focused on planning and discussion, not reporting.

If there is nothing to discuss, cancel it. That is the system working.

How To Propose The Change

Before:

Can we cancel the status meeting, it’s a waste of time

After:

I would like to try replacing our Monday status meeting with written updates for four weeks. Everyone would post Done, Next and Blocked in the team channel by Monday 10:00, and we would keep a 15-minute call on Tuesday only for blockers. That would give each of us back about 30 minutes a week. After four weeks we can decide whether to keep it.

The second version is a time-boxed experiment with a clear format and a review point, which is much easier to agree to.

Atlassian’s team playbook has practical plays for running fewer, better meetings.

Common Questions

Won’t people miss the social side of the meeting?

Some will. Replace status with a short, optional social or planning conversation instead. Reporting and connection are different needs, and combining them serves neither well.

What if people do not post their updates?

Make it part of the routine, with a reminder at the same time each week and a manager who replies. If someone consistently misses it, talk to them about it as you would a missed meeting.

How long should a written update be?

Short enough to read in under a minute: three headings, two to five bullets each. Longer updates get skimmed.

Does this work for client status reports too?

Yes, and clients often prefer a short written update to a call. Keep a regular call for decisions and relationship time.

Download Wrivio for Windows to turn rough notes into a crisp written update before your coffee cools.