Bluebeam Studio Setup for Markup and Collaboration

A design review meeting is called for two o'clock. By two-fifteen, the mechanical engineer has emailed a marked-up PDF, the architect has uploaded a different version with redlines to a shared folder, and the contractor is still trying to find the original set. A week later, no one is sure which comments have been addressed and which were missed. Bluebeam Studio is the cloud-hosted collaboration layer inside Bluebeam Revu that lets your team mark up the same PDF sheet set at the same time or review shared documents over the life of a project, without emailing files back and forth. For architecture, engineering and construction firms in and around New York City that already use Bluebeam Revu, Studio Sessions and Studio Projects turn that chaotic process into a single shared workspace where everyone sees the same version and every markup is tracked.

This article is a setup guide for firms that want Bluebeam Studio configured in a way that holds up across a full project, not just for one coordination call. Studio Sessions are built for live, simultaneous markup during a meeting or punch walk, while Studio Projects are built for ongoing document storage and version tracking across a project's duration. The distinctions matter because setting up permissions, folder structure and naming conventions before the first session prevents the problems that slow down review cycles later.

Studio is a markup and review layer, not a replacement for your main file storage and backup system. Your original Revit central models, AutoCAD drawings and project files still need to live on a managed server, SharePoint or Egnyte. What follows covers how to set up Studio access for your firm, build a folder structure that survives from design development through closeout, manage permissions so sessions do not multiply or get abandoned, connect field teams on job sites, keep large sheet sets and markups performing well, and avoid the common mistakes that turn a good tool into another source of confusion.

Key Takeaways

• Bluebeam Studio lets project teams mark up PDFs together in real time or manage shared documents across a project without emailing files back and forth.
• Studio Sessions are for live simultaneous markup and Studio Projects are for ongoing version tracking, and setting up folder structure and permissions before your first session prevents most review slowdowns.
• Studio is a collaboration layer for markup and review, not a replacement for your firm's main file storage where Revit models and AutoCAD drawings must still be backed up.

What Bluebeam Studio Is and Where It Fits in a Project Workflow

Studio operates as a markup and coordination layer that sits between your project files and the people reviewing them, whether during a live plan check meeting in your conference room or over the course of a six-month construction phase. It does not replace your file server or your design software; it gives teams a shared workspace for PDF sheet sets that would otherwise be emailed, marked up separately, and consolidated by hand.

How Studio Differs From Emailing PDF Markups or Sharing a Single Bluebeam File

When you email a PDF sheet set to three consultants, you receive three separate files back with their markups. Someone then opens all three, copies markups across manually, and sends out a fourth file. The process breaks down as soon as a second round of comments is needed or a field question comes in mid-coordination.

Studio Sessions let every reviewer open the same sheet set at the same time and see each other's markups appear live. A mechanical engineer's clash note shows up on the architect's screen immediately, and the structural engineer can respond to it without waiting for a new file. Studio Projects give you a persistent place to store those sheets, so the same PDF set used in Tuesday's coordination call is still available Friday when the contractor has a field question.

The difference matters most when decisions happen fast. During a punch walk, the superintendent, architect and owner's rep can all mark the same floor plan on their tablets, and the markups sync as soon as they reconnect to the office or job site network. No one emails their version later, and nothing gets lost in someone's inbox.

Studio as a Layer on Top of Revit, AutoCAD and PDF Sheet Sets

Your Revit central model and AutoCAD drawings remain on your file server or in BIM 360. Studio does not store them and does not replace the central model workflow. You publish a sheet set from Revit or AutoCAD to PDF, upload those PDFs to a Studio Session or Project, and the team reviews them there.

Once reviewed, the markups go back into your design software as changes to the model or drawing. Studio holds the coordination record and the marked-up sheets, but the design files themselves continue to live where your firm manages them. Point clouds, Navisworks models and other large datasets stay in their usual locations; Studio handles the PDF output used for review and approval.

This keeps Studio focused on what it does well. It coordinates markup across disciplines without forcing you to move your entire file structure into a new system.

What Studio Does Not Replace: File Storage, Backup and Version History

Studio Projects track versions of the PDFs you upload to them, but they are not a backup system for your firm's project files. Your Revit models, AutoCAD drawings, specification documents and contract files still need to live on a managed file server, SharePoint or a platform like Egnyte that handles backup, retention and recovery.

If your file server fails, Studio will not restore your central model. If you need to pull a drawing set from two years ago for a warranty claim, you retrieve it from your backup system, not from Studio. Studio gives you a record of who marked up which sheet and when, which is useful during coordination, but it does not replace the document control and archive process every firm needs for professional liability and contract requirements.

Treat Studio as the workspace where review happens, and your file server or cloud storage as the system of record where project files are kept long-term. The two work together rather than replacing each other.

