How to Write a Clear Weekly Project Status Update

A guide to Defining the Update and Gathering Evidence, Structuring a Scannable Update, Writing Clearly and Making Requests Explicit, Reviewing and Distributing the Update, Closing the Loop After Publication

Written by Marcus Lee, Project Communication & Delivery Editor

Last updated: November 6, 2026 Sources listed

Download checklist (PDF)

Interactive Step Checklist0 of 23 steps completed (0%)

A useful weekly status update explains what changed, whether the plan still holds, and what readers need to decide or do; it is not a transcript of every task or a dashboard pasted into an email. Use these 23 steps in our Work World collection with your project's approved plan, definitions, and reporting cadence, and keep confidential information in the appropriate authorized system rather than making every update public by default.

How do you write a Clear Weekly Project Status Update?

Overview: How to Write a Clear Weekly Project Status Update

Howcompass | How to Write a Clear Weekly Project Status Update

Method1

Defining the Update and Gathering Evidence

Four people bend over printed plans on a table: a young man writes, a bearded man points, a woman in a scarf and an older man at a laptop.

Howcompass

Name the readers and their decisions

Identify the audience and the decisions or actions the update should support. Ask whether readers sponsor the work, deliver it, depend on its output, or need to approve a tradeoff, then list what they already know and what they must understand this week. Keep the project team and other stakeholders on an appropriate distribution list, and avoid sending sensitive detail to a broad audience merely because the same template is convenient. The related communication guides in our Work World collection cover the other audiences you may need to brief.

A brass hourglass with falling sand and a pocket watch stand on a wooden table beside an open handwritten ledger and pen, with a bridge and spires at sunset.

Howcompass

Fix the reporting period and scope

Set the reporting period, scope, and publication time before collecting information. Name the week covered, the project or workstream included, the cutoff for new data, and the next scheduled update so readers can distinguish current information from a late-breaking event. Use the agreed cadence around holidays or major releases, and label a special out-of-cycle update clearly instead of allowing it to be confused with the regular weekly report. Teams that also hold a weekly one-to-one can treat that meeting as the personal complement to the written cadence.

Laptop on a wooden desk shows a dashboard of colourful bar charts, an external drive cabled beside it, a dome and sunset city visible through the arched window.

Howcompass

Gather facts from authoritative sources

Gather evidence from the project's agreed sources of truth. Review the current plan, task board, milestone record, budget system, risk register, decision log, and relevant delivery or quality measures rather than reconstructing the week from memory and chat messages alone. Atlassian project-progress guidance emphasizes milestones, owners, deadlines, blockers, and regular review; reconcile conflicting sources before choosing which numbers to publish. Our guide to reconciling a bank statement demonstrates the same habit of trusting the verified record over memory.

Young woman in a mustard sweater and an older bespectacled man in tweed sit at a library table, both looking down at an open notebook with a mug and lamp.

Howcompass

Confirm milestone status with its owners

Verify the status of important milestones and deliverables with their owners. Confirm what actually met the agreed completion criteria, which dates moved, and whether a seemingly finished item still needs review, acceptance, deployment, or documentation. Record evidence or a direct link for each significant claim, and do not convert a percentage of tasks closed into a percentage of project value delivered unless that calculation genuinely reflects the plan. The respectful-conversation basics in our guide to communicating better and resolving conflict help when an owner's answer contradicts the board.

Young woman in an orange sweater writes on paper at a desk with a steaming mug, highlighters and printed sheets, gothic windows framing a sunset courtyard.

Howcompass

Separate facts from forecasts and assumptions

Separate confirmed facts, current forecasts, and unresolved assumptions. Mark actual outcomes and approved changes differently from expected dates, estimated costs, probable risks, or information still being checked, and preserve the original baseline where the project requires variance reporting. Do not present an optimistic forecast as a commitment or hide an uncertain assumption behind a precise-looking number; state who can confirm the missing information and when. Our guide to reading a research paper exercises the same separation of what is shown from what is merely claimed.

Method2

Structuring a Scannable Update

Laptop open on a wooden desk shows a circular gauge dashboard, its cable plugged into a wall socket, mug and notebook nearby, rooftops lit by sunset.

Howcompass

Lead with the status and its reason

