Layout: site and zoning
Setbacks, parking counts and accessible routes change by city. Site-plan corrections show where a layout broke a local rule.
Site plan: add one accessible van stall.
Models trained on permitted buildings learn from approvals. The reviewer’s corrections, the prototype re-checked city by city and the calcs behind each beam are the part that is missing. Lasker licenses them from the firms that hold them, mapped into your schema.
For teams whose models produce permit-ready drawing sets, not concept sketches.
Comment 7 from Ana OrtizReviewer: corridor C2 on sheet A-201 needs 44 in clear width for egress.
Answered by Studio RuizFirm on A-201 rev 2. Parcel 512-044-19parcel.
Ana OrtizReviewer · Plan reviewer · +1 559 555 0188phone
Illustrative example. Names, places and numbers are made up.
✓ Cleared to leave · rights on recordDesign models go from layout to systems to a buildable set, then check it against local code. Each stage has its own corrections, and they sit in firm archives.
Setbacks, parking counts and accessible routes change by city. Site-plan corrections show where a layout broke a local rule.
Site plan: add one accessible van stall.
Travel distance, exit count and corridor width follow occupant load. A tenant improvement that changes the use can break all of them.
Corridor C2: show 44 in clear width.
Beam and column sizes the calcs support, and the corrections when a new opening or rooftop unit changed the load.
Provide calcs for beam B4 at new opening.
Ducts, plumbing and conduit have to fit the structure and the ceiling. Each discipline looks right on its own sheet.
RFI: duct conflicts with beam at grid C/4.
References, schedules and details that agree across sheets, so the contractor does not have to ask.
Detail 5/A-501 referenced, not found.
Each city adopts its own edition and amendments. A code check learns them from that jurisdiction’s corrections.
Note the adopted code edition on the cover sheet.
An approval tells a model the set passed. It does not say what the reviewer made the architect change first.
Multi-site rollouts are re-checked for every location. Firms that adapt prototypes hold the same design with a dozen sets of corrections.
Under the standard AIA agreement the architect owns the drawings, so the rights have to come from the firm, project by project.
A model that issues drawings someone will build from, and signs for, needs more than examples of approved sets.
A verifier trained on real corrections, so the model catches what a reviewer would before the set goes out.
Source: plan-check pairs from firm archives
The same store or restaurant prototype permitted in different jurisdictions, with each one’s corrections. The design stays fixed and the code changes.
Source: prototype rollout sets from site-adapt firms
Layouts are the easy part. Member sizes, load paths and duct routing have to agree with the calculations.
Source: structural and MEP packages tied to sheets
Retail, tenant improvements, offices, data centers, warehouses and manufacturing each have their own codes, systems and failure modes.
Source: completed projects from commercial firms
A cost forecast is only as good as the estimate tied to the exact set it priced.
Source: estimates and bid tabulations
RFIs and change orders show what passed review and still failed on site.
Source: construction-phase records
Each record ties back to the sheets and, where the firm has one, the model element it changed. We map records into your schema in the pilot, not ours.
| Dataset | What is in a record | Used for | Format |
|---|---|---|---|
| Plan-check pairs | Reviewer comment, code basis, the sheet before and after, and how it was resolved | Code check, verifier | JSONL + sheet crops |
| Prototype rollout sets | One prototype across several jurisdictions: each site’s set, code basis and corrections | Multi-site adaptation | JSONL + sets per site |
| Engineering packages | Structural and MEP calculations tied to the sheets they support | Systems: beam sizing, load audits | PDF + extracted values |
| Coordination records | Clash or RFI, the disciplines involved and the design change that closed it | Systems: MEP fit | JSONL + linked sheets |
| Native design sets | Revit or IFC model with the matching construction set and schedules | Mapping into your schema | IFC, RVT, DWG, PDF |
| Cost records | Estimate or bid tabulation tied to the exact drawing set it priced | Cost forecasts | CSV + linked set |
| Expert review | Licensed architects and engineers score generated sets against the adopted code | Evals before a set is stamped | Scores + rationale, JSONL |
A plan-check correction tied to the sheets and model element it changed, and a prototype permitted in two jurisdictions with different corrections.
Illustrative. Field names are our draft schema, and we adapt it to your pipeline in the pilot.
{
"record_id": "pc-0184",
"jurisdiction": {
"state": "CA",
"code_basis": "2022 CBC",
"permit_year": 2024
},
"building": {
"occupancy": ["B", "M"],
"type": "retail prototype",
"area_ft2": 8400
},
"discipline": "architectural",
"sheet": { "id": "A-201", "rev": "1 -> 2" },
"category": "egress.corridor_width",
"comment": "Corridor C2: show 44 in clear width.",
"resolution": "Wall moved 6 in, width dimensioned.",
"artifacts": [
"A-201_r1_crop.png",
"A-201_r2_crop.png",
"model.ifc#wall-2231"
],
"rights": {
"copyright": "firm-14",
"owner_release": true,
"personal_data_removed": true,
"license": "non-exclusive, training + eval"
}
}{
"record_id": "pr-0031",
"prototype": {
"id": "proto-qsr-a",
"type": "restaurant prototype",
"area_ft2": 2850
},
"sites": [
{
"state": "CA",
"code_basis": "2022 CBC",
"corrections": [
"11B: accessible stall slope at parking",
"Title 24: lighting control schedule"
]
},
{
"state": "TX",
"code_basis": "2021 IBC + local amendments",
"corrections": [
"Grease interceptor sizing"
]
}
]
}The same questions a plan reviewer and a general contractor would ask, written down so two reviewers can agree.
| Dimension | What the reviewer checks | Evidence per finding |
|---|---|---|
| Code compliance | Egress, accessibility, fire separation against the adopted code edition | Code section cited |
| Coordination | Structure, MEP and architecture agree across sheets | Sheet and grid location |
| Completeness | References, schedules and details a contractor would need | Missing items listed |
| Constructability | Could it be built without an RFI | Reviewer rationale |
| Approvability | Would it clear plan check in the stated jurisdiction | Pass, corrections or reject |
Reviewers are licensed in the state whose code they score. Items with disagreement go to a second reviewer and are adjudicated.
Pick the stage and building type where your model is weakest. The pilot answers whether this data moves it.
One building type, one jurisdiction and the stage to improve: layout, systems or the code check.
Week one
Prototype rollouts and plan-check pairs for that type, mapped into your schema.
Your team audits it
Full set, ongoing feed or stop. Price is set per dataset after the sample.
No commitment before
It says a set passed. It does not show what failed on the way, and those failures, with the reviewer’s reason, are what a code check or verifier learns from.
From the architecture and engineering firms that prepared the drawings and own the copyright, under a non-exclusive license. Each project also needs a written release from the building owner before anything is delivered.
Each record carries a rights record: copyright holder, owner release, a confidentiality check and the license scope, training, evaluation or both. We do not use scraped permit files.
Tell us yours and they shape sourcing. Code basis is recorded per project, because the adopted edition and local amendments change the right answer.
Where firms hold it. Older projects are often PDF only, so we report the format mix before you commit to a full set.
Licensed architects and professional engineers, credential-checked and licensed in the state whose code they score. We are recruiting the bench now.
The license scope is written per dataset: training, evaluation or both, and whether a model trained on it can be used commercially. We negotiate with the firm for commercial use from the start, because that is what design teams need.
Yes. We map records into your schema during the pilot, and keep the source sheets linked so your team can check every field.
Per dataset, after the sample. We do not publish ranges until we have closed deals to base them on.
Hold a drawing archive? Your firm keeps the copyright. License completed projects on your terms.
License your archive →Layout, systems or the code check. We reply with a sourcing plan for that stage and what a pilot would include.