Source: https://unitedwetransform.com/meeting-follow-up-mechanism/
Meeting follow-up guide
A commitment written in an agenda shows a plan. Checking what happened requires a later observation. Use the worksheet below to agree who owns an action, when to review it and what evidence to inspect. Download it to edit locally; this page has no worksheet submission or automatic reminder service.
21,781 of 23,624 captured public agenda records (92.2%) have no captured commitment, follow-up, tracking, baseline or impact signal under this rubric.
12,821 of 14,219 representative event-group records (90.2%) have no captured commitment, follow-up, tracking, baseline or impact signal under this rubric.
Scoring version: ges_agenda_judgment_v2_0. Statistics snapshot: 2026-07-16T23:26:34.623689+00:00. The two populations are separate; do not combine their counts or interchange their denominators.
The absence flag requires all five captured signal counts to be zero. It is broader than the explicit Follow-up label alone. Records are not unique meetings. The representative population uses the corpus grouping process; it is not a random sample of all meetings. Uneven documentation, repeated records and extraction limits remain. A missing public signal does not establish that no follow-up happened privately.
Describe one bounded action and ask a specific person to accept it. Record unresolved ownership rather than assigning an absent colleague.
Agree a realistic due date and a separate review date. Allow enough time for the evidence to become available.
Name the record, artifact or observation that would show the action was taken. Agree its limits and who may inspect it before work starts.
At review, record the evidence actually seen and whether it is self-reported or independently checked. If access failed or nobody replied, record unknown.
Use the review to agree whether to continue, revise or stop. Keep the next owner and review date explicit. Completion alone does not prove a beneficial effect.
Describe what needs to be done in clear terms.
Your entry: ________________________________________
Name a person who has accepted the action. Replace the role placeholder before use.
Your entry: ________________________________________
Set a date by which the action should be completed.
Your entry: ________________________________________
Specify what will be reviewed to confirm completion of the action.
Your entry: ________________________________________
Set a future date for reviewing progress or outcome.
Your entry: ________________________________________
Identify who will observe and report on the action's status.
Your entry: ________________________________________
Use pending, self-reported, verified, blocked or unknown. Apply the definitions below.
Your entry: ________________________________________
Record what was actually observed, the observation date and its limits. Leave a missing observation unknown, not zero.
Your entry: ________________________________________
Define who has access to this information and any confidentiality limits.
Your entry: ________________________________________
Run a small handoff test on three invented requests
Process owner (replace before use)
2026-10-02
Redacted handoff checklist and observation log, compared with the starting process. Check completion separately from any claimed improvement.
2026-10-09
Agreed reviewer (replace before use)
pending
None yet; this is an illustrative plan, not a completed test
Only the agreed working group; no customer identifiers
Pending: the review is not yet due or evidence is awaited.
Self-reported: the owner reports completion; no separate check is recorded.
Verified: a reviewer checked the specified completion evidence. This does not establish causal impact.
Blocked: the owner reports a constraint; record what remains unresolved.
Unknown: evidence is missing, incomplete or inaccessible. No reply is not proof that no work occurred.
The worksheet records a plan and later observations. It cannot verify completion or establish impact by itself.
A note-taking tool may capture or help revisit commitments. Its summary alone is not evidence that an action occurred.
Download and edit locally. This page does not accept worksheet uploads or send reminders.
Keep private evidence in an approved location. Share a reference and its access limits, not confidential contents. If the reviewer is also the owner, disclose self-report.
Editorial review: 2026-09-29. The source statistics retain their original snapshot date.
No. Follow-up may happen privately or appear in material that was not captured. The public-evidence flag describes the captured record.
No. Checking that an action occurred is different from establishing what it changed. A causal claim needs stronger evidence.
Record unknown until you have a usable observation. Do not turn silence into a failed action or a zero result.
No worksheet form or upload is provided. Download the files and edit them in your own approved tools.
This guide helps you design an action review. The related frequency page describes how often specific signals occur in the public corpus.