Permit management covers two quite different jobs. Some teams process applications from the public, councils handling building, planning, licensing and parking permits. Others control high-risk work on their own sites, manufacturers, utilities and contractors issuing permits to work for hot work, confined spaces and electrical isolation. Most off-the-shelf software is built firmly for one or the other, and assumes you will adopt its way of working.
We build permit systems that fit how your permits actually move, whether that is an application crossing three council departments or a permit to work that cannot be issued until isolations are signed off. You pay once, you own the code, and you are not locked into per-user fees that climb every renewal.
We are a London-based development team and we build these systems from scratch for UK organisations.
Where off-the-shelf permit software falls short
Generic permit platforms tend to disappoint in predictable ways, and the research backs this up across both the municipal and safety-critical markets:
- Workflows are fixed. Most SaaS tools assume a simple linear chain: submit, review, approve, issue. Real councils need parallel approvals across building control, environmental health and highways, conditional escalations, and interdepartmental handoffs. When the software cannot model that, staff rebuild the process in spreadsheets and email.
- Permit-to-work tools digitise the form but do not enforce the process. Forms-based apps let someone issue a permit before isolations are confirmed or competency is checked. For hot work, confined space or energy isolation, that is the gap that matters most.
- Notification controls are crude. A common complaint is alert overload with no granular control, so staff disable notifications entirely and then miss the ones that count.
- Historical visibility is poor. Seeing every past permit for a single property or site often means searching several systems, and institutional knowledge gets lost.
- Pricing punishes growth. Per-user, per-module and per-site licensing means costs rise as you add inspectors, permit types or locations, regardless of whether the value rises with them.
- Integrations are shallow. GIS, finance and planning connectors are often incomplete or slow, so manual reconciliation continues and the automation never really arrives.
- Upgrades are disruptive. Forced vendor upgrades break workflows and introduce new bugs on someone else’s schedule, not yours.
The usual result is workarounds stacked on workarounds, and compliance that is harder to evidence than it should be.
What we build instead
We spend the first few weeks mapping how permits actually move through your organisation before any code is written, the permit types you handle, who reviews and approves, what conditions get attached, and where things currently stall. The system then matches that process rather than imposing a generic one.
The build is modular, so you start with the core and add permit types, integrations or reporting later without replacing anything. UK GDPR handling and the relevant compliance requirements are designed in from the start, not bolted on. And because you own the system outright, there are no per-user fees, no forced upgrades, and no renegotiation when you want a change.
Features and modules
Every system is scoped to the organisation, but most builds draw from the same set of modules.
For councils and licensing teams:
- An application portal for citizens, contractors and agents, with status tracking, document upload and online fee payment
- Application intake with completeness checks, automatic fee calculation and rejection handling
- Workflow routing that assigns reviewers, approvers and inspectors by permit type, location or complexity, including parallel and conditional routes
- Plan review with mark-up and collaboration tools
- Permit issuance with conditions attached, expiry dates and renewal tracking
- Inspection scheduling with a mobile app for field inspectors, pass and fail recording, photos and re-inspection workflows
- A central dashboard showing every permit, upcoming renewals and approaching deadlines, plus reporting on cycle time, approval bottlenecks and fee revenue
- Full permit history for any property, so amendments and renewals link back to the original
For permit-to-work and safety-critical operations:
- Control-of-work enforcement: a permit cannot be issued until isolations are confirmed, RAMS are attached and competency is verified
- Isolation checklists covering electrical, pneumatic, hydraulic and other energy sources, with sign-off recorded
- Concurrent-work conflict detection, so the system flags activities that cannot safely run at the same time
- Competency and training validation before a permit is granted, with links to training records
- Contractor management, including verification of training and insurance for external parties on site
- Incident linking, so a near-miss or accident can be traced back to its associated permit for root-cause analysis
Across both, every build includes a tamper-proof audit log recording who did what, when, with before-and-after values, role-based permissions, and automatic alerts before renewals, inspections or condition deadlines fall due.
How the project works
We break every project into four stages:
-
Discovery and planning (2 to 4 weeks) — We map how permits move through the business, agree the permit types and workflows for the first release, and identify the integrations and data you need to migrate.
-
Development (8 to 12 weeks for an MVP) — Our UK developers build in two-week sprints with regular check-ins, so feedback is incorporated as we go rather than at the end.
-
Testing and deployment (2 to 4 weeks) — We run user acceptance testing with your permit officers, reviewers and inspectors, test edge cases, and roll out with as little disruption as possible. Where legacy data is messy, we plan a cleaning and parallel-run period rather than a risky one-shot cutover.
-
Training and support (ongoing) — We train each role on what they actually use and stay on for support after launch.
A focused first release usually covers one or two permit types, a clear approval workflow, mobile inspection capture, online payment and basic reporting. GIS integration, multiple permit types, conditional routing, finance sync and full permit-to-work logic are natural Phase 2 work, added once the core is live and proven.
Cost and ownership
Custom development costs more upfront than a SaaS subscription. That is the honest trade-off. What you avoid is per-user pricing that climbs as your team grows, per-module fees as your needs widen, forced upgrades you did not ask for, and a vendor changing terms at renewal.
The comparison is best made over five to seven years. SaaS costs keep accruing and switching away is expensive, because it means re-migrating data and re-integrating every downstream system. A custom build is a one-off cost plus a predictable support budget, and for mid-size councils and multi-site operators the cumulative figures often end up close, with the difference being that you own the code and the IP.
Every project is different, so we will not put a number on this page. Book a free consultation and we will give you an accurate range once we understand your scope.
Where bespoke makes sense, and where it does not
We will be straight about this. If you are a single-location operation with standard workflows, no unusual integrations and a tight budget, an off-the-shelf platform may be the sensible choice, and we will tell you so.
Bespoke earns its place when:
- Your approval workflows are genuinely non-standard, with multi-department or conditional routing that generic tools cannot model
- You run safety-critical permit-to-work and need enforced control-of-work, not just digital forms
- You need deep, reliable integration with existing GIS, finance, planning or incident systems
- Per-user or per-module SaaS pricing has become unsustainable as you have grown
- You are planning a deployment of five years or more, where vendor lock-in and cumulative fees outweigh the upfront cost
Common trigger points we hear: a failed audit or an incident that exposed weak records, growth to multiple sites that broke the spreadsheets, a regulator or council mandate for digital and mobile-capable records, or a renewal quote that suddenly looked very different from the last one.
Industries we work with
Permits look different depending on what you do. A few examples:
- Local authorities — Building and planning permits, licensing for food, alcohol and housing, code enforcement, environmental health, and parking and resident permit schemes
- Construction — Permits to work for hot work, confined space, work at height and excavation, plus environmental and traffic management approvals across a project
- Manufacturing — Permit-to-work for high-risk maintenance, energy isolation, hazardous processes and contractor work, with competency verification
- Utilities — Excavation near buried services, maintenance permits and high-risk work in hazardous areas
- Healthcare — Permits to work for maintenance in clinical areas, contractor and visitor permits, and equipment installation sign-off
- Waste and environmental — Waste carrier registration, garden waste schemes and hazardous waste permitting
- Events — Film and special-event permits requiring road closures, multi-department approvals and crowd management
Common Questions About Custom Permit Management Systems
How does a custom permit system compare on cost to SaaS?
A custom build costs more upfront, but the comparison usually turns over a 5-year window. SaaS permit platforms charge per user, per module or per site, so costs climb as your team or permit volume grows, and renewals are out of your control. A bespoke system is a one-off build plus a predictable support budget. For a mid-size council or a multi-site operator, the cumulative figures often land close by year five, with the difference being that you own the system and the IP. We will give you an honest range once we understand your scope.
What's the typical development timeline?
A focused MVP, covering one or two permit types, a linear approval workflow, mobile inspection capture and online payment, usually takes 8 to 12 weeks. A wider build with multiple permit types, conditional routing, GIS or finance integration and a proper audit trail runs 16 to 20 weeks. We get core functionality live early, then add modules in phases rather than waiting on one large release.
Can you build proper permit-to-work controls, not just digital forms?
Yes, and this is a common reason teams come to us. Many off-the-shelf tools digitise the permit form but do not enforce the process, so staff can issue a permit before isolations are confirmed or before competency is checked. We build control-of-work logic that holds a permit until its preconditions are met: isolations signed off, RAMS attached, training verified, and concurrent high-risk work checked for conflicts. That matters for HSE HSG250 expectations and for audits.
Can you integrate with our existing systems?
Yes. Common integrations include GIS and mapping for property and location data, finance systems such as Xero or Sage for fee reconciliation, planning and building control records, payment processors for online fees, and document storage. For safety-critical permit-to-work, we also connect to RAMS, training and competency records, and incident management. We build these as direct API integrations rather than brittle adapters, so data flows without manual re-keying.
What about data security and compliance?
Permit data includes personal information about applicants and citizens, so every build includes UK GDPR handling: encrypted storage, role-based access, configurable data retention and support for subject access and erasure requests. We host in UK data centres where data residency matters, which is the norm for council work. For permit-to-work, we build tamper-proof audit logs that record who did what, when, with before-and-after values, so your records stand up to an HSE or internal audit.
Do you provide training and ongoing support?
Yes. We run role-specific training, since a permit officer, a field inspector and a finance administrator each use the system differently, and we provide written guides and short videos. After launch we offer support plans covering fixes, hosting and a budget for changes. Because you own the code, new permit types or workflow changes are straightforward additions, not a contract renegotiation.