Compliance Agent

One agent.
Every jobsite's permit paperwork.

Compliance Agent resolves a Construction & Real Estate jobsite's country into the right permit, zoning, and legal-contract paperwork — Turkey's Ada/Parsel/SGK fields, the US's Parcel ID/OSHA fields, or a safe generic fallback for anywhere else.

Resolve, Prepare, Present Jurisdiction Fields Filing a Permit Where It Fits
Resolve, Prepare, Present

Give it a country.
Get back a working form.

Construction paperwork is not the same everywhere. Compliance Agent reads the jobsite's country, recognizes Turkey or the United States, or falls back to a safe generic form — it never fails to return something usable.

  • 1. Resolve — reads the jobsite's country code and picks the matching jurisdiction
  • 2. Prepare — assembles labeled inputs with format validation built in
  • 3. Present — renders inline using the same shared form-rendering path every screen uses
  • Adding a new jurisdiction extends the agent's own knowledge, not each individual screen
Open Permits & Zoning Compliance
construction-permits-zoning-compliance
Jobsite Country: Turkey
Ada / Parsel142 / 7
Contractor SGK No.4521873
TAKS / KAKS0.40 / 1.80
Fields regenerate per jurisdiction
Jurisdiction Fields

Ada/Parsel here.
Parcel ID there.

A Turkish jobsite files Ada, Parsel and Pafta cadastral references, a contractor's social-security registration number, and floor-area ratios. A US jobsite instead files a Parcel ID, a Contractor License Number, and an OSHA Certification Number.

  • Turkey — Ada, Parsel, Pafta (optional), Contractor SGK No., Site Manager Certificate No., TAKS/KAKS
  • United States — Parcel ID, Contractor License Number, OSHA Certification Number, Zoning Classification
  • Any other country — a safe generic form: document type, site address, and notes
  • Format validation travels with each field, so the rendering screen enforces it automatically
Explore Construction
Jurisdiction: United States
Parcel ID04-217-009
Contractor License No.CL-88214
OSHA Certification No.OSHA-30-5521
Zoning ClassificationR-2 Residential
Same request, different jurisdiction fields
Filing a Permit

One "Generate Form"
button, three screens

Inside the Add/Edit modal on Permit Applications, Zoning & Land Use Rules, or Legal Contracts & Liens, a "Generate Form" button asks Compliance Agent for the jobsite's resolved jurisdiction and renders the result inline.

  • A Turkish jobsite's user sees Ada/Parsel/social-security fields
  • A US jobsite's user sees Parcel ID/OSHA fields — same judgment, different output
  • Each screen carries its own jurisdiction picker, pre-filled but overridable per record
  • Changing it re-asks the agent and swaps the presented fields to match
Explore Permits & Zoning Compliance
Permit Applications — Add/Edit
1 Building Permit · jobsite: Ankara, TR
2 Compliance Agent → Ada/Parsel/SGK form
Same button, all three permit/zoning/legal screens
Where It Fits

One place to ask
"what does this jurisdiction need?"

Compliance Agent has no persistence layer or settings screen of its own — it exists so permit, zoning, and legal screens across Construction (and, in principle, any future add-on with country-specific paperwork) can ask once, in one place, instead of re-deriving the same logic in every screen.

  • The submitted values are stored by the screen that collected them, not by the agent
  • A missing country is rejected outright, never silently defaulted
  • Countries without a dedicated profile stay selectable via the generic fallback
  • Document type labels the resulting form; today, fields depend only on jurisdiction
Read the Full Docs
Compliance Agent — no ledger of its own
// screens that ask for a form
Permit Applications → building/env/scaffolding
Zoning & Land Use → zoning-record form
Legal Contracts & Liens → legal-contract form
Values stored by the calling screen, not the agent