Guide

Drawing revision and variation control for active jobs

By Ray · Lode

A revised drawing can change the work without changing the quote. A drawing register should make that gap visible before a crew installs an old specification. Keep the source revision, affected jobs, scope difference and approval decision together. This guide describes an operating checklist, rather than a customer result or an instruction to approve technical work.

Keep the source and its status

Record the drawing identifier, revision, issue date, sender and transmittal beside the original file. Preserve the earlier revision and the message that delivered it. A newer date alone does not prove that a drawing is approved for construction. The responsible project lead must confirm the permitted use and current status.

Record missing or conflicting information as an open question. Do not silently replace a file or assume that similar filenames refer to the same drawing. The register should let another person trace which source the team relied on and why.

Connect the revision to active work

List the jobs, work packages, materials and scheduled visits that reference the earlier revision. Include any quoted scope and supplier order affected by the change. Ask which crews have already received an earlier drawing and which work is complete.

A useful review file names the affected record and its source. A list of filenames alone does not explain the operational consequence. If a link cannot be established, assign the question to a person instead of guessing.

Compare the change with the quote

Separate a drawing revision from a commercial change order, also called a variation. A revision may clarify existing scope, or it may change quantities, materials, access or timing. The responsible reviewer decides whether the change affects the contract and price.

Prepare a scope comparison with the earlier agreement and the changed instruction beside it. Identify the work already completed and any extra work still proposed. Record the expected cost and price only from the firm's approved records. Missing figures remain missing until the responsible person supplies them.

Review suppliers and the schedule together

A changed specification may affect a purchase order, a delivery promise and the crew plan at the same time. Check those dependencies before proposing a new date. Keep the supplier query, customer notice and crew note attached to one proposed plan.

The supplier delay checklist gives the related handover sequence. The job costing guide explains the difference between estimated and actual costs. The margin calculator can support a manual quote check without storing the inputs.

Keep approval separate from preparation

Name the technical reviewer, commercial approver and person authorized to issue the change. A prepared file does not replace their approval. Record what was accepted, what remains open and which revision the crew may use.

After an approved change, retain the earlier sources and the approval record. Confirm that affected people received the permitted information. A superseded file should remain traceable while its status makes clear that it is no longer the active instruction.

What Lode is built to prepare

Once connected, Lode would link drawing transmittals to active jobs, quoted scope and supplier records. A specialist check would prepare the affected-job list and any unbilled variation question. A bespoke drawing register would keep source evidence beside the proposed next step. External changes would wait for the responsible approver.

Lode links drawing revisions to quoted scope, site notes and job records, then prepares the variation evidence for review. See what Lode runs, the Simpro comparison and the ServiceTitan comparison for the records and approval steps behind that workflow.

Where the workflow fits

Electrical, HVAC, facilities and landscaping teams can use the same review questions. Their approval roles and connected records will differ. Read the operating examples and about Lode for our approach to service-business operations.