AI Site Plan Analysis for Land Development Teams

Home / Case studies / AI Site Plan Analysis for Land Development Teams

Case study · Land development · Computer vision & document AI

AI Site Plan Analysis for Land Development Teams

A European land development consultancy handled site plan analysis by hand, so an expert measured every plot boundary & building offset on each drawing. Brainy Neurals built a drawing reader that uses trained vision models to turn plan pixels into real-world units. Surveyors at the consultancy upload a plan & get plot areas with setback distances marked on it, in place of the scale rule. Measurement now takes one pass, & the system refuses any drawing it can’t read, stating the reason.

  • #SitePlanAnalysis
  • #ComputerVision
  • #DocumentAI
  • #LandDevelopment
  • #CivilEngineering
  • #SetbackVerification

40 plans

In one verification run

One pass

From upload to measurements

On the plan

Where every number comes from

Mitesh

Published October 2026

At a glance

What problem did this solve?

Each drawing kept its facts in drawn lines & printed text, from plot boundaries to the scale marker. An expert had to measure every distance by hand.

What did Brainy Neurals build?

Brainy Neurals built a drawing analysis system for a European land development consultancy. Two trained models find the parts of each plan, & a text reader picks up the printed dimensions.

What changed after it went live?

Plan reading now runs in one pass on upload. Surveyors get the measurements back on the same image, & the system refuses plans it can’t read.

Who else could use this?

Any team that measures land from drawings instead of a fresh survey could use the same approach. That includes property, insurance, cadastral (land registry), utility & solar teams.

Industry

Civil engineering

Sub-vertical

Land development

Client

European land development consultancy

Engagement

Drawing analysis platform

Timeline

Not disclosed

Capabilities

Computer vision & document AI

Delivery

Project-based delivery

Why is measuring a plan still manual?

Site plan analysis stayed manual at a European land development consultancy because each drawing kept its facts in lines & printed text. Staff work from these plans daily, & each carries plot boundaries, neighbouring structures, dimension labels, a scale marker & an ownership block. Getting one number out meant opening the file & measuring by hand before anything was signed.

That’s the kind of job intelligent document processing, software that reads documents for you, was meant to remove years ago. Nobody on the team enjoyed doing it by hand.

  • Each review began with the ownership block & then a hunt for the matching outline.
  • A distance started life as a pixel length & only became a figure after a scale conversion.
  • Folded or faded scans turned a 5-minute check into a phone call to the archive.
  • Second reviewers produced second answers, & neither person could show their working.
  • One land verification run of 40 plans cost a week the team didn’t have.

A 2026 study of buildings known only from scanned plans reached the same verdict about manual measuring[1].

Two hands measure a printed site plan with a scale rule & dividers, a calculator close by
Before the build, every distance on a plan came off a scale rule & a set of dividers.

Which tools already measure site plans?

Teams already measure site plans with four kinds of tool, & each earns its place.

Approach What it gets right Where it stops Who it still suits
Manual CAD or PDF viewer Exact when the file is vector Nothing is automated Small volumes & clean files
Takeoff software Fast, mature, built for quantities An operator still traces every line Estimators working plan by plan
General multimodal model Reads printed text well Miscounts & mislocates drawn symbols Summaries rather than measurements
Trained vision pipeline (our route) Finds & measures without tracing Weeks of drawing-specific work Volume & mixed scan quality

A 2026 benchmark on real architectural & engineering drawings found much the same split between the four routes. General models did well on reading text, yet they scored near half when it came to counting drawn symbols[2].

Chart of how far each route gets before a person takes over. The manual viewer, the takeoff tool & the general model stop early, while the trained pipeline reaches a measured result. How far each route gets Manual viewer Nothing is automated Takeoff tool Every line is hand-traced General model Misreads drawn symbols Our route Trained pipeline Measured automatically Chart of how far each route gets before a person takes over. Three routes stop early, & the trained pipeline reaches a measured result. How far each route gets Manual viewer Nothing is automated Takeoff tool Every line is hand-traced General model Misreads drawn symbols Our route Trained pipeline Measured automatically

Three routes stop at a wall long before they measure anything.

How we designed the analysis pipeline

Brainy Neurals built the pipeline around one rule about where numbers come from. Mitesh Patel, who set the measurement architecture, ruled on which numbers the system was allowed to report. The drawing is the only source of truth, so every number has to come off the drawing.

