Bluebeam Tip: Export Revu markups to XML QA records

Turn your review history into a structured, auditable deliverable by exporting Bluebeam Revu markups as an XML QA record.

• Prepare your data
  • Open the Markups List and show only the columns you need for QA (e.g., Status, Subject, Page Label, Space, Author, Date, Comments, Custom Columns).
  • Standardize Status values and use Custom Columns for discipline, priority, CSI code, or punch category.
  • If you use Spaces, confirm they are applied so location data is captured per markup.
• Export to XML
  • In the Markups List, select Summary.
  • Choose XML as the output format.
  • Scope: All Pages or Selected Markups; respect active filters to limit results.
  • Options to consider: Include Replies, Include Capture references (photos/video), Include Layer/Color, Include Current Sort.
  • Export to a project folder alongside any media folder that Revu creates for Capture items.
• Validate and share
  • Open the XML in a browser or feed it into your QA/QC system, Power BI, or Excel (via XML import) for dashboards and pivot analysis.
  • Verify key fields: Markup ID, Status, Page Label, Space, Author, Date/Time, and any Custom Columns.

Pro tips

• Save a Profile that locks in your QA columns and sorting so every export is consistent across the team.
• Use Page Labels that match sheet numbers; they flow neatly into the XML and downstream reports.
• Export before flattening markups; once flattened, you lose granular markup data.
• For Studio work, run the Summary from the Session to capture a complete, time-stamped audit trail.
• Keep a “QA – Required Fields” Tool Set with preset Subject, Status, and Custom Column defaults to reduce data cleanup later.

Need Bluebeam licenses, upgrades, or guidance on building a QA export workflow? Explore Bluebeam solutions at NOVEDGE, or talk to the experts at NOVEDGE for implementation best practices.

You can find all the Bluebeam products on the NOVEDGE web site at this page.