Where Are Changes To The Drawings Noted: Complete Guide

Ever stared at a set of blueprints, scratched your head, and wondered — who actually writes down the changes?

You’re not alone. In the world of architecture, engineering, and construction, the little notes that say “move this wall 2 ft” or “use a different steel grade” can make or break a project. And if those changes aren’t logged correctly, you’ll end up with costly re‑work, schedule delays, and a lot of angry stakeholders.

So let’s dig into where those changes live, how they’re supposed to be captured, and what you can do to keep the paper trail clean.

What Is a Drawing Change Log?

In plain English, a drawing change log is the record‑keeping side of a revision. Every time a designer tweaks a plan, a new revision number (or letter) is assigned, and the specific alteration is described somewhere on the drawing set.

Think of it as the “change diary” for a building. It lives in a few places:

• The revision block on the title sheet – a table that lists revision number, date, description, and who approved it.
• Clouds and revision clouds – those squiggly outlines you see on a plan, usually with a call‑out like “R‑C‑03”.
• Supplemental sheets – sometimes a separate “Revision Log” sheet is added to the drawing set, especially on larger projects.

These aren’t just decorative; they’re the legal proof that everyone agreed to a change before the work started.

The Revision Block

Most standards (ISO 7200, AIA, BS 1192) require a revision block on the drawing title. It’s a compact table that looks something like this:

Every new entry pushes the previous ones down, so the most recent change is always at the top.

Revision Clouds

When a designer wants to point out a specific area, they draw a cloud around it and tag it with the revision identifier (e.The cloud tells the contractor, “Hey, this spot changed in revision B., “R‑B”). In practice, g. ” The cloud itself isn’t the log, but it references the log entry that lives in the revision block.

Supplemental Revision Sheets

On mega‑projects—think hospitals or airports—you’ll often see a standalone sheet titled “Revision Log” or “Change Register.” It expands on the brief description in the revision block, sometimes adding impact notes, cost implications, and cross‑references to other drawings.

Why It Matters

If you think a scribble in the margin is harmless, think again. A missed change can cascade into a nightmare:

• Cost overruns – building a wall where a door should be means you have to demolish and rebuild.
• Schedule slips – the contractor discovers the mismatch only after a concrete pour, forcing a stop‑work order.
• Safety risks – imagine a structural beam moved without a proper review; the whole building’s integrity could be compromised.
• Legal exposure – contracts often tie payment milestones to “approved drawings.” If the approved set doesn’t match what’s on site, you’re looking at disputes and possibly litigation.

Real‑world example: a mid‑size office tower in Chicago went over budget by $1.2 million because the HVAC designer changed a duct size on a later revision, but the change never made it onto the contractor’s shop drawings. The contractor installed the original size, the system under‑performed, and the owner demanded a retrofit. All because the change log was buried in a supplemental sheet that no one checked Less friction, more output..

How It Works (Step‑by‑Step)

Below is the typical flow from “I think we need to move that wall” to “Everyone knows the new location.”

1. Identify the Need for Change

Designers, owners, or contractors spot a conflict.
A quick site walk‑through might reveal that a column clashes with a new equipment layout. The first step is to document the issue—usually in a Request for Information (RFI) or a change request form Easy to understand, harder to ignore..

2. Issue a Formal Change Request

The request goes to the design lead, who evaluates the impact: structural, cost, schedule, code compliance. If approved, the designer creates a revision It's one of those things that adds up. No workaround needed..

3. Update the Drawing

Open the CAD/BIM model.
Make the geometry change, then:

1. Increment the revision identifier (A → B → C, or 01 → 02).
2. Add a revision cloud around the altered area.
3. Insert a call‑out tag that matches the new revision (e.g., “R‑02”).

4. Fill Out the Revision Block

On the title sheet, add a new row:

If the project uses a supplemental revision sheet, copy the same info there, plus any notes about cost or schedule impact.

5. Review & Approve

