Revit Tip: Revit Revision Cloud and Tag Workflow

Today’s tip focuses on building a clean, reliable workflow for Creating and Managing Revision Clouds and Tags in Revit—so your change history is clear, auditable, and ready for issue at any stage. If you’re refining your team standards or preparing for your next addendum, these practices will keep you fast and consistent. For licensing, upgrades, and expert advice on Autodesk Revit, consider NOVEDGE.

Set up your revision sequences first

• Open the Sheet Issues/Revisions dialog and define sequences before you start clouding.
• Choose Numbering: Numeric or Alphanumeric based on office standards.
• Choose Sequence: Per Project for a single global series, or Per Sheet to avoid gaps on unaffected sheets.
• For each sequence, set Show to:
  • Cloud and Tag during review and markup
  • Tag after issue to keep deltas but hide clouds
  • None for documentation-only entries (still listed in the title block)
• After you issue, check Issued to lock the sequence and freeze the record.

Place clouds and tags with intent

• Cloud in the view if the change is view-specific; cloud on the sheet for sheet-level notes and general revisions.
• Use one cloud per logical change area; then add multiple tags if needed for clarity—avoid overlapping clouds that complicate tracking.
• When working with dependent views, place the cloud in the parent or the correct dependent view to ensure it shows only where intended.

Control graphics for clarity

• Set Revision Cloud types with appropriate Arc Length for different drawing scales (e.g., larger arcs for site plans).
• Standardize line weight, pattern, and color for Revision Clouds via Object Styles to keep appearance consistent project-wide.
• Include visibility rules in your View Templates so review and issue sets render clouds and tags the same way on every view.

Sheet lists and title block behavior

• Use Revisions on Sheet to show a revision in your title block even when no cloud appears (common for document-only updates).
• Configure the Revision Schedule in your title block family with fields like Number, Date, Description, Issued To, and Issued By.
• Keep descriptions standardized (e.g., “Addendum 02,” “Bulletin 03,” “ASI-05”) to align with your issue register.

Team and coordination tips

• Adopt Per Sheet numbering for multi-building or multi-discipline sets to reduce confusion when some sheets skip issues.
• For consultant links, do not rely on linked revision clouds for your sheet records—capture external changes via Revisions on Sheet and a clear description.
• Archive each issue set (PDF set and model snapshot) right after marking Issued to preserve an immutable record.

Quality and troubleshooting

• Avoid editing an Issued sequence; create a new sequence for subsequent changes.
• If tags show the wrong number, confirm the tag references the correct cloud and that the cloud is assigned to the intended sequence.
• If clouds disappear unexpectedly, check the view’s template/category visibility and the sequence Show setting.

A disciplined revision workflow shortens reviews, reduces rework, and makes your deliverables more trustworthy. For software guidance, add-ons, and purchasing options, visit NOVEDGE.