Operational systems for councils, ministries and public entities
Public entities are judged on things that happen away from a desk: whether the refuse truck arrived, whether the clinic opened, whether the rate paid at a satellite office reached the account. We use the cameras, gate hardware, vehicles, scanners and phones a council, ministry or parastatal already owns to turn those events into records the same day, so a ratepayer, a committee and an auditor are answered from one set of evidence.
Own-source revenue, captured where it is collected
Rates, licences, market and rank fees, parking and water are collected at many small points, often in cash and far from the finance office. Handheld capture with a printed or messaged receipt, plate recognition at controlled entrances and camera evidence at weighbridges and landfill gates create a record as money or material changes hands. Reconciling collections, banking and the ledger becomes a daily exception list rather than an argument at year end.
Attendance and payroll across scattered establishments
A local authority runs clinics, schools, depots, pump stations and markets that no payroll clerk can physically visit. Card or facial recognition readers at each establishment record attendance per person against the post they are appointed to, so a name being paid where nobody has seen them is visible inside the same pay period. Allowance, shift and standby claims follow rules your human resources committee approves.
Plant, fleet and fuel that can be accounted for
Graders, refuse compactors, water bowsers, ambulances and pool vehicles are the assets most often questioned and least often evidenced. Vehicle tracking gives route, standing time and out-of-hours movement, while Bluetooth Low Energy tags — small battery-powered markers read by fixed receivers — keep generators, pumps and tools findable between depot, store and site. Fuel draws are matched to a vehicle, an operator and a work order.
Correspondence, files and the paperwork of accountability
Public administration runs on documents that move: applications, minutes, requisitions, tender submissions, invoices, and the file that disappears between two offices. We scan and read those where they enter, attach them to the matter or supplier they belong to, and route them with a record of who held them and for how long. A request for the history of a decision is retrieved rather than reconstructed.
Citizen enquiries on the channel people already use
Most enquiries are a small set of questions asked over and over: what do I owe, has my payment reflected, when is refuse collected in my ward, where is my application. An AI agent on WhatsApp answers those from your own verified records and hands over to an officer the moment it is asked something it cannot confirm. Disputes, waivers and enforcement stay with a person.
Procurement, sovereignty and the rules you work under
Public buyers cannot adopt technology the way a private firm can: competitive procurement, an annual budget cycle, a large legacy estate and a duty of care over citizen data all bind the decision. We scope work to fit a single vote or a phased tender, run systems in your environment or a dedicated tenant in a location you can point to, and document what data is held and who may view it.
What it covers
Evidence at the point of collection
Receipts, images, weights and plate reads captured where the transaction happens, so banking and the ledger are checked against a record rather than a recollection.
One attendance record per establishment
Clinics, schools, depots and satellite offices feed one payroll input, with exceptions raised while the pay period is still open.
Plant and fleet visibility
Live position, standing time and utilisation for council and ministry vehicles, plus tags on equipment that migrates between depots.
Ward-level service proof
Refuse rounds, water deliveries, repairs and inspections logged with time, location and photograph, so a councillor's question is answered from the round record.
Works through an outage
Processing runs on a small computer at the site, so a fibre cut or a load shedding window stops neither capture nor recording. Everything reconciles when the link returns.
Audit trail by default
Every automated action records what it saw, which rule applied and who approved it, which is what an internal auditor asks for first.
How it works
Site assessment (week 0)
We walk the operation with your finance, engineering, human resources and internal audit people: the counters, the depot, the gate, the stores. We document the cameras, readers, trackers, billing and payroll systems in place, and agree the one bottleneck worth attacking first.
Integration (weeks 1 to 3)
We connect to what you already run rather than replacing it, and the system observes only. It records what it would have flagged and calculated while the current process continues untouched, which gives procurement and audit something concrete to review.
Rules and guardrails (week 4)
Access rules, allowance and overtime logic, revenue variance thresholds and escalation paths are agreed, then tested against your own historical records before anything is permitted to act.
Go live and optimise (week 5 onward)
The system takes the workflow and we review weekly at first, removing alerts not worth an officer's interruption. A first system is typically running in about four to six weeks.
Questions buyers ask
How does this fit competitive public procurement?
We expect to be procured properly. The assessment output is written so it can become a specification a competing supplier could also bid against, and scopes stay small enough to sit inside one budget line and one financial year. A narrow phase that survives scrutiny beats a programme that stalls in committee.
Where does citizen and employee data live?
In your environment or a tenant dedicated to you, in a location you know and can state publicly. Access is by role, retention is written into the contract, and we document what personal data each part of the system holds. Zimbabwe's data protection law and its regional equivalents place that duty on you as the controller.
Our district offices have poor connectivity. Does that rule us out, and do we replace our existing billing or payroll system?
No. Capture devices and on-site computers hold data locally and synchronise when the link returns, so an office records normally through an outage. Your billing, accounting and payroll systems stay where they are; we deliver captured events into them through an API, a database view or a scheduled file exchange.
Will this replace staff?
It is not sold on that basis. What it removes is transcription, reconciliation and chasing, the work currently done badly because there is too much of it. Decisions about people, money and enforcement stay with your officers, and anything ambiguous escalates to a person.
Can we start with one department rather than the whole entity?
That is how nearly every engagement starts. One revenue point, one depot or one establishment with two or three rules gives you something working to evaluate and something real to budget from. Extending later means adding readers and cameras to a platform already running.
Start with one depot, one counter or one payroll
Book a platform briefing: a 15-minute technical discussion with an engineer, not a sales call. Tell us the service or revenue line you cannot currently evidence, and we will say honestly what your existing cameras, readers and systems could support. Harare-based, working across Zimbabwe and the region. Email sales@eigenstatesystems.com or WhatsApp +263 77 636 6999.