Bluebeam Revu

Bluebeam Revu is the tool most UK quantity surveyors and estimators actually spend their day in. PDF markup, measurement, drawing comparison, and a shared review session that works. It is not really an AI tool and it is worth saying so plainly. Bluebeam has automation features, some of them genuinely clever, and the marketing increasingly calls them AI. Most of what makes Bluebeam valuable is good, mature software engineering rather than machine learning. That is not a criticism. For measurement work, deterministic beats clever. WHAT IT IS ACTUALLY FOR Measurement and takeoff. Calibrate a drawing to a known dimension, then measure lengths, areas, volumes and counts directly on the PDF, with the quantities dropping into a table you can export. For a QS pricing off drawings this is the core function and it is what justifies the licence. Drawing comparison. Overlay Rev C against Rev D and every change is highlighted. If you have ever missed a drawing change that arrived in a batch of forty and found out on site, you already know what this is worth. This one feature has probably prevented more variations arguments than anything else in the software. Markup and shared review. Multiple people marking up the same drawing set, with a searchable markup list. Better than emailing PDFs back and forth, which is still what a lot of the industry does. Snagging. Markups on a drawing become a snag list with locations, exported to a report. WHERE THE AUTOMATION HELPS Visual search. Pick a symbol, say a double socket, and it finds every instance across the drawing set and counts them. On an electrical takeoff this turns an hour of clicking into a couple of minutes. The important caveat: it finds what matches visually. It does not know what a socket is. Change the symbol between drawing sets, or run it across a set with inconsistent conventions, and it will quietly under-count. Always spot-check a sample against a manual count on a page or two before trusting a total. Automatic quantity counting and dynamic fill for irregular areas. Both save real time on complex shapes. Batch operations across hundreds of sheets. Deeply unglamorous and it is where the hours go. WHAT IT WILL NOT DO It will not read a specification and tell you what to measure. Measurement rules are your job, and if you are measuring to NRM2 the tool has no opinion about whether you have applied it correctly. It will not catch a calibration error. This is the one that actually costs money. Calibrate to the wrong scale and every quantity you take off is wrong by a consistent factor, and the output looks completely normal. Calibrate against a known dimension on every sheet, not just the first, because drawing sets are not always consistently scaled. It will not measure from a scanned or poor-quality PDF reliably. Vector PDFs exported from CAD behave well. A scan of a drawing behaves badly, and a photograph of a drawing behaves worse. It is not a cost database. It gives you quantities. Rates are yours. WHAT IT COSTS Bluebeam moved to a subscription model, with tiers roughly from around £200 to £400 per user per year depending on the tier and whether you need the full measurement and comparison feature set. The higher tiers are where the takeoff and Studio collaboration features sit, which for a QS is the whole point. Check current pricing directly, since the tiering has changed more than once and UK pricing moves with the exchange rate. For a working QS or estimator it is one of the easier software cases to make, because the measurement time saved covers it inside a month. BLUEBEAM VERSUS THE ALTERNATIVES Against Adobe Acrobat, Bluebeam wins comfortably for construction because of measurement and comparison. Acrobat is a general PDF tool. Against dedicated takeoff packages such as Cubit or CostX, it depends what you need. Those are built as estimating systems with rate libraries and BoQ generation. Bluebeam is a markup and measurement tool that exports to your spreadsheet. If your estimating already lives in Excel, Bluebeam fits how you work. If you want an integrated estimating system, look at the dedicated packages. Against measuring from a model, if you have a reliable federated model, quantities from the model beat quantities from drawings. In UK practice, on refurbishment and on a lot of mid-size new build, you are still measuring from drawings, which is why Bluebeam remains the default. FREQUENTLY ASKED QUESTIONS Does Bluebeam actually have AI, or is that marketing? Both, and the honest split matters. Features like visual search and automatic count use pattern recognition, which is reasonably described as AI. The measurement engine, comparison and markup tools are conventional software. Very little of Bluebeam is a language model, so if you are expecting something that answers questions about your drawings in plain English, that is not what this is. What it is instead is a mature measurement tool with some smart automation, and for takeoff that is the more useful thing. Can I trust automated quantity counts? Trust them after you have checked them, and check by sampling. Take one or two representative sheets, count manually, and compare against the automated total for those sheets. If they match, the automation is reading your symbols correctly and you can rely on it across the set. If they do not, you have learned that before pricing rather than after award. The failure mode is silent under-counting where a symbol convention changes partway through a drawing set, and no software will warn you about that. Is it worth it for a small QS practice? For anyone measuring from drawings regularly, yes, and it is one of the clearest software cases in a QS practice. The drawing comparison feature alone tends to pay for the licence the first time it catches a revision change you would have missed. The case is weaker if you mostly work from models or from bills prepared by others. Does it work on a tablet on site? There is an iPad version and it is decent for markup and snagging, less suited to serious takeoff. Most people use the desktop for measurement and the tablet for site markup, syncing through Studio. Worth checking current feature parity, since the mobile version has been catching up. What is the single most common mistake? Calibration. Measuring a whole drawing set that was calibrated against the wrong dimension, or assuming every sheet in a set shares one scale when it does not. The quantities look entirely plausible and they are uniformly wrong. Calibrate per sheet against a dimension you can verify, and if a sheet has no printed dimension to calibrate against, that is a query to the design team rather than a guess.