Bluebeam Studio Sessions vs Studio Projects: Choosing the Right Tool for the Task

Studio Sessions are the tool for real-time markup during a meeting or field walk, while Studio Projects are built for storing and managing document sets over weeks or months. Most firms working on projects in New York City need both, but the choice depends on whether the work requires live collaboration or version-controlled storage.

Studio Sessions for Live Coordination Meetings and Punch Walks

Studio Sessions support simultaneous markup by everyone in the room or on the call. When three consultants need to review the same sheet set during a coordination meeting, a Session lets all three add markups at the same time without waiting for someone else to finish. The same applies to punch walks, where a field team can mark deficiencies on a tablet while walking the job site, and the superintendent can see each item appear in real time.

Sessions work well when the task has a defined start and end. A two-hour coordination call, a half-day RFI review or a punch walk that wraps up by the end of the afternoon all fit the Session model. Once the Session closes, the marked-up PDF can be saved back to the firm's main file storage or uploaded to a Studio Project for the rest of the team.

Sessions support up to 500 users and 5,000 PDF files per Session, with a 1 GB limit per file. For most coordination meetings and punch walks, those limits are not an issue. The Session interface includes a built-in chat panel and markup alerts, so the team can communicate without switching to email or a separate messaging app.

Studio Projects for Ongoing Document Sets and Long-Running Reviews

Studio Projects provide cloud-based storage for PDF sheet sets, submittals, RFIs and other project documents that need to be accessed by multiple people over the life of the project. A Project Manager can upload a 100% DD set to a Studio Project, invite the structural and MEP consultants, and let them download or mark up sheets as needed without sending individual files by email.

Projects support check-in and check-out, so only one person edits a file at a time. This prevents conflicting markups and maintains document integrity when a review spans several days or weeks. Projects also track version history, so you can see who changed a file and restore an earlier version if needed.

Studio Projects support more file types than Sessions, including Word, Excel, PowerPoint and images. A Project can hold the entire project folder, not just PDFs, making it easier to share submittals, schedules and spec sheets with contractors and clients. Projects have no limit on the number of files, users or file size, though keeping total Project size under 10 GB improves performance.

When a Firm Needs Both on the Same Project

Most projects in New York City benefit from using Studio Projects for long-term storage and Studio Sessions for live review events. A typical workflow starts with a Studio Project that holds the current sheet set, specifications and submittals. When the team needs to review those sheets during a coordination meeting, the Project Manager opens a Session, uploads the relevant PDFs from the Project, and invites the attendees. After the Session closes, the marked-up sheets are saved back to the Project so the full team can see the comments.

This combination keeps documents organized in one place while supporting real-time collaboration when needed. The Project serves as the single source for the latest files, and Sessions provide a space for focused markup without cluttering the Project with in-progress work. The ability to create and close Sessions and Projects should sit with a project manager, BIM manager or document control lead to avoid abandoned Sessions or duplicate Projects that scatter files across multiple locations.

Using both tools together also simplifies external sharing. A firm can grant a contractor access to a Studio Project for ongoing document review, then run a Session for a specific submittal review without giving the contractor permanent access to every file. Projects handle permissions at the folder level, while Sessions let you control access by meeting or event.

Setting Up Bluebeam Studio Access for Your Firm

A firm-wide Studio setup requires choosing who creates accounts, who can start Sessions and Projects, and how outside parties join without fragmenting your document control. The decisions you make before the first coordination meeting prevent duplicate Sessions, abandoned Projects and consultants waiting for access while the markup call is already underway.

Creating a Firm Studio Account and Deciding Who Administers It

Every person who uses Studio needs a Bluebeam account, which is created when your firm assigns a Bluebeam Revu license or when a user receives an invitation email to join a Session or Project. If your firm holds an Org Admin Pro subscription, an IT Admin or Studio Admin can manage Studio access, permission groups and feature settings from the Org Admin portal. This is where you decide whether all licensed users can create Sessions and Projects or whether that ability is limited to a smaller group.

Most firms restrict Session and Project creation to project managers, BIM coordinators and document control leads. This keeps one person from starting three overlapping Sessions for the same sheet set or leaving a Project open after substantial completion. You configure this by setting Studio access to Managed rather than Enabled, then assigning the Can use Studio permission only to the users who need it.

The session host is the person who creates a Session or Project and holds the ability to invite others, control document versions and close the Session when the review is finished. On a coordination call involving MEP, structural and the architect, the session host is typically the architect's project manager or BIM lead, not the firm administrator. The administrator sets the permission to create Sessions; the session host runs the individual Session itself.

Inviting Internal Staff Without Creating Duplicate or Orphaned Sessions

Internal staff join a Session or Project by invitation from the session host. The host sends an email invitation directly from Revu or shares a join link during the meeting. Each person who joins must have a Bluebeam account, which is created automatically if they hold a Revu license or established when they accept the invitation.

