Bluebeam Studio is the cloud collaboration environment connected to Bluebeam Revu, with Sessions for simultaneous PDF review and Projects for controlled document storage.
The choice comes down to what your team needs to do with a file: discuss it together now, manage it across its working life, or move it through both stages.
That distinction matters because putting a live review into the wrong workspace can introduce unnecessary check-outs. Treating a Session as a document register can also leave your team without the revision history expected from a Project.
Once you understand how Sessions and Projects should be used, the rest of this guide shows you exactly how to apply that structure. Let’s go.
What is Bluebeam Studio?
Bluebeam Studio is a cloud-based collaboration environment that connects people, PDFs and project documents through Revu and Bluebeam on the web. Bluebeam Studio contains two related workspaces:
- Studio Sessions for concurrent PDF markup
- Studio Projects for cloud document management.
When comparing options, like Bluebeam vs Adobe Acrobat, please note that Revu provides the dedicated PDF creation, markup, measurement and reporting tools used by individual users.
Studio extends those tools into a shared environment, so reviewers can work with the same documents without circulating separate email attachments.
Understanding Studio is different from how to use Bluebeam Revu. While Revu focuses on the tools you use to create, measure and mark up PDFs, the Studio focuses on how your team shares, reviews and controls those files through Sessions and Projects.
Revu provides the PDF tools, while Studio Sessions support simultaneous review and Studio Projects provide controlled document management.
Studio Sessions: Real-time PDF Collaboration
Studio Sessions is the right workspace when several people need to review and mark up the same PDFs at the same time.
Everyone works inside one live review space, so comments appear as they are added and nobody needs to wait for a file check-out.
The following AEC review scenarios show where a Studio Session provides the most practical fit:
- Design coordination: Architects and engineers review the same drawing and respond to discipline-specific comments, which is efficient during BIM coordination meetings.
- Tender reviews: Estimators and project teams mark assumptions, exclusions and scope questions against one PDF set.
- Site and defect reviews: Contractors and consultants discuss issues directly on the relevant drawing.
- Time-boxed reviews: The host sets a deadline and closes the Session after feedback is resolved.
The Session host controls who can join, what participants can do and when the review ends. Then, Studio records markups, comments and chat activity, while each markup remains tied to its author.
This approach gives your team a traceable review without creating multiple PDF copies.
You can see this review pattern across Bluebeam in construction workflows, from tender clarification to design coordination and site issue close-out.
Every Session should also have a defined close-out. Once the review is complete, generate the report, save the reviewed PDFs to the relevant Project or agreed common data environment, and finish the Session.
Studio Projects: Cloud Document Management
Studio Projects is the right workspace when your team needs a controlled cloud location for project files and their revisions.
Files are checked out before editing and checked back in when updates are ready, preventing two people from overwriting the same document.
The following document-management needs show where Studio Projects fit best:
- Controlled working files: Keep current project documents in one shared folder structure.
- Revision management: Record each checked-in update and review earlier file versions when needed.
- Mixed file storage: Store PDFs alongside supported spreadsheets, images and other project files.
- Role-based access: Control which team members can view, edit or manage specific folders.
For example, a document controller can organise drawings and supporting files while consultants access only the folders relevant to their work.
Check-in comments also help the team understand what changed between revisions.
A Project should still have a defined role within your wider information-management process.
If another construction document management software or common data environment is the formal project record, decide:
- Which files belong in Studio Projects
- How approved documents move between the two systems.
When a Project PDF needs simultaneous input, send it to a Studio Session for review and return the reviewed copy as a new Project revision.
Studio Sessions vs Studio Projects: Which to Use When
Choose Studio Sessions for simultaneous PDF review and Studio Projects for controlled document storage. Use both when a managed file needs live collaboration before returning to revision history.
Choose Sessions when a PDF needs simultaneous multidisciplinary feedback; choose Projects when controlled access and file updates are the priority.
However, the decision should follow the next action required on the document. The comparison below maps the operational difference your team will notice first:
| Decision point | Studio Sessions | Studio Projects |
| Primary purpose | Concurrent PDF review | Cloud file management |
| Working model | Many people mark up together | One person edits a checked-out file |
| File types | PDF only | PDFs and supported non-PDF files |
| Change record | Session activity and markup record | File revision history |
| Previous revisions | No Project-style revision restore | View and restore revisions |
| Best fit | Design review, tender review, defects | Working library, controlled updates |
| Close-out | Save files and generate a report | Check in a new revision |
| Use it on its own when | The PDF already has an authoritative home and only needs coordinated feedback | The team needs controlled access to working files without simultaneous review |
| Governance check | Name the Session host and where reviewed outputs will go | Name the Project owner and where approved files will go |
When Sessions and Projects Work Together
Use Sessions and Projects together when a controlled Project file needs simultaneous review before returning as a new revision. Bluebeam supports this hand-off directly.
A user with the right permissions can add a Project PDF to a new Session, run the review and use Update Project Copy to check the Session version back into the Project. The combined workflow follows this sequence:
- Store the current PDF in the appropriate Project folder.
- Add that Project file to a new Session and invite the reviewers.
- Complete the markup review and generate the Session report.
- Update the Project copy so the reviewed file becomes a new revision.
- Save the report in the agreed record location and finish the Session.
A Project PDF moves into a Session for concurrent review, returns as a new Project revision and closes with the Session report saved to the agreed location.
This combined approach fits multidisciplinary reviews where the document controller needs revision control and the design team needs concurrent input.
It also gives the review a visible beginning and end, which is easier to govern than an indefinitely open collaboration space.
How to Access and Set up Bluebeam Studio
To access and set up Bluebeam Studio, first confirm which users need hosting rights, then validate their BBIDs, choose the Studio region and configure the workspace.
Your Bluebeam plan determines who can create Sessions and Projects, while the setup sequence establishes ownership, access and regional settings. Let’s break down.
Which Bluebeam Plans Include Studio
All four current Bluebeam plans provide Studio access, but only Core, Complete and Max can initiate and manage Studio collaboration.
Drawing on our experience as Bluebeam licence pricing service provider in Australia, we recommend reviewing the access differences below.
- Basics: Users can join existing Sessions and Projects but cannot host or manage them. This suits team members who mainly mark up documents after being invited by a host.
- Core: Users can create and manage Sessions and Projects. Core is the starting point for project leads, review hosts and document controllers who own Studio workspaces.
- Complete: Provides the same Studio hosting and management as Core, with additional automation and reporting tools. Choose it when those broader desktop workflows justify the plan, rather than for a different level of Studio access.
- Max: Includes everything in Complete and adds Connected Studio Sessions for Revit. Eligible Revit users can view and interact with Session markups against corresponding 2D sheets and 3D views.
Bluebeam Max connects live Studio Session markups with corresponding 2D Revit sheets and 3D model views through the Bluebeam plugin.
This plan mix lets you match each subscription to a person’s actual responsibility instead of giving every participant the same plan.
Or, if you want to test the workflow before assigning annual seats, you can compare the Bluebeam free trial vs paid plans in Studio‑specific contexts.
Because active trials can host Sessions and Projects, making your small pilot possible before a wider rollout.
The Setup Sequence
The setup sequence should establish ownership, region and access before your team creates its first live Session or Project. It takes only a few configuration steps, but each one affects where data sits and who can control it.
Follow these five steps in order so the workspace, accounts and permissions are ready before external reviewers are invited:
- Name the owners: Assign a primary host or Project owner and a backup for each job.
- Choose the Studio region: A Studio AU region hosted in Sydney. Its regions operate separately, so Projects, Sessions and data are not automatically shared between them.
- Validate BBIDs: Confirm each participant has a verified account for the selected region before the review date.
- Create the right workspace: In Revu, open the Studio panel and create either a Session or Project; Core, Complete and Max users can also manage Studio through the web.
- Set access before inviting people: Configure groups and folder permissions first. Set attendee rights and any Session expiry date, then test the invitation with one internal user.
Pro tip: If consultants already use another Studio region, resolve that before creating the workspace. Bluebeam requires a separate BBID for each region, and moving Session data later involves downloading and re-uploading documents rather than transferring the workspace intact.
Managing Studio for Project Teams
Manage Studio as a project workflow with named owners, role-based permissions and a defined close-out process.
The Bluebeam technology is straightforward, but consistency depends on the rules your team applies around it.
Set Ownership and Permissions by Role
Give full control only to people who need to manage documents, users or settings, then grant narrower permissions to reviewers.
Studio groups can reflect roles such as design lead, estimator, document control and external consultant.
Review these groups when the consultant team changes, rather than relying on an invitation list created at project start.
Ownership also needs continuity. Record the Session host and Project owner in your project setup, nominate a deputy and transfer ownership when someone leaves the job. This avoids tying a live review or document space to one person’s availability.
Standardise Names and Close-out
Use a naming pattern that identifies the project, package, review stage and date without opening the workspace.
A descriptive name such as Project-Package-30PercentReview-2026-07 is easier to distinguish from an informal Session called Review 2.
Close every Session deliberately. Confirm reviewers have finished and generate the required report. Save or update the reviewed PDFs before you finish the Session.
Where Projects and Sessions are linked, check that the Project copy has returned as the intended revision before closing the review.
Train the Workflow Around the Tools
A structured Bluebeam Revu course can help your team practise markups and real-time collaboration using the same conventions.
Training is most useful when it includes your naming rules and review responsibilities. It should also cover permissions and close-out because those decisions sit outside the software buttons.
Adjust the template, role guidance and plan allocation before extending Studio across tenders, site reviews and handover work to support smoother AEC workflow automation.
Adjust the template, role guidance and plan allocation before extending Studio across tenders, site reviews and handover work.
Or, start book a free discussion with an Interscale Bluebeam expert to plan how your project teams will manage Studio Sessions, Projects and review close-out.
