Electrical takeoff
in Bluebeam.

Bluebeam Revu is the PDF most of us live in. It opens plan sets faster than anything, marks up clean, and the Studio side keeps a crew on the same drawings without emailing files around. So it's no surprise estimators reach for it to do takeoff — and for measuring and counting, it genuinely earns the reputation. What follows is how I run an electrical takeoff in Revu start to finish, the mistakes that cost me hours early on, and the point where you should stop pretending it's an estimating system.

1. Set up the session

First decision: Studio Session or local file. If you're the only one touching the set, work local — it's faster and you don't need a connection. The second another estimator or a PM needs eyes on the same markups, put it in a Studio Session so everyone's counts live in one place and nobody overwrites anybody. Studio Projects are for storage; Sessions are for the live takeoff.

Before you touch a measurement, organize the E-set. Pull the electrical sheets into a sensible order, and label them so the Markups List and thumbnails make sense later. Use AutoMark (Document → Page Labels) to read the sheet number out of the titleblock region and label every page in one pass — E2.01, E2.02, and so on — instead of hand-typing forty sheets. Good page labels are not cosmetic; when you export quantities by sheet at the end, this is what makes the report readable.

2. Calibrate every sheet

This is the step people rush and pay for. Grab the Measure tool, hit Calibrate, and draw your line along a known dimension — a dimension string on the plan, the "10'-0"" callout on a grid, anything you can read exactly. Type in the real-world length and Revu sets the scale.

Two things I learned the hard way. First, calibrate every sheet — do not assume the whole set is the same scale. Power plans, lighting plans, and enlarged rooms are routinely different scales, and a single uncalibrated sheet quietly poisons every conduit run on it. Second, the classic blunder: calibrating against the wrong viewport. On a sheet with a key plan or a detail at a different scale, if you draw your calibration line across the little detail instead of the main plan, every measurement on that page is off. Pick a long dimension on the main plan view and confirm a second known dimension reads back correctly before you trust it.

If a scanned plan is skewed or stretched — common with old as-builts — set a separate X and Y scale rather than forcing one. Revu lets you calibrate horizontal and vertical independently, which keeps a 100-foot run from reading 103 because the PDF got squished on one axis.

3. Build a custom electrical tool set

Do not count off the generic markups. Build a real electrical tool set in the Tool Chest once and reuse it on every job — this is the single biggest time-saver in Revu.

For devices, make a Count tool per fixture type: a unique symbol and color for each, so a 2x4 troffer looks different from a downlight, a duplex receptacle from a quad, a single-pole switch from a three-way. Give each one a clear Subject (the field the Markups List groups by) and a sensible label. For runs, make linear (Polylength) tools for conduit and feeders, again with distinct subjects — "3/4" EMT", "1" EMT", "Feeder – 3#4" — and matching colors so a glance at the plan tells you what's what.

The subject naming is what makes the export usable. If your subjects are tidy and consistent, the Markups List filters and sums cleanly. If they're sloppy, you'll spend the export step untangling them. Once the set is built, save it and share it — export the .btx and drop it in a shared location (or push it via Studio) so the whole team estimates against identical tools. A shared tool set is the difference between two estimators' takeoffs reconciling and not.

4. Count devices with Count measurements

Now the actual counting. Work legend-first: open the lighting fixture schedule and the symbol legend before you click anything, and match each plan symbol to its type designation — A, A1, F2, whatever the schedule calls it. Counting fixtures by type off the schedule is the only way the numbers mean anything when you price them, because Type A and Type A1 might be the same housing with a different lamp and very different cost.

Pick the right Count tool from your tool set and click each fixture; Revu tallies as you go and shows a running count. Do the same for receptacles and switches with their own tools. Pace yourself one type at a time across the whole area rather than jumping symbols — your eye stays trained and you miss fewer.

Use Spaces to keep counts honest per room or area. Draw a Space around each room (or each floor on a multi-level plan) and the markups inside it get tagged to that Space. Now your Markups List can break the count down by location instead of giving you one giant lump — invaluable when the GC asks for the second-floor scope only, or when you're checking your count against the panel schedule room by room.

5. Measure conduit & feeder runs