The risk of duplicate Sessions comes when more than one person on your team creates a Session for the same sheet set without knowing the other Session exists. A project manager starts a Session for the Level 3 plan coordination, a field superintendent starts a second Session for the same drawings on the punch walk, and markups end up in two places. You prevent this by limiting who can create Sessions and establishing a clear rule: check whether a Session already exists before starting a new one.

Orphaned Sessions happen when the session host closes Revu, leaves the project or forgets to formally close the Session after the review ends. The Session stays open in Studio, other users see it in their active list, and no one is sure whether it is still current. The session host should close each Session as soon as the review is complete and the final markup set is saved back to the project folder on your file server or SharePoint.

Bringing Consultants, Contractors and Clients Into Studio as Guests

Consultants, contractors and clients join a Session or Project as guests. They do not need a Bluebeam Revu license to participate. The session host sends an invitation email, and the guest clicks the join link to access the Session or Project through Bluebeam on web, which runs in a browser without installing Revu.

Guest access is designed for outside parties who need to review and mark up sheets but do not hold a paid Revu license. A structural engineer on a coordination call, a general contractor reviewing submittals or an owner's representative checking progress drawings all join as guests. They can add markups, reply to comments and see real-time changes during a live Session, but they cannot create new Sessions or upload new document versions unless the session host grants that permission.

You control what guests can do by setting permissions when you invite them. Most firms allow guests to add and edit their own markups but not delete markups added by others or change the document set. On a punch walk, the session host may allow the contractor to upload photos directly into the Session; on a design coordination call, the host typically reserves document upload for internal staff only.

The most common setup issue with guests is the invitation email landing in spam or the guest not having a Bluebeam account before the meeting starts. Send invitations at least a day before the coordination call, and include a note in the calendar invitation that the guest will receive a separate email from Bluebeam and should confirm access before the meeting begins.

Building a Studio Project Folder Structure That Survives a Full Project

A folder structure that makes sense on day one often falls apart by the end of schematic design if it was not built to handle versions, multiple disciplines and the shift from coordination to closeout. The structure you create before uploading the first sheet set determines whether your team can find the current drawings six months into construction or wastes time hunting through nested folders and duplicate files.

Structuring Folders by Phase, Discipline or Sheet Set

Most New York firms start with one of three patterns: folders organized by project phase, by discipline or by sheet set type. Phase-based structures create top-level folders such as Schematic Design, Design Development, Construction Documents and Construction Administration. Each phase folder holds the sheet sets, submittals and RFIs issued during that period.

Discipline-based structures group files by architectural, structural, MEP and civil, with subfolders for drawing sets, specifications and coordination models. This works when each discipline team manages its own uploads and the work does not overlap significantly between trades.

Sheet set structures organize by document type rather than phase or trade: Drawings, Specifications, Submittals, RFIs, Meeting Minutes and Closeout. This is the most common choice for general contractors and construction managers who receive documents from multiple design consultants and need a single location for each type.

The structure that holds up longest combines two levels: top-level folders by phase or contract milestone, then subfolders by document type within each phase. A folder named 03_Construction Documents might contain subfolders for Architectural Drawings, Structural Drawings, MEP Drawings, Specifications and Addenda. When the project moves to construction, a new top-level folder named 04_Construction Administration holds RFIs, ASIs, submittals and marked-up field drawings without disrupting the issued-for-construction set.

Whatever pattern you choose, create the full structure as empty folders before you upload the first file. Restructuring a Project after dozens of sheets are already uploaded requires downloading, reorganizing and re-uploading files, and any active Studio Sessions tied to those files will break.

Naming Conventions for Sheets, Markups and Custom Columns

Sheet file names in Studio should match the sheet numbers shown on the titleblock, followed by the sheet title and the revision or issue date. A file named A-101_First Floor Plan_2026-09-15.pdf is easier to locate in a long file list than FirstFloor_09-15.pdf, and the date makes it clear which version you are viewing when multiple revisions exist.

Avoid renaming files after upload unless absolutely necessary. Bluebeam tracks file history by name, so renaming a sheet breaks the link to earlier markups and comments. If a sheet number changes mid-project, add a note in the file description field rather than changing the filename.

Custom columns let you add metadata that appears alongside each file in the Project tab, such as discipline, package number, review status or approval date. To add a custom column, open the Project, go to Add on the Project tab toolbar and select Add Custom Column. Name the column, choose the data type and set values for each file by right-clicking the file and selecting Edit Custom Columns.

Use custom columns to track review status when multiple consultants mark up the same sheet set during coordination. A column named Review Status with values such as Not Started, In Review, Comments Returned and Approved lets the project manager see which sheets still need feedback without opening each file. A column named Discipline with values Architectural, Structural, MEP and Civil makes it possible to filter the file list to show only the sheets relevant to a specific trade coordination meeting.

