Meetings · October 5, 2026 · 8 min read

Async Updates That Replace Status Meetings

A written pulse with owners, dates, and blockers can replace a status meeting, with a short call only when a decision is stuck.

HowMuchDoesThisMeetingCost.com Editorial Desk

Picture Priya at 9:02 a.m. on a Tuesday, camera off, in a status meeting that already has eleven tiles on the screen. This is an illustrative scene, not a report about a real employer. The facilitator says the group will go around the room. By the time the speaking order reaches Priya, four people have repeated updates that already live in the tracker. Nobody asks her a question. She leaves with the same blocker she had at 9:01, plus a hole in the morning.

That scene is the case against a status meeting used as a broadcast. The facts moved, slowly. The room did not need to be synchronous for them to move. A written pulse can carry what changed, what is next, what is stuck, who owns the next step, and which date matters, without charging every person the full length of the call.

What the status meeting is actually buying

Attendance is visible, and visibility gets confused with being informed. A manager hears voices and feels caught up. Steven G. Rogelberg, in The Surprising Science of Meetings (Oxford University Press, 2019), treats meeting quality as a design problem: a purpose, a fitting guest list, and a close. A round-robin has a purpose, and the purpose is information transfer. Information transfer is a weak reason to freeze a team at the same minute.

The stronger reason to meet is a decision, or a blocker that writing has already failed to move. If the pulse says the vendor contract is unsigned and Friday's launch slips unless legal answers by noon, that sentence earns a short call with the two people who can act. "I finished the draft" does not.

Leslie A. Perlow, Constance Noonan Hadley, and Eunice Eun described the load in "Stop the Meeting Madness" (Harvard Business Review, July to August 2017). They reported that the executives they studied were spending nearly 23 hours a week in meetings, up from less than 10 hours in the 1960s. That figure is their account of executives, not a law of every team. The useful point for a single squad is smaller: stop using the weekly hold as a session for reading the tracker aloud.

The written pulse, field by field

A pulse that replaces a status meeting is dull on purpose. Dull means it can be scanned. Each person fills the same fields, in the same place, before a cutoff. Five fields are enough.

  • - Done. One to three lines on what changed since the last pulse. Link the artifact. Do not narrate effort.
  • - Next. The work you will touch before the following pulse, with a date attached.
  • - Blocked. The decision or dependency, named as a person and a question. "Waiting on Sam" is not a blocker. "Sam needs to choose option A or B by Thursday so the migration can ship Friday" is a blocker.
  • - Owner. The person who will move it if it is yours to move. If it is not yours, name who you already asked.
  • - Date. When the next visible change should exist. A pulse without a date becomes a diary.

Keep each field shorter than a message you would actually send. If a field needs a diagram, link the diagram. The pulse is an index, not the work itself.

Post it where the team already looks. A channel, a shared doc, or the tracker is fine. A second system that nobody opens is how the meeting returns. Pick the tool the team already uses, and delete the duplicate copy.

A cutoff, a reader, and a rule for silence

The pulse dies when nobody is accountable for reading it. Name one reader, usually the person who used to run the status meeting. That person does not reply to every line. They scan before a published time and do one of three things: answer a blocker, put a short call on the calendar with only the people named in the blocker, or write "no meeting."

Silence from the reader is a defect. If people write into a void, they stop writing, and the old meeting crawls back as "just this once." Publish the reading time. For a team spread across zones, the cutoff has to be fair. A 9 a.m. Eastern deadline that punishes a Pacific contributor is the status meeting wearing a different hat. Set the cutoff at a time both sides can hit without performing presence.

Benjamin Laker, Vijay Pereira, Pawan Budhwar, and Ashish Malik surveyed 76 companies with more than 1,000 employees that had introduced meeting-free days, and wrote up the pattern in "The Surprising Impact of Meeting-Free Days" (MIT Sloan Management Review, January 18, 2022). Outcomes in their table varied with how many meeting-free days a company used. Read the article before you borrow a percentage. The local lesson is narrower: a written update only works if the calendar actually gives the time back. If you add the pulse and keep the 40-minute call, you have invented homework.

