Skip to content
Documentation

Blueprint Auditor, in order.

Read a drawing set: quantities, code findings and the sheets they came from.

Blueprint Auditor

Read a drawing set: quantities, code findings and the sheets they came from. Included from Field upwards.

1. Open a set

PDF, DWG, DXF or IFC, uploaded as it is. There is no conversion step and no drawing preparation: the file you hold is the file it reads.

2. Pick the trades

Scoping the audit decides which rules are reported, not how hard the drawing is read. Every reader runs on every file either way.

3. Read the findings

Each one carries its clause and the sheet it came from. A rule the drawing cannot answer is printed as a checklist item and never dressed up as a finding.

4. Measure what you need

Lengths, areas, counts and volumes against your own conditions and cost codes, out as CSV or a workbook whose totals are formulas.

5. Mark it up and send it

Pins, clouds, callouts and stamps, with the marked-up sheets exported as a PDF worth sending and the pins numbered with a legend.

What it will not do

  • An audit is a first pass, not a permit approval. A clean run means nothing obvious, never compliant.
  • A scanned sheet is read by OCR, and OCR on a dense schedule is the weakest part of the path. The audit says which pages it fell back on.
  • Quantities rest on the scale. A sheet that states none is left uncalibrated rather than measured at a guess.

On a paid plan every program opens a sample set, so none of this has to be read before trying it. A free trial starts blank, on your own drawings. See the sample project.

In detail

In short

Upload the set you are pricing and it reads it: a real quantity takeoff (room areas, door, window and fixture counts), plus sheets, disciplines, completeness gaps and code risk, each finding carrying the clause and the sheet it came from. On every plan from Field — and free for fourteen days.

From drawing to done

Drop a file and the pipeline handles ingestion, extraction, code audit and reporting — review the output and ship it.

  • Drop a drawing. DWG, PDF, DXF, image, or schedule. Scanned sheets are OCR'd automatically.
  • Extract. Rooms, areas, openings and quantities are read off the geometry and schedules.
  • Audit. Every sheet is checked against the code pack for your jurisdiction — building, accessibility, fire and zoning.
  • Report. Takeoff, costed estimate and a client-ready Excel/PDF audit — generated for you.
  • Takeoff → costed estimate. Material & labor quantities priced into a full estimate and client bid.
  • Code compliance audit. OBC, AODA, fire, zoning & green-standard checks with clause references.
  • Drawing register & RFIs. Revision history, submittals, RFIs, transmittals and daily logs in one register.

What it opens

Upload the set however it reached you. Most contractors are sent PDFs, some are sent the DWG, and the audit is the same either way: a PDF plotted from CAD carries the line work, the text and usually the layers, and a DWG carries them natively. Nobody has to ask the architect for a different file.

  • DWG. AutoCAD 2004 and later, read directly. Pre-2004 is named and refused rather than silently read as an empty drawing.
  • DXF. Any CAD export. Room boundaries are measured from the geometry itself, so areas the drawing never printed are still computed.
  • PDF. Vector or scanned. A set plotted from CAD carries no text layer at all — those are read from the line work itself. A plan split across several sheets is stitched back into one continuous layout before anything is counted.
  • Sheets. PNG, JPG and TIFF, plus Excel and CSV schedules. Thirteen formats in all, with OCR on every one that needs it.

Take the sheet apart

A drawing is organised by layer, and most tools throw that away the moment they turn it into a picture. This one keeps it. Open the drawing and switch off everything that is not the thing you are checking — walls, doors, glazing, power, life safety, structure, dimensions, hatching, and read what is left without the rest of the sheet on top of it.

  • Grouped the way you think. A sheet carries thirty-plus layers with names like A-WALL-PATT. They arrive grouped under the system they belong to, so one control turns off walls instead of four.
  • Layer names in any language. Layers drawn in Spanish or French are read as what they are — puertas y ventanas is doors and windows, and anything it cannot read keeps its own name instead of being filed under a guess.
  • PDFs too, where they have layers. A PDF plotted from CAD usually keeps its layers. Those work exactly the same way. A scanned sheet has none, and gets the rendered page instead — the file decides, not a setting.

Counted off the file

Walls, doors, windows, fixtures and equipment counted straight off the symbols the drawing places, grouped by trade, with every line traceable back to the sheet it came from. Each figure is the drawing's own count, not an estimate.

A CAD drawing states its own contents. Every door tag, window tag, fixture and device is a placed block the file can be asked about, so those counts are the drawing's own, with no estimate involved, and the report says which is which, because a count read from the file and a symbol recognised on a scan are not the same kind of fact.

  • Every placed symbol grouped and counted, with its legend description where the sheet has a legend
  • Door, window and room schedules read as tables, including two-sided electrical panel schedules
  • Room areas measured from the boundary when the drawing never printed one
  • Stairs, risers, goings and guards checked against the code you build under
  • Counts grouped by trade — framing, openings, plumbing and the rest
  • Metric and imperial handled automatically
  • Exports as JSON straight into the AI Estimator

The code that governs your site

Estimating tools count what is drawn. This one measures the building and then holds it against the code you build under — 105 checks under Ontario’s pack, fewer where a jurisdiction’s pack is younger, each one citing the article it came from so you can check a finding instead of trusting it. The full set is checked against itself too, so a finding can be taken straight to the consultant. The example shown on the product page runs the 2024 Ontario Building Code.

  • OBC, AODA, fire and zoning checks with clause references
  • Cross-discipline coordination conflicts
  • Scope gaps between the specification and the drawings
  • Severity-ranked so you read the expensive ones first

Jurisdiction is a setting

