Update Framework
How to write short but complete progress updates that communicate status, completed work, current focus, risk, decisions, and next steps.
An update is not an activity dump
A list of twenty completed tasks forces the reader to infer the actual state of the project.
Status should state the overall condition
On Track, At Risk, Blocked, or Changed Scope is more useful than a long paragraph with no conclusion.
Framework: Status → Done → Doing → Risk → Decision → Next
Status — what is the overall project condition?
Done — what has been completed and what evidence exists?
Doing — what is the current focus?
Risk — what may affect outcome or timing?
Decision — what needs stakeholder action?
Next — what happens next, and when?
Done should include evidence
“Research complete” is weaker than “12 interviews completed, synthesized, and mapped into insights.”
Doing should show focus
Do not list every open task.
Show which workstream currently matters and why.
Risk should include consequence
“API risk” is vague.
Explain which milestone it affects, when, and by how much.
Decision turns an update into action
If the project is waiting on approval, option selection, or a trade-off, make it prominent.
Next creates continuity
End with what the reader can expect next: milestone, review, deliverable, decision, or next update.
Applying this on Forwork
Forwork can standardize an Update Block: Status, Done + Evidence, Doing, Risks, Decisions Needed, Next Step, Owner, Next Update Date.
Updates then form a timeline readable by clients and AI.
Conclusion
Do not ask, “Is this update detailed enough?”
Ask: “After reading for 30 seconds, does the stakeholder know where the project stands and what needs to happen next?”
Status → Done → Doing → Risk → Decision → Next.