Monday, September 22, 2008


The Revision features in Revit have received some well deserved additions in the 2009 family of products. Things are not perfect, however we are a lot closer to achieving the expected end results especially by keeping in mind some simple facts and tips.


  1. The Revision Schedule will NOT report instances of revisions that have been hidden in the view.

  2. The Revision Schedule will STILL report instances of revisions that have been set to not be visible through the Sheet Issues/Revisions dialog box.
  3. If a sheet contains these revisions, you cannot uncheck their visibility through the parameter Revisions on Sheet in the View Properties dialog. See the highlighted, grayed-out rows below. You can however have the schedule show revisions that are not on your current sheet by checking them in this dialog. This function is mainly intended for when you want to track what sheets were issued for and when there is no associated clouding. Another example would be when a whole sheet is added to the drawing set during an addendum and you don't want to cloud the whole thing. In this case you manually check the revision that applies to this sheet so it shows up in the schedule (thanks to Aaron Maller for helping me rationalize this!).


Some firms like to place a more descriptive tag for their clouds rather than the sequence number or an alphabet letter. So for example for a revision that occurred in Addendum 3, we would want to see “AD3” instead. You can use the Description parameter to house that information and then create a tag with a label that displays this parameter. However, if you want to have a lengthy description for each revision to show up in your revision schedule, you won’t have this parameter available for this purpose. In Revit 2009, we can change the Revision Number to be Numeric, Alphabetic or None. I think we need a Custom option added because of what I just described. In the meantime, if you don’t need to use the Issued to or Issued by parameters, you can use either of them to house this information. As described above, change your tag label to read the relevant parameter.

Issuing revision sketches

When issuing a revision sketch on a small sheet (letter or tabloid size), you probably only want your schedule to display the relevant revision only. If you’re doing things in sequence, then you should be able to achieve this by doing the following to your revision schedule settings (within the title block/annotation family):

  • In the Sorting/Grouping tab: Sort by Revision Sequence in Descending order;
  • In the Appearance Tab: Set the Height to User out for the “Grid lines” checkbox as it might automatically check/uncheck itself! Then size the schedule to only display one row, which will now report the latest revision in the sequence.
If you’re working on multiple revisions and you want your schedule to show a revision other than the last one, you’ll have to at least hide the clouds of revisions that come AFTER the one you’re trying to print. In the Sheet Issues/Revisions dialog box, you can set revisions to not show, but remember that the schedule will still report them. When done, please remember to unhide the hidden elements to prevent your BIM Manager or other team members from hurting you :)

TIP When creating multiple revision clouds in a view that belong to the same revision, use the same sketch rather than creating new sketches. It will make life much easier later when you want to hide a specific revision by selecting a single sketch instead of multiple ones. It is also highly recommended to place your clouds on the view and not on the sheet. The exception to this rule is for schedules, where you have to place clouds on the sheet. EDIT: If using dependent views to split a large plan into smaller views to fit on sheets, place your clouds in separate sketches for each dependent view (you can place them in the parent, but make sure you create a new sketch for each dependent "zone"). This is necessary because your annotation crop region will prevent the clouds from displaying and scheduling since the entire sketch has to be encompassed by the annotation crop extents and that's obviously not what you want to do in dependent views. Also, if you want to itemize every cloud instance, you are forced to create separate sketches, but this is uncommon in my experience.



Aaron said...


It's "an addendum". Addenda is the plural. -

Dave Baldacchino said...

Cut me some slack, I'm a foreigner ;) Thanks for pointing that out, I should have known haha. Now it's corrected.

alleycatbabe said...

In 2008 if you made your sketches in the view you can not edit anything that falls within that bubble once it has been issued. This is why most people put the revision sketches on the sheet view. Do you know if this is still the case in 2009. If so I still recommend putting sketch revisions on the sheet.

Dave Baldacchino said...

That's incorrect. When you set a revision as "Issued", you cannot make changes to the CLOUD. The model elements are totally independent of the clouds and will always be editable. If you want to change clouds belonging to revisions that have been issued, then you have to uncheck the "Issued" option first, then make modifications to the cloud sketch.

Clouding revisions on the sheet, albeit possible, is not recommended. Let's put it this way...Best Practices dictate that you cloud on the view. If you duplicate a view as a dependent and you place your clouds on the sheet, now how will you know what areas changed without having to constantly refer to the sheet?

Anonymous said...

Hi interesting comments - all the companies I have been involved with and talking to fellow users I havn't come accross anyone who puts there revision in the view always on the sheet. This I believe is standard practice.


Post a Comment