Reading revision clouds and deltas: finding what changed on a revised sheet
Revision C arrives for the townhouse structural sheet with a cloud beside one wall. The foreman also notices a different entry in the hold-down schedule outside that cloud. He needs the complete relevant change reviewed before the crew uses the revised information.
Read the revision information and the issuer's marking conventions, then compare the relevant current and prior issues where needed. Record each work-affecting difference and route unclear information for an answer. Clouds and delta marks can help locate a change; do not assume they identify every altered requirement or that a large cloud explains the change itself.
Read the change before briefing the crew
- Confirm the sheet and issue. Check drawing identity, revision information, issue purpose and the associated instruction or transmittal. Establish which prior issue you are comparing and which new issue is authorized for this task. Use the issuer's legend or explanation for unfamiliar marks rather than applying a convention from another consultant.
- Review the marked areas and connected references. Read the changed detail, notes and affected schedules, not only the cloud's outline. Follow references to related sheets where the change depends on them. Identify any differences between the issue description and what the sheet shows. A one-line transmittal description may not describe every workfront affected.
- Compare and ask about gaps. Use an appropriate side-by-side or controlled comparison where marks are absent or too broad. Confirm comparable sheets and display settings before treating an apparent movement as an actual design change. Ask the responsible issuer about an uncertain difference; a visual overlay does not itself authorize a structural interpretation or field solution.
- Record and communicate the relevant change. Link the revised sheet, comparison and response in the document record. Describe the affected location and required next action to the appropriate foremen. Refer potential scope, cost or sequence effects through the actual review process. Check that the field receives the authorized information rather than sending an annotated screenshot without its source.
Do not reduce a complicated issue to one sentence merely to fit the register. A brief summary can point to detailed reviewed changes and pending questions. If part of the answer remains unresolved, make that status visible and identify the affected work. Crews need to know what is current and usable, not simply that a new revision arrived.
Common mistakes
- Reviewing only the cloud and skipping linked notes or schedules.
- Comparing mismatched sheets and calling every visual offset a design change.
- Briefing from an isolated screenshot without the authorized source.
Action list
Review the revised sheet
- Verify identity, issue and comparison basis.
- Read the issuer's revision conventions.
- Follow connected details and schedules.
- Record unclear differences for a response.
- Brief affected crews with current authorized references.
Check your understanding
A schedule changed outside every cloud. Should you ignore it?
