Bluebeam Revu does not review shop drawings; it is a PDF markup and collaboration tool, the place where a checker draws the clouds, writes the comments and applies the stamp. The review is the reading of the sheets and Bluebeam is the pen; Plumb does the reading across 14 documentation categories and returns a marked-up PDF that opens in Revu like any other PDF, within 24 hours.
What Bluebeam does
Revu is the pen. A reviewer opens the set, clouds what is wrong, drops a callout with the comment, measures, stamps the cover and sends it back. The markups list keeps every cloud and comment in one table that can be sorted and exported. A Studio Session puts several people on the same set at once. Overlay and compare show what moved between one revision and the next.
Every one of those is a way to record a judgment or move it between people. None of them is the judgment. Revu will cloud that a dimension changed between Rev 1 and Rev 2; it will not say that the dimension disagrees with the one on the next sheet. It will hold a stamp; it will not know that the stamp says "exceptions noted" and no exceptions are listed. It will not read that the elevation calls the blades 12 Ga. and the detail on the same sheet calls them 16 Ga., or that a plate line in the BOM has no grade, or that a weld symbol has no size. Someone reads the set and decides those things. Then they pick up the pen.
What a documentation review produces
The reading has a fixed output, whoever does it. A finding is one thing wrong, tied to one spot: the sheet, the callout or grid cell on that sheet, what the drawing says, what it should say or fails to say, and how much it matters. A set of findings is a log: one row each, sortable by sheet and by severity, so the shop can assign them and close them.
Plumb's output is that, in three forms. The marked-up PDF is the original sheets with a numbered bubble at each finding, an appendix of detail cards at the back, and a summary; the number on each bubble links to its card, and the card links back to the sheet. The Excel comment log has one row per finding with sheet reference, severity, description and a recommended action. The online viewer shows the same findings sheet by sheet and lets the shop flag or remove one. Each finding carries one of five severities (Critical, Major, Minor, Comment, Advisory) and the PE-Review-Required flag or not. Findings the engine cannot back with the drawing are left out before delivery, so the log is shorter and each row is defensible.
On a louver package in the graded answer keys, the output looked like this: a bubble on the detail's gauge callout, with the card reading that the elevation calls 12 Ga. and the detail calls 16 Ga.; a bubble on the drawing index, with the card reading that the REV column is blank for every sheet; a bubble on an anchor callout, with the card reading that the length is given and the embedment is not, flagged PE-Review-Required. On a structural steel package checked against its spec: a bubble on a splice plate line reading A36, with the card citing the spec section that requires A572 Grade 50 for plate. The sample review is the louver package, delivered as a customer would receive it.
Plumb marks every finding on the sheet it came from, and no change to the review engine ships until it scores at least as well as the last one against hand-graded answer keys from real fabrication packages.
How it fits a Bluebeam workflow
The package is uploaded to Plumb as the PDF the shop already has. Within 24 hours the marked-up PDF, the Excel log and the viewer are ready. The PDF is downloaded and opened in Revu.
It is a PDF, so nothing is installed and nothing is converted. The bubbles and leaders are on the page, the bubble numbers link to the detail cards, and the reliance notice rides on every page. The checker works through it the way they work through any set: clouds the findings they agree with, adds their own, writes "no change" next to the ones they do not, and stamps. Those Revu markups sit on top; Plumb's bubbles stay underneath. If the office runs Studio Sessions, the marked-up PDF goes into one like any other PDF.
The Excel log is the running list. The checker's own columns, assigned to and closed on, go next to Plumb's, and the log goes to the detailer with the Revu file. The online viewer is the quick read before any of that: a finding the shop decides is not a finding gets flagged or removed there, before the log reaches the team.
There is no Plumb plugin for Revu and no integration between the two. None is needed for any of the above, and Plumb does not claim one.
Inside that workflow, Plumb does not diff two revisions; Revu's compare does that. It does not read CAD; it reads the PDF. It does not write the shop's markups; the checker does. How it works walks the upload to delivery.
When a shop still needs a checker and an engineer
Always, for two different reasons.
The checker, because Plumb is a documentation-review layer, not a checker. It reads for missing, conflicting, incomplete and unclear information across the 14 categories and reports what it finds. The checker decides what to do with each finding, writes the response, and signs the drawing. The recommended action in the log is a suggestion, and the viewer exists so the checker can overrule it.
The engineer, because some findings are engineering questions and Plumb is not an engineer. Anchor embedment, whether a redlined bearing-plate setback is acceptable, which code year governs a submittal: on the graded packages, each of those came back as a finding that said only that the drawing was silent or that two things disagreed, flagged PE-Review-Required. The disposition belongs to the licensed professional with authority over that scope. Plumb does not approve, certify or stamp anything, and the notice on every page of the deliverable says so.
The division of labor: Plumb reads, Revu records, the checker decides, the engineer rules on the flagged items. An Anytime Review is $25 for 10 sheets, then $2.00, and covers Tier 1 — Buildability Review and Tier 2 — Submittal Readiness Review; Tier 3 — Specification Correspondence Review needs the Shop or Studio plan, on the pricing page.