That rule cost us the easier design. We turned down pulling boundaries from a parcel register, the official list of land plots, & fitting them onto the plan. Plans & registers disagree often enough to matter, & the drawing is the document the client signs.

That choice also lets the system work on land no register covers, which happens more often than you’d think.

The drawing is the only source of truth, so every number has to come off the drawing.

Our second decision was to read the page before the plot. A first model finds the drawing area, the scale marker, the legend & the ownership block. Within that area, a second model traces each boundary, building, balcony & neighbouring structure as an outline.

Object detection, which spots & boxes each part of the page, does the finding, while plain geometry does the measuring. No model here ever predicts a distance, because guesses from a model look plausible.

Architecture of the site plan analysis pipeline, from plan image to annotated overlay, with every number taken from the drawing & the parcel register left out. From the drawing Measurement Owner text Reading Detection Px per metre Plan image Clean & deskew Region detector Text reader Outline segmenter Scale calibration Geometry engine Plot matcher Annotated overlay Parcel register Not consulted Architecture of the site plan analysis pipeline, stacked from plan image to annotated overlay, with the parcel register left out. From the drawing Detection Reading Px per metre Measurement Owner text Plan image Clean & deskew Region detector Text reader Outline segmenter Scale calibration Geometry engine Plot matcher Annotated overlay Parcel register Not consulted

Two models & a geometry step run in order, tracing each number to the drawing.

The technology stack we used

Each layer of the technology stack had to survive a scan of completely unknown quality. We chose each tool for how it behaves when the input is poor, which it is most of the time. The same technology selection questions come up on nearly every drawing project we take on.

Layer What we used Why What we ruled out
Input & preparation
Input formats Plan images & scanned PDFs What the client already holds CAD-only ingestion
Preprocessing Deskew, denoise & contrast lift Scans arrive folded & grey Rejecting poor scans outright
Detection & reading
Structure detection Compact object detection model Finds the page regions first Segmenting the whole image
Object segmentation Instance segmentation model Boundaries need outlines instead of boxes Bounding boxes for plots
Text extraction Optical character recognition tuned for drawings Dimensions sit small & rotated Generic page-level reading
Geometry & delivery
Scale resolution Calibration from printed dimensions A stated ratio rarely survives a scan Trusting the scale text
Geometry Polygon, length & offset computation Area & distance are arithmetic Model-predicted measurements
Delivery Overlay on the original image Users check against what they know A separate numbers-only report

How does one plan get processed?

Site plan analysis takes each drawing through seven steps, from upload to answer, in the order below.

  1. The system first straightens & cleans the scan, so a fold stops looking like a curved boundary.
  2. A first model marks the drawing area, scale marker, legend & ownership block.
  3. Optical character recognition, which turns printed text into data, reads every dimension figure in those regions. It also captures the scale line & the owner’s name.
  4. Inside the drawing area, a second model traces plot boundaries, buildings, balconies & adjacent structures as outlines.
  5. Next, the system fixes the scale from a printed dimension & the pixel length of its line, or refuses the plan.
  6. Geometry closes each boundary & works out its area & perimeter. It then measures how far every structure sits from its plot line.
  7. Finally, the system highlights the plot that matches the ownership block & annotates it back onto the original image.
Seven-step flow of one site plan, from cleaning the scan to matching & annotating, with a refusal branch when no scale can be fixed. No scale Refuse 1 Clean the scan 2 Mark the regions 3 Read the text 4 Trace the outlines 5 Fix the scale 6 Compute the geometry 7 Match & annotate Seven-step flow of one site plan, stacked top to bottom, with a refusal branch at step five. No scale Refuse 1 Clean the scan 2 Mark the regions 3 Read the text 4 Trace the outlines 5 Fix the scale 6 Compute the geometry 7 Match & annotate

A printed dimension fixes the scale before the system computes any distance from it.

After those seven steps, every number in the answer traces back to a mark on the drawing.

What broke during the build?

Three parts of the build broke, one after another, before the pipeline held up.

The stated scale was wrong

A plan printed at one ratio, photocopied small & scanned askew, is no longer at that ratio. Our first areas came back wrong, & the system reported them with full confidence.

Boundaries closed around the wrong land

Neighbouring plots share edges, so a driveway crossing a line merged two parcels into one. The traced outline still closed, & its area still looked plausible.

