Own that markup
Following our recent Bluebeam 2018 webinar, we received some questions regarding “owning markups” in Revu. With tools as powerful as those found in Revu, there’s always a chance that someone could accidentally (or intentionally) edit your markups. Are you interested to learn a workflow where markups are only editable by the author? If so, read on.
Background: What is Bluebeam “Studio”?
Bluebeam Studio is a collaboration platform included with a Bluebeam Revu license. Studio connects team members on projects, giving them the ability to markup and review documents in real-time. Studio “Sessions” allow team members to add markups to the same PDF document, together, in real-time (or at any time while the session is active). All markup activity is recorded and conveniently links back to the Session PDFs. A built-in chat feature aids communication during the collaboration session. Bluebeam Studio is included in Revu Standard, Revu CAD, and Revu Extreme. Studio “Projects” will be the subject of another post.
We often misuse the term “collaboration” because the practice usually isn’t usually “collaborative” at all. There are two common scenarios for collaboration:
- Involves sending the same document to different stakeholders, then collating their responses in one place.
- For all stakeholders to log into a screen sharing application and take turns to add their comments.
The problem with both scenarios is that “ownership” of the markups isn’t controlled. A markup placed by one stakeholder may be deemed inappropriate or wrong by another and deleted or changed.
In 2010, Bluebeam addressed this shortcoming by focussing on the integrity of the document. Their collaboration solution called “Studio Sessions” allows multiple users simultaneous access to the same set of documents. Each collaborator can add and edit their own mark-ups. This truly collaborative environment gives all stakeholders confidence that their work can’t be edited by anyone else, not even the session administrator.
However, one property remains editable, making the “Sessions” one of Revu’s most powerful best kept secrets: In a scenario where feedback is requested by in a markup, the status field can be changed as needed, whilst recording who made the change, when the change was made, and the status change itself. For example, requesting an update on the completion of some work, the status field can be set as “Completed” when the work is done. The makeup itself cannot be deleted or edited by anyone other than the original markup creator, but there’s a full audit-trail saved in the Session record of who did what, and when they did it.