1. LandOffer
  2. Blog
  3. All articles
  4. How to Write a Project Status Update That Makes the Next Decision Clear

Workplace Communication

How to Write a Project Status Update That Makes the Next Decision Clear

Turn scattered project notes into a decision-ready status update with a clear scope, evidence index, owner, deadline and next checkpoint, then revise it for a sponsor.

9 min readLandOffer team

Write a project status update around the reader's next decision: what outcome is currently achievable, what changed, what threatens it, and what you need from whom by when. Link the records that support the summary and name the next checkpoint. If no decision is needed, say so and explain what would trigger one.

LandOffer.ai publishes this guide for people communicating about active work. The completed localization-release examples below are fictional teaching cases. Their counts, deadlines, evidence aliases, and decisions are invented inputs; no project update was sent, no release was tested, and no employer result is claimed.

A tabletop route map brings several work pieces to an amber decision junction with two possible paths

Decide what the update must let someone do

Start with the audience and the project commitment. A sponsor may need to choose between a smaller release scope and a later date. A delivery team may need a review owner and the exact unresolved item. Both audiences need consistent facts, but they do not need every detail in the same order.

Atlassian's stakeholder-communication play distinguishes contributors from people affected by the work and recommends identifying their information, channel, and engagement needs. It is a working-method guide, not a universal company procedure. Use your organization's agreed decision and communication routes.

Ask what would be unclear if the recipient read only the opening paragraph. “We made good progress” does not establish whether the launch remains achievable. “Localization is blocked” does not identify the affected scope or the intervention required. Put the change that affects the commitment and the requested action near the top, then link the supporting evidence.

When no decision is needed, an awareness update can be sufficient. A project on track may need only awareness and confirmation of the next milestone. State “No decision requested at this checkpoint” when that is accurate. If a condition could change that, name the condition and when you will reassess it.

Establish a cutoff, a baseline, and a meaningful status

Identify the project's agreed scope and target before selecting a health label. “At risk” should mean something about the commitment, rather than how busy the team feels. A completed implementation may coexist with an unresolved approval that threatens the release. Reporting every workstream as green would hide the dependency that matters.

Asana's status-report guide recommends a dated report, a concise health summary, important blockers, next steps, and links for more detail. These are useful content elements even when you use a different tool. The guide's product and efficiency claims are not evidence that your own reporting process will save time.

State the information cutoff when timing matters. “Tuesday, 14:00 project time” makes clear which observations belong to the update. Include the actual time zone in real work. A later approval should become a dated addition or the next update, not an unexplained edit that makes an earlier risk appear never to have existed.

Keep forecasts separate from commitments. A team's estimate that work could finish Monday is not an approved revised launch date. Identify the assumption behind that estimate and the person who can approve a change. If the forecast is not yet available, state the next estimate checkpoint rather than inventing a confident date.

Worked example: turn scattered notes into a yellow update

The fictional Lumen mobile-app project plans a base release plus French and German interface copy on Friday at noon. English is the base release. The example assumes the locales can be withheld separately; that release arrangement is an invented project fact, not a claim about all applications. Release owner Omar confirms the packaging distinction in record R7.

At Tuesday's 14:00 cutoff, writer Talia has these notes: translation drafts entered, eighteen of twenty screens reviewed, two terminology decisions still open, a reviewer unavailable until Thursday, packaging ready, “probably Monday if everything slips,” and “ask product.” The notes contain activity and uncertainty but no usable request.

Within the fictional exercise, Talia checks the supplied records before summarizing. The eighteen reviewed screens and two unresolved screens cover the example's twenty-screen localization scope. The outstanding terminology decisions are in both new locales. The review lead, Anika, has confirmed Thursday availability but has not committed to a completion time. Monday remains an unapproved forecast that depends on completion and release checks.

Her completed update reads:

Lumen localization release — Tuesday, 14:00 cutoff. Status: at risk for the agreed two-locale scope. “Friday noon remains the approved target. Eighteen of twenty screens have completed language review; two screens still require terminology decisions for French and German. Anika cannot resume review until Thursday, and completion before the release cutoff is unconfirmed. The English base package is ready under the example's separate release arrangement.”

Decision requested from product sponsor Dana by Tuesday, 16:00. “Choose whether to keep Friday's base release and defer both new locales, or keep the combined scope and approve a later target once the remaining review and release estimate is confirmed. I recommend preserving the base release while deferring the two locales. That recommendation has not been approved.”

Owners and next checkpoint. “Anika owns the terminology review; Omar owns the release-readiness estimate. Talia will record Dana's decision and update the project record. Next checkpoint: Wednesday, 16:00, with the review plan and release estimate, or earlier when Dana decides. If no decision is received by the requested time, I will use the agreed escalation route; silence will not count as approval.”

