FAQ

Can Bluebeam Do Submittals and RFIs?

This article shares what Bluebeam can and cannot do with respect to submittals and RFIs during construction administration.

Curved structural steel connection with visible bolts against the sky.

Contents

No headings found on page

Bluebeam Revu can review and mark up submittals and RFIs, but it does not manage them as tracked construction administration workflows. Revu does not maintain a submittal register, track ball-in-court end to end, review CA deadlines, or maintain the distribution record when a response is returned.

That distinction matters because reviewing a submittal and managing the submittal process are two different jobs.

This is why many architectural firms are choosing to pair Bluebeam with Part3 for their CA tech stack.

Many architecture firms use Bluebeam every day during construction administration, for good reason. It is a powerful tool for reviewing PDFs, comparing revisions, applying stamps, and coordinating markups between reviewers.

But once dozens or hundreds of RFIs and submittals start moving between the contractor, architect, consultants, and owner, firms typically need something else to keep track of the workflow around those documents.

The common setup is Bluebeam Revu for review, paired with Excel for the log, Outlook for communication, and shared folders or another system for the project record.

Here’s where Bluebeam fits in that workflow and where its role ends.

What Bluebeam actually does in the submittal and RFI workflow

Bluebeam Revu is primarily a document review environment. During construction administration, that makes it useful for several important parts of submittal and RFI review.

Markup and annotation

Reviewers can open a contractor’s PDF and add comments, callouts, clouds, measurements, symbols, and other annotations directly to the document.

For architects and consultants accustomed to reviewing drawings and shop drawings visually, this is one of the core reasons Revu is so widely used.

Submittal stamps and dynamic stamps

Bluebeam stamps can be used to record the review action on a submittal.

Firms can create custom stamps using their own language for example, the specific review actions established by the firm and dynamic stamps can capture information such as the reviewer and date.

This makes the reviewed PDF itself much more useful as a record of what happened during the review.

Comparing resubmittals

This is an area where Bluebeam is particularly useful.

Compare Documents can identify differences between PDF versions, while Overlay Pages lets reviewers visually layer revisions to see what changed.

For a resubmittal where the reviewer needs to determine whether previous comments were addressed or whether something else changed between versions those tools can significantly simplify document review.

Bluebeam Studio Sessions for submittal review

Bluebeam Studio Sessions allow multiple people to review and mark up the same documents.

That can be useful when a submittal needs input from the architect and several consultants. Instead of circulating multiple independently marked-up PDFs, reviewers can work within a shared session.

Studio Sessions also maintain a record of activity within the session.

Studio Projects

Studio Projects provide document storage and management, including file check-in and check-out.

That can help teams maintain shared access to project files rather than relying entirely on local folders or attachments moving between individual inboxes.

Markups List

The Markups List captures information about markups within a PDF.

Teams can add custom columns and export Markups List data to formats including CSV. That means a firm can use markup information to create a structured, log-like export.

That is useful but it is important to distinguish a list of markup data from a submittal or RFI register that maintains workflow state over time.

Bluebeam submittals and RFIs: capability table

CA task

Bluebeam capability

Review and annotate PDFs

Yes

Apply submittal review stamps

Yes

Create custom/dynamic stamps

Yes

Compare resubmittals

Yes

Overlay document revisions

Yes

Coordinate simultaneous document review

Yes, with Studio Sessions

Store and check files in/out

Yes, with Studio Projects

Export markup data

Yes

Maintain a submittal/RFI register

No native CA register

Track ball-in-court

No

Track contractual review deadlines

No

Link a submittal to its specification section as a CA record

No

Maintain transmittal/distribution history

No

Report on open CA items across projects

No

Assemble a CA closeout record

No

The dividing line is fairly straightforward: Bluebeam manages the document review very well. It does not manage the complete CA workflow surrounding that document.

What Bluebeam does not do

The easiest way to understand the boundary is to think about what happens before and after someone opens the PDF.

Bluebeam handles the document review. The rest of the submittal or RFI workflow still needs to be managed somewhere. Some firms do that through a combination of spreadsheets, email, and shared folders. Others pair Bluebeam with Part3, using Revu for document review and Part3 to manage the CA workflow around it.

There is no native submittal or RFI register

A submittal in a CA system is more than a file.

It has a number, specification section, received date, responsible reviewer, current status, due date, response, returned date, revision history, and associated correspondence.

In Revu, the fundamental objects are documents and the markups associated with those documents. There isn't a native CA object representing the complete lifecycle of Submittal 03 30 00-001 or RFI 042.

That information therefore needs to be maintained somewhere else. Part3 maintains the submittal and RFI register while the associated documents can still be reviewed in Bluebeam.

There is no ball-in-court tracking

Consider a project with 60 open submittals.

Some may be sitting with the architect. Others may be waiting for structural, mechanical, or electrical consultants. Some may have been reviewed internally but not yet returned. Others may be resubmittals waiting for another review.

The project team needs to know not just what is open, but who needs to do something next.

Revu doesn't maintain that workflow state across the project's submittal and RFI register. Part3 tracks the responsible party and current status while reviewers continue using Bluebeam for the document itself.

There is no review clock

Submittal review periods can be contractual obligations.

A CA team therefore needs to know when something arrived, how long it has been under review, when it is due, and which items are approaching or exceeding the applicable review period.

Revu does not treat a submittal as an item with a workflow due date or overdue status. Part3 tracks the dates and deadlines associated with the submittal or RFI, rather than requiring the team to maintain that review clock separately from the document.

