Status update template: the six-line update that buys you trust

Junior employees tend to fail in one of two ways. They disappear into work and reappear at the deadline. Or they over-communicate in a way that feels anxious (“just checking in… circling back…”) and still doesn’t create clarity.

A simple, consistent status update fixes both. It signals reliability without creating noise.

The moment a good update prevents

At some point you’ll be in a meeting where someone senior asks:

“Are we on track for next Friday?”

If your only honest answer is “I’m not sure,” you’re already in trouble. Not because things are hard — they are — but because uncertainty spreads. Your manager can’t help. Stakeholders can’t plan. Deadlines become guesses.

A written update turns “not sure” into a calm snapshot of reality.

The copy/paste version

Subject: Weekly status — [Project Name]

• Progress: …
• Next: …
• Risks: …
• Decisions needed: …
• Asks (if any): …
• ETA / next milestone: …

Send it every week, or every Monday and Thursday depending on the pace. You become the person who never surprises anyone.

Rules that make it work

Short enough to read on a phone. If you need paragraphs, you need a separate doc. A status update should feel like a dashboard, not a novel.

Always include Risks (even if the answer is “none”). People don’t fear bad news. They fear late bad news.

“Waiting on access to X; if it isn’t resolved by Wednesday, ETA slips two days.”

Structure: risk → condition → impact.

If you need a decision, propose a recommendation.

Bad: “What do you think we should do?”

Better: “Decision needed: A vs. B. I recommend A because ___. Unless I hear otherwise by EOD Tuesday, I’ll proceed with A.”

That last sentence is powerful when used responsibly. It turns ambiguity into motion.

Separate status from story. If something is complicated, put the complicated part behind a link. “Details: [doc link]”. Your update is the headline. The doc is the article.

If something slips, say it early.

“ETA update: was Friday, now Tuesday due to ___. Mitigation: ___. Risk: ___. Ask: ___.”

Calm. Factual. Accountable.

Match the audience. Same format, different emphasis: managers want clarity / risks / decisions. Stakeholders want milestones / impact. Cross-functional partners want explicit asks plus dates. If unsure, ask: “What cadence and level of detail is most helpful for you?”

A filled-in example (healthy project)

Subject: Weekly status — Onboarding email flow

• Progress: Drafted email copy and implemented tracking events in staging.
• Next: QA with test accounts. Ship to 10% cohort.
• Risks: Legal review may delay launch. If feedback isn’t back by Thursday, ship moves to Tuesday.
• Decisions needed: Confirm whether we prioritize “welcome” email vs. “tips” email for v1. I recommend welcome-first.
• Asks: @Priya — can you intro me to the Legal POC for a faster turnaround?
• ETA: 10% cohort live Friday EOD (pending legal).

Not flashy. Credible.

Example when you’re behind

Your goal is to remove uncertainty.

Subject: Status — [Project] — ETA update

• Progress: Completed A and B. C is 70%.
• Next: Finish C. Start QA.
• Risks: Main risk is still X. If X happens, we slip another one to two days.
• Decisions needed: Confirm whether we cut scope item D to protect the date. I recommend cutting D.
• Asks: Need access to ___ (owner: ___). Without it by tomorrow, I can’t hit the new ETA.
• ETA: Was Fri. Now Tue EOD.

Notice what’s not in there: excuses.

Anti-patterns

• Vague update: “Making good progress.” Progress on what?
• Hidden risk: Risks left blank, then surprise! later.
• Status dump: 20 bullets of tasks with no signal.
• Timid ask: You need a decision but you don’t name it.

—

The status update is the cheapest thing in this archive that produces the highest reputational ROI. Ten minutes a week, every week, for a year, and you become the person who’s known for being on top of their work — even when you’re not, because the format makes the gaps visible early enough to fix. Your peers who skip this are quietly being filed under “surprise risk” in their managers’ heads. Don’t be them.

Use this format to drive decisions in your next Manager 1:1.