For every local authority · Public services
How one secure system lets the council serve every citizen — at the counter, at home, and in the field.
The old way
Before: every service meant standing in line, filling forms by hand, and coming back tomorrow.
A number written on paper, and a whole morning lost waiting.
Files that could go missing, and reports that took days to prepare.
No way to know where an application was, or who was handling it.
Kattankudy Urban Council replaced all of this with one secure system — Smart City Kattankudy.
One system
Two faces, one system: a citizen app for the public and an admin console for staff — both working in all three languages.
Whatever a citizen pays, applies for, or reports reaches the same protected record — with the time and the officer's name attached.
For citizens
What a citizen can do today — not a plan for tomorrow.
At the counter or online — receipt at once, arrears always visible.
A numbered token from the kiosk; the screen shows who is next.
Report it from home and follow it to the end — the system watches the deadline.
A council card with a QR code any officer can verify by scanning.
Certificates and permits, step by step, in your own language.
At the counter
The queue board shows who is next; the officer sees the whole citizen on one screen.
Payment to numbered receipt in one step — a receipt can never be issued twice.
Cancelling a receipt needs a second officer's approval and a written reason.
Staff attendance comes from signed-in activity — not from paper registers.
In the field
Waste rounds and inspections carry proof the council can stand behind.
The collector scans a QR code at the spot itself — time and place are captured.
Fees follow the zone and the real collection record — not an estimate.
The same scan verifies a council ID card — no forgeries, no mistaken identity.
Supervisors see plan versus actual on a live dashboard — collection is no longer taken on trust.
Module tour · the full list
Everything the platform runs, grouped the way the tour walks through it — from the morning sign-in to the dashboards leadership reads.
Where the day begins
Every officer signs in personally. Attendance is marked from that sign-in, leave is handled in the same place, and every action afterwards carries that officer's name.
Each officer signs in with their own account — the door to every module.
Presence is recorded from the officer's own signed-in activity — no paper register.
Leave requests, approvals, and year-end carryover all live in the system.
The duty board shows who is present and who is on leave — and feeds payroll.
Payroll reads the same record — salary follows attendance, not paperwork.
Module tour · 1 of 8
Six modules that say who is who — citizen, officer, and council.
One numbered record per citizen — the spine every module keys to. Duplicate identity numbers are caught; the record follows the person.
A council identity card with a QR any officer can scan to verify — reissue needs a reason and a PIN.
Certificates and permits step by step in the citizen's own language — with status tracking until delivery.
Who may see, approve, or cancel what — granted per role, revocable anywhere, every grant recorded.
Officers pick people by name or number from the register — identity numbers are never hand-typed, so the wrong person is never recorded.
The final step that makes the new register the single source of truth — built, tested, switched on by a deliberate step.
Module tour · 2 of 8
From the street address to the invoice on the counter — the council's revenue base, kept accurate.
Every property with its street, ward, and zone; owners and tenants over time; boundaries drawn on the map.
Valuations become invoices in all three languages; a bill, once issued, is a frozen snapshot — it never silently changes.
Renewals with automatic reminders and a year-end sweep; an open court case blocks a renewal until it is settled.
Citizens see exactly what they owe before asking for anything new — arrears are explained and gated, not discovered later.
Module tour · 3 of 8
Collecting, receipting, and refunding — under two-person rules that make misuse hard.
Day open and close, numbered receipts with gap detection, and voids that need a second officer plus a PIN.
Credit and refunds held safely; charges deduct exactly once — never twice, even when screens double-tap.
Discounts and waivers follow an approval workflow, expire on schedule, and keep their full history.
One payment cannot produce two receipts — the same rule guards every rupee that moves through the counter.
Online payments · IPG
Online card payments arrive through the bank's Internet Payment Gateway — collected in rupees, confirmed by the bank, receipted by the system.
Card details never touch the council's system — the bank's page collects them. Reversals follow the same two-officer rule as the counter.
Module tour · 4 of 8
Six modules that carry a citizen's request from first contact to finished delivery.
Reported from home or taken at the counter with a token; deadlines are watched, escalations are automatic, and the citizen rates the result.
A daybook for incoming letters; files move officer to officer with every hop recorded; confidential files stay with the Secretary's office; stuck files are flagged.
Kiosk token issue, a live queue board for the hall, no-show sweeps, and a service category for each counter.
Book the community hall or grounds — slots are reserved the instant they are taken, deposits tracked, approvals routed.
Notices and receipts record viewed, acknowledged, and downloaded per citizen — proof that the message landed.
News, service tiles, and quick payments — the council's front door on the same platform, in all three languages.
Citizen services · Public library
Membership, catalogue, lending and returns — one more council service on the same record, the same receipts, the same reminders.
Find a title from home in the citizen app — by name, author or subject, in the reader's own language.
A library membership tied to the citizen record; issue and return recorded by scan, not by register book.
Return dates tracked by the system; reminders ride Bcozap, so a nudge costs the council nothing.
Late fees join the same numbered-receipt stream as every other council charge — one ledger, no loose cash.
Council messaging · Bcozap
Paying per message was eating the council's budget. So Winsoftmax built its own messenger — Bcozap, Android first — and every notification now rides that channel, free.
Notifications travel through Bcozap, Winsoftmax's own Android app — no per-message charge, ever.
Deadline reminders, receipt alerts, approval notices — delivered the moment they happen, at zero cost.
Messages never pass through a foreign company's servers — citizen conversations stay on the platform that runs the council.
Paid text messages are reserved for sign-in security; everything else rides Bcozap's free channel.
Built for Android first; other platforms follow. The messaging bill falls while delivery becomes faster and traceable.
Council messaging · how it works
From the event to the pocket, every hop stays on Bcozap — Winsoftmax's own messenger.
Billed per message, in US dollars — a steady foreign-currency drain on the council's budget.
Citizen conversations pass through a foreign company's servers — privacy handed away with every message.
Zero per-message cost — Winsoftmax's own channel; no USD outflow, no per-message bills.
Privacy by design — messages stay on the platform that runs the council, not on a foreign company's servers.
Module tour · 5 of 8
The council's own administration — staff, salaries, cases, and correspondence — runs in the same system.
One record per officer: attendance from sign-in, leave with year-end carryover, service movements, and the duty board.
Salary runs computed and checked by two people; payslips, loans against salary, and corrections that keep the originals.
A case register linked to properties and licences, hearing reminders, and enforcement that holds renewals until a case closes.
A task registry for the Secretary's office, and council news that passes draft → review → publish before it is public.
Module tour · 6 of 8
Inventory, permits, and the council's media — each with its own record and approval trail.
Everything the council owns — stock and equipment issued, transferred, or written off only with recorded approvals; dashboards show what exists and where.
Applications routed through the UDA and HNDI workflow with a two-invoice structure — built and tested, awaiting switch-on.
The council's photos and files, staff badges, and the org tree that routes every assignment and approval.
Module tour · 7 of 8
Waste collection, zones, and collection agents — with proof the council can stand behind.
Vehicles, schedules, and proof of every stop — scanned, timed, acknowledged — with waste-fee billing and a monitoring dashboard.
The zone map that decides collection routes and fees — one zone per property, maintained on the map.
Agents collect on the council's behalf — a PIN at every collection, lockout on failures, daily caps, and an end-of-day digest.
The engine that carried every legacy record into the new system — nothing lost, identity numbers preserved.
Module tour · 8 of 8
Six foundations every module shares — the reasons the record can be trusted.
Every council's records live in their own space — never mixed, so any council can join without a rebuild.
Every action lands in a permanent chain — quiet edits are detected, not assumed away.
A copy of every record is made automatically each night — and the restore path is tested, not assumed.
Records carry their effective time — a report can be re-run exactly as it stood on any past date.
An encrypted channel for every request, and sensitive actions ask for the PIN a second time.
Every module reports into dashboards and charts — the numbers leaders see are the numbers the system holds.
Two polish works are in progress — moving older screens to the new message style, and routine platform upkeep. Neither touches service.
Reporting
Dashboards, charts, and statements — drawn live from the records, for any date, ready to print.
Sample view — live figures come from the council's own records.
Dashboards for every module — waste, complaints, payments, licences.
Statements per citizen and per ward — what was paid, what is due.
Any-date reports — history re-run exactly as it stood.
Print-ready exports for council meetings and ministry returns.
Trust
The rules that protect the council's money and the citizen's data are built into the system itself.
One payment cannot produce two receipts — the system will not allow it.
Every action — including corrections — enters a permanent record that cannot be altered without detection.
A safety copy of every record is made automatically each night.
Every council's records are kept separately and securely — never mixed with another's.
By the numbers
The platform is already in daily service at Kattankudy Urban Council.
Every change to the system passes a second reviewer before it ships — the same two-person principle that guards the council's money.
Working today
For anyone who has seen computer projects that existed only as plans, this one is past that risk.
33 of 37 modules are already in daily service — the rest are built and tested.
Every change passes a second, independent reviewer before it ships.
Nothing switches on by accident — final items go live only through a deliberate, supervised step.
Nightly backups — and the restore procedure is tested, not assumed.
What comes next
Each one extends machinery that already exists and is already audited.
Vouchers, payments, and trial balance inside the same protected system — ready for audit at any date.
Helps draft letters and summarise files — and can never learn from public data.
The system itself decides whose records need updating next — and drafts the notice to send.
Every council
Each council's records live separately and securely — any local authority in Sri Lanka can run on the platform as it is.
Municipal · Urban · Pradeshiya SabhaSystem by Winsoftmax · 2026