Archiving Closed Studio Projects Without Losing Markup History

Studio Projects accumulate hundreds of markups, threaded comments and review records over the life of a job, and that history needs to stay intact after the project closes. The markup data lives in the cloud as long as the Project remains active, but it does not transfer to your firm's main file server or backup system unless you export it deliberately.

Before you close a Project, download the full folder structure with all markup history embedded. Open the Project tab, right-click the root folder and select Download. Bluebeam will package every file with its markup layers flattened or retained, depending on the option you choose. Choose Retain Markups if you want to open the files later and see who marked what and when.

Save the downloaded folder to your document management system or file server in the same location where you store other closeout records such as as-builts, O&M manuals and warranties. Name the folder clearly, such as Project Name - Studio Archive - Closed 2026-09-30, so it is obvious the files came from a closed Project and are not live working files.

Once the download is complete and verified, you can delete the Project from Studio to free up storage and remove it from the active Project list. Go to the Studio panel, right-click the Project name and select Delete Project. Deleting a Project is permanent and cannot be undone, so confirm the archive download is complete and stored in at least two locations before you proceed.

Do not rely on Studio as long-term archive storage. Studio is a collaboration layer, not a records management system, and your firm's backup strategy should treat the files on your server as the authoritative copy once the project closes.

Running a Live Markup Session With Architects, Engineers and Contractors

Studio Sessions work best when the sheet set is organized before anyone joins, markups are visible to everyone as they happen, and the host has a clear plan for converting comments into assigned action items before closing the session.

Preparing the Sheet Set and Agenda Before Opening a Session

Upload your sheet set to the session in the same sequence the team will review it. If the coordination meeting follows the discipline order listed in the project execution plan, organize the sheets in that order so everyone can follow along without jumping between files.

Name each sheet using the project's sheet numbering convention. A sheet named "A101 - First Floor Plan" appears in the session file list exactly as it does in your issue set, which reduces confusion when three consultants are marking up different sheets at once.

Set default attendee permissions before sending invitations. Most coordination sessions work with markups and comments allowed but file deletion and reassignment blocked. You can adjust permissions for specific attendees after they join if the structural engineer needs to delete their own comments or the contractor needs full control over their punch observations.

Create an agenda in the session chat or share it as the first PDF in the set. A typed agenda keeps the discussion on track when markups start appearing quickly, especially during a multi-discipline coordination call where mechanical, electrical and plumbing consultants are all marking up the same reflected ceiling plan.

Managing Simultaneous Markups Without Overwriting Comments

Studio attributes every markup to the attendee who placed it and timestamps it in the session record. You will see each consultant's markups appear in real time as they add them, with their name and firm attached.

Markups do not overwrite each other because they sit in separate layers tied to each attendee. When the mechanical engineer and the electrical engineer both cloud the same ceiling penetration, you see two clouds, not one replacing the other.

Use the Follow Attendee feature when someone calls attention to a specific detail. Right-click their name in the attendees list and select Follow Attendee, and your view will match theirs as they pan and zoom. This keeps everyone looking at the same location during a fast-moving discussion without asking people to read out coordinate numbers.

Turn off Follow Attendee when you need to mark up a different area. The session lets you work independently while still seeing everyone else's markups appear, which is useful when the architects are resolving a storefront detail while the structural team marks up foundation notes on another sheet.

Closing Out a Session and Turning Markups Into Action Items

Generate a session report before you finish the session. The PDF Package Report compiles the record summary and all session documents into a single package, with hyperlinks that jump from each recorded comment directly to its location on the sheet. This report becomes the coordination meeting minutes without retyping anything.

Select which attendees' markups to include in the saved files. If the contractor's field notes are still preliminary, exclude them from the saved set and include only the design team's markups that need to go into the next issue.

Assign responsibility for each markup during the session or immediately after. The session record shows every comment in chronological order, so you can scroll through the list, identify which items need action, and note the responsible party in the chat or in a follow-up email that references the session report page numbers.

Save the session documents back to your project folder on the server or in SharePoint using the Save In Folder option. Do not rely on Studio as the permanent home for these files; Studio is the markup layer, and your firm's managed storage is where the final coordinated sheets belong once the session ends.

Permission Levels and Who Should Control a Studio Session

Studio permissions determine what each participant can do once they join, and the person who creates a session does not automatically need to control it for the project's duration. Firms that decide in advance which roles get Full Control access and which receive View-Only avoid disputes during a coordination meeting or when a project manager leaves mid-project.

The Difference Between Session Creator, Full Control and View-Only Access

The session host is the person who creates the Studio Session and owns it by default. They can rename the session, delete it, invite attendees, manage permissions and set an expiration date. Full Control grants another user the same administrative powers as the host, with two limits: they cannot block the host, and they cannot see or use the host's Studio Groups.

Someone with Full Control can rename or delete the session, manage attendee access, and adjust permissions for other users. They also have full permissions to any folder in the session, regardless of folder-level defaults. This role is appropriate for a second project manager, a BIM manager overseeing coordination across trades, or a document control lead who steps in when the original session host is unavailable.

View-Only access means the participant can see the documents and any markups in the session, but cannot add or edit markups, invite new attendees or modify the session. Field staff who need to reference the current sheet set during a punch walk but should not add comments while onsite typically receive View-Only access.

The default Attendees group applies to everyone in the session, and most permissions for this group are blocked when the session is created. Grant additional permissions to specific users or groups rather than opening access for all attendees.

Setting Permissions for Outside Consultants and Field Staff

Outside consultants joining a coordination session generally need permission to add and edit markups, but should not be able to invite additional attendees, change session settings or delete the session. Add each consultant by email address on the Attendees tab in Session Settings, then set their permissions on the Permissions tab to allow markup creation and editing while keeping Full Control and invite permissions blocked.

Field staff reviewing punch list items on a tablet during a site visit should receive View-Only access so they can reference the current sheet set and existing comments without adding markups from the field that might later conflict with office decisions. If field staff need to document a condition onsite, a separate field observation session with tighter attendee limits is clearer than granting markup permissions in the main coordination session.

When a consultant belongs to multiple groups within the same session, their permissions default to whichever is most restrictive. If you add a structural engineer to both a general Consultants group and a Structural Team group with different permissions, the engineer inherits the more restrictive settings. Avoid placing someone in overlapping groups unless you have confirmed the resulting permissions match what the person needs.

Handing Off Control When a Project Manager Changes

When the project manager who created a Studio Session leaves the firm or moves to a different project, the session does not transfer automatically. Before the original host leaves, they should grant Full Control to the incoming project manager and confirm the new manager can access session settings, manage attendees and adjust permissions.

The original host can also transfer ownership by contacting Bluebeam support, though granting Full Control to the replacement is usually faster and sufficient for most handoffs. Document which sessions and projects each project manager controls in a shared spreadsheet or project directory so the firm knows who to contact when a session needs to be closed, archived or extended past its original expiration date.

If a project manager leaves without granting Full Control and the firm cannot reach them, contact Bluebeam support with proof of the account relationship and the business need. This process takes longer than a planned handoff, so establish a policy that any project manager creating a session must grant Full Control to at least one other person on the team before the first coordination meeting.

Connecting Studio to Field Teams and Job Site Devices

Field teams use Studio on tablets and laptops to review drawings, add markups and complete punch list work without waiting for files to sync later. Connectivity matters, but most job site internet supports Studio if the device and browser are current.

Using Studio on Tablets and Laptops at the Job Site

Studio runs in a browser or through Revu installed on a Windows device, so your field team can use it on most job site tablets and laptops. The mobile app for iOS and Android supports viewing, markup and punch list work without needing a full Revu license.

A project team typically equips field staff with a tablet that can open large sheet sets and respond quickly enough for markup during a punch walk. Tablets with at least 4 GB of RAM and a screen around 10 inches handle typical construction sheet sets without lag. Smaller phones work for quick reviews but become difficult when a superintendent needs to mark up architectural details or MEP coordination drawings.

Your field markups appear in the Studio Session or Project immediately after you save them, so the office sees updates without waiting for the crew to return and upload files manually. This matters during coordination meetings when a general contractor, architect and MEP engineer are all marking up the same reflected ceiling plan from different locations.

Install Revu on field laptops when the team needs full markup tools, measurement and estimation features. Use the mobile app on tablets when the work is limited to reviewing drawings, adding comments and updating punch list status. Both connect to the same Studio Projects and Sessions, so a punch list item created on a tablet appears in Revu at the office within seconds.

What Job Site Internet Quality Means for Studio Performance

Studio runs over standard internet connections, so a job site with stable WiFi or cellular service supports real-time collaboration without specialized network equipment. Slow performance on site usually points to weak signal strength, an overloaded router or too many devices sharing limited bandwidth rather than a Studio limitation.

A typical construction trailer with broadband service handles Studio Sessions and Projects without issue. Job sites relying on cellular hotspots may see slower file loads when opening large sheet sets, but markups and comments still sync once the document loads. Studio does not require constant connectivity after a file opens, so brief signal drops do not interrupt work already in progress.

Field teams working in areas with intermittent connectivity should open the needed drawings while connected, then continue markup and review offline. Studio syncs changes back to the project when the connection returns. This pattern works well in below-grade areas, steel structures under construction and other locations where cellular signal fades temporarily.

