How to Write a Status Update When There Is No News

Every recurring update eventually hits a week where nothing happened. The work is blocked, waiting on someone, or simply mid-stream with no milestone reached. The temptation is to skip the update entirely, or to pad it with activity that dresses up a lack of progress as motion. Both erode trust.

A no-news update is a real skill, because it has to inform without inventing progress and reassure without pretending. Here is how to write one.

Silence Is Worse Than “No Change”

Skipping the update feels considerate, as if you are sparing people a pointless message. It reads as the opposite. To someone waiting on your work, silence is ambiguous: it could mean nothing happened, or that something went wrong you are not mentioning. A short “no change, here is why, here is when it changes” removes that ambiguity, which is the entire job of a status update. Async-first teams treat this as a norm, not an exception, and the GitLab handbook is a good example of writing things down even when there is little to say.

The point of a status update is not to prove you were busy. It is to keep everyone’s picture of reality current. A week where reality did not change is still information.

State the State, Not the Activity

A no-news update goes wrong when it substitutes activity for status: a list of meetings attended and emails sent that adds up to no movement. Readers see through it, and it makes a quiet week look like a hiding one.

Instead, say plainly where things stand, why they are there, and what changes them. “Still blocked on X, which we need before we can start Y, expected by Thursday” is a complete, honest update. It tells a reader the state, the cause, and the next moment worth checking. We covered the executive version of this in how to write a status update executives read.

Name the Blocker and Who Owns It

If the reason for no progress is that you are waiting on someone, say so, specifically, without blame. A vague “still in progress” hides a blocker that someone reading could clear. Naming it, “waiting on the signed contract from legal,” turns a stalled update into a small nudge that can unstick the work. We covered the mechanics in how to write a waiting-on-someone update and the blocker-specific version in how to write a project blocker update.

Before and After

The difference between filler and a real no-news update is honesty about the state.

Before:

Continued working on the migration this week, had several syncs with the team, lots of moving parts, will keep pushing on it.

After:

No change on the migration this week. We are still blocked on the security review, which has to clear before we can move production data. I have asked for a decision by Friday and will update the moment it lands. Nothing else is at risk.

The second version is shorter and tells the reader everything the first one hid: where it stands, why, and when to expect movement.

A Wrivio Context for a status update could say:

Rewrite this as a short, honest status update. Keep every date, name, and commitment exactly as written. State where things stand, the cause of any delay, and the next expected change. Do not pad a lack of progress with a list of activity, and do not invent progress.

Press Ctrl+Shift+Space, paste your draft, and check the diff. A rewrite that keeps “no change” and the named blocker intact is doing its job; one that turns “still blocked” into “making good progress” has lied for you, which is exactly what a status update must not do.

Keep the Cadence

The reason to send the no-news update rather than skip it is that cadence is itself the reassurance. When updates arrive on schedule whether or not there is news, people stop worrying between them, because absence stops being a signal. Skip one and the next silence becomes a question. A reliable “nothing to report” is worth more than an occasional impressive one.

Common Questions

Should I send a status update when nothing happened?

Yes. Silence is ambiguous and reads as either no progress or a hidden problem. A short “no change, here is why, here is when it changes” keeps everyone’s picture current, which is the point of the update.

How do I write an update with no progress without it looking bad?

State where things stand, the reason, and the next expected change. Do not pad it with a list of meetings and activity, which readers recognize as filler and which makes a quiet week look worse.

What if I am waiting on someone else?

Name the blocker and who owns it, without blame. A specific “waiting on the signed contract from legal” can prompt a reader to help clear it, whereas a vague “in progress” hides it.

How long should a no-news update be?

Short. A few sentences covering state, cause, and next change is enough. Length does not add credibility when there is no news to report.

Why does keeping a regular cadence matter?

Because reliable updates make silence stop being a warning sign. When people know an update arrives on schedule regardless of news, they stop worrying between them.

Download Wrivio for Windows to turn a blunt “nothing moved” into a clear, honest update in a few seconds, without inventing progress.