Run permits, notices and appeals without the paper chase
Residents apply, pay and appeal in one place. Officers get a single queue with the evidence already attached, and the finance and case systems update themselves.
- Best for
- Councils and parking operators
- Deployment
- Self-hosted or cloud, UK data
- Works with
- Stripe, your case and finance systems
Permits and appeals move at the speed of the inbox
Applications arrive by form, email and phone, then travel between a spreadsheet, the payment provider and the back office, with somebody retyping at every hop.
- Rekeying. The same registration, address and dates are typed into three systems.
- Slow appeals. Cases wait while evidence is gathered from different places by hand.
- Payments adrift. Money lands in one system while the case sits open in another.
- Thin audit trail. When a decision is challenged, the reasoning is spread across mailboxes.
One flow, from application to decision
Publish the form, take the fee, apply your rules, and put a person in the loop only where judgement is actually needed.
Forms residents can actually use
Accessible, multi-page forms with conditional questions, file uploads and photo evidence. Welsh and English from the same form where you need both.
The fee taken in the form
Collect payment with Stripe as part of the same submission. The flow only continues once the payment has cleared, so nothing is issued unpaid.
Decisions with a person in the loop
Route an appeal to the officer who owns it with the evidence attached, then record the decision, the reason and who made it.
What a permit application looks like in Flomation
A resident applies and pays, the checks run themselves, and an officer only sees the cases that need a human answer.
- TriggerOnline applicationResident submits and pays
- ConditionalEligibility checksAddress, vehicle and entitlement rules
- HumanOfficer decisionOnly where a judgement is needed
- OutputPermit issuedCase, finance and resident all updated
Shorter queues, cleaner records
Give the paperwork somewhere else to go
Start with one form and one flow, keep the data in your own environment, and add the next process when the first one is quietly running itself.
Get started