The Flattened Silt Fence and the Fast Camera Clock
During a weekly inspection of a 14-acre residential subdivision, you find the silt fence behind lots 12–18 flattened where tracked equipment crossed it, with a 40-foot sediment track running down the curb to a storm inlet. You take 12 photos on your phone and 3 on the site camera. Back at the trailer you realize none of the photos include a scale or a recognizable landmark, and the site camera's clock reads three hours fast. The SWPPP site map is dated five months ago; a grading revision approved since then moved this fence line roughly 15 feet upslope. Thursday's forecast calls for 1.2 inches. The grading superintendent says, "Just write it up as minor and we'll get to it next week."
1. Before you leave the site, what must you add to or correct in the photo record, and how do you handle the mis-set camera clock?
Read the worked answer
A photo that can't be located or scaled is decoration, not documentation.
Add before leaving:
- A wide, medium, close sequence for each deficiency: wide shows the lot and street context, medium shows the fence run and the sediment track, close shows the torn fabric, undermined posts, and the depth of the sediment deposit against a scale or boot.
- A scale or a fixed reference in at least one frame (folding ruler, clipboard, or a landmark such as the inlet grate or a lot marker).
- Location: GPS-tagged phone shots, or a photo of the site plan with the location circled, plus written station/lot references in the log.
The clock:
- Do not edit the original files. Record the offset ("site camera +3:00 vs. actual") once in the inspection log, note that all three images carry the wrong timestamp, and state the corrected time in the narrative.
- Why it matters: the timestamps establish that the condition existed before Thursday's rain. A timestamp that is three hours wrong is arguable; a timestamp that is wrong by a documented, consistent offset and cross-referenced to phone photos is defensible.
- Cross-reference the phone and camera images to the same inspection event in the log so the two sets corroborate each other.
2. The site map doesn't match what's in the field. What is the correct way to reconcile it?
Read the worked answer
Treat this as two separate problems that must not be merged.
Problem 1 - the record. Obtain the current approved plan revision and confirm the approval date. Mark the discrepancy on a copy as an "as-found" or field markup; never redraw the approved sheet as though the 15-foot shift were approved. Note who you asked for the revision, when, and what you received.
Problem 2 - the function. Ask the engineering question, not just the paperwork question: does the fence as installed still intercept sheet flow at the right location? A fence moved upslope may actually be better sited; moved downslope into a swale it may be worse. Inspect the contributing area, slope, and whether flow now bypasses the ends.
Then decide: if the field condition is functionally acceptable, the fix is a plan revision through the proper approval path, not a field change. If it is not, the fix is reinstallation per plan. Either way the report states: field condition, plan condition, the difference, and which correction path is required.
3. How do you respond to "write it up as minor" and what actually goes in the report?
Read the worked answer
Response: "Minor" is a classification the permit defines, not a term I can trade for a schedule. What I can do is describe what's there and set the correction deadline against Thursday's rain. If the fence is re-anchored and the track cleaned before the storm, the record will say so.
Keep the tone collaborative but the substance fixed - the report is not a negotiation.
In the report:
- Factual condition: length of fence affected (measured, not estimated), extent of sediment track, whether the inlet is currently protected.
- Cause as observed (equipment crossing), without assigning blame.
- Photos referenced by number with the clock-offset note.
- Corrective action requested, with a date and time tied to the forecast rather than to convenience.
- A neutral record of the conversation: who said what, when, and that the correction was requested verbally on site.
- Whether the operator/permittee was notified in writing.
If the work is not done before the storm, the follow-up entry documents the consequence with the same specificity. That sequence - report, deadline, verification - is what makes a documentation file hold up.