Included with every plan

A takeoff workspace that snaps to what's actually drawn.

Draw areas, linear runs and counts directly on the sheet — in the same tender file as your scope of work, so a quantity and the clause that governs it never end up living in two different tools.

Built on the AutoCAD/PlanSwift input model estimators already have in their hands, plus one thing neither offers: it snaps to the drawing's own vector lines, not just points you've already clicked.

Takeoff — Loading Dock SOG
Boundary cut
perimeter follows every notch — 621.2 LF
Area
8,294 SF
Perimeter, boundary cut
621.2 LF
Concrete volume
115.6 m³
An ordinary deduction reads 384.8 LF here — the boundary cut counts what it actually misses
What it does

Four things, done properly.

01

Draw on the sheet

Areas, linear runs and counts, in the same tender file as your scope of work — a quantity and the clause that governs it never drift apart into separate tools.

02

Snaps to the drawing itself

Content-snap reads the PDF's own vector linework directly, so a shape lands on the real edge instead of an eyeballed guess near it.

03

Gets the boundary right

A purpose-built boundary-cut tool rewrites the shape's own edge instead of subtracting a separate cutout, so notches and returns actually count toward the perimeter.

04

Assemblies roll into volume

Split an item by pour, then by thickness within it, and concrete volume computes automatically from each piece's own depth — never one thickness assumed for the whole slab.

Built the way you already draw

The AutoCAD input model, not a new one to learn.

Polar and ortho tracking that locks to 45°/90°, endpoint and midpoint snapping, alignment guides between points you've hovered, and typed exact-distance entry while you draw — the interaction model PlanSwift estimators already have in their hands, muscle memory intact.

We didn't design a new way to draw a rectangle. If you've used PlanSwift, you can sit down and measure without re-learning anything.

Dynamic input, while drawing
Endpoint · Drawing
42'-6" @ 90.0°
Snap name, live segment length, and bearing — the same readout AutoCAD gives you
Items — Cross Dock SOG
Cross Dock SOG2,808 SF · 104.13 m³
└ Pour #11,966 SF · 72.37 m³
16" Area1,569 SF · 406 mm
14" Area397 SF · 356 mm
└ Pour #2842 SF · 31.76 m³
Volume rolls up from each piece's own depth — never one thickness assumed for the whole item
Poured in stages, priced the way it's actually built

Items split the way a slab actually gets poured.

An item can carry sub-items up to two levels deep — the pours it's executed in, and within a pour, the areas at their own thickness. A thickened edge or an equipment pad inside an otherwise uniform slab just states its own depth; everything else inherits from the pour or the assembly above it.

Assemblies carry the floor build-up — thickness, exposure class, curing method, finish — so an item's concrete volume is computed once, correctly, instead of guessed at against a single blended number.

What comes out the other end

Print exactly the sheets carrying takeoff, at their real size.

Print to scale

Sheets export at their true size and orientation — a 34" ARCH-D drawing comes back as a 34" ARCH-D drawing, not shrunk and rotated onto Letter paper.

CSV export

Every item and sub-item, with both cubic yard and cubic metre columns, ready for a spreadsheet read away from the app.

Same file as the scope

Takeoff lives in the same tender as the extracted scope of work — no separate project to open, no separate login, nothing to keep in sync by hand.

What TH Takeoff doesn't do

No pricing, no cost database

Quantities only, deliberately — SF, LF, EA, m³. No unit rates, no assembly pricing. Where you price the job stays exactly where it already lives.

New, not proven over a decade

PlanSwift and Bluebeam have years of real-world edge cases behind their tooling. TH Takeoff is newer — judge it against your own drawings, not our word.