FOD Collection and Findings Log
The response sequence, log fields, and six disposition codes used to document every FOD finding from discovery to closure — free form included in the Complete FOD Prevention Program Guide. Get the Free Log FormQuick answer: A FOD collection and findings log documents what was found, where, in what quantity, and what happened to it. It helps teams document findings, what corrective action was taken, and whether follow-up is needed. Consistency in logging is what converts individual findings into organizational learning. It is Form 03 in the Complete FOD Prevention Program Guide toolkit, referenced in Section 21.
The Routine Finding Response Sequence
Every FOD finding follows this controlled sequence. Consistency here is what converts individual findings into organizational learning.
1. Isolate and Assess
Do not touch, move, open, smell, test, or place an item in a collection container if it could be a sharp, battery, chemical, biological material, unknown powder or liquid, suspected ordnance, or other hazardous item. Keep people clear, mark or cordon the location if safe, and notify the area leader and the responsible safety, hazmat, security, or emergency function. A trained and authorized person must confirm an item is safe before collection.
2. Document
Log the finding immediately — do not wait until the end of the walk. Details vivid at the moment of discovery are hazy 30 minutes later. Minimum documentation: time, location, item description, quantity, category code, probable source (if known), disposition code, and photograph where permitted.
3. Classify
Assign the category code at the time of logging. The person who found the item knows what it looked like and where it came from — deferring classification means the most informed person’s knowledge is lost.
4. Dispose or Escalate
Based on the disposition code, either dispose of the item as trash (D1), return it to tool control (D2), hold it for investigation (D3), or escalate it (D4–D6). The disposition decision determines what happens next.
5. Trend
The logged finding enters the trend dataset. The program owner reviews findings periodically — daily or weekly, depending on volume — to identify repeat patterns and emerging hotspots.
What the Log Captures
A sample entry from the guide’s findings log format (Section 21.2):
| Time | Location | Item (Qty) | Category / Source | Disp. |
|---|---|---|---|---|
| 0715 | Bay 3 | Safety wire, 4 in. (1) | HARD / Widget assembly | D1 |
| 0722 | Bay 3 | Washer, 3/8 in. (1) | HARD / Unknown | D3 |
The Six Disposition Codes
| Code | Meaning | When to Use |
|---|---|---|
| D1 | Disposed as trash | Non-hazardous, not a tool, not a suspected part, not a repeat finding warranting investigation |
| D2 | Returned to tool control | Item is an identifiable tool or tool component |
| D3 | Held for investigation | Suspected part, repeat finding, unknown origin, or potential process implication |
| D4 | Work order generated | Facility deterioration or a condition requiring maintenance |
| D5 | Safety/quality escalation | Immediate or significant safety or quality risk |
| D6 | Customer/authority notification | May require notification of a customer, regulator, or other external party per contract or regulation |
Frequently Asked Questions
Should findings be logged immediately or at the end of the walk?
Immediately. Details that are vivid at the moment of discovery are hazy 30 minutes later, and the person who found the item is the most informed person to classify it.
What should never be handled directly during collection?
Any item that could be a sharp, battery, chemical, biological material, unknown powder or liquid, or suspected ordnance. Keep people clear and notify the appropriate safety, hazmat, security, or emergency function — only a trained and authorized person confirms an item is safe before collection.
What happens to an item dispositioned D3?
It is bagged, tagged, and stored separately from general trash, then investigation is assigned to the appropriate function — quality, safety, maintenance, or engineering — depending on the nature of the item.
Who reviews the findings log data?
The program owner reviews findings periodically, daily or weekly depending on volume, to identify repeat patterns and emerging hotspots feeding into the Repeat FOD Investigation process.
Related Forms in the FOD Prevention Toolkit
Daily FOD Walk Checklist
The walkdown procedure that produces the findings you log here.
Internal Audit Checklist
Verify that findings are being logged consistently and acted on.
FOD Prevention Program Guide
The complete 216-page guide, all 17 forms, and the Excel tracker.
Get the Complete Guide and Toolkit
The FOD Collection and Findings Log is one of 17 free forms included with the 216-page Complete FOD Prevention Program Guide.