Configurable Workflows Without Consultants

No two municipalities run their permitting process the same way. One city routes all commercial permits through a fire review step that residential permits skip. Another requires a heritage review for anything in the downtown core. A third has a parallel engineering sign-off that happens concurrently with planning, not after it.

Most permitting software ignores this reality. It ships with a fixed workflow and sells customization as a services engagement. Need to add a step? That’s a change order. Need to rename a field? Scheduled for the next release.

The Consultant Trap

The consulting model isn’t just expensive — it creates dependency. Municipalities that rely on their vendor to make configuration changes aren’t in control of their own process. When a department reorganizes, when regulations change, when a new permit type is needed, they have to wait.

The result is that municipalities stop trying to make their software fit their process and start bending their process to fit their software. That’s backwards.

What Real Configurability Looks Like

There’s a spectrum between “fixed workflow” and “build your own from scratch.” The right answer sits in the middle: a visual workflow designer that’s powerful enough to handle real complexity, but approachable enough that a department manager can use it without a developer.

In Civaptic, that means a drag-and-drop workflow editor where you can:

• Define step types: user action, system action, wait, parallel branch, or sequential sequence
• Set conditional logic: route to different steps based on permit type, construction value, zone, or any other field
• Configure SLA targets per step with automatic escalation when they’re breached
• Assign tasks to roles, not just individuals, so coverage survives staff changes

Every permit type gets its own workflow. Every municipality gets its own set of permit types. Clone a workflow from a neighboring municipality to get started, then adapt it to how you actually work.

Configuration vs. Customization

The distinction matters. Customization is code changes — it takes time, costs money, and creates a fork of the software that’s harder to update. Configuration is data — it happens in the UI, takes minutes, and doesn’t require a vendor relationship.

Civaptic is built so that everything a municipality needs to adapt for their jurisdiction — permit types, workflows, fee schedules, email templates, field labels, inspection checklists — is configuration. Not one of those things requires opening a ticket.

That’s not an accident. It’s the entire design philosophy.