For homeruns, branch conduit, and feeders, use the Polylength measurement and trace the run segment by segment. The plan only gives you the horizontal path, so the real skill is the vertical: drops to receptacles, rises to lighting, the climb up a wall to a panel. Don't eyeball these into the length — handle them as adders in custom columns (more on columns next), so the horizontal trace stays clean and the rise/drop math is explicit and checkable. Set per-segment height or slope adders the same way; a sloped run between elevations is just horizontal length plus a vertical delta you record in a column.

One temptation to resist: Dynamic Fill. It's brilliant for flooding an enclosed area and getting a square-footage measurement, but conduit isn't an area — it's a path with quantity-bearing endpoints and adders. Keep conduit and feeders on real Polylength measurements you traced, not auto-filled regions. You want every linear foot to be something you can point at on the plan.

6. Custom columns for material math

This is where Revu goes from "markup tool" to "light takeoff engine." In the Markups List you can add Custom Columns — numeric columns and, crucially, formula columns — that do math on your measurements automatically.

Use them to turn raw quantities into material. A formula column can multiply each Polylength by a factor for waste, add your rise and drop adders, or convert a run length into wire linear feet by multiplying conductors per run. Another column can derive box counts from device counts. Numeric columns let you stamp a unit cost or a length adder against each markup. It's not assemblies — you're wiring the relationships up by hand — but once the columns exist on your tool set they travel with it, and the Markups List sums them per subject for free.

7. Markups List → summary export

Everything you've clicked lives in the Markups List. Open it, and filter by Subject to isolate one device or run type at a time — this is why the subject naming in step 3 mattered. Confirm the totals look sane against your gut and the panel schedule before you trust them.

Then export. The Markups List Summary writes out to CSV or XML (also PDF if you just want a record), and CSV drops straight into your Excel estimate where your labor units and pricing live. Save your filter setup as a filter profile so the next electrical job opens with the same view instead of you rebuilding columns and filters every time. Between a shared tool set and a saved filter profile, the per-job setup tax drops to almost nothing.

8. Revisions with Compare or Overlay

Addenda always come. When a new set lands, don't re-count from zero. Use Compare Documents to have Revu diff the two PDFs and auto-cloud what changed, or Overlay Pages to stack revisions in different colors so added and removed work jumps out visually. Compare is better for clean dimensional changes; Overlay is better when sheets shifted or rescaled. Either way, you cloud the deltas, then re-count just the changes against your existing markups — add the new fixtures, void the deleted runs — and re-export. That's how you keep a bid current through three addenda without losing a night each time.

Where Revu hits its ceiling for electrical

Here's the honest part. Bluebeam is excellent at what it is — a PDF markup and measurement tool — and everything above is real, repeatable work. But it is not an estimating database, and electrical estimating is where that gap bites hardest.

• No native assemblies. Click a fixture in Revu and you get one count, full stop. You don't get the whip, the box, the connectors, the conductors, and the labor that come with it. You rebuild that relationship by hand in custom columns or downstream in Excel — every job.
• Every symbol is still hand-clicked. There's no real automation. VisualSearch can find some matching symbols on one page, but it doesn't read the schedule, doesn't reliably separate types, and doesn't carry across sheets — so you're clicking every device on every sheet, all over again on each revision.
• No panel-schedule intelligence. Revu can't read a panel schedule, won't reconcile your device count against connected loads, and has no idea what a feeder feeds. The drawing's most structured data is invisible to it.

None of that is a knock on Bluebeam — it's just not what the tool is for. But it's why a careful electrical takeoff in Revu still eats hours, and why the count is only as good as the estimator's stamina at midnight.

The work Revu makes you do by hand — read the schedule, separate types, attach the wire and box and labor, re-count every revision — is exactly the work an AI takeoff does for you.

That's the whole idea behind Pilars. Upload the same plan set and the spec book, and the AI reads the fixture schedule, counts devices by type, traces conduit and feeders, attaches assemblies, and flags the code and spec scope that wrecks bids — then hands you quantities you can price, not a blank canvas to click on. It's cloud, it runs on any machine, and it's $100 per trade with no per-seat fees. If you want the markup discipline of Revu without the hand-counting tax, that's where to look.

Questions estimators actually ask