Eight jurisdictions carry shipped rule coverage across Canada, the United States and England, and the report cites that jurisdiction’s own articles. Ontario’s pack is the deepest, at 105 rules spread over six code categories (OBC, AODA, Ontario fire code, Toronto zoning, the Green Standard and the trade engines: OESC electrical, NFPA 80 door hardware, TIA-568 low voltage), and it is the standard the rest are built to. Younger packs run fewer checks and say so before showing you a finding, so a pass never reads as more than it is. Where a region has no rule set yet, the report says that too, instead of quoting the wrong code at you. See Jurisdictions.

What it could not read

Every audit opens with how much of what it needed was actually on the drawings, and lists every assumption it had to make to finish. A tool that hides its gaps is a tool you have to check twice.

One trade, or all of them

Scope an audit to electrical, structural, mechanical, doors and hardware, low voltage or fire protection before you upload, and get that trade's findings instead of reading past a hundred that belong to somebody else.

Split sets, stitched

A building bigger than a sheet is drawn in parts, and every part overlaps its neighbour across the match line. Blueprint Auditor reads the grid lines two sheets share, works out where each one sits in the same frame, and merges them into one continuous floor layout, so a device drawn on both sides of a match line is counted once instead of twice. It reports how closely the shared grid lines agreed, in millimetres, so the join is something you can check. Tested on sets of twelve sheets in a single plan.

And when it will not stitch them: a floor plan and the reflected ceiling plan of the same floor share a grid exactly, and stitching those together would double every count on the level. So sheets are only joined when they are parts of one plan — same level, same discipline, overlapping without coinciding, and a sheet it cannot place is named beside the total, with the reason, because a silently dropped sheet is a silently missing count.

2D drawings to a 3D model

Open an IFC and it is built from the solids the model already carries. Give it a DWG, a DXF, or a PDF that kept its CAD line work, and the plan is extruded into a 3D model in seconds — walls, openings, floors and stairs, colour-sorted by what they are, with section cuts, orthographic elevations, on-model measurement and PNG or PDF export. An extruded model stands on an assumed storey height, on an assumption the viewer states, and the viewer says so on screen: it is a model of the drawing, not a survey of the building.

Tender risk: the clauses that cost money

The bid documents read for the terms that carry real exposure — bonding, liquidated damages, fair wage, restricted hours, sole-source products — before you commit to a number.

  • Onerous clause detection across the tender package
  • Bonding and insurance requirements surfaced
  • Liquidated damages and schedule exposure flagged
  • Each finding quoted with its source excerpt

Consistency scan and revision compare

  • Consistency and clash scan. Flags internal contradictions — GFA against room sums, counts, ceiling heights.
  • Overlay and revision compare. Pixel-diff two revisions, or plan against as-built, with additions and removals highlighted. See Comparing revisions.

After award, it keeps working

The same engine tracks revision-to-revision drift and builds the deficiency list, so the exposure you priced at tender is the exposure you can still see at closeout.

  • Revision compare — what changed between issues
  • Change-order risk tracked against the original scope
  • Deficiency lists generated and cross-referenced
  • RFI backlog checked against the current drawings

The rest of the job, from the same screen

Drawing register, submittals, RFIs, deficiencies, change orders, minutes and daily logs, on the project the audit ran on.

  • The drawing register — every sheet, its revision and where it stands
  • The RFI backlog — what is open, what blocks the schedule, and who owes the answer
  • Submittals through their review cycle
  • Transmittals — who sent which drawings to whom, and when
  • The correspondence log — notices, delay notices and letters, with response dates
  • The project document folder
  • Project contacts — architect, engineers, inspectors and subtrades
  • Deficiencies by trade, with who found each one and when it is due
  • OBC inspection checklists, saved per inspection
  • Change orders scored for exposure and missing backup
  • Nine days of daily logs, read into manpower, delays and flags
  • Actions pulled out of the minutes, with an owner and a date on each

It grades its own work

Extraction accuracy is scored against drawings with hand-written ground truth, and invented output is charged at the same rate as missed output. Nothing here quotes a number that did not come out of that harness. See Accuracy.

Nothing leaves your workspace

The model runs on infrastructure Marapone operates, and no commercial AI API is in the path. Your drawings are not sent to a third party, and they are not training anybody's model.

What every plan includes

No metering, no per-sheet fee, no feature gate. The working app on day one, and cancel any month from your dashboard if it doesn’t earn its keep. Estimators tell us drawing review runs four to six hours before every trade meeting, and a full day per tender takeoff.

  • The complete program the moment you sign in — nothing to install, no licence key, no machine to provision
  • Unlimited drawings, sheets, projects and machines in your company. No per-sheet or per-project fee, ever
  • Every code check in your jurisdiction’s pack, at no extra cost
  • Thirteen file types, counting each supported DWG release back to 2004 on its own — plus PDF and scanned PDF, DXF, drawing images and Excel or CSV schedules, with OCR built in
  • Scope an audit to one trade, or run all of them
  • Takeoff, costed estimate, RFI, deficiency and change-order lists, as Excel and client-ready PDF
  • Every improvement the day it ships, no version to buy, no upgrade to schedule
  • Fourteen free days first on Field, then cancel any month from your dashboard, no long-term contract

Not included — that’s a customised setup, from $1,500:

  • Fine-tuning on your drawing conventions, title blocks, standard details and past project sets
  • Your own internal design standards, or extending a jurisdiction pack beyond the depth of the shipped reference pack
  • Wiring into Procore, Sage, Bluebeam or your own document management system
  • Bespoke development beyond the eight programs — that is quoted as project work

Buying the product first doesn’t lock you out of a build later — most teams start here, then commission the parts that are specific to them. See custom builds.