From team updates to accountable next actions
One evidence-based review with decisions, owners and follow-through.
Stop and check if…
- Invented progress or owner
- Unknown figures presented as facts
- Decision without actual approval
Do not mark a stage done just because AI produced a draft. Use actual evidence and human approval. Keep private records in your approved tools. Prompt Bro never submits, posts, pays or approves anything.
0 of 4 stages verified
Stages unlock in order. Only completion ticks are saved in this browser; no documents, inputs or AI outputs are stored.
All 4 stages verified. Keep the approvals and evidence in your own records; this tick list is not proof.
- What you need
- Current team updates and cash position
- What to produce
- Five-line brief, known numbers and blocked items
- Who checks it
- Team and accounts verify facts
Open the tasks
- Daily ops report · Tested
- Reading team updates · Tested
- Morning cash position · Tested
If this happens
- An update has no owner, date or source: Send it back to the team member; don't fill gaps with guesses.
Handoff template
Workflow: From team updates to accountable next actions Stage: Collect (1 of 4) Source refs (document no. / date): [confirm] Item / unit / quantity: [confirm] Known (verified against source): [confirm] Unknown / held items and why: [confirm] This stage produced: Five-line brief, known numbers and blocked items Approval status (approved / pending / rejected): [confirm] Approved by (Team and accounts verify facts): [name / role] Evidence ref (where the proof is kept): [confirm] Next stage: Review, needs: Approved MIS, targets and blockers
- What you need
- Approved MIS, targets and blockers
- What to produce
- Agenda, questions and goal gaps
- Who checks it
- Owner confirms decisions
Open the tasks
- Understanding MIS · Tested
- Weekly review meeting prep · Tested
- Goals and targets · Tested
If this happens
- Cash or sales figures are unverified: Mark them unverified in the review; decide only on confirmed figures. Switch to: From month-end checklist to owner MIS
Handoff template
Workflow: From team updates to accountable next actions Stage: Review (2 of 4) Source refs (document no. / date): [confirm] Item / unit / quantity: [confirm] Known (verified against source): [confirm] Unknown / held items and why: [confirm] This stage produced: Agenda, questions and goal gaps Approval status (approved / pending / rejected): [confirm] Approved by (Owner confirms decisions): [name / role] Evidence ref (where the proof is kept): [confirm] Next stage: Delegate, needs: Approved decisions and meeting notes
Unlocks after stage 1 is verified.
- What you need
- Approved decisions and meeting notes
- What to produce
- Action ref, owner, deadline and acceptance checks
- Who checks it
- Owner confirms assignment
Open the tasks
- Clear task briefs · Tested
- Minutes of meeting · Tested
- Chasing tasks across teams · Tested
- Decision and approval log · Tested
If this happens
- A task has no single owner or due date: Don't assign it to 'team'. Name one person and a date. Use: Clear task briefs
Handoff template
Workflow: From team updates to accountable next actions Stage: Delegate (3 of 4) Source refs (document no. / date): [confirm] Item / unit / quantity: [confirm] Known (verified against source): [confirm] Unknown / held items and why: [confirm] This stage produced: Action ref, owner, deadline and acceptance checks Approval status (approved / pending / rejected): [confirm] Approved by (Owner confirms assignment): [name / role] Evidence ref (where the proof is kept): [confirm] Next stage: Follow through, needs: Current project/task evidence
Unlocks after stage 2 is verified.
- What you need
- Current project/task evidence
- What to produce
- Status, overdue and unresolved items
- Who checks it
- Owner verifies completion and carries forward open actions
Open the tasks
- Project status reports · Tested
- Chasing tasks across teams · Tested
- Project risk, issue and dependency tracker · Tested
If this happens
- Action overdue or blocked: Log the blocker and the decision needed; carry it to next week. Use: Project risk, issue and dependency tracker
Handoff template
Workflow: From team updates to accountable next actions Stage: Follow through (4 of 4) Source refs (document no. / date): [confirm] Item / unit / quantity: [confirm] Known (verified against source): [confirm] Unknown / held items and why: [confirm] This stage produced: Status, overdue and unresolved items Approval status (approved / pending / rejected): [confirm] Approved by (Owner verifies completion and carries forward open actions): [name / role] Evidence ref (where the proof is kept): [confirm] Next stage: none. Workflow ends after this approval.
Unlocks after stage 3 is verified.