Butte County, California, has experienced 12 federally declared disasters since 2017. That’s a pace of response that would break most governments.
Yet when the Park Fire swept through 671 square miles in 2024, Butte County’s team didn’t spiral. They spun up a disaster recovery permitting program in 44 days, down from five months just a few years earlier. And they did it with a two-person IT department.
In this episode of Civic Innovators, Patrick Miner, IT Manager for Butte County, walks us through how they got there: the decisions, the automation, and what it means to have a technology partner that shows up when it matters most.
In This Episode
Patrick has spent years building systems for a county that has no margin for error. Butte County’s disaster profile is staggering, from the Camp Fire in 2018, which destroyed 22,000 parcels and made global headlines, to the Park Fire in 2024, one of the largest in California history.
What makes Butte County’s story instructive isn’t just the scale of what they’ve survived. It’s that they’ve gotten better at it. Each disaster has sharpened their systems, tightened their timelines, and deepened their confidence that the technology will hold.
We Don’t Just Scale Up. We Scale Down.
Most conversations about government technology focus on scaling up: handling more permits, more applicants, more volume. Butte County thinks about it differently.
For Patrick, the hardest challenge isn’t managing a surge of post-disaster applications. It’s returning to normal. “The tendency after a disaster is to keep running at emergency speed even after the emergency passes,” he explains. “That’s exhausting for staff and confusing for residents.”
The systems Butte County has built with Accela are designed to flex in both directions: standing up quickly when disaster strikes and winding down cleanly when recovery is complete. That kind of operational symmetry is only possible with infrastructure built for consistency, not just capacity.
Three Words That Drive Every Technology Decision
When Patrick describes what Butte County looks for in any technology investment, he comes back to three words: flexibility, consistency, and transparency.
Flexibility means the system can adapt to the unknown, and disasters, by definition, are unknown. No two fires burn the same footprint. No two storms flood the same parcels. The technology has to handle variation without requiring a rebuild each time.
Consistency means every resident gets the same experience, regardless of which staff member they’re working with or which disaster they’re recovering from. It means inspectors and reviewers are executing a process that has been refined across 12 disaster responses.
Transparency means residents can see where their application stands. It means supervisors can see what their teams are working on. And it means, when FEMA comes to audit, Butte County has the documentation to show exactly what happened and why.
“Flexibility, consistency, transparency. If a system doesn’t deliver all three, it doesn’t belong in disaster recovery.”
The Wayne Gretzky Approach to Disaster Recovery
Patrick is fond of a particular analogy: Wayne Gretzky’s famous line about skating to where the puck is going, not where it’s been.
After the Camp Fire, Butte County had a choice. They could rebuild for the disaster they’d just experienced, or they could build for the next one. They chose the latter. That meant designing systems that didn’t just handle fire recovery, but could be repurposed quickly for flood response, earthquake damage, and debris removal.
It also meant making decisions about their technology partner before the next disaster hit. “You don’t want to be evaluating vendors in the middle of a crisis,” Patrick says. “You want to already know what your system can do and that the people behind it will pick up the phone.”
That forward-looking posture has paid off. When the Park Fire broke out in 2024, Butte County didn’t start from zero. They had templates, workflows, and institutional knowledge that compressed a five-month deployment into 44 days.
Automation That Does the Heavy Lifting
A two-person IT department can’t manually configure 22,000 parcels. That’s the mathematical reality behind Butte County’s automation strategy.
- Bulk record creation
When a disaster boundary is drawn, Accela allows Butte County to generate permit records in bulk for every affected parcel. What once required days of manual data entry now happens in hours. That head start matters enormously when residents are waiting to begin repairs. - Jurisdiction check automation
One of the most persistent pain points in disaster recovery permitting is misdirected applications: residents filing with the county when they should be filing with a city, or vice versa. Before Accela, Butte County saw 1,300 wrong-jurisdiction submissions. Since go-live on August 18, 2025, that number is zero. The system identifies the correct jurisdiction automatically and routes applications accordingly before they enter the queue. - Condition automation
Different parcels require different recovery conditions, including setbacks, inspections, and environmental reviews. Accela applies those conditions automatically based on parcel characteristics, eliminating the manual lookup process and ensuring that no condition is missed or inconsistently applied.
Taken together, these automations don’t just save time. They eliminate the categories of error that erode resident trust and create audit headaches down the road.
What a True Partnership Looks Like
Patrick is direct about the difference between a vendor and a partner: “A vendor sells you software. A partner answers the phone at 9 PM when your county is on fire.”
He’s experienced both. What distinguishes Accela, in his view, isn’t the feature list; it’s the relationship. When Butte County needed to move fast on the Park Fire response, Accela wasn’t waiting to be asked. They were already working through what needed to happen and flagging what Butte County might not have thought of yet.
That proactive posture is what Patrick means when he talks about partnership. It’s the difference between a product you use and infrastructure you can rely on.
“We’ve worked with vendors who disappear after the contract is signed. Accela shows up. That’s not something you can put in an RFP, but it’s everything when you’re in crisis.”
5 Key Lessons from Butte County
- Build for the next disaster, not the last one: Design your systems with flexibility for unknown future scenarios, not just the specific incident you just survived. Templates, workflows, and configurable boundaries will compound in value across every future response.
- Automation is a staffing strategy: For lean teams, automation is the only way to match the scale of a major disaster. Bulk record creation, automated routing, and condition logic are what make it possible to run disaster recovery with a small IT shop.
- Consistency protects everyone: Standardized processes protect residents from uneven service, protect staff from ad-hoc decision-making pressure, and protect the county in audits and FEMA reimbursement reviews. Inconsistency has real costs.
- Speed comes from preparation, not improvisation: Butte County’s 44-day deployment wasn’t a miracle. It was the result of years of deliberate system-building. The time to build that infrastructure is before the disaster, not during.
- Partnership is not a contract term: Evaluate your technology partners on how they behave when things go wrong, not just how they present when things are calm. The counties that recover fastest are the ones with partners who treat their success as a shared mission.
Looking Ahead
Butte County isn’t done building. Patrick describes ongoing work to tighten integration between Accela and other county systems, including GIS, records management, and payment processing, so that disaster recovery becomes less of a special mode and more of a seamless extension of how the county operates every day.
He’s also thinking about self-service. “Residents shouldn’t have to call us to know where their permit stands,” he says. “The goal is a system transparent enough that people can check in on their own.”
For a county that has been through 12 disasters in eight years, that kind of resident-facing transparency is a form of community resilience, one that helps people feel less alone in recovery.
Want to learn more about how your agency can benefit from a partnership like this? Request a demo today.
Explore More
Listen to the full episode and explore resources from this conversation:
Dive deeper into Butte County’s transformation journey and read the full transcript below to discover the specific strategies, challenges, and solutions that made their success possible.
Joe Morris: Welcome to Civic Innovators. I’m Joe Morris, Chief Innovation Officer with Government Technology and E.Republic. Joining me today is Noam Reininger, CEO of Accela. Noam, welcome back.
Noam Reininger: Thanks, Joe. Great to be back.
Joe: Today we’re joined by Patrick Miner, IT Manager for Butte County, California. Patrick, welcome to the show.
Patrick Miner: Thanks for having me. Happy to be here.
Joe: Patrick, Butte County has a remarkable story — 12 federally declared disasters since 2017. Can you start by giving us a sense of what that’s meant for your team?
Patrick: Yeah, it’s been a lot. When I tell people 12 federally declared disasters in eight years, they sometimes don’t believe me. But that’s the reality of operating in Northern California. We’ve had fires, floods, winter storms, earthquakes. Each one requires us to spin up a response — often while the previous one is still ongoing.
Patrick: The Camp Fire in 2018 was obviously the biggest. Over 22,000 parcels affected. The whole town of Paradise was essentially destroyed. That was the moment we realized we needed to fundamentally rethink how we approach disaster recovery permitting.
Noam: What was the process like before you had the systems you have now?
Patrick: Manual, slow, and inconsistent. After the Camp Fire, it took us about five months to get a functional disaster recovery permitting program up and running. That’s five months where residents couldn’t start rebuilding. Five months of people living in trailers or hotels while waiting for the system to catch up.
Patrick: We also had massive inconsistency problems. Different staff applying different standards. 1,300 applications going to the wrong jurisdiction. It was exactly what you don’t want when people are already dealing with the trauma of losing their homes.
Joe: So what changed?
Patrick: A few things. We decided to invest in building real infrastructure rather than just patching things together every time something happened. And we got serious about finding the right technology partner — not just the right software.
Patrick: We’d had experiences with vendors who were great at the sales process and then basically disappeared after contract signing. We needed someone who would actually be there when things got hard.
Noam: How do you evaluate for that during a procurement process? Partnership versus vendor behavior isn’t something that shows up in an RFP response.
Patrick: You’re right, it’s hard to evaluate in advance. What we tried to do was talk to other counties — specifically counties that had gone through difficult situations. Not just “what do you like about the product” but “what happened when something went wrong?” That tells you a lot more about a partner than any demo will.
Patrick: And then you find out pretty quickly once you’re working with them. The Park Fire was the real test for us. We went live with Accela on August 18, 2025. The Park Fire had started in July. So we were literally configuring the system in the middle of an active disaster response.
Joe: That’s a trial by fire, literally.
Patrick: Exactly. And what I can tell you is that from day one after go-live, we had zero wrong-jurisdiction submissions. Zero. The system automatically routes applications to the correct jurisdiction based on parcel data. That alone eliminated a problem we’d been dealing with for years.
Noam: Can you walk us through some of the specific automation that made the difference?
Patrick: Sure. There are three big ones. First is bulk record creation. When a disaster boundary is established, we can generate permit records for every affected parcel at once. With Camp Fire, that was 22,000 parcels. Doing that manually would have taken weeks. We can now do it in hours.
Patrick: Second is the jurisdiction routing I mentioned. Butte County has several incorporated cities — Chico, Oroville, Paradise — and sorting out which applications belong to the county versus the cities used to be a constant headache. Now it’s automatic.
Patrick: Third is condition automation. Different parcels have different requirements — environmental reviews, setback rules, inspection sequences. The system applies those conditions based on parcel characteristics without anyone having to look them up manually. That eliminates a major source of inconsistency and error.
Joe: You mentioned you went from five months to 44 days for the Park Fire response. How much of that is the technology versus the organizational knowledge you’d built up?
Patrick: Honestly, it’s both and you can’t really separate them. The technology captures the organizational knowledge. When we’ve figured out the right way to handle a particular situation, we encode that into the system. So by the time the next disaster hits, we’re not starting from scratch — we’re starting from where we left off.
Patrick: I think about the Wayne Gretzky quote — skate to where the puck is going, not where it’s been. We’re always trying to get ahead of the next disaster rather than just responding to the current one. That means investing in the infrastructure now, before we need it.
Noam: What about the ‘scaling down’ challenge? You mentioned that returning to normal operations can be as hard as standing up emergency operations.
Patrick: Yeah, this is something people don’t talk about enough. There’s a lot of focus on spinning up for a disaster. But if you stay in emergency mode too long, you burn out your staff and you create a confusing experience for residents who are at different stages of recovery.
Patrick: Having systems that can flex in both directions — scale up fast, wind down cleanly — that’s been really important for us. It’s part of why flexibility is one of the three words I come back to when evaluating technology.
Joe: You mentioned three words — flexibility, consistency, and transparency. Can you say more about transparency specifically?
Patrick: Transparency is about making sure everyone can see what’s happening. Residents need to know where their permit stands. Supervisors need to know what their teams are working on. When FEMA comes to audit our disaster reimbursement requests, we need to show them an audit trail of every decision that was made.
Patrick: One of our goals going forward is to give residents more self-service visibility. They shouldn’t have to call us to find out where they are in the process. That creates anxiety for them and volume for us. If people can check their status online, that’s a better experience for everyone.
Noam: What advice would you give to other IT managers in jurisdictions that are disaster-prone but haven’t yet built this kind of infrastructure?
