Repeat Trackout Finding and a Blank Communication Log
You are a third-party inspector on a 3-acre commercial site. You have inspected weekly for six weeks. Your last three reports contain the same finding: "sediment tracking at exit; no corrective action noted." You learn that the superintendent signed the reports, but the subcontractor responsible for street sweeping was never notified because the general contractor's communication log is blank. Today you see 60 feet of trackout on the public road and a mud trail entering a curb inlet about 20 feet away. It has not rained. The general contractor's project manager says it is "not a stormwater issue until it rains" and asks you to stop documenting the same item because it makes the project look bad.
1. Is the trackout a reportable inspection finding even though it has not rained? Explain.
Read the worked answer
Yes. Trackout is a pollutant pathway and a BMP failure, not a weather-dependent event. The site has a stabilized construction entrance for a reason: to prevent sediment from leaving the site. Sixty feet of trackout on a public road, with a mud trail entering a curb inlet 20 feet away, is an off-site discharge condition that is already occurring. Rain would make it worse, but the inspection obligation is not suspended in dry weather. The permit and SWPPP typically require inspections at defined frequencies and corrective action when BMPs are not functioning. The project manager's "not until it rains" statement confuses the trigger for a stormwater discharge with the trigger for an inspection finding. Document the condition objectively and tie it to the SWPPP requirement for the construction entrance and trackout control.
2. What does the blank communication log tell you about the corrective-action process, and what should you do?
Read the worked answer
The blank log explains the repeat finding. A signed inspection report is not a corrective-action system. If the responsible subcontractor was never notified, the finding could not have been corrected. The process is broken at the handoff between identification and assignment. Do not simply write a fourth identical report. Instead:
- Document the absence of a notification trail and the repeat condition.
- Request a named responsible person and a deadline for the sweeping subcontractor.
- Verify the correction yourself and record the verification date and photo.
- Escalate to the project manager and owner's representative in writing, stating that the same finding has appeared three times without a documented correction.
The judgment is to treat recurrence as evidence of a management-system failure, not as a reason to stop documenting. Stopping documentation would hide the failure and weaken the record if a regulator or owner later asks what the inspector knew.
3. Write the key elements of a report entry that will drive action rather than repeat the same finding.
Read the worked answer
A corrective entry should be specific and verifiable:
- Condition: "Approximately 60 linear feet of sediment trackout on the public road at the site exit, extending from the stabilized construction entrance to the curb inlet; mud trail enters the inlet at the southeast corner."
- Standard: cite the SWPPP BMP for trackout control and the inspection requirement.
- Evidence: time-stamped photos, location, and a measurement or estimate.
- Responsible party: the sweeping subcontractor, with the superintendent copied.
- Action and deadline: "Sweep the full trackout length and clean the inlet approach by 4 p.m. today; repeat after any further tracking."
- Verification: "Inspector to re-inspect and photograph the cleaned road and inlet by 5 p.m."
- Escalation: note that this is the fourth consecutive finding and that the prior reports had no documented notification.
The entry should make it difficult to claim the issue was unclear. It should also separate the condition from the person, so the report drives a correction rather than a dispute.