Start with the decision
Write the commitment and its intended outcome, then define the states needed to deliver it. A pledge, funding agreement, scheduled activity and completed event each provide different information. Preserve who accepted the commitment and what resources are actually available.
Build the record
Record responsible roles, funding status, timing, dependencies, acceptance and completion evidence. Attach relevant agreements without publishing private values or identities. Keep plans visible when an activity is postponed or cancelled rather than deleting them to protect a success count.
Check before acting
Advance the state only when the relevant confirmation exists. Review actual delivery against the original scope and record deviations. Do not use registration, promised donations or planned attendance as evidence of achieved social outcomes.
Worked example — illustrative
A fictional project promises a repair session but has not agreed a venue. Its record remains pledged. After resources and organiser acceptance are confirmed it becomes scheduled, then delivered only after the session occurs. Attendance and participant feedback are recorded under their own permissions.
Keep a useful handover
Record the responsible person, decision date and next review trigger with the evidence version. Keep planned actions distinguishable from confirmed activity. If later information changes the result, preserve the earlier record and update current guidance.
- Define the commitment states.
- Record actual resources.
- Keep dependencies visible.
- Require state-specific confirmation.
- Review delivered scope.