FOD Program Documentation and Records

Walks, tool audits and investigations only count if you can show they happened, and only help if the information can be compared over time. Good FOD program documentation makes that possible. The guide covers it in several places: how to structure the document package, how to control it, how to keep the data clean and how long to keep records. This article pulls those pieces together.

The Documentation Hierarchy

A mature program separates policy, procedure, work instructions and forms. The reason is practical: a change at one level should not cascade unpredictably through the whole system. The guide describes four levels:

• FOD policy. The program charter, accountabilities, area classifications and core principles, kept to one page and signed by senior leadership. It is written for all personnel, leadership, customers and auditors, and reviewed annually or when program scope or accountability changes.
• FOD procedure. The walkdown process, classification system, risk matrix, investigation triggers, corrective action process and training requirements. Its audience is the program owner, walk leaders, supervisors, quality and safety. Review it every 6 to 12 months and update it based on investigation findings and improvement initiatives.
• Work instructions. Area-specific walk maps, zone checklists, hotspot lists and tool control specifics for each area, aimed at walk participants and zone captains. They change when areas, hotspots or equipment change.
• Forms and checklists. The briefing card, daily walk checklist, findings log, investigation worksheet, corrective action tracker, dashboard template and audit checklist, used by field personnel and updated when procedure changes require it.

Many of the forms in that bottom level are available in the free toolkit. See the FOD walk checklist, the FOD inspection form, the repeat investigation worksheet and the corrective action tracker.

Document Control

A structure is only useful if people are working from the current version. The guide sets out simple document control rules:

• Each document has a unique identifier, version number and effective date.
• The FOD Program Owner owns the policy and procedure, while area supervisors own the area-specific work instructions.
• Obsolete versions are removed from points of use, and the current version is available at every point of use, whether posted, in the FOD kit or on the shared drive.
• A document change log records what changed, why and when, for each version.

Posting the current area map and rules where work happens is a natural fit for FOD signs, which also help make the classification of each area obvious to everyone who walks in.

Data Quality Standards

The guide reminds readers that data is only as useful as it is consistent. A healthy data pipeline captures findings at the moment of discovery, keeps them in one central system, produces standard reports on a schedule and makes sure every trend or issue becomes a tracked corrective action. Within that pipeline, five quality standards apply to what gets recorded:

• Location names. Use a standard taxonomy and a shared location master list so that a label like Bay 3 means the same thing on every shift.
• Category codes. Use the guide’s ten-category system consistently. The guide notes that this is its recommended taxonomy, not a NAS412 or SAE mandate. Give personnel a quick-reference card with each code, its meaning and examples. Our article on the FOD classification system explains it.
• Item descriptions. Be specific enough for trend analysis. Fastener is less useful than 1/4-inch hex bolt, steel, and debris is useless.
• Quantity. Count items instead of guessing: a logged ten-ish tells you less than an exact twelve.
• Timeliness. Log findings within minutes of discovery, because a log reconstructed from memory an hour later loses detail.

Tools that keep debris separated at the point of collection, such as labeled FOD cans, make accurate counting and categorizing far easier. And every walk, even one with zero findings, should produce a completed checklist: the guide notes that a blank checklist is evidence of an incomplete walk.

Record Retention Minimums

The guide recommends retaining FOD records per your organization’s document retention policy, but sets these as a minimum:

• Daily walk checklists and findings logs: at least 12 months, preferably 24 to 36 months so you can compare year over year.
• Investigation reports: at least 3 years, or per regulatory or customer requirements.
• Corrective action records: for the life of the action plus 12 months after verified closure.
• Training records: per your personnel record policy, typically the duration of employment plus a defined period.
• Audit reports: at least 3 years for trend comparison.

Check your own customer and regulatory requirements against these minimums, since the guide’s figures are a floor rather than a compliance standard.

Program Records That Prove Program Health

Finally, the guide lists the records that demonstrate program health to auditors and should be organized and retrievable:

• Completed daily walk checklists and findings logs.
• Investigation reports.
• Corrective action records with verification evidence.
• Training attendance and competency verification records.
• Internal audit reports and the corrective actions arising from them.
• Monthly dashboards and management review minutes.
• Document change history.

If you can pull each of these on request, an auditor can follow the chain from policy to practice to results. The FOD audit checklist is a useful way to check your own readiness. Once your records are in order, the next step is deciding which numbers to trend from them; see FOD leading and lagging indicators.

Get the Templates

The complete guide includes the full documentation package structure and the toolkit forms that populate the bottom tier. Request the free 216-page guide and toolkit to build yours.