The updated drawing goes through the same review cycle as the original set: peer review, client sign‑off, possibly a building official stamp. Once approved, the revision is released—meaning it’s the version the contractor must follow Simple, but easy to overlook..

6. Distribute the Revised Set

Distribution can be digital (BIM 360, SharePoint) or physical. Because of that, most firms use a revision control number in the file name: BldgA_Rev02. Day to day, dwg. That way, anyone opening the file instantly knows which version they have That's the part that actually makes a difference..

7. Record the Change in the Project Log

Beyond the drawing itself, many firms maintain a master Change Log in a spreadsheet or project management tool. It aggregates all revisions across disciplines, linking each to a cost code, a responsible party, and a status (Open, Closed, Pending) Most people skip this — try not to..

Common Mistakes / What Most People Get Wrong

Mistake #1: Skipping the Revision Cloud

A designer might think a simple note in the margin is enough. Worth adding: in practice, the contractor scans the whole sheet; a cloud is the visual cue that says “look here. ” Without it, the change can be missed entirely That alone is useful..

Mistake #2: Using the Same Revision Letter Twice

Some teams recycle letters (A, B, A again) when they run out of them. Think about it: that’s a recipe for confusion. Still, the rule of thumb: once you hit Z, start numeric (01, 02). Consistency beats cleverness.

Mistake #3: Forgetting to Update the Title Block

It’s easy to change the geometry and forget to add a row in the revision block. Which means the result? The drawing says it’s still “Rev A” even though the cloud says “R‑B.” Auditors love to spot that discrepancy.

Mistake #4: Relying Solely on Paper Copies

If you only hand out printed sheets, you lose the ability to track who received which version. Digital signatures and version control in a cloud platform eliminate that blind spot Practical, not theoretical..

Mistake #5: Not Communicating the Impact

A change to a structural member might affect the foundation, but the revision description only says “increase beam size.” That’s a red flag. The supplemental sheet should note “requires foundation footing enlargement – see Sheet F‑2 Simple as that..

Practical Tips / What Actually Works

1. Standardize the Revision Block Layout
   Pick a template and lock it down in your CAD standards. Everyone will know exactly where to type the date, description, and approver.

2. Use Automatic Revision Numbering
   Most CAD packages (AutoCAD, Revit) can auto‑increment revision numbers when you save a new version. Turn that feature on; it removes human error That's the part that actually makes a difference..

3. Create a “Revision Cloud Library”
   A set of pre‑made cloud blocks with built‑in tags (R‑01, R‑02…) speeds up the drawing update process Still holds up..

4. Link the Cloud Tag to the Revision Block
   In BIM tools, you can attach a parameter to the cloud that pulls the description from the revision block. Click the cloud, and the note pops up. Saves time and prevents mismatches.

5. Run a “Revision Check” Before Release
   A quick checklist:

   • [ ] Revision block updated?
   • [ ] All clouds have matching tags?
   • [ ] Title sheet date matches file save date?
   • [ ] All disciplines have been notified?

6. Maintain a Central Change Register
   Use a simple Google Sheet or a dedicated module in your project management software. Columns to include: Revision, Discipline, Description, Cost Impact, Schedule Impact, Owner, Status Not complicated — just consistent..

7. Communicate via a “Change Notice” Email
   When a new revision is released, fire off a short email:

   “Team, please note that Rev 03 of the Structural Drawings (file: Struct_Rev03.pdf) is now live. Key change: column C‑12 moved 0.8 m east. See Cloud R‑03 on Sheet S‑4. Approvals attached.”
   Keep the email terse; the attachment does the heavy lifting Which is the point..

8. Archive Old Revisions
   Store superseded drawings in a read‑only folder labeled “Archive.” That way, if a question arises later, you can pull the exact version that was in effect at the time Still holds up..

FAQ

Q: Do I need a revision cloud for every change?
A: In practice, yes. The cloud is the visual flag that tells anyone reading the drawing where the change lives. Small text edits (like a note change) can be captured in the revision block alone, but geometry moves need a cloud Still holds up..

