You need a short update and supporting material for questions.
State the current position, then compare the plan with actual progress.
Select the main risk and request. Keep details for questions.
Name the next update and rehearse before trimming.
Fictional example: six of eight units planned this week are complete; two await interface information. The Friday demo scope may be affected and remains unconfirmed.
Keep the weekly plan distinct from the overall task count. Rehearse the timing; a word count cannot guarantee a one-minute update.
Open the outline
Overall status:
Plan and actual progress:
Risk or open question:
Request:
Next action:
Supporting evidence for questions:
Progress requires another person's resources, confirmation, or approval.
Request a specific action and explain its basis.
Specify the response deadline and what needs confirmation.
Keep conditional alternatives and pending approval visible.
Fictional example: confirm the contact by 17:00 today. If information is still missing at 12:00 tomorrow, propose a six-unit Friday demo. The scope change needs approval.
Act on an alternative plan only after it is approved.
Open the outline
Specific request:
Reason and evidence:
Confirmation needed:
Response deadline (date and time):
Conditional alternative:
Pending approval:
A delivery deviation is known, but the full causes may not be.
Compare the original agreement with the current deviation.
Separate known impacts, possible impacts, and proposed explanations.
State actions, support needed, and the next update time.
Fictional example: eight units were due by the agreed check-in; six are complete and two await information. Check the demo impact and update at 12:00 tomorrow.
Waiting for information does not prove a sole cause. Do not delay an urgent risk update until a full solution exists.
Open the outline
Original agreement:
Current deviation:
Known and possible impacts:
Possible causes and open questions:
Actions:
Support needed:
Next update (date and time):
Facts, judgments or priorities differ and a next step needs deciding.
Check what was actually said, material versions and the shared goal.
Separate facts, interpretations and priorities; state what would change your view.
Record actual decisions, reservations and pending actions. Discussion is not approval.
Fictional example: A leads at 40% quality weight, B at 60%, and they tie at 50%. Ratings are simulated; confirm mandatory conditions and comparison evidence.
Data has scope and evidence limits. Scores do not settle priorities.
Open the outline
Shared goal:
Actual disagreement and material version:
Facts, interpretation or priorities:
Evidence and unknowns:
What would change my view:
Checkable question or action:
Actual decision, authority and reservations:
Owner, date and time and approval:
A review or self-assessment needs visible work and clear ownership.
State your actual role, actions and outputs against the goal.
Explain how individual outputs relate to team results and retain colleagues’ contributions.
Link claims to evidence, acceptance and feedback scope; leave unmeasured impact open.
Separate fictional role example: you completed 3 units and colleagues 3, for 6 team units; you also prepared one checklist. Do not add your 3 to the team’s 6.
Unit share is not business value share. A completed checklist does not establish improved efficiency.
Open the outline
Goal and period:
Actual personal role, actions and outputs:
Team result and colleagues’ contributions:
Relationship between personal and team outputs:
Evidence locations, completion/acceptance definition and feedback scope:
Unfinished work and unknowns:
Observed impact and unsupported claims:
Next check and status:
Describe individual roles and team delivery with evidence. Reflect on reusable learning and responsibilities, retaining unmeasured impact without promising promotion.
