[Troy DeGroot]

Great post @lizlarsen

I do see some pushback from some users, typically because it’s a little more advanced to set up (but easy after the 3rd time). I am and will remain a HUGE advocate for using sets. My only complaint is that I wish they called it a “Binder” instead of a “Set”. It was a set before we exported all the sheets and pulled them back together again!

The biggest benefit I see for teams switching to Binders is that everyone is looking at the exact same set of drawings and it’s always current. Typically when a user runs into a “read-only” file, they create their own copy on their desktop. pretty soon there are six copies out there and a revision comes through and not everyone knows. Slip Sheet is one of my favorite tools in Revu because of the value it provides and how easy it is to run.

When I was working for a structural engineer, our folder structure was always, Drawings > Discipline > Date or issue

This makes it easy to map to a folder of updated drawings. Only one person needs to manage the updates also because everyone else has the .bex file pinned for the life of the project. This folder structure is also important so if the drawing folder is moved all the sub-folders stay relative with hyperlinks.

As a best practice, you might slip sheet updates, and create a brand new Binder for an Issued Set.

As for Binders in Studio, I build the drawing folder structure in the Studio Project along with the .bex file and encourage all my users to work from there. In the rare chance two users need to look at the same sheet, you can push that sheet to a Session. Once you’re finished collaborating return it to the Project. Pushing to a Session checks out the document from the Project until you check it back in when you finish the Session.

Whew, did I cover everything?

In summary, I hate “Sets”, but I love “Binders”🤣