Syncing Field Markups Back to the Office Without Version Conflicts

Studio handles version conflicts by tracking every markup with a timestamp and user name, so when two people mark up the same sheet at the same time, both sets of comments appear rather than one overwriting the other. This avoids the version chaos that happens when project teams email marked-up PDFs back and forth.

A field superintendent adding punch list items to a third-floor plan while a project manager reviews the same sheet at the office sees both sets of markups merge automatically. Studio does not create duplicate files or ask anyone to choose which version to keep.

Your project team should agree that field markups stay in Studio rather than being exported, edited outside Studio and re-imported later. Exporting a PDF from a Studio Session, marking it up locally and uploading a revised file breaks the markup tracking that prevents conflicts. The office loses visibility into who added which comment and when.

Finalize a Studio Session after a coordination meeting or punch walk to lock the current state and create a clear revision point. This prevents further edits and gives the project team a fixed record of what was agreed during that review. A finalized session can be archived or exported as a complete set with all markups flattened, depending on what your document control process requires.

Keeping Large Sheet Sets, Point Clouds and Markups Fast in Studio

Studio Sessions handle large drawing sets and heavy markup activity as long as you prepare the files first and keep the most bandwidth-intensive content out of the Session itself. Performance issues usually trace back to embedded images, unflattened AutoCAD markups or very large attachments that force Bluebeam Revu to transmit more data than the connection can handle smoothly during a live coordination meeting.

Why Large PDF Sets and Embedded Images Slow Down a Studio Session

Studio transmits every markup change between the host and each attendee in real time. When 15 people mark up the same mechanical sheet during a coordination call, the Session sends those changes across your firm's internet connection and the connection of every consultant joining remotely.

High-resolution images and grouped markups create the largest data burden. A field photo captured at full camera resolution and placed on a sheet using the Image tool can weigh several megabytes by itself. Multiple images across a 200-sheet set add up quickly, especially when the Session has to send each change to a dozen devices at once.

SHX file markups exported from AutoCAD carry unnecessary vector data that inflates file size without adding value to the review. Flatten those markups in Revu before uploading the sheets to Studio so the Session transmits a simpler raster or flattened vector element instead of the full SHX data.

Grouped markups slow transmission when a single group contains dozens of individual elements. Each element inside the group still transmits as part of the change. Break groups apart or avoid grouping unless the coordination workflow genuinely requires it.

Handling Point Cloud References and Large Attachments Outside Studio

Point clouds and other scan data do not belong inside a Studio Session. A Session works best with the 2D sheet set that references the point cloud, not the cloud file itself.

Keep the point cloud, Revit central model and any large supplementary file on your file server or SharePoint. Export the necessary PDF sheet set from Revit or Navisworks, apply page labels and calibrate scales in Revu, then upload only the prepared PDFs to the Session.

If the team needs to reference the point cloud during a live Session, share your screen or open the cloud in a separate viewer while the markup happens in Studio. The same approach works for large 3D models or any file that would otherwise push the Session beyond the bandwidth a typical job site connection can sustain.

Practical Steps to Keep Sessions Responsive on Big Projects

Before uploading drawings to a Studio Session, complete the following preparation steps in Revu:

• Use Reduce File Size to remove unnecessary embedded content and compress images without losing clarity for coordination purposes
• Flatten SHX markups and any markup layers you do not need to edit during the Session
• Apply page labels with AutoMark so attendees can navigate by sheet number rather than scrolling through thumbnails
• Rotate all pages to the correct orientation, because you cannot change orientation once the sheets are in the Session
• Calibrate measurement scales in the Measurements panel and delete any untitled viewports so field teams can measure accurately without adjusting settings during the review

Upload large drawing sets to a Studio Project first, then copy only the sheets your team needs for the live review into a new Session. Once the coordination meeting finishes, use Update Project Copy to move the marked-up sheets back into the Project with a full revision history.

When markup volume is heavy, limit the number of simultaneous attendees or split the review across multiple Sessions organized by discipline. A mechanical-only Session with six attendees performs better than a single Session with 20 people from every discipline marking up the same core and shell sheets at once.

Studio Security and Where It Fits in a Firm's Broader IT Setup

Studio accounts authenticate the same way your other cloud tools do, and they sit alongside your file server and email rather than replacing them. Understanding how access control, password policy and backup responsibility split between Studio and your existing infrastructure keeps project data protected without duplicating effort.

How Bluebeam Handles Access Control and Session Data

Studio requires a Bluebeam ID with a username and password for each user who participates in Sessions or Projects. A licensed Revu user creates Sessions and Projects and invites others, while users without a subscription can join as read-only participants with limited markup tools.

