Engineering and architecture
Can you license Bluebeam Revu and Studio markups?
By SourceX Editorial · Updated
Short answer
You can often license Bluebeam markups once the underlying projects clear a rights review, and the practical route is a markup summary export rather than marked-up PDFs. A Revu markups list records the comment, author, date, status and page for each markup, so it can be reviewed and redacted line by line without sharing the drawings underneath.
Key takeaways
- The markups list, not the PDF, is the useful record: it holds comment, author, date, status and page as separate fields.
- Exported summaries can be redacted field by field, while marked-up PDFs carry drawings that may be client-owned.
- Studio Session markups are attributed to each attendee, which shows the review conversation but adds names to replace.
- Flattening usually strips markups of their author, date and status fields, so export summaries before a set is flattened for issue.
- Automated scanning of comment text needs a human pass before any export leaves the firm.
What does a Bluebeam markups list record?#
A Bluebeam Revu markups list records each markup on a PDF as a row, with fields such as type, comment text, author, date, status and page. That structure turns a drawing review into a log of who raised what, where, and what happened to it.
Exact columns depend on your Revu version and the profiles your firm uses, so check an export from your own setup before planning anything. The table shows the fields most firms will see and how each is usually treated in a licensing review.
Status is the field most often left blank. Teams that never set statuses can still have a usable record if replies close each item, but a list where every markup sits at the default status says little about outcomes.
| Field | What it records | Licensing note |
|---|---|---|
| Subject or type | Cloud, callout, text box, measurement or stamp | Useful for grouping review comments |
| Comment | The reviewer's text | Core value; scan for names, addresses and client details |
| Author | The person who made the markup | Replace with a consistent role or reviewer code |
| Date | When the markup was created or changed | Keep; the sequence shows how the review unfolded |
| Status | Review state the team set, with history if used | Keep; links a comment to its outcome |
| Page or sheet label | Where the markup sits in the set | Keep sheet labels; drop project identifiers |
| Replies | Threaded responses to a markup | Keep; often holds the resolution |
| Custom columns | Fields the firm added, such as discipline or severity | Document what each value means |
Why exported summaries beat marked-up PDFs#
Exported markup summaries are easier to license than marked-up PDFs because they separate the review conversation from the drawing it sits on. A summary file can be read, filtered and redacted field by field, while a marked-up PDF carries the full sheet, title block, owner name and design content along with the comments.
The drawing underneath is usually the harder rights question. Construction documents may be instruments of service subject to client terms, or include consultant sheets the firm cannot license. Sharing comments without the sheets keeps most of the review reasoning and leaves those questions out of scope.
Flattened PDFs are the worst case. Flattening usually merges markups into the page, so they no longer appear in the markups list with their author, date and status, and the comment becomes part of the drawing. Export summaries before any set is flattened for issue.
Revu files, Studio Sessions and Studio Projects compared#
Where markups live decides how you get them out. Revu stores markups inside each PDF, Studio Sessions gather markups from several attendees on shared documents, and Studio Projects keep files in a shared store with version history.
- Ask your Bluebeam administrator how long session and project history is kept under your firm's settings.
- Check whether closed sessions were saved back to the document system or left only in Studio.
- Confirm who can export from each location before scheduling the work.
| Where markups live | What it captures | How to get a usable record |
|---|---|---|
| Revu PDFs on a server or document system | Markups by one or more reviewers, saved into each file | Export markup summaries per file, keeping file and sheet references |
| Studio Sessions | Live review with markups attributed to each attendee | Use the session's own records or saved session files, then export summaries |
| Studio Projects | Shared files with check-in and version history | Export summaries from the versions that matter |
| Markups attached in Procore or another platform | Review comments tied to an RFI or submittal response | Export from the platform with the RFI or submittal number to keep the link |
A redaction note for markup comments#
Markup comments need redaction because reviewers write the way they talk: names of client staff, phone numbers, owner and tenant names, addresses and sometimes frank remarks about a contractor. The author field adds every reviewer's name on top.
The practical sequence is to replace author names with consistent codes, so one reviewer stays one reviewer, then scan comment text for names, emails, phone numbers, addresses and project identifiers, and remove stamps that carry seals or license numbers. Keep a log of what was removed for the privacy record.
Automated tools speed up the scan but do not finish it. The maintainers of Presidio, an open-source PII detection SDK, say plainly that automated detection carries no guarantee of catching everything and that other protections are needed. Markup comments are a hard case for scanners because they are short, abbreviated and full of sheet references, so a person should read a sample from every export.
Steps to export markups for a first review#
The steps below assume a COO or BIM manager is preparing a sample for a rights and value review, not a final delivery.
- Pick a handful of closed projects that already passed a rights review.
- Locate the review sets: internal QA/QC reviews, consultant coordination sets, and submittal and shop drawing reviews.
- Export markup summaries with all columns, including status history and replies.
- Keep a key that maps each summary to its file, sheet and project, stored apart from the export.
- Replace names and run redaction before anyone outside the review team opens the files.
- Log which projects and sets were exported, by whom and when.
Illustrative: an architecture firm's QA/QC markups#
Illustrative: a fictional architecture firm runs internal QA/QC reviews as Studio Sessions, with senior reviewers marking up construction document sets before issue. Its Revu profile adds discipline and severity columns. The COO wants to know whether those reviews could be licensed.
A sample export shows comments with statuses and replies that close each item, which makes the history coherent. The rights review clears private commercial projects but excludes a data center client under a strict NDA. The firm exports summaries only, replaces reviewer names with role codes, strips project identifiers from comment text and keeps every PDF out of scope. The sample goes into a metadata-only fit check.
The sample also exposes a gap: older reviews were done on paper and scanned, so they have no markups list at all. The COO leaves them out rather than paying to transcribe them.
How SourceX treats markup data#
SourceX treats markup summaries as review records, assessed with the SourceX Enterprise Data Value Framework for linkage and depth and handled through the SourceX five-step transaction. The first assessment uses descriptions rather than files, a package built from summaries leaves the PDFs and drawings in the firm's own systems, and the redaction log becomes part of the privacy record in the SourceX Evidence Packet.
Frequently asked questions
Do we need Bluebeam's permission to license our markups?
Markups your staff write are generally your firm's work product, but check Bluebeam's terms for Studio and any cloud service you use, plus your client agreements for each project. The software vendor's terms govern use of the service, while client contracts govern the project information inside the comments.
Are markups made by clients or contractors in our sessions ours to license?
Not automatically. Client, consultant and contractor attendees author their own markups, and that content may belong to them or fall under the project's terms. Many firms filter exports to markups authored by their own staff and leave the rest out.
Can we license measurement and takeoff markups?
Possibly, but they carry less reasoning than comments. Measurements and quantities are tied closely to the drawings and the project, so they are harder to separate from client-owned content. Review comments with statuses and replies usually show more of the decision-making.
What about our markups on manufacturer submittals?
Your review comments and actions on a submittal are your firm's work, but the submittal pages belong to the contractor or manufacturer. Export the comments and review actions, and leave the product data and shop drawings out of the package.
Is a Studio Session record better than individual PDF markups?
It depends on the review. A session gathers several reviewers' markups on the same set with attribution and timing, which shows how a coordination review unfolded. Individual PDFs are often the only record of internal checks done outside Studio. Assess both, and favor whichever links comments to outcomes most clearly.
Sources
- Presidio's documentation warns that because it uses automated detection mechanisms, there is no guarantee it will find all sensitive information, and additional systems and protections should be employed. Source
Related resources
- InsightHow do I de-identify project plans and status reports for AI training?
- InsightDo you need client consent to license de-identified RFIs and submittals?
- InsightLicensing project review notes and lessons learned: what to remove
- SolutionData partnerships between businesses and AI developers
- IndustryBPO & contact centers data
- IndustryRecruiting & staffing data
See if your company qualifies
A short company assessment. No data uploads are needed.