FIELD NOTES / AYESHA SULTAN
A status update should help someone decide.
Turn project reporting into clear decisions, ownership, and next steps.
A project report can be accurate and still leave its reader unsure what to do. Lists of completed tasks show activity. A useful status update also explains what that activity means for delivery and where attention is needed.
When I shape reporting, I start with the reader. A production team needs detailed handoffs. A program lead needs dependencies across workstreams. An executive may need a concise view of the goal, the risk, and a decision they can help resolve.
Lead with what changed
Start with the material change since the last update. Has a milestone moved? Has a dependency been resolved? Has new information changed the scope? Explain the effect on the plan, rather than asking the reader to infer it from a list of tasks.
Keep routine detail available through the working plan. The summary should help people find the issues that deserve their attention.
Make risks actionable
“Approval pending” describes a state. “The regional review is due Thursday; a later decision would move production into next week” describes a dependency and its consequence. Add the owner and the next action so the issue has a clear route forward.
Distinguish a possible future risk from a blocker already stopping work. Teams need room to raise uncertainty early, before it becomes a missed commitment.
Ask for a decision clearly
When a decision is needed, state the question, the options, the tradeoffs, and the date by which an answer is useful. Identify who has the authority to decide. A recommendation can help, provided the assumptions behind it are visible.
For example, a team may need to choose between reducing scope and moving a launch milestone. The update should explain the delivery impact of each option and the people who need to be involved.
Close the loop
Once a decision is made, reflect it in the plan and tell the affected teams. Record the owner of the follow-through. Otherwise, a productive meeting can still leave different people working from different assumptions.
A practical update can follow five prompts: what changed, what comes next, what is at risk, what needs a decision, and who owns the action. Keep the cadence appropriate to the pace of the work.
The purpose of reporting is shared understanding that leads to action. When a reader knows where to focus and what they can do, the update has earned its place.