Worked example · City of Larkhaven · Example company
One city department, five people, one year.
The City of Larkhaven issues building permits for a growing city. Its council has goals, its permit desk runs a process spread across policies, procedures, years of records and the experience of its people, and the pieces do not always agree. This is how Inovagio learns that work and puts it to use.
Every agency has these five roles.
The city council
Sets the plan
Three-year goals, and the budget that funds them.
Rosa Delgado
City Manager
Needs every department pulling toward the same goals.
Frank Moreau
Building Official
Runs a process spread across policy, records and experience.
Linda Cho
Senior Plans Examiner
Handles the exceptions the procedures leave unclear.
Jamal Hayes
Permit Technician
Keeps every application moving and every resident informed.
The board sets the goals; the team shows how the work is really done.
Week 1
The council’s plan goes in first
The strategy, the budget and the state’s requirements become the top of Larkhaven’s rulebook: decide routine permits within five business days, no repeat audit findings, keep up with growth with flat staff. Each goal carries its owner and its target.
Week 2
The city manager’s interview becomes a draft
Rosa answers one question: what must be true in twelve months? Her answers become a draft the department heads accept, edit or reject in one meeting.
Weeks 3 to 6
The Building Official describes the process
“Every permit type has its own checklist, the code changes every few years, and our procedures, our systems and our people don’t always agree.” His interview, the city’s procedures and its permit history become a first draft, with its open questions listed, that his team corrects.
Weeks 4 to 8
It learns from the procedures, the records and the examiners
Linda and two other examiners walk through how the work is really done: where it follows the procedures, where it differs, and where the procedures are unclear.
Week 8
Every task traces to a goal
Each rule links up to the goal it serves and down to the Virtual Employees that follow it, with its reason one click away. The same pattern serves the permit desk: when an application is missing a contractor’s license number, the AI holds Jamal’s approval notice and asks.
Where policy and practice part.
In his interview, Frank says every residential permit needs a site plan. Linda says: “For a like-for-like replacement, a water heater or a roof, we don’t ask for one. Everybody knows that.” Two other examiners agree. Inovagio flags the gap instead of guessing, and Frank decides: like-for-like replacements need no site plan but do need a photo of the existing installation; everything else still needs the site plan. That approved rule is now followed on every application.
- The gap between policy and practice is where AI that only reads documents goes wrong.
- Every rule links back to the interviews and documents it came from.
- Nothing is used until an expert approves it.
Rule review · Residential permits
City of Larkhaven · Building permits
Stated rule
Every residential permit needs a site plan.
Building Official · interview
Actual practice
Like-for-like replacements go ahead without one.
Three examiners · interviews
Approved rule
Like-for-like: no site plan, photo of the existing installation required. Everything else: site plan.
Approved by the Building Official
In force on every application. The Virtual Employees follow version 2, and each decision links back to the rule and the interviews it came from.
What Larkhaven sees.
Every name and record here is an example.
- The card app its people use to decide and correct.
- A map of how its records connect.
- Search that finds the rule in other words.
- The workflow its Virtual Employees follow.
The AI drafts. Linda decides every one.
Nothing goes out without a person. Every correction teaches the Virtual Employees, and they take on the routine checking one permit type at a time, after go-live and as accuracy holds. Linda still signs off every permit.
A draft for every application.
Each application arrives with the documents checked, the code sections that apply listed and a decision drafted, for Linda to mark right or wrong.
Every correction teaches it.
When a draft is wrong, Linda says why: the wrong code edition, a missed setback. “By the second month the drafts read like mine.”
Larkhaven stays in control.
It runs in the city’s own cloud account, and Larkhaven owns the data and the models. Residents’ records stay with the city.
Linda’s new job.
The target: Linda spends her day on the plans that need an examiner. The “with Virtual Employees” column is what shadow mode measures before anything goes live: a target, never a result.
| Linda’s work | Today | With Virtual Employees |
|---|---|---|
| Her day | Checking routine applications line by line | The plans that need an examiner |
| Routine permits | Every one by hand | Signs off permits the Virtual Employees have already checked, reviews in depth only the ones they flag, and rates each result: right, wrong, and why |
| When the code changes | Updates checklists by hand | Approves the rule changes her feedback raises |
Permits reviewed against the code, with a record of every decision.
- Routine permits done inside rules the city’s own experts approved.
- Fewer applications sent back to residents.
- The cost of every permit shown beside what the same work costs today, counted the same way.
- Every decision shows the rule, the record and the person who approved it.
- The knowledge, the models trained on it and the record belong to the city.
Further reading
Articles and guides that draw on this worked example.
Start with one workflow and the people who know it.
A 30-minute briefing on how Inovagio would learn one of your workflows, where your people approve, and the record it leaves.
