Announcements

Welcome to ACC Ideas! View the ACC Product Roadmap here. Top-voted ideas may be considered for future development. Learn more about the feedback process here.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Submittal Markups - New file

Submittal Markups - New file

The current process when reviewing a submittal is to click on the file make edits in the editor then save and a new file is generated under the current steps user/role assigned.  Additionally, if the reviewer enters some comments but has not finished the review and saves the document, another document will be generated when going back in to make additional comments.

 

Intuitively, users seem to want to click the copy to bring the file down to their review step, and I think this makes more sense.

 

When clicking on the attachment you should be able to open/save your progress on the same file until you are ready to submit.  Some submittals have 100s of pages and may take multiple sessions reviewing the submittal before the review can be completed.  With multiple files generated there is a much higher risk of an incomplete submittal review being used as the complete review.

2 Comments
rbowenSHNUD
Enthusiast

There was a workaround for this

- save the file outside of build and make comments/markups.  Markups made outside of build do not always transfer back in to build and vice versa resulting in incorrect and/or missing information.

- save the submittal, move to the next step, then step back.  This does not allow for you to modify any of the markups that were previously made.  Additionally, the person in the next review step would get two notifications.

 

The ability to begin review of a document, save, and come back to the same document and have full edit ability is a must when reviewing submittals.

jsappMTCSW
Contributor

Not being able to edit or delete your old markups is the worse part of this for us.  It should really function like Files with each reviewer getting their own copy for that step and editable markups.  Either a button to commit the changes or happens automatically when the step proceeds.  Very inconsistent that submittals has its own file markup system, despite Files being integrated everywhere else.  

 

I agree that the workarounds are bad, whats the point of using the cloud if everyone has their own local file system for the submittal reviews in Bluebeam?  Thank you for posting this!

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea