Compare
Euclid HL vs a
general-purpose chatbot.
Plenty of tools can put a chat box on a city website. For zoning, the question is where the answers come from, and whether a resident can check them.
Side by side
What changes when answers
come from adopted code.
| Question to ask | Euclid HL | Typical general-purpose chatbot |
|---|---|---|
| Where answers come from | Your adopted zoning code, plans and staff-reviewed FAQ | Often website pages, or a general-purpose AI model's training |
| Citations | Every answer cites the governing section | Often none, or a link to a page |
| Parcel awareness | Looks up the address and shows the parcel, zoning and overlays on the map | Usually no map or parcel lookup |
| Diagrams | Returns the code's figures when they answer better than text | Usually text only |
| When it doesn't know | Says so and routes the question to staff | Varies; general models may guess |
| Staff interpretations | Recorded on the provision and used in later answers | Not usually captured |
| Policy vs regulation | Distinguishes comprehensive plan policy from zoning requirements | Rarely distinguishes the two |
Why it matters
Zoning answers carry weight.
A resident who is told a fence or an addition is allowed may spend money on that answer. That is why Euclid HL answers only from your adopted documents, shows the section, and says when a question needs a planner.
A general-purpose assistant can be useful for many city services. For zoning, ask any vendor: where does the answer come from, can the resident see the source, and what happens when the code is ambiguous?
Keep reading
See it with your code.
Bring a question your counter gets every week. We'll show you how Euclid HL answers it from adopted documents like yours, and what it hands back to staff.
Request a demo →