Field notes · Guides
How to handle drawing revisions without recounting the whole takeoff
Rev D lands. Here is what actually needs re-checking, and what does not.
Handling a revision without recounting means treating it as an update to a schedule you already trust, not a reason to start over. Read what the revision actually changed, touch only those units, and leave the rest of the schedule as it stood.
Read the revision block before you read anything else
Every sheet in a plan set carries a revision block that names what changed since the last issue. Check that block first. If a sheet’s block did not move, the units drawn on it did not either, and there is nothing on that sheet worth re-reading. Spend the time on the sheets the block actually flags.
A cloud tells you where to look, not what to keep
A drafter’s cloud marks their own attention, not a guarantee. Some real changes ship without one; some clouds circle something that never touched fenestration scope. Use the cloud as a starting point for the sheets the revision block already named, not as the full list of what to check.
What a revision should not cost you
A full recount rebuilds the schedule from a blank page, which means redoing the reading, the reconciling, and the flagging you already did on Rev C — on top of whatever actually changed in Rev D. It also throws away the decisions your team already made on the units that never moved.
How this works with One to Many
A revision is a new upload against the same job, not a new project. The schedule from the last pass stays the baseline, and the new pass reconciles it against what the revision changed — flagging only the units it actually touched. See the full workflow, or how commercial packages handle revision churn on curtain wall jobs.