How to Build a Bluebeam Tool Chest for Drawing Review

A Bluebeam Tool Chest tool set for drawing review is a saved group of markups where each tool already carries the right subject, color, line style, and layer. Reviewers click Coordination Conflict or Code Question instead of drawing a cloud and typing the label, so the Markups List sorts into a clean issue log at the end.

To build one in Revu 21: open Tool Chest, choose Manage Tool Sets, then Add and Add New. Draw each markup once, set its properties, right-click it, and pick Add to Tool Chest. Export the set as a .btx file from its Properties menu and share it on a network drive or in a Studio Project.

Which markup tools belong in a drawing review tool set?

Fifteen tools cover most review findings. The colors follow the convention in how to mark up PDF drawings for coordination: red for conflicts, yellow for questions, orange for missing or field-verify items, blue for information and RFIs, green for verified. The subject is the field that drives sorting in the Markups List, so keep it short and identical across the team.

How do you create a tool set in Bluebeam Revu 21?

These steps follow Bluebeam's Revu 21 Tool Chest guide and custom markup instructions, checked November 1, 2026.

• Open the panel with Window > Panels > Tool Chest.
• Select Tool Chest > Manage Tool Sets > Add > Add New. Name it something like "Drawing Review 2026", tick Show In All Profiles, and choose where to save the .btx file. Save it to the shared folder now if you plan to share it.
• Open any project PDF and draw the first markup, for example a Cloud+ for Coordination Conflict.
• In the Properties panel, set Subject, color, line width, line style, and Layer. Subject is the one field you cannot skip.
• Right-click the markup, choose Add to Tool Chest, and pick your new tool set.
• Repeat for the other 14 tools, then delete the sample markups from the PDF.
• Open the tool set's Properties and choose Export to write a backup .btx.

How do you share a Bluebeam tool set with your team?

Share it from a network drive if you want one version for everyone. Bluebeam's share tool sets article explains that a set added with Add Existing from a network location updates for every user, caches locally for offline use, and shows a lock so only one person edits it at a time. A set added with Import is copied locally, so later edits do not reach anyone else.

For outside reviewers, upload the .btx to a Studio Project folder and have them import it. One caution from Bluebeam: Basics users may lose markups that rely on measurement tools beyond length and area, so keep the review set to clouds, callouts, and stamps if consultants are on Basics.

How do you turn Tool Chest markups into an issue log?

Use the Markups List. Every markup becomes a row with Subject, Page Label, Comments, Author, Date, Status, Color, and Layer, and you can add custom columns. Bluebeam's Markups List guide and custom status guide cover the details.

Two plan limits matter here. Custom status models need Core, Complete, or Max, and Basics can only export a PDF summary, not CSV or XML. Save the status model to the PDF if the file is going into a Studio Session, so every attendee sees the same statuses; save it to your profile to reuse it across projects.

Once an item is marked RFI Candidate and confirmed, write it up using the format in the PDF-to-RFI workflow, then track it with the method in how to track RFIs.

What makes a review tool set work in practice?

• Lock the subjects. Two spellings of Code Question split your log into two groups.
• Keep it under 20 tools. Reviewers stop scanning a longer list and fall back to plain clouds.
• Put the most-used statuses first so Shift+1 to Shift+3 cover most clicks.
• Version the file name (Drawing Review 2026-11.btx) and keep the old one when you change colors mid-project.
• Turn on the Layer column in the Markups List so reviewers can hide verified items before a meeting.

Where does Helonic fit with a Bluebeam review tool set?

A tool set makes marking faster; it does not tell reviewers where to look. Helonic reads the full 2D PDF set in 15 to 30 minutes and returns a located issue list in categories that map to these tools: coordination, code compliance, missing information, dimensions, and QA/QC. Reviewers open each location in Revu, confirm it, and drop the matching Tool Chest markup. Helonic does not create markups or .btx files. Relevant checks include annotation detection and code compliance review. The Helonic vs Bluebeam comparison and Bluebeam pricing guide cover which Revu plan you need for custom statuses and CSV export.