Printed dimensions were hard to read

The text reader failed third, as dimension text is small & rotated over hatching, the shading lines on plans. European drawings write 12.5 as 12,50, & a lost comma turns that into 1250.

A published comparison found today’s reading tools inadequate for text on architectural drawings[3]. A controlled study also found that a 5% error in scale moves the total area by 10%[1].

At this stage, clients often ask us about adding specialist engineers to their team.

A folded site plan photographed in the field, showing the input quality limit for automated drawing analysis
A fresh print folded for the site bag & photographed in the field is a normal input.

What we changed to fix the failures

We changed three parts of the pipeline, & each fix was quicker to describe than to find.

Scale

We stopped reading the stated ratio & started measuring it instead. The system pairs each printed dimension with the line it labels, then works out pixels per metre.

When those pairs disagree, the system refuses the plan instead of estimating a scale.

Boundaries

We retrained the model that traces outlines on driveways & annotations crossing a line. We then added a check that has nothing to do with the model. Wherever a plan prints its own area, the area the system computes must match that printed figure.

Text

We now rotate each dimension crop upright & tie it to its line. Then the reader checks it against both decimal conventions.

A scale rule carries six scales on three faces with no moving parts, & it’s the only tool here that never needed replacing.

An AI proof of concept exists to surface this kind of work before anyone promises a result.

How the scale is fixed: the printed dimension divided by its length in pixels gives pixels per metre. The stated scale is not trusted, & plans whose pairs disagree are refused. 12,50 The printed dimension ÷ Same line, counted in pixels = Pixels per metre The scale the system uses Scale stated in the title block Not trusted Pairs disagree, plan refused Never estimated How the scale is fixed, stacked: the printed dimension divided by its pixel length gives pixels per metre, & disagreeing pairs are refused. 12,50 The printed dimension ÷ Same line, counted in pixels = Pixels per metre The scale the system uses Scale stated in the title block Not trusted Pairs disagree, plan refused Never estimated

When the stated ratio & the measured one disagree, the system keeps the measured one.

What changed after go-live?

After go-live, measuring moved from a person at a viewer to one pass on upload.

What Before After
Where the measuring happens By hand, in a viewer In one pass, on upload
Who reads the scale A person, from the label The system, from the drawn dimensions
What a second reviewer gets A second set of numbers The same numbers, shown on the plan
Plans that stop the process Faded, folded or unclear Refused, with the reason given
Cost of the 40th plan The same as the first Close to nothing

We haven’t published a timing figure or any accuracy & error rates, even though the client reports a positive direction.

Brainy Neurals only prints results it has measured, which is why this page reports the change in words.

Day to day, the change is smaller than a headline figure & more useful. A reviewer opens the annotated plan & checks the boundary the system used. If someone disagrees, the argument is now about the drawing itself instead of about somebody’s arithmetic.

Measure your own plans the same way

Tell us which drawings your team still measures by hand, including the folded & faded ones. We’ll say what the system could read from them & where it would refuse.

Where is site plan analysis running today?

Today the pipeline runs in production at the consultancy, on the firm’s own plans. Surveyors & civil engineering staff use it to verify plots & check offsets before documents go out.

Since handover, the set of plans it reads has grown well past the drawing styles we started with. Nothing in the pipeline changed when the drawings got worse, & every refusal still goes to a person for review.

The annotated overlay is still the interface, & nobody has asked to see the numbers on their own.

A surveyor crouches at a boundary marker with a rolled site plan on a land development site
A surveyor confirms a boundary on the ground against the plan the system measured that morning.

What would we do differently?

Next time, we’d put scale calibration at the very start of the work.

Calibrate before you segment

We built the boundary work first & treated scale as a simple conversion at the very end. Scale is the foundation, & every layer above it inherits its error.

Ask what the drawing already tells you

Those plans printed their own areas all along, yet we ignored that check for weeks. A drawing that states a fact can check our work.

Collect the ugly scans on day one

Our first sample was clean, because clean files are the ones people email. The real population is folded & faded from being copied over & over.

Decide early what a refusal looks like

A stated scale records how a sheet was once printed & says nothing about the copy you hold. Deciding when to refuse is a product call, & we made it far too late.

A stated scale records how a sheet was once printed & says nothing about the copy you hold.

Where else does plan reading fit?

