Process management and software for local government.
A municipality's work is not lost in committee chambers — it is lost in the dozens of parallel streams running beside them: a citizen complaint waiting in someone's tray, a business licence stalled between departments, a field crew that never received the work order, a council decision that was never formally recorded. Tenderely BPM connects those streams into a single, auditable flow without code, and it adapts to how your administration already works rather than the other way round.
What does a municipality repeat every week?
01
Citizen requests and complaints
Residents submit requests about roads, lighting, noise, waste and dozens of other matters. Without a structured intake, the same complaint can arrive by phone, counter visit and e-mail simultaneously and never be linked.
02
Business licence approvals
Opening a business requires sign-off from planning, fire, environmental health and treasury departments in sequence. Each handoff between departments is a point where the file can go quiet for weeks.
03
Field work orders
Public works, sanitation and parks crews need to know what to do, where and by when. A verbal instruction or a phone call leaves no record of what was assigned, started or finished.
04
Municipal police inspection reports
Inspectors visit premises, record findings and issue notices. If the report stays on paper, following up on an outstanding notice depends entirely on someone's memory.
05
Council and committee session records
Sessions produce agendas, minutes and formal decisions. When these live in separate word-processed files, finding a specific decision later means searching through folders by date and hoping the filename is helpful.
06
Municipal property and lease management
Municipal properties are leased to businesses and individuals under terms that change over time. Tracking lease periods, rent revisions and outstanding payments is work that repeats every month.
Where does this break down today?
Citizen complaints lose their thread
A complaint registered at the counter, forwarded by e-mail to a department and then followed up by phone becomes three separate events with no shared record. The resident calls again because they never heard back, and nobody can tell them what happened.
Licence applications wait between departments
Each department adds its own condition and passes the file on. Without a shared status, the applicant has no idea where the application is, and the clerk at the counter cannot answer either.
Field assignments are unverifiable
A crew supervisor told a team to fix a pothole on Tuesday. By Thursday, was it done? Nobody knows unless the supervisor calls the crew, and even then there is no timestamped record that anything happened.
Decisions are hard to retrieve
Council voted to approve a lease, encumber a property or accept a tender. Six months later that decision is needed for a legal query, and the answer involves searching through printed minutes.
What changes with Tenderely BPM
01
Citizens submit without a counter visit
A public form published as a link or embedded on your website lets residents submit requests and complaints from any device at any time. The submission becomes a structured record from the first moment.
02
Multi-department approvals route themselves
Conditional routing and parallel approval steps are configured without code. A business licence application moves to the next department only when the previous one has completed its review, and a waiting step reminds the responsible officer when the deadline passes.
03
Work orders reach crews on mobile
The same flow runs in the iOS and Android apps, so a field crew receives the assignment, updates its status and closes it from the site. The record captures when each action happened.
04
Inspection reports are structured from the start
An inspector fills in a form on their phone rather than a paper sheet. The findings, photographs and any notices issued attach to the same record, and follow-up actions can be tracked until they are resolved.
05
Council decisions are searchable and auditable
Each session, its agenda items and the resulting decisions are stored as structured records with an audit history. Finding a decision later is a search, not an archive expedition.
06
Tenderely makes the whole flow visible
Open complaints by neighbourhood, licence applications awaiting sign-off, overdue work orders, upcoming lease renewals — these stop being questions you investigate and become numbers that are simply there on a dashboard.
FAQ
Can residents submit requests without creating an account?
+
Yes. A public form published as a link requires no login from the person submitting it. If you want residents to be able to track their own request afterwards, they can be connected as external users who see only their own submissions — never internal data.
Can we route requests to different departments based on the type of complaint?
+
Yes. Conditional branching in the flow means a road repair request goes to public works while a noise complaint goes to municipal police. The routing is configured without code and can be changed at any time without restarting live applications.
How do inspectors and field crews work when there is no internet connection?
+
The iOS and Android apps are the same interface as the web version, so a crew or inspector who has a phone or tablet can open an assignment, fill in a report and attach photos. What they enter syncs when connectivity is restored.
Who can see which records?
+
Role- and unit-based permissions decide who sees what. A sanitation crew sees its own work orders. A licensing clerk sees only licence applications. Senior management and elected officials can be given dashboard access without access to individual case details. Field-level permissions mean a sensitive column can be hidden from a specific role.
Can we start with one process and add others later?
+
Yes. The starter set installs with an initial set of flows ready to adjust and publish, but each process is independent. You can go live with citizen requests first, then add business licences, then work orders, without each change affecting the others.