How to Write a Project Status Update (With a Real Example)

If you searched for a project status update example, you probably have a deadline and a manager waiting. This guide gives you a fill-in template and a complete worked example so you can send a clear update today instead of staring at a blank page.

A status update is shorter than a full status report. It tells stakeholders three things: where the project stands, what changed since the last update, and what needs attention now. Written well, it removes the need for three follow-up messages.

What goes in a project status update

Keep every update in the same shape. Readers learn the pattern and stop hunting for the part they care about.

• Status label — On track, At risk, or Off track. One word, stated up front.
• Progress since last update — What shipped, what moved, what got closed.
• Current focus — The one or two things the team is working on now.
• Blockers and risks — Anything that could push the date, with an owner and a specific ask.
• Next milestone — The date and the definition of done.

That is the whole structure. Most updates fit in 150 to 250 words. If yours runs longer, cut the narrative and keep the facts.

How to pick the right status label

• On track means you expect to hit the next milestone on the planned date with no help.
• At risk means the date is in doubt but still recoverable. State the risk and the fix.
• Off track means the date will move unless something changes. Give the new estimate.

Using these three labels consistently lets a busy exec scan ten updates in seconds. Avoid soft words like "concern" or "watching" that hide the real state. A clear label is a courtesy to everyone reading.

When to send a status update

Send on a fixed cadence so nobody has to ask. Weekly works for most active projects; biweekly suits steady ones. Send the same day and time each cycle. A predictable rhythm is more useful than a perfect report that arrives late.

Also send an off-schedule update the moment status flips from On track to At risk. Stakeholders dislike surprises more than bad news. A quick "status changed, here is why, here is the plan" message builds more confidence than a polished report delivered three days late.

Reusable template

Project: [Name]
Status: On track / At risk / Off track
Period: [Date range]

Progress
- Shipped: [what is done]
- In progress: [what is moving]
- Closed: [risks or tickets resolved]

Current focus
- [Top priority this week]

Blockers
- [Issue] — Owner: [name] — Need: [decision, access, approval]

Next milestone
- [Milestone] due [date]

Copy this block into your notes and fill one line per bullet. The template works for email, Slack, or a weekly doc.

A real example

Here is a complete update for a fictional product launch. Notice how it states the status first and keeps each line short.

Project: Checkout Redesign
Status: At risk
Period: Oct 13 – Oct 19, 2026

Progress
- Shipped: New address form, card validation
- In progress: Payment retry flow (80% done)
- Closed: QA found 12 bugs, 9 fixed

Current focus
- Finish payment retry and run load test before Friday

Blockers
- Payment provider API keys delayed — Owner: Dana — Need: prod keys from vendor by Wed

Next milestone
- Internal launch due Oct 24; public launch Oct 31

This example shows the key habit: the blocker names an owner and a specific need. A status of "At risk" with no ask leaves the manager guessing. An "At risk" with "need prod keys by Wednesday" tells them exactly how to help.

Common mistakes

Writing a novel. Long updates get skimmed or skipped. Lead with the status word and use bullets. Save the story for the meeting.

Hiding bad news. Marking everything "On track" destroys trust the first time something slips. Use "At risk" early, while there is still time to act.

No owner on blockers. "The API is slow" is a complaint. "API slow — Owner: Sam — Need: infra review Thursday" is a plan.

Mixing status and tasks. A status update reports; a to-do list assigns. Keep them in separate sections so readers know what is done versus what is planned.

Forgetting the date. Updates without a period become impossible to compare week over week. Always stamp the range.

Put it to work

Pick one active project and write its update using the template above before your next standup. If you want a fuller structure with sections for scope and budget, see our project status report guide and the project status report template. For a lighter weekly cadence, the weekly status report keeps the same habit on a shorter loop.