Revit Tip: Revit Revision Workflow: Numbering, Clouds, and Schedules

Dial in your revision workflow so every cloud, tag, and entry reads cleanly and audits flawlessly across sheets.

Start with a clear numbering strategy

• Decide early: Per Project vs Per Sheet. Per Project keeps a single running sequence; Per Sheet restarts numbering on each sheet—ideal for large, multi-package sets.
• Choose numbering type: Numeric (1, 2, 3) or Alphanumeric (A, B, C or A1, A2…). Set prefixes/suffixes (e.g., “SK-”, “AD-”) for addenda, bulletins, or discipline splits.
• Lock history by marking issued revisions as Issued. This freezes descriptions and hides/locks clouds depending on your settings, preserving audit trails.

Configure the Sheet Issues/Revisions dialog

• Create distinct sequences for typical milestones: ASI, Addendum, Bulletin, Permit, IFC. This avoids renumbering conflicts mid-project.
• Populate Description, Issued To, Issued By, and Date for every entry. Consistent metadata ensures clean title block output and downstream traceability.
• Control visibility per revision with Show: Cloud and Tag, Tag, or None. Use Tag when you must record an issue without a visible cloud; use None for record-only items.

Place and manage revision clouds with intent

• Use Tag on Placement to auto-tag each cloud; it reduces missed annotations and speeds QC.
• Set a consistent Arc Length (type property) for legibility at your common sheet scales—coarse arcs for small-scale plans, finer arcs for details.
• Standardize graphics via Object Styles and Line Styles for Revision Clouds, and keep a View Template that enforces line weights and visibility.
• Place one focused cloud per change area; avoid “blanket” clouds that span multiple unrelated edits.

Make title block revision schedules bulletproof

• Edit your title block family and add the built-in Revision Schedule if it’s missing. Configure it to Per Sheet to avoid listing global revisions unintentionally.
• Limit rows to a practical number (e.g., 5–8). Older revisions remain in the model history while the schedule displays only current items.
• If you must show a revision with no cloud (e.g., spec-only change), set Show to Tag or None and add the revision to the sheet via Revisions on Sheet.

Quality control and team habits

• Before issue, run a visual sweep: toggle Thin Lines and use Temporary Hide/Isolate to check cloud placement and tags.
• Avoid deleting revisions; supersede them by updating the description and marking Issued. Deletion risks breaking paper trails.
• Document your standard in the project template and BIM Execution Plan so numbering and visibility choices are consistent across teams.

Pro tips

• Use a dedicated working view to place and review clouds without cluttering production views; then duplicate with detailing to publish.
• For mixed packages, create separate sequences with clear prefixes (e.g., AD-, BUL-) to keep schedules intelligible.
• Consider Dynamo/API to batch-assign Revisions on Sheet for large sheet sets.

Need Autodesk Revit or expert guidance on standardizing revisions? Connect with NOVEDGE. Explore Revit solutions and licensing options at NOVEDGE | Revit, and tap their team for implementation best practices and workflow tuning at NOVEDGE.