Objective. Students apply Bluebeam Revu markup tools—including clouds, callouts, stamps, layers, and the Markups List—to annotate a construction drawing set for a design review and produce a summary report.
This lesson, its worked examples and its practice questions has not yet been verified by a credentialed professional in the field or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
Bluebeam Revu is a PDF-based markup and collaboration platform widely used in the construction industry. It allows project teams to annotate drawings, track design issues, manage submittals, and produce documentation—all within a controlled, searchable PDF environment. Many owners, general contractors, and specialty subcontractors require Revu proficiency from their project management staff. Learning Revu is a direct investment in your employability.
When you open Revu, the screen is organized into a few key zones. The toolbar runs across the top and gives you access to file, edit, view, and markup commands. The Properties panel on the right shows the settings for whatever tool or markup is currently selected—color, line weight, author, and more. The Markups List appears as a panel (usually at the bottom) and is the real backbone of a design review workflow. The Tool Chest is a customizable panel that stores your most-used markup tools so you do not have to hunt through menus during a fast-paced review.
Take a few minutes at the start of any session to dock the panels you need—Markups List, Properties, and Tool Chest—so your workspace is clean and efficient.
Clouds are the standard symbol for drawing revision areas in the AEC industry. In Revu, the Cloud tool wraps a revision bubble around any area of the drawing you want to flag. Use a cloud to outline the physical zone of the conflict—for example, a structural beam that conflicts with a mechanical duct.
Callouts pair a text box with a leader arrow that points to the exact location of the issue. After placing a cloud, add a callout inside or adjacent to it. The callout text should be brief but specific: trade affected, nature of the conflict, and any relevant drawing or specification reference.
Stamps are pre-built graphic overlays—"For Review," "Preliminary," "Void," and others—that communicate document status at a glance. In a design review package you might stamp a sheet "Under Review" before distributing and then replace it with "Reviewed" when the cycle closes.
Layers are the organizational key to a multi-discipline review. Bluebeam layers work like CAD layers: each discipline (Civil, Structural, Mechanical, Electrical, Plumbing) can place its markups on its own named layer. When all reviewers contribute, the project manager can toggle layers on or off to see one discipline at a time, or all disciplines together, without losing any data. Always create and name layers before you begin marking up; adding them after the fact is tedious.
Every markup you place—cloud, callout, stamp, or measurement—automatically populates the Markups List. The List is a live spreadsheet inside Revu that records the markup type, author, date, page, layer, color, and any text you typed. You can sort and filter by any column. For a design review, sort by Layer to group conflicts by discipline, or sort by Status to see which issues are still open.
The Markups List can be exported to a CSV file (File > Export > Markups List). That CSV becomes the basis for a formal review log or, as you will practice today, a set of Request for Information (RFI) write-ups.
1. Open the drawing in Revu and zoom to the area of the conflict.
2. Select or create a layer matching the discipline responsible for the issue (e.g., "Mechanical").
3. Draw a Cloud around the conflict zone. Keep it tight to the area—do not wrap half the sheet.
4. Add a Callout pointing to the center of the cloud. In the text box, enter a short description such as: Conflict: Mechanical duct (Sheet M-201) clashes with structural beam (Sheet S-112) at Grid B-4, EL 12′-6″. Coordination required.
5. Set markup properties: choose a consistent color for the discipline (e.g., red for Mechanical), and confirm the author name is set to your name in Preferences.
6. Verify the Markups List shows the new entry with the correct layer and description.
7. Repeat for each conflict on its appropriate layer.
When the review is complete, the marked-up PDF is flattened so all markups are burned into the document and can no longer be accidentally moved or deleted. Go to Document > Flatten. You can choose to flatten all markups or only specific layers. After flattening, the file is ready to distribute.
Publishing a PDF package in Revu means combining multiple marked-up sheets into a single organized PDF (File > Combine or the Batch functions). The published package is what you deliver to the design team or upload to the project management information system.
Markup work happens in an office or job-trailer environment, but the drawings you are reviewing document physical work that carries real hazards. When you flag a conflict, consider whether the issue could create a fall hazard, an electrical hazard, or an egress blockage if it were built as shown. Note those safety implications explicitly in your callout text. This habit directly supports the OSHA principle that hazard recognition begins in the planning phase—long before workers set foot on the site. Additionally, protect drawing files: mislabeled or overwritten PDFs can send workers the wrong information. Always use clear, dated file-naming conventions and version-control your packages.
The CSV you export from the Markups List is not just a record—it is the raw material for formal project communication. In the next lesson you will convert these entries into full RFIs inside Procore. Today, practice writing your callout text as though the design team will read it immediately: be specific, reference the drawing number and grid location, and state what decision or action you are requesting. That discipline now makes the RFI step nearly automatic.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.