The phone rings. It's Friday, 2 PM. There's been flooding in the council area. Roads are cut, drains have failed, a footbridge is damaged. You're told: "We need to get the main road open by Monday. Everything else is secondary." By 4 PM, you're standing in mud with the director, the shire engineer, and a contractor, looking at a road that's underwater.
Welcome to flood recovery. If you've done normal capital works before, forget most of what you know. The systems that work for planned projects break down almost immediately. The planning that protects you becomes irrelevant. The budgets become meaningless because you don't know the true scope yet. I've spent the last 15 months managing flood recovery at Indigo Shire Council, and I'm still learning what I didn't know before I started.
This is what nobody tells you about before you're in the mud.
How Flood Recovery Projects Are Different From Normal Capital Works
In normal capital works, you have a contract, a scope, a budget, and a timeline. The contractor bids based on known information. They plan their resources. You manage delivery against that plan.
In flood recovery, the scope isn't clear for days or weeks. You might think a road failure is just surface restoration, but when you excavate, you find the subgrade's undermined. You might think drainage repair means cleaning a pipe, but half the pipe's missing. Every time you dig deeper, the scope changes. Your original budget becomes a rough guess.
The contractor can't plan anything. They can't mobilize crews until they know what they're fixing. They can't price it accurately. So they either quote with a massive contingency (which kills you on budget), or they quote low and then claim variations constantly (which kills you on credibility and schedule).
Flood recovery also happens on someone else's timeline—weather, seasonal factors, and the political imperative to "get things back to normal fast." The council's receiving pressure from residents, media, and state government. That pressure lands on you. You get told to accelerate, cut corners, or "just approve the variation—we'll sort it later." You have to hold the line on standards while the whole system is pushing you to abandon them.
Add to that the fact that normal procurement can't happen. You can't run a six-week tender. You need contractors on-site within days. You're dealing with whoever's available, whether they're the best fit or not.
The Grant Application Process and Funding Reality
When flooding happens, councils access state or federal grants. In Victoria, that usually means applying to the Reconstruction Authority or accessing emergency funding through state government. The funding comes with conditions, reporting requirements, and rules about what work qualifies.
Here's what they don't tell you clearly: the grant covers "restoration to pre-existing condition." If a road was in poor condition before the flood, the grant covers fixing it to that poor condition, not upgrading it. If a resident wants their private driveway rebuilt to a higher standard, they're paying the difference. This creates immediate conflict with community expectations—residents assume the council is rebuilding everything better.
Also, all flood work is eligible for grants, but not all work is eligible for the same grant. Emergency repairs might be 100% funded under one program. Permanent repairs might be 80% funded under another, with council covering 20%. Preventative works might not be funded at all unless you can prove they're directly connected to preventing future flooding in the same area. You need someone (ideally not you) managing the grant categorization because it's complex and if you categorize work wrong, you don't get reimbursed.
Finally, grant acquittal is tedious. You need evidence for everything: invoices, photographs, variation approvals, payment records. If the grant auditor decides work wasn't eligible, you're covering the cost. You're not just delivering a project—you're managing your council's grant compliance simultaneously. It's a second full-time job.
Insurance Claims and the Politics of Timing
Some councils have insurance. Some don't. Either way, there's a claims process, and it runs parallel to reconstruction. The insurer wants evidence of damage. The council wants repairs approved and underway. These timelines conflict.
The insurer will send an assessor. The assessor will take weeks to assess everything. Meanwhile, you're under pressure to start repairs immediately. You either start repairs before the insurance assessment (risky—they might argue damage photos don't support your repair scope) or you wait for their assessment (costly—delays mean roads stay closed, frustration builds).
The compromise is to do emergency repairs immediately and document them meticulously. Take photos before work, during work, after work. Keep all receipts. Pay the contractor (council pays out of pocket initially). Then provide everything to the insurer and claim reimbursement. It's cash flow pressure, but it gets roads open.
What I've learned: get the insurance assessment started immediately. Don't wait. Also, loop the insurer in on your timeline—tell them you're starting repairs and when, so it's not a surprise. And document the absolute hell out of everything. Photographs aren't nice-to-have—they're essential for claiming reimbursement.
Scope Creep and the Pressure to Fix "While We're There"
This is where flood recovery becomes political. A road's flooded. You excavate and find the subgrade's failed. You repair the subgrade. The contractor says, "While we're here, should we fix that cracked asphalt on the shoulder?" The council says yes because "we're already there." The resident two hundred metres away says, "If you're fixing the road, what about our driveway that was damaged?" The councillor says, "Fix it—the insurance will cover it."
Before you know it, you've gone from repairing a flooded road to doing a full road upgrade, fixing private property, and resurfacing streets that were fine before the flood. The grant auditor later says half the work wasn't flood-related. Your budget's blown. Your timeline's extended. Your contractor's claiming they can't keep crews available for that many extra weeks.
You control scope creep by being very clear about what qualifies as flood recovery work. Flood damage. Direct consequence of flooding. That's it. Deferred maintenance that the flood happened to expose? Not flood recovery. Pre-existing problems that the flood revealed? Not flood recovery. You say this clearly, in writing, to council and community, before work starts. Otherwise, you're managing community expectations after the fact, which is losing battle.
I've learned: write a one-page scope document. What work will be done. What work won't be. Why. Send it to council, publish it on the website. When someone asks for extra work, you point to that document. "This is outside flood recovery scope. We can consider it for a separate project, but it's not part of this program." Hard boundary. Keeps you sane.
Managing Community Expectations When Assets Are Damaged
Flooding damages people's homes, assets, and sense of safety. They're scared, frustrated, and angry. They see the council as responsible for fixing everything. They don't distinguish between council assets and private assets. To them, the road's damaged—someone needs to fix everything that was affected.
Your job includes communicating what the council will and won't do, and why. This is politically dangerous. Say no, and you look unfeeling. But you have to say no to private property claims, deferred maintenance, and non-flood-related work.
I do this with dedicated community updates. Within 48 hours of flooding, we publish: what happened, what's damaged, what the council is doing, what residents need to do, what's covered by insurance, what isn't. We update it weekly. We set up a dedicated email for questions. We hold community meetings if the area's badly affected.
The tone matters. You're not being unsympathetic—you're being clear. "We understand the impact. Here's what we're doing. Here's what isn't our responsibility. Here's where you can get help." Clarity prevents worse political fallout than saying yes to everything and then delivering less.
Contractor Management When Urgency Pressures Standards
The contractor wants to work fast. The council wants it done fast. You want it done right. These create tension.
You're under pressure to approve variations immediately. The contractor says they need to shore something differently, or they need more equipment, or they've found more damage than expected. The impulse is to approve and move forward. The right response is to understand what they're asking for, why, and whether it's fair.
If a contractor's genuinely found more damage, document it with photos and measurements. Then assess if the variation's justified. If it is, approve it. But don't approve it because you're in a hurry. The difference between "I approved this because the scope was genuinely larger" and "I approved this because they asked and we needed to keep moving" becomes important if the project ends up over budget and the council asks why.
I also treat safety differently in flood recovery than in normal works. In normal projects, you monitor OHS carefully. In flood recovery, you're watching constantly because contractors are working in difficult, unstable conditions. You're also watching because they're under pressure and might skip safety steps to go faster. You don't let them. You shut sites down if conditions are unsafe. You refuse to certify work until it's done safely. Speed isn't worth someone getting hurt.
Documentation When Everything Is Moving Fast
This is the inverse of the pressure you feel. Everything's moving fast, so documentation is easy to skip. "We'll catch up on paperwork later." You won't. Later never comes. You end up with no record of decisions, variations, costs, or reasoning.
I double down on documentation in flood recovery. Every day site record. Every decision via email with summary. Every variation with photos, measurements, and cost justification. Every cost tracked separately as "emergency," "permanent," or "contested" so I can report accurately to the grant auditor.
It slows you down by maybe 10%. It saves you from 50% of disputes and 100% of grant compliance issues. Worth it.
Lessons from Indigo Shire (2023-2024)
At Indigo, the 2023 floods damaged 47 council assets: roads, drainage, bridges, and community facilities. The repair program ran 18 months. The initial damage assessment underestimated costs by 40%. Insurance took four months to assess. The state grant went through two program changes during execution. We had three different contractors because the first one couldn't mobilize. I managed 14 variations, eight of which were legitimate, four were scope creep we rejected, and two we approved despite concerns because council needed movement.
What I'd do differently: Start the insurance claim on day one, not week two. Push harder on community communications upfront—we had fewer complaints when we were clearer early. Demand better damage assessments before finalizing grant applications—our underestimation created budget stress. And push back harder on scope creep—we said yes to things we shouldn't have, and it cost money and time.
Practical Takeaways for Council Engineers
- Establish scope immediately. First 48 hours, draft a scope statement. What's in flood recovery. What isn't. Get council endorsement. Publish it. Reference it constantly.
- Start insurance claims on day one. Don't wait for full assessment. Start the process immediately. Document everything you do. Claim reimbursement methodically.
- Build in assessment time. Your initial damage estimate will be 20-40% under the true cost. Plan for that. Communicate it to council so budget pressure isn't a surprise.
- Prioritize by criticality, not politics. Fix roads that cut off communities first. Fix high-risk drainage next. Aesthetic damage last. This protects life and property. Politics will push you otherwise—resist it.
- Document every variation and decision. Photograph everything. Email summaries of site conversations. Keep cost records meticulously. Your documentation is your protection.
- Protect contractor OHS obsessively. Flood recovery conditions are dangerous. You shut sites down for unsafe work. Full stop. Faster delivery isn't worth injuries.
- Manage community expectations actively. Too many councils stay silent and then complain when community demands are unreasonable. Communicate proactively. Explain what will and won't happen.
- Don't approve variations because you're in a hurry. Understand them. Question them. Approve them because they're justified, not because speed is critical.
What It Teaches You About Your Craft
Flood recovery is brutal project management. Nothing goes to plan. Your assumptions are wrong almost immediately. You're managing conflicting pressures: speed, budget, community expectations, contractor constraints, grant requirements, and standards compliance.
What it teaches you is that documentation, clarity, and objectivity matter even more when things are chaotic. Because when everything's falling apart, your only protection is a clear record of why you made each decision. When the grant auditor questions work, you have evidence. When the community complains, you have your scope statement. When the contractor disputes a claim, you have photos and measurements.
It also teaches you that "normal" project delivery is a privilege. When you have time to plan, when you can run tenders properly, when you can understand scope fully before starting work—that's the good case. Don't take it for granted. And when floods come (they will), you'll know why those systems matter.
Flood recovery is hard. But it forces you to be a better project manager, because indecision or poor documentation becomes expensive quickly. You learn the habits that make projects resilient: documentation discipline, clear communication, careful variation management, objective decision-making. Those habits serve you in every project after.