Review drawings, revisions and specifications before they become rework

The dangerous issue is rarely a drawing that is obviously wrong. It is the drawing that changed, the specification that says something different, or the missing detail that everyone assumed somebody else had seen.

Establish the current set

Put the drawings, specifications, addenda and relevant correspondence in one Workshop project. Name the files with their issue or revision information and keep the older versions available for comparison. Before reviewing a sheet, establish what governs the question you are answering. A clean-looking PDF is not proof that it is the current issue.

Compare changes, then follow their consequences

Workshop’s sheet comparison surface lets you compare project sheet rasters. Use it to locate what moved between versions, then follow that change into the details, schedules, specifications, quantities and interfaces it affects. A revision cloud tells you where an author marked change; it does not tell you whether the changed item conflicts with another document.

For each finding, record the exact source: drawing number, detail, grid, specification section or document page. Capture the question in the work register with its status, responsible party and due date. The register supports RFIs and submittals as first class work types, and each item can carry evidence and frame the relevant drawing area.

Worked example: a revised tenant fit-out set

Revision 4 moves a plumbing wall and changes the reflected ceiling plan. The electrical drawing still shows the earlier fixture locations, and the finish schedule names a ceiling type that is no longer shown. Comparing the sheet images shows the move; reading the linked details and schedules tells you what the move changes.

Use Workshop with a direct objective:

Compare Revision 3 and Revision 4 of the tenant fit-out drawings. Identify changed locations, then check the electrical, plumbing, ceiling and finish documents for affected interfaces. Create evidence-linked findings for each conflict or missing instruction. For each finding, state the source, likely consequence, responsible party and the decision needed.

The review output should be a short register, not a long summary: reference; source locations; what conflicts or changed; affected discipline, quantity, cost or sequence; required decision; owner; due date; and disposition. Frame each finding on its sheet before sending it. That gives the recipient an answerable question instead of a paragraph about “coordination.”

Review the scope across documents

Read drawings for location and geometry. Read the specification for products, performance, installation and testing. Read schedules for quantities, equipment or finishes. Read the commercial documents for responsibility, exclusions and timing. The same item may appear in all four places, and a review is incomplete when it checks only the sheet that first revealed it.

Classify the result honestly:

• a confirmed requirement has a clear source and can be carried into scope;
• a discrepancy needs a question or direction;
• an assumption needs to be made visible in the offer or plan; and
• an unresolved item needs an owner and a date, not another unread email.

Verify the correction

When an answer or revised issue arrives, return to the original finding. Check the new evidence, update the disposition and recheck any dependent quantities, cost, programme or work item. Closing a register row because a response arrived is not the same as confirming the response resolves the issue.

Open Workshop to keep the documents, comparisons, findings and their evidence together while the review is still actionable.