Revision Cloud Tag Revit Family: Setup That Auto-Updates

November 18, 2026 · 10 min read

Key takeaways

  • A revision cloud tag is an annotation family that reads revision data from the cloud's assigned revision, so the Revisions schedule acts as the database and the tag is just a view of it.
  • The stock Revision Tag.rfa loads from the Annotations library folder, but it is a simple label with no built-in auto-update logic.
  • A blank or stale tag almost always means the cloud was never assigned to the correct revision in the Sheet Issues/Revisions dialog, not a broken family.
  • Building a custom parametric tag takes 2-4 hours once and pulls number, date, and description per sheet, which pays off by the second correction letter for offices handling 1-3 permit sets a month.
  • Set per-project or per-sheet numbering before clouding anything, because switching mid-resubmittal forces you to reassign every existing cloud manually.

A revision cloud tag in Revit can pull the revision number, date, and issued status straight from the Revisions schedule, so your resubmittal clouds update themselves after a correction letter. This guide shows you where to load the stock tag, why it often fails to auto-update, and how to build a parametric revision cloud tag revit family that matches your office standard.

What is a revision cloud tag family in Revit?

A revision cloud tag is an annotation family: a small, repeatable symbol placed inside or beside a revision cloud that reads data from the revision assigned to that cloud. The cloud itself is just geometry marking what changed; the tag is what carries the revision number, date, or description onto the sheet.

Plan check reviewers read the tag, not the cloud. When a correction letter comes back and you cloud the fixes for a resubmittal, the tag has to match the Revisions schedule and the sheet's revision table exactly, or you get a second round of city comments. Autodesk documents how clouds, the Sheet Issues/Revisions dialog, and schedules connect in its Revit help on revisions, and the tagging step is where most offices customize (see our resubmittal workflow).

Where do you find and load the stock revision cloud tag?

Loading from the Annotations folder

Revit ships a revision tag in the US Imperial and US Metric libraries, under C:\ProgramData\Autodesk\RVT 2025\Libraries\US Imperial\Annotations. The file is Revision Tag.rfa (imperial) or the metric equivalent, and it is a simple note-style tag with a label parameter, not a cloud. If the Annotations folder is missing on a fresh install, run the Revit content installer or copy the file from another workstation. Load it with Insert > Load Family, or drag the .rfa straight into a sheet view.

Placing the tag on a clouded view

On the Annotate tab, draw the cloud with Revision Cloud, then pick Tag by Category (keyboard shortcut TG) and click the cloud. The tag reads the Revision Number from the sheet's Revisions schedule, so it shows the correct delta once the cloud's revision is assigned. If the tag lands blank, the cloud has no revision assigned yet; select the cloud and set it in Properties. For offices that want the number, delta description, and date pulled automatically instead of typed per sheet, tools like Pretiva Studio apply that office standard before sheets reach your team.

Why doesn't the stock tag auto-update with the Revisions schedule?

Because the tag is only a label. A revision cloud tag is a generic annotation family that reads shared parameters off the cloud element, and Autodesk's own documentation on the Generic Annotation family template shows it has no built-in logic. It displays whatever the cloud is bound to, nothing more.

The Revision Sequence link

The tag pulls the Revision Number only when the cloud is assigned to the correct revision in the sequence. If you add a cloud before creating the revision, or pick the wrong sequence entry, the tag shows a stale number or nothing. Every cloud must be assigned to the right revision on the Sheet Issues/Revisions dialog.

Issued and Date parameters

Issued, Date, and Description come from the Revisions schedule on the sheet. If the revision isn't issued to that sheet, those fields stay blank. The tag and the schedule must reference the same revision row.

Numbering: per project vs per sheet

Per-project numbering uses one sequence across all sheets; per-sheet restarts the count on each sheet. Pick one before clouding, because switching mid-resubmittal forces you to reassign every cloud manually. This is the kind of setup work we handle in the overnight clouding pass at Pretiva Studio for interior designers.

How do you set up the Revisions schedule so the tag pulls the right data?

Adding a revision in Sheet Issues/Revisions

Open Manage > Additional Settings > Sheet Issues/Revisions and click Add. Give the revision a Number, Date, and Description that matches your correction letter, then set Issued to (the city or plan checker) and Issued by. Leave Issued unchecked until the resubmittal actually goes out, and set Show to Cloud and Tag so the tag appears wherever you cloud.

The tag family reads the Number, Date, and Description parameters from this dialog, so spelling them here correctly is what makes the tag correct on every sheet. If your office standard shows "2" instead of "02", fix the Number format here, not in the tag.

Clouding on sheets vs on views

