The 18 agents that work on your file
AutoRize is not one model doing everything. It is 18 agents, each on a narrow job, grouped into the five stages a permit file goes through.
A building permit file goes through the same stages whoever prepares it: somebody reads the paperwork, somebody studies the drawings, somebody checks what the regulation allows, somebody writes the documents and somebody checks them before submission. AutoRize splits the work the same way, across specialised agents. The reason is simple: an agent that does one thing can be tested on that thing, and when it gets something wrong you can see where.
Stage 1: reading the paperwork
Four agents handle what you upload. One pulls project data out of text documents, one reads owner identity from the land registry extract, and two read the metadata of the drawings and approvals you attach. The result is a set of fields with confidence scores you can correct before anything moves on.
Stage 2: interpreting the drawings
Five agents study the drawings. One interprets the sheet as a whole, one reads the title block, one extracts the room schedule with areas, one identifies neighbouring plots and boundaries, and the last reads the per-zone areas off the site plan legend. This is where the data that ends up in the technical statement and the F.8 annex tables is gathered.
Stage 3: fitting the regulation
Three agents compare the project against what the regulation permits. One determines which zoning unit the plot falls in and which indicators apply, one takes from the certificat de urbanism the avize and approvals the town hall requires, and the third phrases the scope and title of the work as it must appear on the application.
Stage 4: drafting the documents
Four agents write. One drafts the architectural statement, one completes the F.8 annex, one takes the works value (C+M, excluding VAT) from the deviz general you upload, and the last prepares the energy audit part where it is required. All start from the same data extracted in the earlier stages, so nothing has to be entered twice.
Stage 5: checking the file
Two agents check the result. One produces the verification report, the other reviews the project as a whole and flags what is missing or what does not line up between documents. It is the equivalent of a careful read before you reach the counter.
Why the split matters
- A narrow agent can be evaluated on its own job, against real examples, on every change.
- When a field comes out wrong, you can see which stage produced it.
- Every extracted field carries a confidence score you can check before generating.
- Data flows between stages, so the same information is never entered twice.
Frequently asked questions
Why 18 agents and not one?
Because an agent doing a single job can be tested on that job. A model that does everything is hard to verify and, when it is wrong, hard to locate.
Do I get to check what the agents extract?
Yes. Every extracted field appears with a confidence score and can be corrected before the documents are generated.
Do the agents submit the file for me?
No. AutoRize prepares the documents in editable form, ready to submit. Submission stays with you.
What happens if an uploaded document is unclear?
Confidence scores drop and those fields are flagged, so you fill them in yourself rather than letting them travel onward wrong.
Does it work for any locality?
The document structure is the one set out in national legislation, so it works anywhere in Romania. Local regulations, with their indicators and fees, are configured for Târgu Mureș, and the zoning list also covers Bucharest.
Useful pages for the same dossier
See the agents at work
Upload a certificate of urbanism and watch what each stage extracts. Free account, no card.