How to Do a Takeoff in PlanSwift, Step by Step

Skip scale calibration in PlanSwift to save two minutes, and every measurement after it comes out wrong by the same margin. That single step decides more about a PlanSwift takeoff than any other. The full process runs like this: import the plan, calibrate against a known dimension, set up conditions for each material, then measure with the area, linear, and count tools before exporting quantities to a report.

This walkthrough covers the whole sequence, from opening a blank digitizer to exporting a finished takeoff: page setup, scale calibration, building conditions, running area, linear, and count takeoffs, using assemblies to move faster, and the habits that throw off a quantity report without anyone noticing until it's too late. We run PlanSwift on real projects every week. None of this is pulled from a manual.

Getting Started: Importing Your Plan Set

Open PlanSwift and start a new project by importing your plan set, usually a PDF, though PlanSwift also handles image files and some CAD formats depending on your version. Each sheet imports as a separate page inside the project, so a 40-page commercial set becomes 40 pages you can flip through inside the digitizer.

Before you touch a single tool, take a minute to look through the full set. Note which sheets carry the scopes you're pricing, floor plans for area work, details for assemblies, schedules for count items like doors and fixtures. Knowing where everything lives saves you from hunting mid-takeoff, and it's the kind of prep step a lot of beginners skip.

Name your project file something that actually means something six months from now. "123 Main St - Concrete Takeoff - Rev 2" beats "Untitled1" every time you or a teammate has to reopen it.

Calibrating Scale: The Step That Decides Everything Else

This is the step that makes or breaks the whole takeoff. PlanSwift measures based on pixels on your screen, not real-world units, until you tell it what scale the drawing is at. Skip calibration, or calibrate against the wrong dimension, and every area, linear foot, and count you pull afterward is off by whatever percentage that error introduced.

Here's how it works in practice. Find a known dimension on the plan, a dimension string is best, but a standard door width (3 feet is common) works in a pinch if nothing else is marked. Use PlanSwift's calibration tool to click both endpoints of that known distance, then enter the actual real-world length. PlanSwift back-calculates the scale for that page from those two points.

Do this for every page individually. Scanned or rasterized plan sets sometimes have sheets printed at slightly different scales, or a sheet gets stretched during scanning, and calibrating once and assuming it carries across the whole set is a mistake we catch in review constantly. If a sheet has a printed scale note (1/4" = 1'-0", for example), you can enter that directly, but always verify it against an actual dimension on the page first. Printed scale notes are occasionally wrong, especially on plans that went through a few rounds of revisions.

Setting Up Conditions Before You Measure

A condition in PlanSwift is a saved definition, material type, unit of measure, color, and pricing info if you're using it, that you apply every time you measure that item. Concrete slab, 2x4 wood framing, ceramic tile, exterior door, each of these gets its own condition before you start clicking on the plan.

Set conditions up by CSI division if you're running a multi-trade takeoff. It keeps your project organized and makes it obvious later which numbers belong to which trade when you're pulling a report. Give each condition a name that means something, "4in Concrete Slab on Grade" tells you more six months later than "Condition 12" ever will.

You can build conditions one at a time as you go, but setting up your full list before you start measuring is faster in the long run. Switching between tools mid-takeoff to create a condition you forgot breaks your rhythm and increases the odds you'll mislabel something.

• Area conditions for things measured in square feet: slabs, flooring, drywall, roofing.
• Linear conditions for things measured by length: baseboard, conduit, framing members, curb and gutter.
• Count conditions for discrete items: doors, windows, fixtures, outlets, light fixtures.

Running an Area Takeoff

Select your area condition, then trace the boundary of the space you're measuring directly on the plan. PlanSwift calculates square footage automatically based on the calibrated scale, and the traced area highlights in the condition's assigned color so you can see at a glance what's been covered.

For a slab or flooring takeoff, trace the actual floor area room by room, or the whole footprint if you're pricing a single continuous pour. For roofing, trace each roof plane separately if the pitch varies, since PlanSwift measures the flat plan area, and pitched surfaces need a separate pitch multiplier applied to get true roof area.

Zoom in before you trace. Working at a zoomed-out view feels faster, but it's exactly how you clip a corner or miss an alcove. A few extra seconds zoomed in on tricky boundaries saves a lot more time than the rework of catching the error during review.

Running a Linear Takeoff

Linear takeoffs work the same basic way, select the condition, then click along the path you're measuring, wall centerlines for framing, pipe runs for plumbing, conduit routes for electrical. PlanSwift totals the linear footage as you go and shows a running count in the condition list.

