Want to Get More Out of Bluebeam? Standardise It

Bluebeam’s dexterity as a construction technology makes it invaluable to the industry, but standardising its tools and features to specific job roles or workflows makes it even more valuable
Share on facebook
Share on linkedin
Share on twitter
Share on email

Standardisation is paramount in construction. Whether you’re a site manager on a multibillion-pound skyscraper project or an estimator on a mixed-use development, every industry player needs to abide by a set of standards to get the job done.

Using construction technology is no different. As digital collaboration tools continue to play an outsized role in the industry, it’s critical that those who are leading technology implementations customise the tools so workers can learn them quickly and apply them on the job effectively.

Perhaps no construction technology benefits more from standardisation than Bluebeam. The tool’s pliability is one of its greatest strengths. Here’s how to apply standards to Bluebeam so you can get the most out of the technology.

Simplify what you see

Construction is a complex industry. Any given job may have more than 100 different types of roles, from the contractor overseeing the production of a build, to the architects and engineers determining a project’s fine details, to the electrician carrying out those details.

Bluebeam is designed to help all of these people do their jobs better. Still, its capabilities are so robust that any first-time user might become overwhelmed. Therefore, it’s critical that, upon implementation, Bluebeam is customised with standards that are specific not just to each role but also to any particular workflows. 

The best way to do this is to eliminate anything that’s unnecessary in Bluebeam’s interface. If you don’t need to create forms in Bluebeam, for example, scrap the icons and buttons to remove them from view. Repeat this with any other unneeded tools, panels or capabilities.

Create Custom Profiles, Tool Sets, Icons, Etc. 

Revu, Bluebeam’s flagship PDF markup tool, has a seemingly endless amount of features. One way to completely customise Revu to better serve a job role or workflow is to save specific interface settings as a Profile, which can then be shared with other project colleagues.

By creating custom Profiles, users can re-order and even turn off any of the interface’s panels and tools, ensuring that only the most used and relevant tools are in view. Users can do the same with the tool bars within Revu. Standardising workspaces in Bluebeam with custom Profiles, and sharing those Profiles across teams, will go a long way towards simplifying the overall experience of using the technology.

Customisation doesn’t stop with Profiles in Bluebeam. Markup tools – the symbols that are saved in the Tool Chest – can also be standardised as a custom tool set. Moreover, users can upload their own markup icons to standardise for use in a specific project or workflow.

Like with Profiles, implementation leaders should take advantage of such customisation. From tool sets to specific markup icons, create a standardised experience in Bluebeam for your team that is as specific and simple as possible.

Review standards often

While establishing standards in Bluebeam is essential at the beginning of the tool’s implementation, it’s equally important that custom elements – from Profiles to tool sets – are reviewed and updated regularly.

Bluebeam is like a fine wine: it gets better with time. As knowledge of Bluebeam expands as people on your team continue to use it, it’s worthwhile to potentially integrate new tools and features as part of your customised standards.

Review these standards on an informal level every quarter, while larger, more robust standardisation updates should happen once every six months to a year. Use these opportunities to gain feedback from users on which standards should be updated or eliminated.

The bottom line

Bluebeam’s versatility as a construction technology makes it invaluable to the industry. But with such flexibility comes the need to customise it for specific types of users and workflows. Failing to set standards when using Bluebeam (or any construction technology) risks slowing down the tool’s adoption and overall effectiveness over time.

Bluebeam Studio Sessions vs. Studio Projects

Here’s how to use Studio Projects and Sessions in Revu most effectively.