Plan reading fits wherever the drawing is the record & no fresh survey exists. Site plan analysis does this by turning a drawn plan into measured geometry, with its pixels matched to real units. Plot plans & situation plans are other names for the same drawing, which German firms call a Lageplan.

Industry The equivalent problem What changes in the build
Real estate & property Confirming plot area before a transaction Title-block reading, area against the register
Government & planning Checking a situation plan against setback rules Cadastral reference, rules as an input
Insurance Measuring distance from a building to a hazard Wider plans, more adjacent structures
Utilities & telecom Checking clearances inside an easement corridor Long thin drawings, corridor-first geometry
Manufacturing Plant layouts & equipment clearances Denser symbols, tighter tolerances
Solar & renewables Usable area & setbacks from every edge Sloped surfaces, exclusion zones as inputs

Porting it means retraining the detector & checking the scale markers on the client’s folded & faded scans.

A solar layout read by the same pipeline, showing the plot boundary, a measured setback from every edge & the usable area filled with panel rows. Plot boundary Usable area Setback, measured A solar layout read by the same pipeline, stacked for small screens, with the plot boundary, edge setbacks & usable area. Plot boundary Usable area Setback, measured

The same pattern reads a solar layout for usable area & edge setbacks.

Questions buyers usually ask

Buyers usually ask these questions before they scope a build like this one.

How it works

Can AI read a site plan & calculate the plot area?

Yes, as long as the drawing prints the dimensions it will be measured from. A vision model finds the boundary while a text reader picks up the printed dimensions. Geometry then turns pixels into real units.

Does site plan analysis replace a licensed land survey?

No, because it measures the drawing you already have, to the accuracy that drawing allows. A stamped survey measures the ground itself. Use plan reading for review & triage, & order a survey when a boundary is actually contested.

Will it work on scanned or photographed plans?

Usually, yes, because the system straightens & cleans each image first. Calibrating from printed dimensions then fixes the scale on folded scans & phone photos alike. Image quality still sets the ceiling, so the system reports what it couldn’t read instead of guessing.

Does it check a plan against zoning or setback rules?

Not on its own, since the system only measures the distances a rule would apply to & shows them on the drawing. Testing those numbers against a rule set is a separate layer, & you’d need to supply the rules.

Time & cost

How long does it take to build a system like this?

A proof of concept on a folder of your own real drawings usually takes a few weeks. Each stage, from structure detection to scale calibration, needs its own pass. Production follows once everyone agrees how refusals should behave.

How much does a drawing analysis build cost?

Cost depends on your drawings, meaning how varied they are & how much text they hold, & on what you already have. Brainy Neurals scopes it from a short call & a folder of your real plans, then quotes a fixed price. An AI readiness assessment tells you first whether your drawings carry enough to measure.

What do your drawings need to tell you?

Describe what your team measures by hand today, even in a sentence. Brainy Neurals is ISO 27001 certified, & we can send the security summary or a technical brief first if you ask.







    Services behind this case study

    Brainy Neurals drew on five services & one industry practice for this build.

    Start with our AI readiness assessment if you’re unsure your drawings hold enough detail to measure. Our engagement models set how a build runs, & the industries hub shows where the pattern fits. For everything around this work, see the list of all AI services.

    Similar case studies

    Three more Brainy Neurals builds share this shape, since each one shipped into a working environment instead of a demo. Each card below opens the full case study on its own page.

    Cite this case study

    Patel, Mitesh. AI Site Plan Analysis for Land Development Teams. Brainy Neurals, August 2026. https://brainyneurals.com/case-studies/ai-site-plan-analysis/

    Sources cited on this page

    1. Guo Y, Zhou X, Tang S-K. LLM-Integrated Semantic Deep Learning Framework for Automated Floor Plan Analysis, Area Estimation, and Compliance Assessment of Existing Buildings. Applied Sciences, 2026, 16(13), 6290. DOI 10.3390/app16136290.
    2. Kondratenko A, Birhane M, Hsain HE, Maciocci G. AECV-Bench: Benchmarking Multimodal Models on Architectural and Engineering Drawing Understanding. arXiv:2601.04819, 2026.
    3. Schonfelder P, Stebel F, Andreou N, Konig M. Deep learning-based text detection and recognition on architectural floor plans. Automation in Construction, 2024, 157, 105156. DOI 10.1016/j.autcon.2023.105156.