Watch for overlaps here. It's easy to double-trace a wall section when you're moving fast between rooms, especially on a plan with a lot of jogs and offsets. PlanSwift's undo function handles quick corrections, but a second pass reviewing your linear takeoffs against the plan catches overlaps a first pass alone won't.

For framing takeoffs specifically, decide upfront whether you're measuring centerline or face of stud, and stay consistent. Mixing methods across a project is a quiet way to introduce error that's hard to trace back later.

Running a Count Takeoff

Count takeoffs are the simplest tool in PlanSwift, and also where errors from working too fast show up most. Select your count condition, then click each instance of the item, doors, windows, electrical outlets, plumbing fixtures, on the plan. Each click adds one to the running total.

Cross-reference against the schedule whenever the plan set has one. Door and window schedules exist for exactly this reason, and comparing your PlanSwift count against the schedule total is a fast, reliable check before you move on. If the numbers don't match, figure out why before finalizing the takeoff, not after the estimate has already gone out.

Use different markers or colors for different count conditions on a dense sheet. A mechanical or electrical plan with dozens of overlapping symbols gets hard to track visually if every count condition looks the same on screen.

Using Takeoff Assemblies to Speed Things Up

Once you've built conditions for individual materials, PlanSwift lets you group several of them into a takeoff assembly, one click that applies multiple conditions to a single measurement. A wall assembly might bundle framing, sheathing, insulation, and drywall into one linear takeoff instead of four separate passes.

Assemblies pay off most on repetitive items: standard wall types that repeat across a floor plan, door and window units with hardware and trim bundled in, or roofing systems where deck, underlayment, and finish material always travel together. Set the assembly up once, then apply it everywhere that wall type or door type appears.

The tradeoff is upfront setup time. Building an assembly takes longer than creating a single condition, so it only makes sense when that combination repeats enough times on the project to earn back the setup effort. For a one-off item, a standard condition is faster.

Exporting Your Takeoff to a Report

Once your conditions are measured, PlanSwift generates a report summarizing every condition, its total quantity, and unit of measure. Most estimators export this to Excel for pricing, since that's where labor rates, material costs, and markup usually get applied.

Check the report against your conditions list before sending it anywhere. Confirm units of measure match what you expect (square feet versus square yards trips people up more than you'd think), and scan for any condition that shows a suspiciously round number or a zero, both are usually signs something got missed or double-counted.

Label your export file with the project name, revision number, and date. Estimates get revised, plans get updated, and a report file sitting in a folder without version info is a problem waiting to happen on a project with more than one round of changes.

Mistakes That Quietly Wreck a PlanSwift Takeoff

Most PlanSwift problems aren't the software's fault. They come from how it gets used under a deadline.

Skipping or rushing scale calibration tops the list, by a wide margin. A takeoff built on a miscalibrated page looks complete and reads clean, right up until someone compares it against actual field measurements or a competing bid.

Inconsistent condition naming causes trouble on bigger projects with multiple people touching the same file. "Concrete" and "Conc Slab" and "4in Slab" all referring to the same thing scatters your quantities across three line items instead of one clean total.

Working too fast on count takeoffs without cross-checking against a schedule is a quiet source of missed items, especially on dense mechanical or electrical sheets where symbols overlap.

Not reviewing layer visibility before finalizing a takeoff can mean measuring against a superseded revision that's still showing on screen underneath the current one. Confirm you're working off the latest sheet, every time.

Forgetting waste factors on materials that need them, tile, roofing, flooring, rounds out the list. PlanSwift gives you the raw measured quantity. Applying the right waste percentage on top of that is still the estimator's job.

Our guide on what a takeoff actually is in construction covers the fundamentals this tutorial builds on, useful background before opening PlanSwift for the first time. Once quantities are pulled, they feed straight into the next phase, which our breakdown of the construction estimating process walks through in full. And if the deadline's too tight to run this yourself, our quantity takeoff services team handles the full PlanSwift workflow on residential, commercial, and industrial plan sets every week.

Frequently Asked Questions

Bottom Line

PlanSwift handles the measuring. Getting a usable takeoff out of it still comes down to calibrating scale correctly, setting up clean conditions before you start, and staying consistent sheet to sheet. Get those pieces right and the software does exactly what it's built for, fast, accurate quantities you can price with confidence.

Running PlanSwift takeoffs daily is exactly what our team does. Blaze Estimating covers every CSI division across residential, commercial, and industrial work, all 50 states, flat-fee pricing. Send us your plans. We'll handle the rest.