All connections between Revu and Studio use HTTPS with Transport Layer Security encryption. Data is encrypted both in transit and at rest using AES-256 encryption, with files stored on Amazon S3 servers and managed through AWS Key Management Service. Studio does not send inbound connection requests to your network, so you only need to allowlist outbound HTTPS traffic to the Studio domains that correspond to your region.

Session and Project access is controlled by invitation. The user who creates a Session or Project decides who receives an invitation, and only invited participants can view or mark up the documents. This works well for coordination meetings where three consultants need simultaneous access to a sheet set, but it also means you should limit who can create Sessions in the first place so invitations do not go out without review.

Protecting Studio Accounts With Strong Passwords and MFA

Studio enforces password requirements that align with typical IT policies: between 8 and 32 characters, with at least one uppercase letter, one lowercase letter, one number and one special character. Passwords are hashed before storage using a salted one-way algorithm, and accounts lock for five minutes after five failed login attempts.

Multi-factor authentication adds a second verification step beyond the password. MFA rollout has its own dedicated article, but the short version is that you configure it at the Bluebeam ID level and it applies to all Studio access for that user. A project manager opening a Session on a tablet at a job site or a project engineer reviewing markups from the office both benefit from the same protection.

You should treat Studio accounts the same way you treat access to your file server or email. That means onboarding new users through a consistent process, removing accounts when someone leaves the firm, and auditing who has access to active Projects at the end of each phase.

Where Studio Fits Alongside the Firm's File Server, Backup and Email Security

Studio is a markup and review layer, not your primary document storage. Your Revit central models, AutoCAD drawings, point clouds and original sheet sets still live on your file server, SharePoint or Egnyte, where your existing backup and version control processes apply. Studio holds the marked-up PDF copies and tracks who added which comment during a coordination call or punch walk, but it does not replace the managed storage you already rely on.

Bluebeam performs daily backups of Studio databases and stores PDF files with versioning on S3, but those backups cover the last 24 hours and are intended for disaster recovery rather than long-term project archiving. Your backup strategy article covers the full picture, but the principle is straightforward: export Studio markups and documents back to your file server at milestones and closeout so you have them alongside the rest of the project record.

Email security intersects with Studio when invitation emails go out to consultants, contractors or clients. Studio sends emails from domains such as @bluebeam.com and @bluebeamops.com through amazonses.com, so your email administrator may need to allowlist those domains to prevent invitations from landing in spam. A consultant who never receives the Session invitation cannot join the coordination meeting, and you lose the time spent troubleshooting it.

Common Studio Setup Mistakes That Slow Down Review Cycles

Multiple people creating sessions without coordination, no agreed folder structure before the first upload, and dormant sessions with guest accounts still active all add friction to what should be a fast markup cycle. Each slows performance, confuses consultants, and makes closeout harder than it needs to be.

Too Many Session Hosts and No Single Point of Ownership

When anyone on the team can create a Studio Session, projects accumulate duplicate sessions covering the same sheet set or discipline. You end up with one session started by the MEP lead, another by the architect's job captain, and a third by the contractor's superintendent, each containing slightly different versions of the same coordination drawings. Consultants don't know which session to join. Markups scatter across all three, and no one has a complete record when the discussion ends.

The fix is to assign session ownership to a single role: your project manager, BIM manager or document control lead. That person creates every session, sets permissions, and closes it when work finishes. Everyone else joins as an attendee. If someone needs to start a session when the designated owner is out, they request access ahead of time rather than creating a duplicate on the spot.

This also solves the problem of orphaned sessions that never close. When one person owns all sessions for a project, they know what is open and what needs to wrap up at each milestone.

Skipping a Folder and Naming Standard Before the First Project

Uploading files to a Studio Project without an agreed folder standard forces you to reorganize mid-project or live with a structure that made sense to one person on one day. A typical example: drawings land in folders named by date, then by discipline, then by submittal package, because three different people uploaded files at different times without talking first. Consultants waste time hunting for the current electrical sheets, and version history becomes meaningless when the same drawing appears in four locations.

Agree your folder structure before the first upload. Most teams organize by discipline at the top level (architectural, structural, MEP, civil), with subfolders for phase or package if the project needs them. Match the folder names to how your team already thinks about the work, not to an abstract document control system no one follows.

Apply the same discipline to sheet names and page labels. If your AutoCAD or Revit sheets export with labels like "A-101" or "S-201", make sure those labels carry through to the PDF before it reaches Studio. Attendees navigate large sets using the Thumbnails panel, and unlabeled sheets slow everyone down during a live coordination meeting.

Leaving Old Sessions and Guest Accounts Open After Project Closeout

Sessions left open after substantial completion continue to consume storage and create confusion when someone searches for an active project. Worse, guest accounts invited for a single coordination call remain active indefinitely unless the session owner removes them. That means a contractor's subcontractor still has access to your full sheet set months after their scope finished, even though no one intended ongoing access.

