Municipal operations
Procedures that run the same way every time
Leave requests, purchase approvals, internal referrals and departmental sign-offs, configured rather than remembered.
Why it matters
Procedures that survive the person who knows them
Every administration has procedures nobody has written down. They work until the person who knows them is away. Turning them into configured workflows makes the steps, the approvers, the deadlines and the substitutes explicit — and makes the whole thing auditable.
The steps, written down
What was custom becomes a configured sequence.
Approvers and substitutes
Absence stops being the reason a file waits.
Auditable end to end
Every step leaves a record of who did what, and when.
What can be automated
The parts of a procedure people improvise
Approvals, referrals, notifications, documents, deadlines and cover.
Approvals
Sequential, parallel, conditional or value-based, with delegation built in.
Internal referrals
A file passed between departments with the reason and the deadline attached.
Notifications
Who is told what, through which channel, and when it escalates.
Document generation
Decisions, letters and certificates produced from templates and data.
Deadlines
Terms counted, suspended and restarted by rule rather than by hand.
Substitution
Absence rules that keep the procedure moving without informal hand-offs.
How it works
Described, attached, run, improved
The department that owns the procedure is the one that changes it.
01
Describe the procedure
The department that owns the procedure maps the steps, the roles and the conditions — in a visual editor, not in code.
02
Attach it to a case type
The workflow becomes the behaviour of that case, service or document type everywhere it is used.
03
Run it
The system assigns, reminds, escalates and records, so the state of the procedure is never a matter of opinion.
04
Improve it
Bottlenecks show up as measurements, and a new version can be published without disturbing files in flight.
Outcomes
What changes
Procedures that outlive people, and bottlenecks that are measured rather than argued about.
Procedures that outlive people
Holidays and staff changes stop breaking the process.
Visible bottlenecks
Time is measured per step, so the slow one is identified rather than guessed.
Audit without reconstruction
Who approved what, when, is already recorded.
Configured per administration
What is configured
- The procedures modelled, and who owns each
- Roles, approval limits and delegation rules
- Conditions, branches and parallel steps
- Deadlines, suspensions and escalations
- Templates for the documents produced
- Substitution and absence handling
- Versioning, and what happens to files in flight
- The measurements published to management
Connected to
The rest of the platform
- The platform workflow engine, which executes what is configured
- Case management, document registry and HR
- The organisational structure, for roles and hierarchy
- Reporting and internal audit
One procedure
Pick the one that breaks when somebody is on leave.
We model it with the department that owns it and run it the same afternoon.