Revision clouds - In the view or on the sheets?

[Marcus.Isacsson]

Hi fellas!

We have an internal discussion here at our office. 
How do you place your revision clouds, in the affected views or on the actual sheets?
And why do you place them like you do?

Thanks in advance!

[ToanDN]

---

@Anonymous wrote:

If you do are likely to do future tenant improvements in the same buildings as previous projects, clouding on sheets is absolutely the way to go. 

My office does many tenant improvements in the same buildings. When the next TI begins, we'll migrate the previous Revit project as it has all of the latest existing conditions, sheets and majority of the views already created. We merge down all model content to be "existing", purge out the old demo content that's now "temporary", and merge down all revisions to one that becomes the first new revision/submittal milestone for the new project. When clouds are on the sheets, its very easy to purge them all by opening each sheet, doing a big crossing window and deleting, so you start with a completely blank slate. When they are in views, it gets infinitely more complicated and becomes a time suck. Sheets you want to issue later will have that merged down revision that can't be uncheck and it can cause later users to chase their tail trying to find it if they're not a savvy user. I personally always cloud sheets, but after encountering this difficult issue, it cemented my stand.

---

I started clouding on sheets more than in view but for other reasons.  For yours, why do you need to delete the actual clouds?  Just delete the Revision entries from the Revision manager and all the associated clouds and tags will be gone.

[Anonymous]

I find that placing revisions in a view is the best practice. If I am clouding in a view its much quicker and easier to cloud right when I make the changes and not have to deactivate my view then cloud the reactivate my view. Or use the other process of making all of my changes and then deactivating and clouding all of my changes. This can lead to accidentally miss clouding a change. Another advantage is if I am working on a project that has match lines I can go to my overall view and see the clouds, the only way you can see clouds if clouding on the sheet is to look at the sheet view. Still another advantage is when making sketches. If I cloud in the view, I can duplicate the view and my clouds are already there. If I am doing it on a sheet view I have to draw the clouds twice. Finally if a view is moved on purpose or by accident, if my clouds are in the view, they will move right along with the view being moved. It doesn't work that way if they are on the sheet.

[jake.smartARTVU]

In my view this is the principal disadvantage and we have a protocol in place in our practice to state that people should not apply clouds in views. 

The trouble arises when a cloud has been applied, then switched off for a further revision, then that view is duplicated for use on a sheet for another purpose (e.g. a general arrangement plan that has been issued multiple times and then used as the basis of a floor finishes plan). If the revisions clouds are present in the view, the new sheet will have multiple revisions even though it has not been issued. It is then not possible to remove the revision from the sheet without first finding it in the revision window and changing its visibility. Then the cloud can be deleted from the new view and the visibility can be reset. Very annoying when there are hundreds of the things and no way of finding just the ones in views.

Another argument for sheets - sometimes you want to cloud the omission of a view or some change to the titleblock.

[tjkollar_MKE]

Hands down views! By doing so, you can use the comments parameter to write a breif discription on what that the revision is for. Why do that? Well, you can schedule the revisions to show the detail name + number, in addition to the sheet name and number that the revsion is in. This makes it vastly easier to create your ASI/CB narrative. 
Downsides, pulling the detail/sheet information does not work in depentent views. Just one of the reason why I dispise them. They create more work needed than simply modifing your project browser organization. 

[HVAC-Novice]

On sheets. Revisions also apply to schedules and text and that only can be done on the sheet (AFAIK).

[RSomppi]

Choose a methodology that works for you.