Subcontract variation records: what to document when work changes

Start with the package baseline

Identify the work area and the relevant scope item before describing the difference. Link the subcontract scope, pricing basis, drawing register and agreed qualifications used for that item. Retain the previous revision alongside the new one so a reviewer can see exactly what changed.

Distinguish an added requirement from an omitted item, a design clarification, a quantity adjustment or correction of work that did not meet the agreed requirement. Record the facts without deciding the commercial outcome from the label alone.

RICS describes change control as a project-specific process tied to the applicable contract provisions and the roles of those requesting or administering changes. Its overview also distinguishes a change from a contractual variation. For a Dubai subcontract, have the responsible commercial team identify the actual procedure, authorised recipients and applicable notice requirements; this article supplies a record template, not a contractual determination.

Use one reference across the records

Give the potential change an identifier and retain successive versions under it. For example, use the same reference on the marked drawing, enquiry, quotation, site diary entry and measurement record. Keep factual information separate from an assessment that is still under review.

The following fields are a suggested working template. Adapt them to the project procedure and link to controlled documents rather than copying conflicting versions into several spreadsheets.

Track instructions and price review separately

Use separate status fields for the technical instruction, work execution and commercial assessment. A request to price an option can remain a proposal while its effect is investigated. An issued instruction and its valuation may also have different review dates; the record should show the actual position rather than forcing everything into one “approved” box.

Preserve the original communication and identify the sender and recipient roles. Ask the designated contract administrator or commercial lead to resolve an unclear instruction through the applicable procedure. Do not treat an informal site discussion, drawing upload or unanswered email as automatic acceptance of a price or programme effect.

If immediate action is required under an applicable instruction or safety procedure, follow that procedure and record what happened at the time. This checklist does not override duties to proceed, notify or protect the work under the actual subcontract.

Make site records traceable to the affected work

Record the date, location and activity with each photograph or measurement. A photograph of reinforcement or shuttering without an identifiable work area may be difficult to connect to a particular change. Keep the drawing mark-up or location reference with the image and identify what it shows.

Where the team records labour, plant or material use, identify the activity and distinguish the changed work from the original package. Note whether a figure is measured, estimated or awaiting checking. Retain supporting delivery or issue references and identify unused or returned material where relevant.

Record who checked a measurement or site sheet and what their acknowledgement covers. If scope, quantities or rates remain disputed, show that separately. A factual record of resources used should not be presented as proof that every associated charge has been agreed.

For programme discussions, retain the affected activity reference, the planned work sequence, actual events and any instructions or access constraints. Record observable facts without assigning a delay duration or cause that the responsible programme team has not assessed.

Present additions and omissions together

A reviewable proposal should state the baseline item, the changed quantity or activity, the calculation basis and its assumptions. Identify work or material removed from the original scope as well as additions. Link supporting quotations and records to the same change ID.

Separate confirmed information from unresolved allowances. If a measurement or design detail is pending, name the person obtaining it and the point at which the proposal will be revised. Keep superseded proposal versions available, with one clearly identified current version.

Track the amount proposed, the amount agreed where applicable and any outstanding difference in separate fields. Keep payment and final-account status distinct from physical completion. Recording a completed activity does not by itself settle its contractual treatment.

Example: a revised opening after package release

Hypothetical example: a revised drawing changes an opening in a wall included in an issued package. The team opens record CH-017 and attaches the earlier and revised drawing references, a location mark-up and the actual work status when the revision was received. It identifies which associated trades need to review the change.

The responsible project team confirms the applicable technical direction. The subcontractor records the proposed additions and omissions, any affected ordered material and the activity requiring programme review. The register keeps instruction status and commercial review status visible separately.

During execution, measurements and relevant site records carry CH-017. On completion, the team links the inspection record and final measured position, then identifies any commercial matter still open. This is an illustrative record trail, not a reported ABA PRIME project or an instruction to alter an opening without the required technical review.

Review open changes before they become untraceable

Use each coordination review to identify missing instructions, unanswered technical queries, unverified quantities and unresolved proposals. Assign the next action to a named role and retain the response. Close a record only with the documents that explain what has been closed; keep unresolved parts visible.

To discuss a construction package with ABA PRIME, share the location, package boundaries, current drawing register, intended supply arrangement and target sequence. Identifying the scope and document baseline at enquiry stage makes later changes easier to describe.

• Can a reviewer find the original and revised scope from the change ID?
• Are the instruction, execution and commercial statuses separate?
• Do quantities and site records identify the work area and date?
• Are omissions and unresolved assumptions visible in the proposal?
• Is the next action assigned, with the relevant project procedure identified?
• Does the closure record distinguish completed work from outstanding assessment?