Keep the current system in view
PermitLite left a records system without an API in place. StreetSignal handed structured reports to the dispatch process, and WaterStart exported requests for manual import into billing tools.
See PermitLite case →Methodology
Start with one process.
We map what a person submits, what staff review, what existing system receives the result, and who remains responsible for the decision. The case studies show the work and the limits of each evaluation.
Working method and outputs
| Stage | Output |
|---|---|
| Understand one process | Workflow map and constraints |
| Define the smallest useful scope | Applicant and staff paths |
| Build or test a demonstrator | A reviewable workflow |
| Check the evidence | Measures, samples, and open questions |
| Decide what follows | A scoped implementation proposal, if needed |
What the project evidence supports
These are lessons from the work shown on this site, not universal performance guarantees.
Show what happens offline
FieldLog stored reports until a connection returned and exposed sync states; all 63 reports eventually arrived, with three retries. StreetSignal drafts also remained on the device until they could be sent.
See FieldLog case →Design for applicants and staff
The permit and utility workflows paired guided intake with a staff queue, status history, and a path for missing information or non-standard cases.
See WaterStart case →Keep official decisions with staff
The permit pilot supported review but did not replace legal approval. The OpenRecords concept left disclosure decisions and jurisdiction-specific rules with the responsible authority.
See OpenRecords case →Report what the evidence covers
Results include the review window, sample, source, and limitation. For example, StreetSignal measured initial routing, not repair speed; OpenRecords measured modeled-task completion, not a live service.
See StreetSignal case →