A progress update should explain what has changed, what remains and whether a decision or help is needed. Work can be incomplete and still be reported clearly. Separate completed evidence from ongoing activity, make material blockers visible and avoid optimistic labels that conceal uncertainty. The reader should understand the effect on the agreed outcome, not only that you have been busy.
A practical approach to the situation
Start from the task’s definition of done and previous update. State what is now completed or verified, then identify current work and remaining dependencies. If a forecast changes, explain the reason and impact. Distinguish an estimate from a commitment and avoid giving a precise completion percentage without a meaningful basis.
For blockers, describe the missing input, access or decision and the person who can help. Include options when you can assess them, such as completing an independent part while waiting. Keep the update proportionate to the audience: a manager may need a decision summary, while a collaborator may need implementation detail. Link to the underlying work rather than copying every activity into the message.
| Area | Useful approach | What to check |
|---|---|---|
| Completed | State what is delivered or verified since the last update | Avoid counting activity as finished outcome |
| Remaining | Identify current work, dependencies and uncertainty | Do not hide a blocker behind almost done |
| Decision needed | Explain options, owner and effect on timing | Make the requested action explicit |
A fictional workplace or interview example
Fictional example: an analyst’s report is not finished because one data source has not arrived. Instead of writing “almost done,” she states that the available records have been checked and the summary structure is ready, but the final comparison depends on the missing file. She identifies the owner and the effect on the review date.
She proposes sharing the verified partial findings now or waiting for the complete comparison, with the limitations of each option. The update helps the manager decide. It does not hide the dependency behind a reassuring percentage or imply the unfinished analysis is already validated.
Completed
Show: State what is delivered or verified since the last update
Check: Avoid counting activity as finished outcome
Remaining
Show: Identify current work, dependencies and uncertainty
Check: Do not hide a blocker behind almost done
Decision needed
Show: Explain options, owner and effect on timing
Check: Make the requested action explicit
Apply the process to your own material
- Compare: Review progress against the agreed outcome and previous status.
- Separate: Distinguish completed work, work underway and blocked dependencies.
- Explain: State the effect on scope, timing or quality with relevant assumptions.
- Request: Identify the decision or help needed and the next planned update.
Practise with a genuine experience you can discuss appropriately, or use an explicitly fictional scenario. Ask a partner to describe what they understood, including the decision or next action. Compare their interpretation with your intention and revise the part that caused confusion. Keep facts, assumptions and proposed actions distinct. If the situation involves a real employer, follow its assessment instructions or workplace processes rather than treating a practice example as permission to ignore them.
- Compare
Review progress against the agreed outcome and previous status.
- Separate
Distinguish completed work, work underway and blocked dependencies.
- Explain
State the effect on scope, timing or quality with relevant assumptions.
- Request
Identify the decision or help needed and the next planned update.
Use the sequence as a guide, then adapt it to the actual question, people and constraints. Clear communication should make the next decision easier.
Check the result and the next action
Check whether the update gives the reader enough information to act. Remove task lists that do not explain progress or risk. Verify claims of completion against the actual artefact and identify assumptions behind a forecast. Communicate significant changes early through the appropriate route rather than waiting for a scheduled update after the decision window has passed.
A closer check that improves the approach
Check whether the update is about effort or evidence. “Spent two days investigating” describes effort; “ruled out the import step and isolated the mismatch to date handling” describes progress in understanding. Both may be relevant, but the second tells a collaborator what to do next. Use this distinction when work is exploratory and no final artefact is ready. Do not pretend investigation is complete if uncertainty remains. Explain the narrowed question and next check so the update shows useful movement without overstating certainty or treating every hour spent as an equivalent amount of progress.
Common questions
Should I use a percentage complete?
Only when it has a meaningful, explainable basis. A precise-looking number can mislead when the remaining work contains unknowns or uneven effort. A description of completed outputs and unresolved dependencies may be clearer. Do not use a percentage simply because a reporting template has a field for it.
What is wrong with saying almost done?
The phrase does not tell the reader what remains or whether a blocker affects completion. It can create false confidence if the final step is uncertain. State the actual completed work and remaining task instead. A concise specific update is more useful than an optimistic label that different people interpret differently.
How early should I report a blocker?
Report it when it materially affects the work or needs someone else’s action, using the team’s process. Do not wait until the deadline if earlier information could enable a decision. Explain what you checked and what is needed. Avoid escalating every minor uncertainty before doing reasonable investigation within your authority.
Can I report partial progress?
Yes, provided you identify what is complete and what conclusions or uses remain limited. Partial evidence can support a useful decision when labelled clearly. Do not present it as the final result or omit a missing input that could change the interpretation. Explain the next step and the dependency on completion.
What should I say when an estimate changes?
State the revised expectation, the reason and the effect on the agreed outcome. Separate facts from assumptions and identify options if available. Do not hide the change until the original date passes. A clear update gives others a chance to adjust priorities or scope rather than discovering the problem through a missed commitment.
How detailed should a progress update be?
Include the information the audience needs to understand status, risk and next action, with links for deeper inspection. A collaborator may need more technical detail than a manager. Avoid reproducing every activity. The update should connect work to the outcome and make important changes easier to see.
What if there has been little visible progress?
Explain the actual investigation or blocker and what it means, without inventing completed outputs. Identify the next decision or experiment. A period of uncertainty can be reported honestly, but the update should still show how you are moving towards resolution rather than merely repeating that the task is difficult.
How do I end a useful update?
State the next action, its owner where relevant and when another update or decision is expected. Make any request explicit. This helps the recipient understand whether they need to act now or simply remain informed. Avoid ending with a vague assurance that everything is on track when material dependencies remain unresolved.
Sources and further reading
Reviewed 7 November 2026. Examples and exercises are original editorial guidance. University, employer and professional guidance reflects its own context; actual assessment instructions and workplace processes take priority.
Resume & Workplace Desk
MP Job Hub’s organisational byline for presenting genuine work and communicating clearly in professional settings.
Resumes · Portfolio evidence · Interviews · Workplace communication
View profile →Read our research process or request a correction.
