---
name: construction-change-order-pack
description: Builds a documented construction variation package from the change trigger, contract terms, quantities, rates, and time effects. Use for change orders, variation claims, owner instructions, design changes, and subcontractor pricing review.
license: Apache-2.0
metadata:
  adlass.categories: "projects-pmo/change-control, finance-accounting/planning-budgeting"
  adlass.industries: "construction"
  adlass.tags: "change-order, variation, construction, cost, schedule"
  adlass.adaptation: "reference-doc"
  adlass.source: "n8n:C-04"
  adlass.version: "1"
---

# Construction change-order pack

## Purpose

Translate a documented scope change into a traceable cost, time, and entitlement package ready for project review.

## Scope

Changes to construction scope, quantities, sequence, materials, or access conditions under an existing contract. **Excluded:** approval, negotiation, notice delivery, and legal conclusions beyond the supplied contract wording.

## Data basis

- Change trigger, contract and amendments, baseline estimate, drawings, quantities, rates, schedule, and prior approved changes.
- The fixed records, tables, or folders in the skill scope that hold the relevant history or schema.

## Result

A change-order draft, calculation sheet, entitlement memo, and assumptions or evidence-gap list.

## Quality criteria

- The changed scope is bounded against the original scope.
- Every amount traces to a quantity, rate, contract basis, or explicit assumption.
- Time impact distinguishes direct duration, sequencing, and uncertain effect.
- The package identifies notice, valuation, and supporting-document requirements from the contract.
- No unverified entitlement is stated as established.

## Instructions

Build the baseline-versus-change comparison before calculating value. Use contract rates where applicable and separate new rates, allowances, overhead, and markups. Link each quantity to a drawing, measurement, or record. Treat schedule effects as scenarios when the critical path is not evidenced. Quote the relevant contract clause and state unresolved interpretation questions.

## Adapt before use

Keep the source trail close to every conclusion and preserve the difference between a source fact, a calculated value, an assumption, and a recommendation. Use stable identifiers across the document and sheet so a reviewer can move from a summary statement to the underlying row and source. Prefer a complete, transparent partial result over a confident answer built on missing evidence.

- Add the contract, change-control procedure, and approved rate schedule.
- Define markup, overhead, contingency, and rounding rules.
- Specify schedule evidence and time-impact conventions.
- Set approval and escalation thresholds.