For the public sector
The workspace where a government, its districts, and the people it serves all meet.
One workspace, grounded in the real rules of your place: your own code, your own procedures, your own meeting record, captured at the source. Your staff handles the front counter, council and agency work, and the districts you coordinate with. The residents and businesses in your jurisdiction work off that same captured reality, so a permit question or a license check isn't a back-and-forth across two systems.
Departments and districts included. Sign in for existing tenants.
Why this is hard today
Your code lives in PDFs. Your procedures live in inboxes. Your interactions live in back-and-forth.
A resident asks the same question six ways and gets a different answer each time. Staff hunt through a council packet, a code page on the legacy CMS, a procedure binder from 2019, and the city attorney's inbox to give an answer that's actually defensible. The work is real. The system around it isn't.
Tools you build yourself
Build the tools your office actually needs.
Same composable workspace. Your team puts together the surface that fits your office: the front counter, the council pipeline, the procedures binder, the internal ops dashboards, all grounded in your own code, your own meeting record, your own procedures.
The front counter
Permit, license, and code-interpretation questions answered from your own code, cited. Residents and businesses get a real answer the first time, and your staff has the citation in hand.
Council and agency work
Agenda items, ordinance changes, and meeting records summarized and queryable. Staff catch what happened in a session without re-watching the recording, and the redline is preserved.
Internal procedures and ops tools
An "ask our own procedures" assistant for staff. Plus permit-routing dashboards, inspection trackers, and code-violation queues, built by your team on top, no new system to buy.
And whatever else your office actually runs on. The tools are yours to build, and yours to share across departments.
The districts you coordinate with
School, water, transit, special. One workspace, all of them.
A school district issues its own rules. A water district enforces its own permits. A transit authority runs its own procurement. Each one has its own code and procedures, and each one touches your work. On Votion they sit on the same captured rules and the same workspace as your office, so a coordination question isn't a phone tree.
The other side of the table
Residents and businesses already work off the same rules.
On Votion, the regulated business across the counter isn't reading a different version of your code. The resident asking a permit question isn't getting a guess from generic AI. Everyone is working from the same captured reality of the place you govern. When the same question comes from both sides, the answer is the same, and it's cited to your own source.
Yes, with an annual STR license and a primary-residence requirement. R-2 zoning permits accessory STR use.
Yes, with an annual STR license and a primary-residence requirement. R-2 zoning permits accessory STR use.
Why it's trusted
Grounded in your own code, your own procedures, your own record.
Every answer is cited to your source: your municipal code, your council record, your procedure binder. Captured directly from the publisher you already use, never a third-party aggregator. When a resident, a business, or a regulator pushes back, you can point at the line and the date it was pulled.
Yes. The amendment passed at the May 14 council session became effective May 21. The prior version was superseded; the redline is preserved in your council record and linked from this answer.
See it on your own code.
Bring a code chapter, an ordinance, or a procedure binder. We'll show you the workspace running on your actual record, then walk through what a pilot looks like for your office.