You can sketch a revision cloud on the sheet itself or inside a view placed on the sheet. Clouding in the view is the safer habit: the cloud and its tag stay attached to the model geometry and move with the view on resubmittals. Either way, the tag pulls from the revision you assigned in the dialog above, and the Revisions schedule on your title sheet updates from the same source. Tools like Pretiva Studio (https://studio.pretiva.io/) apply this sequence when clouding permit sets overnight.

How do you build your own parametric revision cloud tag family?

Starting from the Generic Annotation template

New Family → Annotations → Generic Annotation.rft. This template gives you a family with no model geometry and full access to shared revision parameters, which is exactly what a tag needs. Draw nothing; a tag family can be an empty box that only carries labels.

Adding labels for Revision Number, Date and Issued

Place three label parameters and bind them to Revision Number, Revision Date, and Issued. Per Autodesk's documentation on revision schedules and tags, these are the instance parameters Revit pushes to any tag attached to a clouded element once the revision is assigned in the project. Stack them as three lines: number on top, date under it, and Issued as a yes/no-driven text swap or a parameter-driven line. Set the label text to your office standard font and size, typically 2.5mm or 3mm on residential CDs.

The reason this works at all is that the tag is not storing anything. It reads whatever revision is assigned to the cloud in the project browser, so a resubmittal that adds Revision 2 with a new date updates every tag on the sheet without touching a single family. That is the whole trick: the Revisions schedule is the database, the tag is just a view of it. If your correction letter adds a revision and your tags do not change, the problem is almost always that someone drew a cloud but never assigned the revision to it in Manage Revisions, not that the family is broken.

Visibility settings for issued vs unissued clouds

Add a Yes/No family parameter called something like Show Issued Line, or drive the Issued label's visibility off the built-in parameter directly. On the label's Visibility Graphics override in the project, you can also grey out issued clouds so reviewers see at a glance what is new in this resubmittal versus what was clouded on the previous plan check.

Saving and swapping the family in existing projects

Save as A-REVT-Tag_OfficeStandard.rfa, load into your project, and overwrite the existing version when prompted. All placed tags update in place. If you run 1-3 permit sets a month, keeping the family in your office template means the swap happens once, not per project. For residential practices working through Washington State plan check cycles, the same logic applies to drafting automation: tools like Pretiva Studio's residential drafting workflow return sheets already clouded to your office standard, so your custom tag does the labeling on the way out.

Which tag setup fits which office standard?

Three setups cover most residential practices, and the right one depends on how many resubmittals you handle and how fussy your plan check reviewers are.

SetupSetup timeAuto-updates from Revisions schedule?Resubmittal fit
Stock tag, loaded as-isMinutesNo, you type the revision number manuallyFine for occasional one-off clouds
Modified stock tag30-60 minutesPartial, if you add a label bound to a revision parameterWorks until a city comment demands a detail the stock label can't show
Custom parametric tag2-4 hours onceYes, pulls description and number per sheetCleanest for 1-3 permit sets a month with recurring correction letters

If you cloud one or two sheets a year, stop at the stock tag. If every resubmittal means re-clouding across full sheets, the custom parametric tag pays for itself the second correction letter. The modified stock tag is the honest middle ground when a contract drafter needs something working by Friday.

How does clouding work on a resubmittal after a correction letter?

When the city returns a correction letter, add a new revision first: Issue Date set to the resubmittal date, Description matching the letter's language, and Numbering set to "Per Project" or "Per Sheet" per your office standard. Then cloud only what changed. Select the revision as Active in the Sheet Issues/Revisions dialog, sketch clouds around the affected conditions, and the tag you built in the previous section pulls the new sequence number automatically. Anything unclouded stays untouched, which is exactly what the plan checker wants to see.

The tag numbering should match the city's expectations: if the correction letter references "Sheet A2.1, cloud 3," your tag on that cloud should read 3, not a project-wide count. Number per sheet for residential plan check unless your jurisdiction says otherwise.

If you draft 1-3 permit sets a month and the clouding cycle is eating your evenings, this is where automation earns its keep. Pretiva Studio handles the overnight drafting and returns clouded sheets for your review, with the Solo plan at $349/month, priced "For a one-architect practice" (Pretiva Studio pricing).

Can drafting automation handle the clouding and tagging for you?

Partly. Pretiva Studio runs the repetitive drafting overnight in your own Revit 2025-2027, to your office standard, and sheets come back clouded and ready for your team to review, redline and stamp. You stay the one who decides what gets clouded on a resubmittal; the tool does the sheet setup and tagging so your contract drafter spends hours on judgment instead of placement.

Run it through the same criteria as anything else: does it work inside Revit, does it follow your sheet setup, and does it leave you in control of the stamp? Pretiva scores well on all three for residential CDs. Swapp and ArchiLabs aim at larger firms and full CD generation. Draftmate by Civly targets residential sets directly. None of them replaces your review, and none should. The test is simple: if the output fails your plan check, it goes back, exactly like a drafter's work would.

FAQ

Why is my revision tag showing the wrong number on the sheet?

The cloud is almost certainly assigned to the wrong revision in the sequence. Select the cloud, check Properties, and confirm it points at the correct entry in the Sheet Issues/Revisions dialog. A tag also goes stale if you drew the cloud before creating the revision at all. Fixing the assignment fixes the number everywhere.

How do I make the revision cloud tag show the date instead of the sequence number?

Edit the tag family, select the label, and change its bound parameter from Revision Number to Revision Date. Save, load into the project, and overwrite the existing version when prompted; every placed tag updates in place. If you want both, stack two labels in the family: number on top, date underneath, sized to your office standard.

Can I copy a revision cloud tag family from an old project into Revit 2026?

Yes. Open the old project, find the family in the Project Browser under Families > Annotation Symbols, right-click, and copy, or use Insert > Load Family to browse a saved .rfa. Annotation families carry forward cleanly between Revit versions. Paste into the new project and overwrite the stock tag if prompted, then verify the labels still bind to the revision parameters.

Do revision clouds have to be on the sheet or can I cloud in the model view?

Either works, but clouding in the model view is the safer habit. The cloud and its tag stay attached to the model geometry and move with the view on resubmittals, so nothing drifts out of position. Clouding directly on the sheet works fine too; the tag still pulls from the revision assigned in the Sheet Issues/Revisions dialog either way.

How do I number revisions per sheet instead of per project?

Open Manage > Additional Settings > Sheet Issues/Revisions and set Numbering to Per Sheet. Each sheet restarts its count at 1. Decide this before you cloud anything: switching mid-resubmittal forces you to reassign every existing cloud manually. Per-sheet numbering matches most residential plan check expectations, unless your jurisdiction's correction letter references a project-wide count.