The 10 most commonly missed conditions on infrastructure projects

After analysing hundreds of approval documents across Australian infrastructure projects, these are the conditions that get missed most often. Not because they're hidden — but because they require ongoing attention, triggered responses, or coordination between multiple parties.

1. Weather-triggered erosion inspections

The condition: "All erosion and sediment controls must be inspected within 24 hours of rainfall exceeding 20mm."

Why it's missed: Nobody checks the rain gauge on weekends. The 24-hour clock starts ticking at the rainfall event, not at the start of the next business day. Weekend rain on a Saturday means the inspection must happen by Sunday — not Monday morning.

2. Pre-clearance fauna surveys

The condition: "Pre-clearance surveys for threatened fauna must be completed minimum 14 days before vegetation removal."

Why it's missed: The 14-day lead time gets squeezed when the program accelerates. The ecologist isn't booked, the survey can't happen in time, and the clearing proceeds anyway. This is an EPBC Act issue with federal enforcement.

3. Community notification before high-impact works

The condition: "Residents within 200m must be notified 7 days before piling, blasting, or night works commence."

Why it's missed: The works schedule changes and the notification window shrinks. Or the notification goes out but isn't recorded in the register. When the complaint arrives, there's no evidence of notification.

4. Annual Return submission deadline

The condition: "Submit Annual Return to EPA within 60 days of licence anniversary."

Why it's missed: 60 days feels generous — until day 55 when you realise you need 12 months of monitoring data compiled, reviewed, and formatted. Late lodgement is a separate offence.

5. Complaint response within 48 hours

The condition: "All complaints must be responded to within 48 hours and logged in the complaints register."

Why it's missed: The complaint gets handled informally — a phone call, a chat at the fence line — but never logged. The EPA expects a written register with timestamps. Verbal resolution doesn't count.

6. Heritage unexpected finds protocols

The condition: "If Aboriginal objects are discovered, cease all work within 10m and notify Heritage NSW within 24 hours."

Why it's missed: Workers don't recognise artefacts. The protocol exists in a management plan that nobody has read. By the time it's identified, the context is disturbed and the notification is late. This is a hold point in practice — work must stop until the protocol is followed.

7. Dust deposition gauge maintenance

The condition: "Dust deposition gauges must be maintained at four boundary locations with results reported monthly."

Why it's missed: Gauges get knocked over by plant, filled with rainwater, or simply not read on schedule. Missing data is a compliance gap — the EPA treats no data as non-compliance.

8. Water quality trigger value reporting

The condition: "If any water quality parameter exceeds trigger values, report to EPA within 7 days."

Why it's missed: Lab results take 5-10 days to come back. By the time you see the exceedance, the 7-day window has started from the sampling date, not the result date. Some interpretations say it starts from when you "become aware" — check your specific condition wording carefully.

9. Noise monitoring during first occurrence

The condition: "Attended noise monitoring must be conducted during the first occurrence of each noise-intensive activity at the nearest sensitive receiver."

Why it's missed: "First occurrence" of piling starts at 7am. The acoustic consultant isn't on site until 9am. Those first two hours of piling without monitoring are a breach.

10. Revegetation within 30 days of completion

The condition: "Revegetation of disturbed areas must commence within 30 days of completion of works in each zone."

Why it's missed: Works "complete" in a zone but the team moves on to the next zone. The 30-day clock is ticking but no one tracks zone completion dates separately from project completion.

The pattern

All 10 of these conditions share one characteristic: they're triggered by events, not by dates. You can't put them in a calendar. They require monitoring, awareness, and immediate response when the trigger occurs.

The solution isn't more diligent spreadsheet management — it's a system that understands condition types and prompts the right action at the right time.