Bluebeam and Excel vs estimating software: the join that leaks
Quantity Link moves a total into a cell. The revision, the quote's basis and the exclusions stay behind, and an addendum shows what that costs. Estimator+ keeps the quantity and its price in one live tender.
In short
- Bluebeam measures and Excel prices, and tenders leak money at the join between them. Estimator+ gets rid of that join.
- Quantity Link sends a measurement total into a cell, and that's about it. The drawing revision, the basis each quote was priced on and the exclusions stay behind in other files.
- An addendum is where you feel it. The linked cell updates, but the lump sum, the packages already out with subbies and the qualifications just sit there until someone goes and finds them.
- In Estimator+ the quantity, its drawing revision, its quote and its exclusions sit in one live tender. The AI does the takeoff from your own tender folder, and it processes the addendum too.
So where's the leak, then?
Bluebeam measures, Excel prices, and the money leaks at the join between them. That join is exactly what Estimator+ removes.
"We've already got Bluebeam and Excel, why would we need estimating software?" Fair question, and both tools are good at what they do. Revu is a good measuring and markup tool. A well-kept workbook prices a job properly too, with your own rates, formulas and comparison sheets.
The trouble is the hand-off. Each file holds part of a number's story, and a person carries the rest of it between them. On a commercial tender most of the price comes from subcontractors, their quotes turn up qualified, and the drawings change in the final week. Every one of those lands right on a join.
Let's follow one wall into cell D27
Here's an example. Wall type W3: steel stud with plasterboard both sides, 3.0 m high, on sheet A-201 Revision B. The figures are invented and all ex GST.
- You measure the W3 runs in Revu as polylengths (Bluebeam's multi-segment lengths). The Markups List totals them at 412.5 m.
- Quantity Link, which comes on Revu's Complete and Max plans, sends that total into cell D27 of your internal walls sheet. In Bluebeam's words, it transfers "measurement totals from a local PDF to an Excel spreadsheet in real-time". Handy.
- A formula multiplies it by the 3.0 m height, so you get 1,237.5 m². A check rate of $62 per square metre gives you $76,725.
- The plasterer's quote arrives as a PDF. Lump sum, $71,800, for "W3 partitions as per A-201 to A-204 Revision B, excludes bulkheads".
- You type the quote into a comparison sheet. The exclusion goes in a cell comment, and a note goes into the qualifications document, which is a separate file again.
By step five that one quantity has three homes. The geometry sits in the PDF. The number sits in D27. And the basis the plasterer actually priced on is split between a comment and a separate document.
What D27 can't tell you
Nothing in those steps is a mistake. You'd probably do exactly the same. The leak is in what each file can't see.
- A linked cell holds a total. Bluebeam describes Quantity Link as transferring "measurement totals", and the drawing revision and the segments behind that total aren't among what it says it transfers.
- New wall types wait for a person. Bluebeam's own support page says "your filtering criteria need to be changed manually", so a new type like W3a stays out of the workbook until somebody edits the link.
- A lump sum is priced against a moment. It covers the quantity on the drawings it was given against, and nothing in the workbook says which revision that was.
- Exclusions live in comments, and that bulkhead exclusion depends on whoever typed it remembering it's there. Which is a bit much to ask late on a Thursday.
Then Addendum 01 lands
Picture it. There's a week to go, and Addendum 01 issues A-201 Revision C. A store off the corridor gets smaller, and two of your W3 runs get shorter.
In Revu, Batch Slip Sheet (also a Complete and Max feature) swaps the superseded pages for the revised ones and can carry the markups across. You edit the two runs, the total drops to 398.0 m, and Quantity Link updates D27. The area becomes 1,194.0 m² and the check price $74,028. So far, so good.
The link reaches the measured quantity, though, and nothing else.
| What changed | Updated by the link? |
|---|---|
| The measured quantity | Yes |
| The plasterer's lump sum, priced on Revision B | No, someone has to find it |
| The packages already sent to the other plasterers | No, someone has to find them |
| The qualifications document | No, someone has to find it |
| The bulkhead exclusion in a cell comment | No, someone has to find it |
To be fair, teamwork inside each tool is well looked after. Bluebeam Studio Sessions let a team mark up the same PDF together, and Excel's co-authoring shows your colleagues' changes "in a matter of seconds".
The join between the tools is still a person, though, in the busiest week of the tender. And a missed join shows up after award, when the plasterer's price turns out to cover Revision B rather than the walls being built.
When the two of them are plenty
For a small job with one estimator, one trade and no revisions expected, Bluebeam and Excel do the job. We're not going to pretend otherwise.
But every extra trade adds a join someone keeps by hand, and so does every extra quote, every extra person on the job and every addendum. Past a point, your last week goes on keeping files in agreement, and the risk sits in whichever join nobody got round to checking.
The same wall in Estimator+
We reckon there's a better way. Estimator+ keeps the quantity, its drawing revision, its quote and its exclusions in one live tender, so there's no join to keep.
It starts in your own tender folder. Claude or ChatGPT, running in its desktop app on your plan, reads the documents where they sit, creates the tender in Estimator+ and uploads A-201 to A-204 as sheets. The spec and schedules stay on your drive, read there for context.
Then the AI does the takeoff. It never types a quantity. The W3 runs are lines on A-201, and Estimator+ works out the wall area from those lines, the 3.0 m height and the sheet's printed scale, which is proven on the sheet itself. The line reads 1,237.5 m², and you can see every run it's made of. Rather draw it yourself? The manual tools are there.
The AI files the plasterer's quote into Quotes straight from the PDF. The $71,800 lump sum stays fixed to the 1,237.5 m² it was priced on, and "excludes bulkheads" sits on that price, where it belongs. The other plasterers' rates follow the live quantity. No hunting through cell comments.
Now Addendum 01. You drop it in the tender folder, say Addenda/Addendum 01, and tell the AI. It reads it, matches Revision C to Revision B, uploads the new sheet and supersedes the old one, so the takeoff and the subbies work off the current set.
The two shorter runs are measured on Revision C and the line reads 1,194.0 m². The rates move with it. The lump sum holds at $71,800 against the 1,237.5 m² it was priced on, so your call to that plasterer starts from a known 43.5 m² difference. And Sendout adds a revision note for the plastering trade on the subbies' links, so the plasterers know Revision C is out.
Is Excel still in the picture?
Sure is. You can export BOQs with marked-up plans, in PDF and Excel, for subbies to price from. The Excel files carry live formulas, and subcontractors can price inside the sheet. The submission exports to Excel too, alongside the branded PDF.
So whoever in the office loves a spreadsheet still gets one. It just isn't where the tender lives anymore. Our posts on tender addenda and revisions and tender exclusions and qualifications dig into those two joins further.
Got a tender with an addendum in it? Bring it along and book a demo, and watch the quantity and its price move together.
Frequently asked questions
Can Bluebeam send measurements to Excel?
Yes, it can. Bluebeam's Quantity Link, on its Complete and Max plans, transfers measurement totals from a local PDF to an Excel spreadsheet in real time. The catch is that Bluebeam notes the filter criteria have to be changed manually, so a new markup type needs the link edited before it reaches the workbook.
Why would I move from Bluebeam and Excel to estimating software?
Because the money leaks at the join between the two. When a number crosses over, the revision it came from, the basis each quote priced and the exclusions stay behind in other files. In Estimator+ the takeoff, quotes, exclusions and addenda are one live tender, so a change reaches the price with its reasons attached.
What happens to a lump-sum quote in Estimator+ if the quantity changes?
A lump sum stays fixed to the quantity it was priced on, while a rate follows the live quantity. So an addendum moves the rate-based prices and leaves each lump sum as quoted, and you can see the difference you need to raise with that subcontractor.
Can I still export to Excel from Estimator+?
Yes. You can export BOQs with marked-up plans in Excel for subcontractors, with live formulas they can price inside, and the submission exports to Excel as well as a branded PDF.
Can Estimator+ do the takeoff from my own drawings folder?
Yes. Claude or ChatGPT, in its desktop app, connects to the tender folder on your computer, uploads the measurable drawings as sheets and does the takeoff. Specs and schedules stay on your drive, and when an addendum lands in the folder, the AI supersedes the old drawings with the new ones.
Sources
Read 2 October 2026: Bluebeam plans, Bluebeam: Improve takeoffs with Quantity Link, Bluebeam: Transfer markups with Batch Slip Sheet, Bluebeam: Five things you may not know about Studio Sessions and Microsoft: Collaborate on Excel workbooks at the same time with co-authoring. Estimator+ is our product and is independent of Bluebeam and Microsoft; product names identify the products discussed.