Kabacan PUV

Traffic enforcers in Kabacan logged violations on printed sheets, then manually transferred the data into an Excel file at the end of each shift. The process guaranteed transcription errors and delayed supervisor visibility by hours. The local government unit needed a digital replacement.

The constraint: internet coverage across enforcement areas is inconsistent. A system requiring a live connection would fail in the field, becoming a more expensive version of the paper log.

I spent a morning observing two shifts before writing a single wireframe. The paper system had two distinct failure modes.

Enforcers were formatting plate numbers differently across every shift. The data wasn't wrong — the input had no structure to be wrong against. The implication: any digital replacement needed strict, structured input fields.

Supervisors managed field operations on yesterday's data. A violation logged at 9am existed only on paper until transferred hours later. The implication: the system needed automatic background syncing to give supervisors real-time visibility without adding manual steps for the enforcers.

The framing decision: deploy a Progressive Web App to the Android smartphones enforcers already carried. No app store, no new hardware, no IT provisioning. The enforcement workflow stayed the same. The tool changed.

Built structured input for all violation fields — plate numbers follow a defined format, and violation types are selected from a list.

Ran two rounds of on-device testing with enforcers during development. The first round surfaced a parsing failure for edge-case plate formats, which was fixed before the second round.

Implemented an offline-first architecture using Service Workers and IndexedDB. Every violation logs immediately to local storage, requiring zero connection.

Built a background sync layer — records upload automatically when signal returns, requiring no enforcer action.