Why controlled change matters
No set survives construction unchanged. Conditions emerge, owners adjust, and authorities ask for more. The question is never whether the documents will change but whether everyone can trust what changed. Uncontrolled revisions are how two crews end up building from two different versions of the same wall. Document control exists to prevent exactly that.
A revision is a small contract amendment. It has to be visible, dated, and traceable. Best-practice markup tools such as Bluebeam Revu have made this discipline faster, but the principles predate the software: show what moved, number it, and log why.
Revision clouds and delta tags
A revision cloud is a freeform outline drawn around the part of a sheet that has changed since the last issue. Next to it sits a delta — a numbered triangle — that ties the change to a row in the revision block. Together they let a reviewer scan a sheet and land on the change instantly, without comparing two drawings line by line.
A revision nobody can find is a revision nobody will build. The cloud is not decoration — it is how the change reaches the field.
Clean revision graphics depend on the same discipline as the rest of the set. They sit alongside well-organised technical callouts and a current index, all of which we maintain as part of our construction documentation services.
The issue log as project memory
Behind the clouds sits the issue log: the running record of every revision number, its date, the sheets it touched, and the reason behind it. It is the project's memory. Months later, when someone asks why a beam grew or a door swing flipped, the log answers without anyone reopening an argument.
A reliable log depends on a stable foundation, which is why we pair it with a disciplined sheet index that always matches the set.
Running a clean re-issue
- Cloud only what changed since the last issue, then clear old clouds.
- Assign a new delta number and a single issue date across the package.
- Update the revision block on every affected sheet, not just the index.
- Record the change in the issue log with a plain-language reason.
- Distribute a complete reissued set so no partial versions circulate.
Professional document-management guidance from the American Institute of Architects underpins these steps and keeps the record defensible.
Frequently asked questions
What is a revision cloud?
A revision cloud is a freeform outline drawn around an area of a sheet that has changed since the last issue, paired with a numbered delta tag, so reviewers can find exactly what was modified without comparing whole drawings.
What belongs in an issue log?
An issue log records each revision's number, date, description, affected sheets, and the reason for the change. It is the authoritative history of the set, letting anyone trace why a sheet looks the way it does at any point in the project.
Keep your changes traceable. Request a free quote or explore more in our Insights library.
Cadeonn builds permit-ready construction document sets — sheet indexes, callouts, spec coordination, and revision-controlled deliverables to your office standards. Keep principals on design while we draft the set: request a quote or start a pilot scope.