A Meeting Record Should Make the Next Check Possible
A participant can describe a need without accepting responsibility for meeting it. An organization can offer to investigate capacity without committing supplies. A confirmed delivery still needs actual evidence. Record these stages explicitly instead of writing a broad sentence that "partners agreed to cover all gaps."
This tutorial continues the fictional Riverbend provisional situation brief. It draws on the LOG assessment cycle's sharing guidance for clear findings and limits, while the commitment design below is original OpenAid practice. Use coordination and authority to distinguish a shared discussion from each organization's actual decision powers.
Prepare the Discussion From a Dated Baseline
All records, roles, times and offers in this exercise are invented. At day 3, 16:00, Riverbend has verified delivery of 48 kits against a plan of 60. Twelve remain undelivered. A separate request for 30 more is unverified and may overlap. Current bridge access and particular water/health service questions remain unresolved. The team has no verified people-affected total.
Before the meeting, identify which decision each question needs, who can accept a task and who must approve a resource commitment. Share only the permitted version of the brief. Give participants usable formats and an actual route to correct the record; attendance alone does not prove language, disability or connection needs were met.
Distinguish What Each Statement Establishes
| Statement in the Exercise | Correct Record | What It Does Not Establish |
|---|---|---|
| Program lead asks another organization to cover 30 kits | Request for a specified contribution; need/overlap and acceptance remain pending | A confirmed commitment, 30 new eligible households or delivered assistance |
| Partner operations role says it may have ten kits, subject to stock and management approval | Conditional offer to check ten-kit capacity; source, conditions and decision owner recorded | Available stock, permission to transfer or a guaranteed delivery date |
| Logistics lead accepts the task of reconciling the twelve undelivered kits by 18:00 | Confirmed verification task with an owner and due time | A promise that all twelve will be delivered by 18:00 |
| WASH and health leads accept separate service-verification tasks | Two sector checks, with scopes and intended updates | A diagnosis, safe-water certificate, patient referral or universal sector agreement |
| Meeting chair proposes a combined public update | Proposed information product; source/disclosure/release authority still needed | Permission to publish restricted details or speak for every organization |
A useful record captures the exact object and unit: ten kits, a stock check, a route question or an information product. Do not convert "we will check" into "we will deliver" while shortening the minutes.
Use an Action and Commitment Ledger
Record item | who/what/where/when | statement type | accepted owner | capacity/authority evidence | conditions | status | next check | completion evidence. A role should accept its own task; the note taker should not assign an absent partner by assumption.
For the conditional ten-kit offer, the ledger says: "Partner operations role checks stock and management permission for up to ten complete kits; decision expected by 18:00 through the approved coordination channel. No stock or delivery confirmed. If no answer, meeting coordinator records pending and uses the agreed escalation. Program lead separately verifies the thirty-kit request and overlap."
If the partner later confirms ten available and authorized kits, record the actual decision, version, conditions and proposed delivery arrangement. Only after the receiving evidence is checked should the item become delivered. Do not add ten to Riverbend's 48 delivered merely because a manager approved an offer. Keep source and recipient units consistent to avoid double counting.
Resolve Disagreement Rather Than Write Around It
Suppose the partner thinks it accepted a stock check while the minutes say it committed ten kits. Ask it to correct the statement before relying on the supposed commitment. Retain the correction and any resulting planning gap. A majority of participants or an unchallenged email cannot substitute for an organization's actual authorized decision.
Where no one accepts a necessary task, record the gap, the consequence and the actual escalation owner. Do not fabricate consensus to produce a clean action list. Sensitive operational or individual issues may need a restricted bilateral channel instead of the general minutes.
Close the Loop Without Confusing It With Learning
At the agreed update, compare the promised check with its evidence and decision. Report missed conditions and changed capacity in the next situation brief. Inform affected participants through the permitted accessible channel when a checked decision changes what they were told. This is prospective coordination and follow-through; a retrospective lessons discussion is a different task.
No meeting here certifies services, grants membership, authorizes spending, replaces organizational command or supplies a current referral directory. The ledger makes those responsibilities visible so the real owners can act and the next reader can distinguish progress from a proposal.