How to Add a Revision Cloud in Revit
Key takeaways
- Create the revision in the Sheet Issues/Revisions dialog before sketching, because a cloud only appears in a revision schedule if it is attached to a revision.
- Reassign every cloud to a surviving revision before deleting one, since deleting a revision blanks deltas and shifts the numbering sequence on your sheets.
- Use per-sheet numbering for residential permit sets so a resubmittal restarts at 1 on changed sheets while the rest of the set keeps its numbering.
- If you cloud changes in Word or Excel, create the matching revision in Revit first and use the same number, or your schedule and clouds will tell different stories.
- Clouds only print and appear on sheets when the view is placed on a sheet, the revision is issued and visible, and the cloud sits inside the crop region.
To add a revision cloud in Revit, open the sheet, go to the Annotate tab, click Revision Cloud, sketch the boundary around the change, and Revit tags it with the active revision's delta number. Assign the revision first under the Sheets' Revisions dialog so the cloud pulls the right number and date into the schedule. This guide covers creating and editing clouds, how issuance numbering and sequence work on your sheets, and a workaround for clouding changes that come back as Word or Excel markups.
How do you add a revision cloud in Revit?
Adding a revision cloud in Revit 2025-2027 takes three steps: create the revision, sketch the cloud, then tag it. The cloud only appears in a revision schedule if you attach it to a revision first, so start there. Autodesk documents the full workflow in its Revit Help on revision clouds and the Sheet Issues/Revisions dialog.
Step 1: Create the revision in the Sheet Issues/Revisions dialog
Open the View tab, click the Revisions dropdown, and choose Sheet Issues/Revisions. Click Add, set Numbering to per sheet or per project, choose a delta symbol (triangle, circle, or tag), and type the description your city's correction letter uses, such as "Plan check corrections 1." Leave Issued unchecked so the revision stays editable.
Step 2: Sketch the cloud
On the Annotate tab, click Revision Cloud, then pick the revision you just created from the options bar. Sketch around the changed geometry and close the loop. If nothing is clouded yet, the revision stays invisible on sheets.
Step 3: Tag it with a delta
With the cloud selected, add a Revision Tag from the Annotate tab. The tag pulls the delta and sequence number automatically.
| Setting | Where | Typical residential value |
|---|---|---|
| Numbering | Sheet Issues/Revisions | Per sheet |
| Delta | Revision tag type | Triangle |
| Description | Sheet Issues/Revisions | Matches correction letter |
If you want the whole resubmittal clouded overnight against your office standard instead of by hand, that is what Pretiva Studio's revision cloud workflow handles on your own Revit files.
How do you edit a revision cloud in Revit?
Reshaping and moving the cloud
Select the cloud and you get sketch mode, same as when you drew it. Drag individual segments to tighten the bubble around the change, or grab the whole cloud and move it. If a cloud sits on the wrong element, it is usually faster to delete and redraw than to fight the segments. Keep the cloud inside the sheet's crop region, or it will vanish on the plot.
Reassigning a cloud to a different revision
Open the cloud's Properties and swap the entry in the Revision field. Revit retags the delta and updates the revision schedule on that sheet automatically. This is how you fix a cloud that got tagged with the wrong resubmittal number without redrawing anything. If the delta tag does not move, check that the revision is set to Visible and that the tag family is loaded.
Why deleting a revision breaks existing clouds
Deleting a revision from the Revisions dialog does not cleanly remove it. Clouds assigned to that revision lose their assignment, deltas can show as blank, and the numbering sequence on your sheets shifts. The safe path is to reassign every cloud to a surviving revision first, then delete. If a correction letter drops an item entirely, delete the cloud, not the revision, and let the schedule renumber. The same discipline applies if you are reviewing overnight-drafted sheets from a tool like Pretiva Studio: fix assignments before touching the revision list.
How does the revision schedule work on a Revit sheet?
Numbered vs. alphanumeric sequencing
Each revision you create in the Revisions dialog carries a Numbering setting: Numeric, Alphanumeric, or None. Revit assigns numbers in the order revisions are issued, and that sequence drives both the cloud tag and the revision schedule row. If you set a revision to None, its clouds still appear but the schedule skips it.
Per-sheet numbering for residential permit sets
For a 1-3 permit set a month, per-project numbering is usually fine, but city comments can bite you. If plan check comes back and you add a second revision to one sheet only, per-sheet numbering restarts that sheet at 1 while others show 2, which is exactly what some jurisdictions expect on a resubmittal. Per the Autodesk Help documentation on revision schedules, the revision schedule placed in a title block family pulls only the revisions that appear on that specific sheet, in sequence order, showing number, date, and description. That is why a per-sheet schedule stays clean: a sheet with one clouded detail shows one row, while the full set's numbering stays intact elsewhere. If your title block has no revision schedule family yet, edit the family, place a Revision Schedule element, and set its fields to match your correction letter format, then reload it into the project. The same title block logic applies to interior design sheet sets (Pretiva Studio for interior designers).
Adding the revision schedule to your title block family
Open your title block family, use the Revision Schedule tool from the View tab, and drag it into the border. Choose which fields appear (Seq, Date, Description are typical) and whether it shows per-sheet or per-project data, then load it back in. Every sheet using that family now lists its own clouds automatically.
How do you set up revisions for a resubmittal after plan check?
Open the Sheet Issue/Revisions dialog (View tab > Revisions) before you cloud anything. Create one revision per correction letter, numbered per sheet, and name it so the city can trace it: "Plan Check 1 – 2025-06-12 – City of Seattle SDCI" works. When the second correction letter lands, add a second revision rather than reusing the first, so each resubmittal has its own delta and date.
Naming revisions so the city can trace them
Keep one convention across every permit set: round number, date, jurisdiction. If a plans examiner asks which clouds answer which city comments, the revision schedule on each sheet answers for you.
Issued vs. not-issued clouds
Set the revision to "None" (not issued) while you draft, then flip it to the actual issue date when you stamp and send. Unissued clouds never print a delta on the sheet, so a half-finished resubmittal stays clean.
Clouding only what changed on resubmittal
Cloud only sheets with real changes, and tag each cloud to the correct revision. If a contract drafter handles the redlines, a tool like Pretiva Studio can return sheets already clouded to your office standard overnight (https://studio.pretiva.io/residential-designers), and you spend the morning checking instead of clouding.
How do you handle revision clouds when drawings leave Revit for Word markups?
Sometimes the city's correction letter comes back as a Word file with comments pasted over your sheets, or a consultant sends markups you want to cloud without reopening every view. You can still keep the cloud-and-delta record in Revit while clouding in Word.
Exporting the sheet and clouding in Word
Print or export the affected sheets to PDF, then insert them into a Word document. Use Word's Insert > Shapes > Cloud callout (or the Scribble tool) to draw the cloud, and type the delta number and description next to it as a text box. This mirrors what you'd draw in Revit, just on a flattened copy.
Keeping the Word cloud and the Revit revision in sync
The trap: if you cloud in Word but never issue a revision in Revit, your revision schedule and your clouds tell different stories. Create the matching revision in Revit first, note its number, then use that same number in Word. Autodesk documents how numbered versus per-sheet revision numbering assigns sequences, so match whichever scheme your title block reports.
For scanned existing conditions that need clouding after the fact, a scan-to-as-built pass (https://studio.pretiva.io/scan-to-as-built) gets the base model current before you start the resubmittal cycle.
Can you make a revision cloud in Excel?
Drawing a cloud shape in Excel with inserted shapes
Excel has no revision cloud tool, but Insert > Shapes gives you a Scallop shape you can stretch over a pasted screenshot or PDF snapshot of a sheet. It approximates the look, but it is not a Revit object: it carries no revision number, no sequence, and it never appears in a revision schedule. You also lose the underlying model geometry, so any dimension you check against the markup is a guess. Treat Excel clouds as communication, not documentation.
Using Excel as the revision log across a permit set
Where Excel earns its keep is the revision log itself. A sheet with columns for revision number, date, description, and clouded sheets tracks the full history of a permit set across correction letters and resubmittals, and it is easier to share with your plan check contact than a schedule buried in each title block. The practical split: cloud and number the revisions in Revit so the sheets stay authoritative, then keep a running Excel log as the project-level record. If drawings have already left Revit for Word markups, note the change in the Excel log and mirror the same revision number once you redraw the cloud in the model.
What are common revision cloud mistakes in permit sets?
Clouds assigned to the wrong revision
If a cloud is tagged with the previous resubmittal's number, the city sees a delta that matches nothing in the revision schedule. Check the Revision property in the cloud's instance, not just the sheet's Issued value. When you add a revision cloud in Revit, the cloud inherits whichever revision is current in the project, so confirm it before the sheet prints.
Forgetting to issue the revision
A clouded sheet with a schedule row that shows no date or sequence reads as incomplete at plan check. Set the revision to Issued before exporting, so the number, date, and description populate on every schedule.
Clouds on views that are not placed on sheets
Clouds drawn in a draft view or an unplaced view never appear anywhere, so a correction gets missed silently. Cloud only views that are on a sheet, and sweep the sheet set for clouds with no delta before the resubmittal goes out. If corrections came back as a Word markup instead, rebuild the cloud in Revit rather than tracing shapes from a Word file, since Microsoft's documentation on inserting shapes in Word and Excel covers drawing shapes manually, not linking them to a revision schedule.
How do you speed up clouding a full resubmittal set?
Copy/paste aligned and revision transfer between files
When a correction letter touches sheets that exist in another file, open both projects, select the clouded views, and use Copy/Paste with Aligned to Selected Views. The clouds land in the same sheet positions, and the revision sequence travels with them. For linked models, use Transfer Project Standards to bring over the revision sequence itself, then renumber the new round so the sheet's revision schedule shows the resubmittal number your city expects. Check one sheet per round before batch-pasting the rest; a misnumbered sequence across 20 sheets is worse than doing two by hand.
Where overnight drafting changes the clouding workflow
If you run a one-architect practice, the repetitive part is not the clouds, it is regenerating the sheets that need them. Pretiva Studio runs that drafting work overnight in your own Revit, to your office standard, and each sheet returns clouded and ready for your redlines and stamp. You spend the correction round reviewing instead of modeling, which is the shift from modeling to managing. Swapp and ArchiLabs target larger production workflows; Draftmate by Civly and Blueprints AI also work in this space. For 1-3 permit sets a month, the Solo plan at $349/month is priced for exactly this buyer.
FAQ
Why is my revision cloud not showing up on the sheet?
Three usual causes: the cloud was drawn in a draft view or a view not placed on a sheet, the revision is set to Issued with visibility off, or the cloud sits outside the sheet's crop region. Also confirm the revision is set to Visible and that the delta tag family is loaded into the project.
How do I change a revision cloud from a cloud shape to a triangle or rectangle?
The cloud shape itself is fixed; the delta number beside it is what changes. Select the Revision Tag and pick a different tag type in Properties, or edit the tag family to swap the triangle for a circle or rectangle. The delta symbol is set per revision in the Sheet Issues/Revisions dialog, so changing it there updates every cloud using that revision.
Can I renumber revisions in Revit after issuing them?
You can edit the Numbering field in the Sheet Issues/Revisions dialog, but Revit assigns sequence numbers in issue order and clouds reference the revision they are assigned to, so renumbering after issue risks blank deltas and shifted schedule rows. The safer path is reassigning every cloud to a surviving revision first, then adjusting the list.
How do I copy revision clouds from one Revit file to another?
Open both projects, select the clouded views, and use Copy/Paste with Aligned to Selected Views so clouds land in the same sheet positions with their revision sequence attached. For linked models, use Transfer Project Standards to bring the revision sequence over, then renumber the new round. Check one sheet before batch-pasting the rest.
Does a revision cloud print on the PDF by default?
Yes, as long as the revision is set to Issued and the cloud sits on a placed view inside the crop region. Unissued clouds never print a delta, so a half-finished resubmittal stays clean. Before exporting, sweep the set for clouds with no delta and confirm each schedule row shows a number, date, and description.