Revit Tip: Standardize Revit Revision Clouds and Revision Schedules

Make every issuance unambiguous and auditable by standardizing how you use Revision Clouds and Revision Schedules in Revit.

Set up once in your template (Manage > Additional Settings > Sheet Issues/Revisions):

• Numbering method:
  • Per Project for a single running sequence across the set.
  • Per Sheet to restart numbering on each sheet (helpful for long projects or discipline packages).
• Number format:
  • Numeric when you want 1, 2, 3…
  • Alphanumeric when you need custom IDs (e.g., ASI-01, BUL-02). Enter the exact value in each revision row.
• Parameters to maintain for each revision: Description, Date, Issued By, Issued To. Fill these consistently to power schedules and sheet lists.
• Visibility after issue:
  • Clouds and Tags visible (during review).
  • Tags only (common after issue—retains the delta without the cloud).
  • None (archives the history but cleans drawings).

Placing and managing Revision Clouds:

• Place clouds in the relevant view so they travel with the view onto the sheet. Use sheet-level clouds only for sheet notes that don’t belong to a specific view.
• Select each cloud and assign it to the correct Revision entry in Properties to ensure it shows in the right schedule row and delta number.
• Use appropriate Revision Cloud Types (arc length) for legibility at different view scales.
• Load and use a Revision Tag family (delta symbol) to display the revision number where required by your standards.
• Avoid duplicating the same change across multiple clouds; one clear cloud and a concise description reduces clutter.

Driving the Revision Schedule on title blocks:

• Embed a Revision Schedule in the title block family and set a reasonable maximum number of rows to prevent crowding.
• On each Sheet, use the Revisions on Sheet property to control which revisions list in the schedule.
• Include key fields (Number, Date, Description, Issued By/To) to match your QA/QC and contract requirements.
• For large histories, show only recent items in the schedule and provide a separate, project-level log when needed.

QA and release workflow:

• Before publishing, create a Sheet List with Current Revision parameters to verify every sheet’s state.
• Mark revisions as Issued to lock the record; then switch visibility to Tags only or None per your standard.
• Archive a PDF set with revision identifiers in filenames and transmittal records for traceability.

Common pitfalls to avoid:

• Deleting clouds after issue—hide them via settings instead to preserve the audit trail.
• Inconsistent numbering between packages—decide Per Project vs Per Sheet up front and document it in your template.
• Unfilled metadata—empty Description/Date fields undermine schedules and legal records.

Standardize these practices in your office template and document the steps in your BIM Execution Plan. For licensing, training, and expert add-ons, consider partnering with NOVEDGE. Explore Autodesk Revit options and services through NOVEDGE’s Revit offerings to strengthen your revision control workflow.

You can find all the Revit products on the NOVEDGE web site at this page.