A status update is a meeting or communication designed to inform an audience about the current state of a project, without requiring any decision from the audience. A decision request is a meeting or communication designed to get a specific decision from the people in the room, with all the information and options already prepared.
The confusion between the two is the most common source of wasted meeting time. Status updates that end with 'any thoughts?' and decision meetings where nobody has read the pre-read are both symptoms of the same problem: the meeting owner has not defined what they need.
Key takeaways
- Status updates inform; decision requests decide. Define which one you are running before the invite goes out.
- A meeting with no decision needed is probably an email.
- A decision meeting where the options are not prepared is a status update with anxiety.
- The person who calls the meeting is responsible for defining what they need from the room.
Why it matters
When a status update and a decision request are combined in the same meeting, neither works. The status portion eats time that the decision needs. The decision arrives without enough preparation. People leave having heard a lot and decided nothing.
The pattern is especially common in engineering and product meetings. A team gives a twenty-minute update, then at the end asks 'so should we push the launch?' The question requires a decision, but nobody came prepared to make one. The meeting either ends without a decision or with one made on incomplete information.
The fix is structural. When writing a meeting invite, finish this sentence: 'At the end of this meeting, I need...' If the answer is 'for everyone to know X', send an email or async update. If the answer is 'a decision on X', run a decision meeting with options prepared and pre-reading sent in advance.
How it works in practice
How to tell which one you need
-
Finish the sentence before sending the invite
'At the end of this meeting, I need...' If the completion is 'for people to be aware,' make it async. If it is 'a decision on X from these specific people,' that is a synchronous meeting. Send the invite only for the latter.
-
Check the attendee list
Decision meetings need the decision-makers. Status updates need the people who should be informed. If your attendee list includes both and the meeting serves neither well, split it: an async update for the informed group, a focused meeting for the decision.
-
Prepare options before a decision meeting
A decision request without options is a brainstorming session. Come with two or three prepared options, your recommendation, and the criteria. If you cannot prepare options, you are not ready to hold a decision meeting yet.
-
Send status updates as documents, not meetings
Most status updates do not require a meeting. A well-written Loom, Notion update, or structured Slack post contains the same information and lets people process it on their schedule. Reserve synchronous time for what only synchronous time enables: real-time discussion and decisions.
-
End decision meetings with a read-out
Close every decision meeting by stating the decision out loud: 'We have decided X. Daniel owns it. The target date is Y.' If you cannot state it that way, no decision was made. Reschedule with better preparation.
Common mistakes
Ending a status update with 'any thoughts?'
This phrase converts an informational meeting into an open-ended discussion with no defined output. If you need a decision, schedule a decision meeting. If you do not need one, close the status update cleanly and move on.
Calling a meeting when an async update would work
If nobody needs to respond in real time, the meeting is a synchronous status update. These are typically the lowest-value meetings on a calendar. If the information can be consumed on the recipient's schedule without loss, make it async.
Running a decision meeting without pre-reading
A decision meeting where people are learning the context during the meeting is a two-part meeting compressed into one. Send the background, the options, and your recommendation before the meeting. Use the meeting time for the discussion and decision, not the briefing.
Combining both in one invite without labeling them
A meeting titled 'Q3 project update' that ends with 'and we need to approve the budget' has not given attendees enough information to prepare. Label the meeting purpose: 'Status update (first 20 min) plus budget approval (15 min, options in pre-read).' Most people will appreciate the clarity.
What it sounds like
Product team, Monday planning session.
“I called this meeting to show you where we are on the migration,” Daniel said, sharing his screen.
Twenty minutes in, Merav asked: “So are we going live next Thursday or not? I need to tell the account team.”
Guy stopped the meeting. “That is a different question. I will send the options document today and we will decide Thursday. Today was a status update.”
Questions managers actually ask
What is the fastest way to tell which type of meeting you are in?
Ask yourself: do I need an answer from the room today? If yes, it is a decision meeting. If the room just needs to know something, it is a status update. If you cannot answer the question, the meeting probably should not exist.
Can a meeting be both?
Yes, but only if both parts are explicitly labeled in the invite and the time is allocated separately. 'First 20 minutes is an update; final 15 minutes is a decision on X with options in the pre-read.' Most hybrid meetings fail because neither part was labeled.
Who should attend a status update?
Only people who are blocked on the information or whose work changes based on what they hear. If the update does not change what someone does next, they do not need to attend; send them the notes.
Who should attend a decision meeting?
Only the decision-maker, the people with direct input, and the person who will execute. If someone in the room is not involved in the decision or its execution, remove them from the invite.
What if the decision-maker is not available until next week?
Wait, or make a provisional decision the team can move on, with explicit sign-off from the decision-maker before it becomes final. Do not hold a decision meeting without the decision-maker; you will rerun the meeting.
What should a status update look like if it is not a meeting?
A structured document with three sections: what happened, what is coming, and what you need from the reader. If you need nothing from them, the third section is 'no action required.' Send it as a Loom, a Notion page, or a Slack message with a clear header.
See how Leap improves execution in your meetings
Leap sits in your meetings, captures decisions and owners in real time, and shows you where execution breaks down before the week is out.