Practical workflow automation for local government.
Cities run on forms, approvals, records, and handoffs between departments. I help agencies find the workflows worth improving, build them inside the systems staff already use, and keep a person accountable for every decision.
City staff are stretched. I help you handle more requests with the people you already have, so they spend their time on the decisions that need a person. That includes bringing AI in safely, with a clear record of what it did.
How a permit request moves
Example: permit intake
Your systems
Pulled together
One view
Departments decide
Work goes out
- Online application
- Parcel records
- Prior permits
Permit queue
- Permit 3301Review ready
- Permit 3302Waiting on fire
- Permit 3303Issued
- Planning
- Fire
- Public Works
- Permit issued
- Applicant letter draftedAI
AIAI does this work
See where everything stands. Decide faster.
Staff often check several systems to answer one question, and no one can see the whole picture. I pull the relevant information from each system into one view, so the person making the decision has what they need in front of them, and managers can see where every request stands.
Visibility
Every request, who has it, and how long it has been waiting, in one place. No more chasing updates by email.
Faster decisions
Staff see the context they need on one screen, so a routine approval doesn't need a round of lookups and emails.
Setting your AI policy
Many city staff are already trying AI tools, and most cities don't yet have clear rules. I help you set them: what staff can use AI for, what information never goes into it, how its use is recorded, and who approves new tools. It's also a good first step, and it makes your first workflow easier to approve.
An AI use policy
A plain-language policy that staff can follow, written to fit your city's size and the way your departments work.
An approved-use list
Clear examples of what is encouraged, what needs approval, and what is off limits.
Public records and sensitive information
How AI use is recorded and retained, and which resident and employee information must stay out of AI tools.
Staff guidance
A short briefing for staff and department heads, so the policy is understood and not just filed.
I work alongside your city attorney and IT staff. Legal review of any policy stays with them.
Where it tends to help
Common examples, not claims about any one city.
- Permit and plan-review intake and routing
- Public records request tracking
- Agenda and staff-report assembly
- Paper approvals turned into tracked digital ones
- Inter-department approvals
How I work with public agencies
A person decides
AI drafts and flags. Staff review and approve every consequential step, and nothing irreversible happens without sign-off.
Your environment
Built inside the agency's own Microsoft 365 and Azure environment where possible. Data stays in your tenant.
Records-ready
Every AI action is logged so it can be retained and produced under the California Public Records Act and your retention schedule.
No PII to public tools
Resident and employee information is never sent to public AI services.
Start small
One workflow and a measurable result, not a citywide program.
See it as it's built
A private preview lets your staff watch and test the work along the way, so nothing arrives as a surprise.
Open to every resident
Anything residents use is built with accessibility standards (WCAG) in mind.
You own it
Fixed scope and fixed price. The system and its code are yours, with full documentation and handoff so your staff can run and change it. No subscription, no lock-in.
A way to start
Schedule a free workflow review. I'll spend time with your team to learn how the work really gets done, then send you a short written summary of what I found and the best places to start.
Or write me directly at [email protected].
Already working with sensitive information
I've built systems for a law firm and a medical clinic, where confidentiality is not optional. See the work.