Q: How often should the revision block be updated?
A: Every time a new revision is released. Even if the change is minor, the block must reflect the latest date and description Small thing, real impact. Surprisingly effective..

Q: Can I use colors instead of clouds?
A: Some firms use colored lines, but most standards still require clouds for legal traceability. If you do use color, keep a consistent legend and still include a cloud tag.

Q: What if a contractor works from an outdated drawing?
A: That’s a breach of the contract terms. The contractor is responsible for checking the latest revision list before starting work. Document the misstep with a site photo and an RFI Easy to understand, harder to ignore..

Q: Are digital signatures enough for approval?
A: For most projects, yes—provided the digital workflow is part of the contract. The signature should be tied to the specific revision file, not just a generic “approved” note That's the whole idea..

So there you have it. Think about it: the next time you see a cloud on a plan, you’ll know exactly where that change lives, why it matters, and how to keep the record straight. A tidy revision log isn’t just paperwork; it’s the backbone of a smooth, on‑budget build.

Happy drafting!

9. put to work Automated Revision Tracking Tools

If you’re still stamping clouds and typing notes by hand, you’re leaving room for human error. Modern BIM platforms (Revit, Navisworks, Tekla) and cloud‑based document management systems (Procore, Newforma, Autodesk Construction Cloud) can automate much of the revision workflow:

Tip: Start small. Pick one discipline (typically structural or MEP) and pilot the automated cloud workflow on a single package of drawings. Measure the reduction in RFI volume and the speed of issue resolution. Once the ROI is clear, roll it out across the project And that's really what it comes down to. And it works..

10. Integrate Revisions Into the Construction Schedule

A revision is only as useful as the time it has to affect the field. To prevent “late‑late” changes that scramble crews:

1. Create a “Revision Milestone” in the master schedule.

   • Example: Milestone C – Issue Rev 02 Structural Drawings – 12 May.
   • Link the milestone to the corresponding activity (e.g., “Foundation Concrete”) so the schedule engine can flag any downstream tasks that may be impacted.

2. Run a “What‑If” Impact Analysis.

   • Most project‑control tools let you overlay a change request and instantly see which tasks shift.
   • Document the outcome in the change register (Schedule Impact column) and circulate to the CPM manager.

3. Lock the “Construction Start” date for each discipline until the latest approved revision is issued.

   • This practice forces the design team to stay ahead of the schedule and gives the contractor a reliable baseline.

11. Audit Your Revision Process Mid‑Project

Even the best‑designed process can drift over time. Conduct a brief audit at the 25 % and 75 % marks of the project:

If any item fails, schedule a corrective “Revision Huddle” with the responsible discipline lead, update the SOP, and re‑run the audit after one week.

12. The Human Element: Culture Over Tools

All the clouds, registers, and automation mean nothing if the team doesn’t treat revisions as a shared responsibility. grow a culture where:

• Everyone owns the latest data. Encourage field supervisors to ask, “What’s the newest revision?” before any crew starts work.
• Mistakes are reported, not hidden. A “near‑miss” RFI (e.g., a worker almost installed a pipe to the old location) should be logged and used as a learning case.
• Recognition follows compliance. Publicly thank the drafting team when a revision cycle is completed ahead of schedule or when RFIs drop dramatically after a process tweak.

Conclusion

Revision clouds, change notices, and a tidy register may feel like administrative overhead, but they are the nervous system of any construction project. By standardizing the visual cue (the cloud), coupling it with a solid digital trail (revision block, change register, and automated notifications), and embedding the process into the schedule and culture, you eliminate ambiguity, reduce costly rework, and protect all parties from contractual disputes That's the part that actually makes a difference..

In short: draw the cloud, log the change, notify the team, archive the old, and repeat—with the aid of modern software and a disciplined audit routine. When every stakeholder can answer the simple question, “Which revision am I looking at?” with confidence, the project moves forward faster, safer, and on budget.

This changes depending on context. Keep that in mind.

Happy drafting, and may your clouds always be perfectly placed.