The exact contractual review requirements vary by contract and project, so teams should refer to their applicable agreement rather than assuming a universal review period.

There is no spec section linkage

The specification provides important context for submittal review.

A CA register may associate an individual submittal with its specification section so the team can see what has been submitted, what is still outstanding, and how individual packages relate to project requirements.

Revu can contain and review those documents, but it does not maintain that relationship as part of a structured submittal record. Part3 keeps the submittal record and its specification information together while Bluebeam remains the environment for reviewing the PDF.

There is no transmittal or distribution record

Stamping the PDF is only part of completing a review.

Someone still has to return it.

If the reviewed submittal is sent through Outlook, the record of when it was transmitted, who received it, and what was said in the accompanying correspondence is now in email.

The PDF contains the review. The inbox contains the distribution record.

When Bluebeam is paired with Part3, the reviewed document returns to the CA workflow in Part3, where the response and distribution record can remain associated with the submittal or RFI.

There is no cross-project CA reporting

A project manager may need to know what is outstanding on one project. A practice leader may need to know what is outstanding across 10, 20, or 50 projects.

Revu isn't designed to provide a portfolio-level view of open RFIs, overdue submittals, consultant response times, or other CA workflow data across projects.

Part3 provides that CA-level view across projects while Bluebeam continues to handle document review.

There is no automated CA closeout package

At the end of a project, firms need to retain the appropriate record of their CA activity.

Bluebeam can contain the reviewed PDFs and their markups, but it does not automatically assemble the complete history of the submittal and RFI workflows—including their metadata, correspondence, distribution history, and status changes—into a project closeout record.

That broader CA record is maintained in Part3, keeping the workflow history associated with the documents reviewed in Bluebeam.

Frequently asked questions

Can Bluebeam do submittals?

Bluebeam Revu can handle the document-review portion of a submittal workflow: opening the PDF, adding markups, applying review stamps, coordinating reviews, and comparing resubmittals.

What it does not do is maintain the complete CA workflow around that submittal, including the register, ball-in-court, review deadlines, distribution, and history. Firms that want to keep using Bluebeam for review can pair it with Part3 to manage those parts of the workflow.

How do you manage RFIs in Bluebeam?

Bluebeam can be used to review and mark up documents associated with an RFI, but the RFI itself still needs to be tracked somewhere.

Some firms maintain that record in Excel and Outlook. Others pair Bluebeam with Part3 so the RFI number, status, responsible party, dates, response history, and distribution record are managed in Part3 while the document review continues in Bluebeam.

Can you use Bluebeam Studio Sessions for submittal review?

Yes. Bluebeam Studio Sessions can support submittal review by allowing multiple reviewers to mark up documents in the same session and by maintaining a record of activity within that session.

Studio Sessions do not replace the overall submittal workflow. Firms can use Part3 to track the submittal record, ball-in-court, deadlines, status, and final distribution while reviewers collaborate in Bluebeam.

Can you use a Bluebeam submittal stamp or dynamic stamp for review?

Yes. Bluebeam supports custom and dynamic stamps that firms can configure for their submittal review process, including firm-specific review language and reviewer information.

The stamp records the review action on the PDF. Part3 can maintain the broader submittal record around that reviewed document, including its status, dates, workflow history, and distribution.

Can the Bluebeam Markups List be exported as a submittal log?

The Bluebeam Markups List can contain custom columns and can be exported to formats including CSV, so teams can create structured, log-like data from their markups.

That is different from maintaining a live submittal register with workflow state, ball-in-court, deadlines, revisions, and distribution history. Firms that want to keep Bluebeam for markup can use Part3 as the system that maintains that CA record.

Do I need CA software if I already have Bluebeam?

Not necessarily. If your team is comfortable using Bluebeam for document review and separately maintaining submittal and RFI logs, deadlines, consultant follow-up, correspondence, and project records, your existing workflow may be sufficient.

CA software becomes useful when those administrative parts of the process are difficult to manage reliably. Part3 is designed to work alongside Bluebeam, so firms can keep Revu for markup and review while using Part3 for the register, workflow, deadlines, and project record.

What does a Bluebeam Revu construction administration workflow look like?

A common Bluebeam Revu construction administration workflow uses Revu to review, annotate, stamp, and compare PDFs.

The surrounding workflow still needs to be managed somewhere: receiving the item, logging it, assigning reviewers, tracking deadlines, returning the response, and maintaining the project record. Firms can manage that through spreadsheets and email, or pair Bluebeam with Part3 so Revu remains the review environment while Part3 manages the CA workflow around it.

See For Yourself

Ready to modernize construction administration?

Book a personalized demo and see how architects are cutting review time, reducing risk, and gaining control with Part3.

Updates

Stay ahead of what’s changing in CA.

Get practical insights on construction administration, AI, risk reduction, and how leading firms are modernizing operations.

See For Yourself

Ready to modernize construction administration?

Book a personalized demo and see how architects are cutting review time, reducing risk, and gaining control with Part3.

Updates

Stay ahead of what’s changing in CA.

Get practical insights on construction administration, AI, risk reduction, and how leading firms are modernizing operations.

See For Yourself

Ready to modernize construction administration?

Book a personalized demo and see how architects are cutting review time, reducing risk, and gaining control with Part3.

Updates

Stay ahead of what’s changing in CA.

Get practical insights on construction administration, AI, risk reduction, and how leading firms are modernizing operations.