Lead with the overall status and the reason behind it. Use the project's agreed label, such as on track, at risk, or off track, and add one sentence connecting that label to a milestone, outcome, budget, scope, or quality criterion rather than relying on a color alone. The Atlassian business status update template places headlines first so readers can grasp major achievements, misses, blockers, and risks before reading the detail. The headline-first lesson from our guide to writing emails that get replies applies directly to the first line of any status update.

Bearded man in a dark shirt, seen from the side, holds up a printed sheet with charts and a green checkmark above a desk with an open laptop.

Howcompass

Report outcomes instead of activity

Summarize completed outcomes instead of listing every activity. Select the few delivered results that changed what users, the project, or the business can now do, and link each outcome to its acceptance evidence or milestone where useful. Replace “worked on onboarding” with a precise result such as “completed and accepted the onboarding accessibility review,” while avoiding claims of impact that have not yet been measured. The outcome-over-activity discipline behind our guide to presenting your first 90 days works the same way when you describe delivered results.

Woman in a dark blazer and bearded man in a navy blazer sit side by side at a table, both writing with pens on one large sheet in warm light.

Howcompass

Commit to realistic next-period priorities

State the next period's priorities as realistic commitments. Name the most important deliverables, owners, and expected checkpoints, keeping the list short enough to reflect actual capacity and dependencies. Distinguish committed work from optional ideas, and do not copy every open task into the update when the project board already provides that detail for readers who need it. Agreeing the commitments in person during a weekly one-to-one keeps the published list honest about capacity and dependencies.

Man in a blue work shirt leans over a wooden bench, turning a screwdriver on a carved wooden piece, with a tray of bits and pliers under a sunset window.

Howcompass

Describe blockers with effect and response

Describe blockers, risks, and issues with their effect and response. Explain what is happening or could happen, which deliverable or constraint it affects, who owns the next action, and when that action is expected, using your project's definitions for each term. If the problem requires a behavior-focused conversation with a colleague or supplier, our SBI workplace-feedback guide can support that discussion, but the status update itself should remain factual and free of personal blame.

Laptop on a wooden desk shows a ninety-four percent usage panel, a brass shaded lamp and potted plant beside it, a domed cathedral glowing through the window.

Howcompass

Report schedule, budget, and scope changes together

Report significant schedule, budget, scope, and quality changes together. Show the approved baseline, current position or forecast, and the reason for the variance in a compact form, including dependencies that explain how one change affects another. Do not bury an overspend, reduced scope, failed quality gate, or moved launch date inside a general progress paragraph, and do not quietly reset the baseline to make the update appear unchanged. Our guide to building a personal budget shows the same discipline of reporting every variance against a fixed baseline.

Method3

Writing Clearly and Making Requests Explicit

Young woman in a green sweater writes with a pen on a printed report sheet at a wooden desk with a pocket watch, inkwell, stacked books and a mug.

Howcompass

Write with concrete verbs and numbers

Use concrete subjects, verbs, dates, and quantities wherever they add meaning. Replace vague phrases such as “progress is being made” or “the team is aligned” with observable evidence and consistent project terms, while keeping sentences short enough to survive a quick scan. PlainLanguage.gov word-choice guidance recommends familiar words, consistent terms, and avoiding jargon and unnecessary abbreviations for the intended audience. The specificity principle behind our guide to performance feedback that lands works just as well on paper.

Man in a denim shirt and green apron sits at a desk working on an open laptop with a probe and brush, screwdrivers laid out, sunset town in the window.

Howcompass

Explain why each material variance matters

Explain why a material variance matters and what is being done about it. Connect the cause, effect, current response, and remaining uncertainty without turning the update into a defensive story or assigning blame, and distinguish an approved corrective plan from an idea still awaiting support. If the effect is not yet known, say what could be affected and when the team expects to know rather than filling the gap with confident speculation. Our guide to communicating better and resolving conflict shows how to explain a cause and a response without blame.

Three students at a table with open notebooks: a woman in green writes, a woman in rust holds up a card, a bespectacled man rests a pen at his chin.

Howcompass

Make every ask specific and answerable

