Purpose of the Template
Many compliance programs can show that a procedure exists, but fewer can prove that the procedure matches what crews actually do, especially during off-hours. This template is a one-page walkdown record designed to make that comparison. It also includes an aged-repair review to ensure that a safety-critical work order doesn't remain "urgent" without a named person accepting the risk.
The need for this template is highlighted by the 2014 incident at DuPont's La Porte plant, where nearly 24,000 pounds of toxic methyl mercaptan were released indoors, resulting in four fatalities. A daily draining task was in operating instructions but not in a written procedure, and it was never reviewed through management of change (MoC). Two rooftop ventilation fans were broken, with an urgent repair order open for nearly a month, despite previous audit warnings. The CSB found that the site never formally assessed its process safety culture. Documents existed, but controls did not.
If you're a CISO, the parallel is clear. An undocumented firewall exception that becomes routine is your drain valve. A critical patch ticket marked urgent for weeks is your fan work order.
Prerequisites
- A named owner for each safety-critical or security-critical process.
- Access to the current written procedure and change record for each process.
- Your open-items backlog (work orders, tickets, audit findings) with creation dates.
- Authority for the reviewer to observe work without advance notice. A prepared walkdown is just a document review.
- A Policy Exception Registry, even a spreadsheet, for deferrals.
The Template
PRACTICE-VS-PAPER WALKDOWN RECORD
Section A: Identification
- Process / system: ______
- Location / team: ______
- Reviewer (not the process owner): ______
- Date and shift observed: ______
- Procedure ID and version reviewed: ______
Section B: Observation (complete before opening the procedure)
- Describe each recurring task observed, in the crew's own words: ______
- Which tasks are done daily or on a schedule? ______
- Tools, protective equipment, or access used: ______
- Samples, checks, or records the task calls for, and whether they were produced: ______
Section C: Comparison to Paper For each task in Section B:
- Is there a written procedure covering it? Y / N
- Was it reviewed through change management before becoming routine? Y / N / Unknown
- Does actual practice match the written steps? Y / N
- If N to any: describe the gap: ______
Section D: Unreviewed Changes
- Any workaround, bypass, temporary heating, valve realignment, or configuration change observed? ______
- Change record number, or "none found": ______
Section E: Aged-Item Review
| Item ID | Description | Opened | Priority | Linked audit finding | Days open | Compensating control | Approver (name/title) | New due date | Rationale |
|---|
Section F: Disposition
- Gaps requiring a new or revised procedure: ______
- Tasks requiring a retroactive change review: ______
- Owner and due date for each: ______
- Escalation required (Y/N), and to whom: ______
Section G: Sign-off Reviewer: ______ Process owner: ______ Senior manager: ______
Customizing the Template
Section B comes before the procedure intentionally. Observing first prevents the reviewer from seeing only what the document states. Keep this order even if there's resistance.
Section D is your MoC trigger list. Tailor it to your environment. In IT, replace "valve realignment" with firewall rule changes, emergency access grants, manual data fixes, or scripts run outside the change process. The principle is the same: flag any routine change without review.
Section E is where audit follow-through happens. Set thresholds for when an aging item needs senior sign-off based on your Impact Tolerance and regulatory exposure. Extending a due date requires a named approver, a stated compensating control, and a rationale. Written extensions invite scrutiny; silent extensions become norms. Link each item to any audit finding that raised the same issue to identify patterns.
Frequency. Review high-consequence processes more often than low-consequence ones, and rotate reviewers to avoid normalizing gaps. Feed repeated Section C failures into your Policy Gap Analysis cycle.
Scale it down for small teams. If you can't walk every process, start with the three tasks where failure would hurt most, and ask each crew one question: what do you do every day that's not in a procedure?
Validation Steps
- Test the reviewer's independence. Ensure the person completing Section C doesn't report to the process owner. Self-review defeats the purpose.
- Sample for unannounced coverage. Check that some walkdowns occurred without advance notice, and compare findings to announced ones. Consistent differences reveal program issues.
- Trace one gap to closure. Follow a Section F item to a revised procedure, a completed change review, and verified training. If any link is missing, your remediation loop is open.
- Audit the extensions. Review every Section E deferral from the last cycle. Each should have a named approver and a compensating control. Blank approver fields are findings.
- Check the backlog against the registry. Every aged safety-critical item should appear in your Policy Exception Registry or have a dated closure. Anything missing is invisible risk.
- Ask what changed. If a quarter of walkdowns produce zero Section C gaps, question the method before celebrating.
The DOJ's Evaluation of Corporate Compliance Programs asks if a program works in practice, not just if it exists. This record provides evidence collected by observing work, not just reading documents.