When you should still get on a call

Do not convert every conversation into text. Meet live when at least one of these is true.

  • - Two people disagree about a fact that a document has already failed to settle.
  • - A customer or an incident is moving faster than a thread can.
  • - The topic is sensitive enough that tone will be misread in writing. Even then, keep the guest list short and write the decision down afterward.
  • - Someone is new and needs the social map of the team. That is an onboarding conversation, not a weekly status for the whole group.

If none of those are true, the pulse is the meeting. A practical test: if you can predict, on Monday, that Friday's call will be a tour of tickets, cancel Friday now and keep the doc. You can add a call when a blocker appears. You cannot get the hour back after twelve people have sat through a tour.

An illustrative clockburn for one weekly status

The table uses this site's formula and invented inputs. It is not a measurement of Priya's workplace or of any other organization. The meeting cost calculator uses the same method: attendees × annual salary × 1.3 ÷ 2,080 hours × length. The 2,080 figure is 40 hours times 52 weeks, a planning convention. The U.S. Office of Personnel Management computes many federal civilian hourly rates by dividing annual basic pay by 2,087 hours, under 5 U.S.C. 5504(b). Until the early 1980s the federal divisor was 2,080. The shift is a reminder to swap in your own finance number when a decision is real. OPM's fact sheet, Computing Hourly Rates of Pay Using the 2,087-Hour Divisor, is the primary source for that rule.

Assumptions for this illustration only: 9 people, $88,000 average annual salary, 40 minutes, every week.

Piece Illustration
Loaded hourly rate $55.00
One 40-minute session $330.00
Year of weekly sessions $17,160.00
Nine people writing for 6 minutes $49.50 that week

The writing line is the same formula applied to 54 person-minutes. It prices the time spent producing the pulse. It does not promise that the other dollars become finished product. If a blocker still needs a 15-minute call with those same nine people, that call prices at $123.75 under these assumptions. Book it only when the pulse names a question. Most weeks it should not exist.

Rerun the assumptions with your own headcount on the calculator. The guide How Much Does a Status Update Meeting Cost? walks through why a round-robin is expensive even before prep time. The glossary defines clockburn as the live salary figure and clocktoll as the yearly toll of a habit.

How to pilot it for two weeks

Skip the culture memo. Pick one recurring status hold.

  • Tell the group the next two occurrences are optional if their pulse is in before the cutoff.
  • Paste the five fields into the tool you chose. Fill yours first, in public, so the format is visible.
  • At the old meeting time, the reader posts three lines: blockers that need a live answer, decisions already made in writing, and "no call" when that is the honest result.
  • If you do meet, invite only the people named on a blocker. Everyone else gets the notes. Who Should Be Optional on the Invite is the companion piece for that guest list.
  • After two weeks, ask one question in the doc: which blocker moved faster in writing, and which one actually needed voices?

If the answer is that none of them needed voices, delete the series. If one topic keeps needing voices, give that topic its own short meeting with the decision in the title, and leave the rest in the pulse.

Where the pulse goes wrong

People write novels. Cap the fields. If an update needs more than five short lines, it is a document, and the pulse should link to it.

People perform certainty. "No blockers" becomes a slogan while the work is quietly late. The date field is the check. A next step without a date is a wish.

Managers use the pulse as surveillance and comment on tone instead of blockers. The writing then gets shorter and less true. Read for decisions, not for style.

Some teammates will miss the room. Say that out loud. Offer a monthly working session that is not a status tour: one problem, a small group, an end time. Do not smuggle the round-robin back under a friendlier name.

The dollars above are the site's formula on made-up inputs. They are not your payroll, and they are not a forecast of output. The disclaimer is the plain boundary: educational estimate, not financial, legal, or employment advice.

Which status hold on your calendar this week could be a five-field note, and who is the one person responsible for reading it before anyone else is asked to show up?