Make every decision request or ask visible and answerable. State the question, available options, your recommendation where appropriate, the decision owner, the date a response is needed, and the consequence of no response, then place urgent asks near the top instead of hiding them after general activity. Keep the request within the recipient's authority and provide enough evidence to choose without forcing them to interpret the entire project history. The request structure in our guide to writing emails that get replies models how to make an ask impossible to miss or defer.

Rugged open laptop on a wooden desk glows with a green shield and checkmark, a brass lamp and inkwell beside it, red roofs and spires outside the window at dusk.

Howcompass

Remove jargon and confidential detail

Remove unnecessary jargon, personal information, and confidential detail. Expand or briefly define a technical term when readers need it, link sensitive supporting material in its authorized location, and omit customer data, credentials, private employee information, commercially sensitive figures, or legal detail that the update does not require. Check the project's retention and access rules before forwarding the report outside its original audience, and never use a public AI or document service to sanitize confidential content without authorization. Handle sensitive personal records with the same care our guide to checking credit reports recommends for financial paperwork.

Method4

Reviewing and Distributing the Update

Open notebook of handwritten arithmetic circled in red lies on a desk with corrected sheets, a fountain pen, red inkwell and spectacles, a bridge glowing at sunset.

Howcompass

Verify each figure against its source

Verify every number, date, name, status label, and supporting link before publishing. Reconcile the update with the current plan and previous report, check that a changed forecast is intentional and explained, and open the evidence links with the same access your readers will have. Ask the responsible owner to confirm a sensitive or surprising claim, and correct the source record as well as the narrative when you find a genuine discrepancy. The line-by-line habit in our guide to reconciling a monthly bank statement is the same verification applied to money.

Young woman in a rust sweater writes in an open notebook with a pen at a wooden desk, ink cup and books beside her, sunset village in the window.

Howcompass

Edit for concise, objective scanning

Edit the update for concise, objective, and accessible scanning. Use informative headings, short paragraphs, meaningful bullets, and text labels alongside any color or icon, then move long explanations into linked appendices rather than deleting essential qualifications. Nielsen Norman Group research-based writing guidance supports concise, scannable, objective web content; test whether a reader can find the overall state, main risk, and requested decision without reading every line. Our guide to writing emails that get replies runs the same scannability test before sending.

Open laptop on a wooden desk shows a paused cloud-sync screen and folder icons, a black coffee cup on a saucer beside it, a stone bridge and river at sunset.

Howcompass

Choose a dependable async channel and time

Choose an asynchronous channel and posting time that readers can rely on. Publish in the agreed project space, email, or update thread with a consistent subject and reporting date, allowing people in different time zones to review and respond before the decision deadline. GitLab communication guidance describes asynchronous channels as a way to create durable artifacts and work across time zones, but urgent safety, legal, or operational events should use the organization's escalation path rather than waiting for a weekly post. Agree the escalation route in advance, the way a family emergency communication plan fixes backup contact methods before they are needed.

19Howcompass

Tailor detail without changing facts

Tailor the presentation without creating conflicting versions of the facts. Adjust the order or level of detail for sponsors, delivery teams, clients, or dependent teams while preserving one verified source for numbers, dates, decisions, and approved changes. Link back to the canonical update or source record, mark any audience-specific redaction clearly, and never give one group a more optimistic status simply because the underlying message is uncomfortable. The audience-aware phrasing in our guide to feedback that actually lands transfers cleanly to written updates.

Method5

Closing the Loop After Publication

Bearded man in glasses and a dark blazer sits across a round wooden table from a woman in a grey blazer, closed notebooks and a mug between them.

Howcompass

Open one clear route for corrections

Invite questions, corrections, and missing context through a clear response route. Give readers a reasonable deadline when their answer affects a decision, monitor the appropriate channel, and distinguish a factual correction that requires an updated report from a preference or new idea that belongs in later planning. Our remote brainstorming guide can help include quieter contributors when a synchronous discussion is genuinely needed.

Howcompass

Log decisions, owners, and due dates

Record decisions and actions with owners, dates, and links to the discussion. State what was decided, who authorized it, what happens next, and which assumptions or options were rejected, then update the action when evidence shows it is complete rather than when someone merely agrees to start. Keep the decision record durable enough for absent teammates to reconstruct the outcome without searching through every reaction and side conversation. Our weekly values review journal guide shows how a fixed record format lets absent readers reconstruct what happened later.

