An action register connects a condition to an owner and test
Meeting notes often mix observations, ideas, complaints, and promises. An action register separates them. Each row should state the observed condition, evidence source, intended change, responsible owner, dependencies, next action, target date, status, and how the group will check the result.
Keep four statements distinct
- Condition
- What was observed, where, when, and by whom.
- Interpretation
- Why the condition may matter, including uncertainty or conflicting evidence.
- Action
- The specific change requested or test to run.
- Outcome
- What would indicate improvement and what unintended effect will be checked.
This distinction prevents a perception from being presented as a confirmed incident or a completed repair from being presented as proof of prevention.
Route work by ownership and scale
- Quick maintenance: failed lamp, damaged sign, obstructed path, or broken latch.
- Operating practice: staffing, opening hours, reporting route, or check-in procedure.
- Program or service: outreach, youth activity, support, transport, or place activation.
- Policy or capital work: crossing, layout, building change, service contract, or funding decision.
Use the community safety walk worksheet to collect place conditions. The evaluation guide supports outcome and limitation reporting.
Close actions with evidence, not a green status
Recheck at the relevant time
Confirm that the change exists and functions under the condition that triggered the action. A lamp repaired during daylight must be checked after dark. A new sign must be visible from the decision point. A program must reach the intended participants with the planned quality.
Keep unresolved dependencies visible and record why a proposal was rejected, changed, or delayed. Publish an accessible summary that protects personal information. A trustworthy register shows completed, incomplete, and ineffective actions rather than turning every activity into a success claim.