Template
Write an update with a clear request
A status colour does not tell the reader what to decide.
Before you use it
- Use when
- People outside the immediate work need enough context to coordinate or decide.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
A template to use
Status: ___. What changed since the last update: ___. Evidence/result: ___. Risk or blocker: ___. Decision/help needed: ___. Next checkpoint: ___.
Why it matters
Record what changed, the evidence, the unresolved risk and the help or decision needed. Give the next checkpoint so the reader knows when uncertainty will be revisited. Keep observed results separate from expected benefits; a list of activity cannot stand in for either.
An example
A migration passed staging checks. Production performance is still unknown, so the update requests a limited rollout rather than declaring completion.
Check your result
Can the reader find the current evidence, unresolved question and requested decision?
Keep this limit in mind
- Do not hide uncertainty behind green status language or flood readers with activity logs. Sensitive information still follows access rules.
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Connected ideas
Useful withClose a meeting with real commitments
Evidence and sources (1)
This update template keeps current evidence, unresolved risk and the decision request explicit.
Editorial design and source provenance only. No causal benefit, percentage improvement or validated intervention is claimed. Access: selected_source_sections; 2026-10-11. Registered first-party project text; template provenance, not an efficacy study.
Send a stakeholder update that supports a decision — Brali source record · Selected template fields
Edition and review
Version 0.1.0 · Published
Agent review: Agent editorial and scoped evidence review · 2026-10-11