22Howcompass

Return every change to its record

Update the canonical plan, milestone record, risk register, and other affected sources. Reflect approved scope, date, budget, ownership, or dependency changes in the systems the team actually uses, preserving the previous baseline or decision history where required. Do not leave the status update as the only place where a change exists, and avoid silently editing the published report without noting a material correction. The master-copy discipline our guide to organising a growing photo library applies to pictures applies just as well to plans and registers.

Curly-haired woman in an olive sweater sits at a wooden desk lifting a pocket watch from an open drawer, a lamp, open book, pen, books and globe around her.

Howcompass

Chase blocked actions before next week

Follow up on blocked actions and overdue decisions before the next weekly cycle. Check whether the promised response happened, escalate through the agreed route when a deadline passes, and record any new effect on the forecast instead of carrying the same blocker forward unchanged. Use our SBI follow-up approach for a specific accountability conversation where appropriate, while keeping systemic workload, access, and priority problems visible to the people who can actually resolve them.

Open laptop on a wooden desk displays an application uninstaller list with buttons, next to a coffee mug, stacked books and a handwritten notebook, sunset town beyond.

Howcompass

Improve the template from recurring questions

Improve the template from recurring questions and reporting outcomes. Review whether readers found the status, understood the evidence, answered the asks, and could locate the source data, then adjust section order, definitions, detail, or cadence without changing several variables at random. Use our blameless project post-mortem guide for a deeper retrospective when reporting failures reveal a broader process problem, and keep a stable format long enough for readers to compare successive updates.

Frequently Asked Questions

Question: What should I write when nothing material changed this week?

State plainly that there was no material change, update the reporting date and evidence cutoff, and confirm whether the next milestone and forecast still hold. Mention any verification performed or upcoming dependency rather than recycling optimistic commentary. A short current update is more trustworthy than manufactured activity or a copied status with no explanation.

Question: Do I need red, amber, and green status labels?

Only if they are useful and defined for your project. Use the agreed labels with written criteria and a sentence explaining the reason, and never rely on color alone for accessibility or meaning. Plain terms such as on track, at risk, off track, paused, or blocked can work when the team applies them consistently.

Question: How long should a weekly project status update be?

Make it long enough to convey the overall state, material outcomes, next priorities, significant variances, risks, and explicit asks, then link to supporting detail. A one-page or one-screen constraint can help some teams, but completeness and clarity matter more than an arbitrary length. Remove low-value activity before cutting a necessary qualification or decision deadline.

Question: Should I copy task percentages straight from the project board into the update?

Only when the percentage genuinely reflects delivered value and the board is current. Explain what changed since last week, which milestones are affected, and what the figure excludes, because a bare number without interpretation invites the very questions the update was meant to answer. If the board and reality disagree, correct the source record first and note the correction in the update.

Tips

Keep a running decision-and-risk note during the week so Friday's update starts from verified events rather than a search through every chat thread.
Write “no decision needed this week” when appropriate; an empty-looking section is clearer than inventing an ask or making readers wonder whether the section was forgotten.
Use the same status definitions across successive reports and include a short reason beside every label so the update remains understandable without color or project-specific folklore.

Warnings

Do not hide a material delay, budget variance, scope reduction, quality failure, or unresolved dependency behind an optimistic overall label or a revised baseline.
Keep credentials, personal data, customer information, confidential financial detail, and other sensitive content out of broad updates and unauthorized external tools.
Use the organization's urgent escalation path for safety, security, legal, or operational emergencies instead of waiting for the weekly status cycle.

Things You'll Need

The approved reporting period, audience, owner, and publication cadence
The current baseline plan, milestones, and agreed completion criteria
Authoritative task, budget, quality, risk, and decision source links
Verified outcomes, forecasts, assumptions, and variance explanations
Explicit decision requests and actions with owners and due dates
A consistent accessible template and a durable canonical update location

Try it with a free tool

You have read the method — now work through your own numbers or text. These free tools run in your browser, need no sign-up and link back to this guide.

Work WorldTime BlockingBuild a day, spot overlaps and see where the hours go.Open free tool →Work WorldGoal WorksheetTurn a vague aim into an action list you can print.Open free tool →