The update makes the affected commitment visible without claiming the entire project has stopped. It also avoids a misleading “90 percent complete” summary. Eighteen reviewed screens do not establish that the remaining approval fits the release window or that the reviewed and unresolved work require equal effort.

Attach an evidence index that answers a real question

Give each material claim a short path to the record that supports it. The following index is completed for the fictional update. Its aliases are teaching references, not functioning links into an employer's systems. In a real update, use authorized links that the intended recipients can access.

Evidence alias What it establishes at the cutoff What it does not establish
L4 — localization review log Eighteen screens reviewed, two awaiting terminology decisions across the new locales Overall release approval or an effort-weighted completion percentage
V2 — reviewer availability note Anika can resume Thursday A promised review-completion time
R7 — release-owner note The base release can be packaged separately in this example Authorization to remove locales from agreed scope
P3 — current project commitment Friday noon and combined scope remain approved Approval for Monday or any other changed target

Select the records the recipient needs to evaluate the choice, so the review gap and release arrangement are easy to find. A sponsor deciding scope needs the review gap and release arrangement. A review lead may need the exact terminology items behind L4. Link that detail once rather than copying sensitive project content into every audience's update.

Check that the summary and the record agree on status. If an issue says “submitted for review,” the update should not say “approved.” If a record is stale or contradictory, resolve it with the owner or make the uncertainty explicit. A tidy report is not evidence that its underlying facts are correct.

Revise the short update after three sponsor questions

Suppose Dana responds with three questions: “Is English blocked too? Is Monday a commitment? What exactly do you need me to approve?” These questions reveal missing decision context in the scattered notes. The following completed revision targets the sponsor without replacing the detailed team record.

“Decision needed by Tuesday, 16:00: approve a Friday English-only base release with French and German deferred, or retain both new locales and wait for a confirmed later target. English is not blocked under Omar's separate-package assessment. Two of twenty localized screens remain unresolved; the reviewer resumes Thursday, with completion time unconfirmed. Monday is an unapproved forecast, not a revised commitment. I recommend the base release; Wednesday's 16:00 checkpoint will provide the review plan and release estimate.”

The revision answers all three questions. It retains the scope gap, the forecast limit, the recommendation, and the next checkpoint. The detailed record still identifies the review and release owners. Shortening for the sponsor does not authorize changing the underlying project facts or omitting the uncertainty that affects the choice.

For the delivery team, Talia writes a different action line: “Anika: confirm the plan for the two open terminology items when review resumes Thursday. Omar: prepare the release-readiness estimate for Wednesday's 16:00 checkpoint using the current review uncertainty. Dana's scope decision remains open until recorded.” That version makes work ownership clear without assuming the sponsor has approved either option.

Two release routes separate a Friday base package from a later combined-scope forecast awaiting a sponsor decision

Show a healthy project without inventing an urgent ask

A useful update also works when the agreed commitment remains achievable. Consider an earlier fictional checkpoint before the reviewer became unavailable. At that point, the review lead had confirmed coverage for the planned work and no unresolved item was known to threaten the approved target. That earlier checkpoint records confirmed coverage; Tuesday records the later loss of availability. It does not establish that the disruption was predictable.

The completed earlier update is: “Lumen release — prior Friday checkpoint: on track against the approved combined scope and next Friday noon target. Translation drafts are entered, and language-review coverage is confirmed for next week. No scope or date decision is requested today. Talia will reassess at Tuesday's 14:00 checkpoint; a loss of review coverage or a terminology item without an owner will trigger an earlier update.”

This version still gives the reader a baseline, an observation, and a next checkpoint. It does not need a fabricated escalation. When the risk later appears, the new update explains what changed. Keeping the two dated states makes the transition understandable rather than treating a yellow label as evidence that every earlier report was wrong.

Atlassian's weekly-update play provides written or video formats for reflecting on progress, explaining priorities, and asking for specific help. That supports a repeatable communication habit. It does not mean a weekly schedule is sufficient when a material decision must be made sooner.

Close the request with a decision record and a next check

After the authorized person decides, record what was approved, by whom, when, and which scope or target changed. Keep a recommendation distinct from that approval. If Dana selects the smaller release, the next update should say the locales were deferred by that decision; it should not quietly redefine the original commitment as English-only.

When the answer is delayed, use the agreed follow-up or escalation channel before the decision window closes. Include the consequence of waiting and the current constraint. Do not assume an emoji, a read receipt, or absence of objections supplies approval when the project requires an explicit decision.

Before sharing, read the opening as the recipient: can you identify the commitment, the change, the decision owner, the requested time, and the next checkpoint? Verify each against the underlying record. If no intervention is needed, say that clearly and retain the trigger for reassessment.

Rewrite the opening of your next update around those facts, verify the supporting records, then use the project's agreed communication channel. Return to this LandOffer.ai guide when a new risk changes the decision, keeping the evidence and the current approval state together.

Sources and Further Reading