Close every Studio Session as soon as the review or meeting ends. Use the "End Session" function to lock markups, then move final sheets back to the Studio Project or your main file server depending on your retention workflow. If you need to keep a record of the markup discussion, save a flattened PDF with all comments visible before you close the session.

Review guest accounts at every project milestone (end of design development, before bid, at substantial completion) and remove anyone who no longer needs access. Bluebeam Studio Projects track every invitation, so you have a list of who was added and when. Removing old accounts is faster than troubleshooting a access question six months later when someone who should not have access downloads a current revision.

Bluebeam Studio for Architecture Firms and Design-Build Teams

Architecture firms working across multiple consultants need a way to coordinate markups during live design reviews, while design-build teams need to connect field observations back to the original design drawings without printing or emailing files. Studio Projects store the project record, while Studio Sessions handle real-time review when consultants and contractors are working through the same sheet set together.

Why Architecture Firms Rely on Studio for Multi-Consultant Review

Multi-consultant coordination on a New York City project means the architect, structural engineer, MEP engineer and envelope consultant all need to mark up the same architectural or coordinated drawing set during a single review meeting. Studio Sessions let each consultant add their markups to the same PDF in real time, rather than emailing individual copies back to the architect and reconciling four different versions after the fact.

You create a Studio Session for the coordination meeting, upload the current sheet set and invite each consultant using their BBID email address. During the call, each consultant marks up conflicts, clashes and coordination issues directly on the sheets. All markups appear on everyone's screen as they are placed, so the team sees the same information at the same moment.

After the Session ends, you download the marked-up sheets and distribute them to the project team or import them back into the Revit central model as coordination comments. The Session record stays in Studio until you finish it, and you can reopen the same Session for the next coordination meeting rather than starting from scratch.

A Studio Session replaces the older workflow where the architect exports PDFs, emails them to each consultant, waits for individual responses and then manually combines markups into a single coordinated set. That process takes days and creates version confusion when one consultant is working from an outdated file.

How Design-Build Teams Use Studio to Bridge Design and Field Markups

Design-build teams need field crews to add punch list items, as-built observations and RFI markups directly to the design drawings, then bring those markups back to the design team without losing detail or waiting for the next in-office meeting. A Studio Session opened on a tablet at the job site lets the field crew mark up the same sheets the design team is working from, even when the crew is standing in front of the actual wall or system being documented.

You upload the current architectural, structural or MEP sheets to a Studio Session, then share the Session link with the field team. The field crew opens the Session on their tablet using Bluebeam Revu installed locally or through a web browser if they have a Bluebeam plan that supports web access. They add markups, measurements and photo annotations to the sheets while standing at the location, and those markups sync back to the Session as soon as the device reconnects to the internet.

The design team sees the field markups appear in the Session in real time if both groups are online simultaneously, or the next time the Session refreshes if the field crew is working offline and syncs later. This workflow keeps field observations tied to the original sheet number and detail reference, so the project manager does not need to translate handwritten notes or separate photo files back into drawing annotations after the fact.

Fitting Studio Into a Firm's Overall IT and Software Stack

Studio sits between the firm's primary file storage system and the live review tools the project team uses during coordination, punch walks and client meetings. Your Revit central models, AutoCAD drawings and project archives still live on the office file server, SharePoint or a managed cloud storage service such as Egnyte, and Studio does not replace that system. Studio handles the review and markup layer when multiple people need to work on the same PDF sheet set at the same time or track document revisions over the course of a project.

Most architecture and design-build firms export PDFs from Revit or AutoCAD, upload them to a Studio Session or Studio Project, conduct the review or coordination meeting in Studio, then download the marked-up sheets and file them back to the main project folder on the file server. The firm's backup and disaster recovery plan covers the file server, not Studio, so Studio Sessions and Projects should be finished and archived promptly after the review is complete rather than used as long-term storage.

Studio requires an active internet connection to sync markups and documents, so the firm's network setup needs to support reliable connectivity for users working in the office, at home and on job sites. Performance issues during a Studio Session are usually caused by slow upload speeds, weak Wi-Fi at the job site or too many large files loaded into a single Session at once, rather than a limit of Studio itself. Job site connectivity and device performance are covered in separate articles focused on field IT setup.

A small number of people should have permission to create, invite to and close Studio Sessions and Projects, typically the project manager, BIM manager or document control lead. If every team member can create Sessions, the firm ends up with abandoned Sessions that sit open for months, consume storage and make it harder to find the active project files when someone needs them.

Bluebeam Studio is a cloud-based collaboration layer included with Revu that supports real-time markup during coordination meetings and document management across a project's duration. The following questions address how Studio fits into a firm's workflow, what each component does, and what licenses your team needs.