You owe someone an update, but the honest answer is: nothing has moved yet. Maybe you are waiting on another team, a client has not replied, a technical issue is still open, or you simply have not had enough uninterrupted time to make meaningful progress. This is exactly when people tend to delay the update because they feel they have “nothing useful to say.”
That delay usually makes the situation worse. A good status update is not a progress trophy. It is a tool for keeping expectations aligned. Even when the result has not changed, you can still communicate what is known, what is blocked, what you are doing next, and when the next useful checkpoint will be.
The real job of a status update
Most people think a status update answers one question: “How much is done?” In practice, the person receiving your update usually needs answers to four different questions:
- Is the work still under control?
- Has anything changed that affects me?
- Do you need a decision, input, or escalation from me?
- When should I expect the next meaningful update?
You can answer all four even if the completion percentage has not changed. That is why “no progress” does not have to mean “no update.”
Use the four-part no-progress update
When there is little or no visible movement, keep the message short and structured. A reliable format is:
- Current state: say what remains unchanged.
- Reason: explain the blocker without turning the update into a long defense.
- Next action: state what you are doing to move it forward.
- Next checkpoint: give a specific time for the next update.
For example:
“Quick update on the pricing review: I do not have a final answer yet because Finance is still validating two cost assumptions. I sent the missing figures this morning and will follow up again at 3 p.m. If there is still no confirmation by then, I will send you the options we can proceed with without it. I will update you again by 4 p.m.”
Nothing in that message pretends progress happened. But it still gives the reader confidence that the work is being managed.
Separate a blocker from an excuse
The fastest way to make a no-progress update sound weak is to spend most of the message explaining why the delay is not your fault. The reader usually does not need a detailed history. They need the constraint and your response to it.
Compare these two versions:
Weak: “I have not been able to finish because I had a lot of meetings yesterday, then the vendor sent the wrong file, and this morning I had to help with another urgent request.”
Better: “The final review is blocked by a corrected vendor file. I requested the replacement this morning and have prepared the rest of the review so I can finish as soon as it arrives.”
The second version is shorter, calmer, and more useful. If meetings or competing priorities are genuinely preventing progress, use the same principle: name the constraint, then show how you are managing it. If your day keeps getting fragmented, the approach in How to Protect Focus Time Without Looking Unavailable can help you make the next checkpoint more realistic.
Do not wait until someone asks
A late update creates two problems: the original delay and a communication gap. Once the other person has to chase you, they are no longer only thinking about the task. They are also wondering whether they can trust the follow-up process.
If you know a promised checkpoint is approaching and the work is still stuck, send the update before that checkpoint. A two-minute message is usually better than silence followed by a longer explanation.
This is especially important when you are waiting on other people. Keep those dependencies somewhere reliable instead of trying to remember them mentally. A simple waiting-for list makes it much easier to see which promises need a follow-up before they become overdue.
Match the update to the type of delay
When you are waiting on someone else
State what you are waiting for, when you last followed up, and what you will do if the dependency does not arrive. Avoid making the other person the villain.
“The draft is ready except for the final usage figures from Operations. I followed up this morning. If they are not available by 2 p.m., I will send the draft with the figures marked as pending so the rest can still be reviewed.”
When the work is taking longer than expected
Do not hide behind “still working on it.” Say what turned out to be more complex and give the new checkpoint.
“The data cleanup is taking longer than planned because the source file contains duplicate records that need manual review. I have completed the first two sections and am continuing with the remaining records. I will send a revised completion estimate by noon.”
When priorities changed
If another urgent item displaced the work, say so plainly and explain the consequence. If you need a manager to choose between competing priorities, ask directly rather than silently trying to do everything. The same discipline used in asking a precise question in a meeting works here: make the decision required obvious.
“The customer escalation took priority this morning, so the policy draft has not moved since yesterday. I can return to it at 2 p.m. and still send a first draft tomorrow morning. If you need it today, I will need to move the onboarding review to tomorrow.”
Give a checkpoint, not a hopeful promise
When progress is uncertain, people often promise a finish time they cannot actually control. That creates another missed commitment. A better approach is to promise the next checkpoint rather than the final result.
Instead of:
“I should have it done by 3.”
Use:
“I will update you by 3 with either the completed version or the remaining blocker and revised timing.”
You still commit to something specific, but you are committing to communication you control. This works particularly well for uncertain dependencies, approvals, vendor responses, and technical investigations.
Keep the update proportional
A routine delay does not need a six-paragraph email. In many cases, three or four sentences are enough. The more senior or busy the reader, the more useful it is to lead with the actual status rather than background.
If the update follows a meeting, pair it with the same action-oriented structure used in a strong meeting recap: clear owner, clear next step, clear timing. That prevents the status message from becoming another piece of information everyone reads but nobody acts on.
What to say when there is truly nothing new
Sometimes there genuinely is no new information. The dependency has not moved, there is no new estimate, and no action is required from the reader. You can still close the communication loop:
“No change since yesterday: we are still waiting for Legal’s approval. I followed up again this morning and there is nothing needed from you right now. I will check again tomorrow at 10 a.m. and update you by noon, even if the status is unchanged.”
That last phrase matters. It tells the reader they do not need to chase you.
A quick checklist before you send
Before sending a no-progress update, check that the message answers these questions:
- What is the current state?
- What is preventing movement?
- What action is happening next?
- Does the reader need to do anything?
- When will the next update arrive?
If you struggle to keep those checkpoints visible during a busy day, use a short daily planning habit such as the 5-minute daily plan. The goal is not to create more administration; it is to make sure promised updates do not disappear underneath new work.
The bottom line
A status update is valuable because it reduces uncertainty, not because it proves you finished something. When progress is stalled, communicate the state, the blocker, the next action, and the next checkpoint. Keep explanations brief, avoid invented certainty, and update people before they have to chase you.
If you consistently do that, “no progress yet” stops sounding like failure. It becomes what it really is: a temporary state that is being actively managed.