Skip to content

Scope and changes

The change order package: attachments that make the review easier to follow

By Review.LivePublished 3 min readHow we write

The coordinator receives a returned change request marked backup missing. The quote was attached to a different email, and the marked plan has an old filename. The reviewer cannot follow the submitted total to one complete, current package.

A thick black ring binder packed with bound documents lies on a wooden desk.
Photo: Kelly Sikkema on Unsplash

Put the cause, requested amount and time effect on a short cover, followed by indexed support that lets the reviewer trace each statement. Use the same readable order for recurring submissions, adapting it to the project's actual requirements. A complete package can reduce avoidable searching, but it cannot guarantee agreement or a single review round. Identify unresolved evidence and commercial questions instead of making the submission look more settled than it is.

Build one navigable review package

  1. Write the cover as a map. Give the change ID, location, source instruction, scope, price, requested time effect and response needed. Reference the contractual basis approved by the commercial reviewer. Link each material statement to an attachment rather than reproducing every email on the first page.
  2. Put pricing support together. Follow the build-up with the applicable labour basis, supplier and trade quotes, and relevant tickets. Check that versions and totals match. Explain an assumption or omitted quote beside the affected line so the reviewer can distinguish an estimate from confirmed support.
  3. Show the changed work visually. Include a marked current plan or sketch and relevant dated photographs where permitted. Label location, revision and what each image demonstrates. Remove unrelated pictures; a large attachment pile should not bury the one interface the reviewer needs to understand.
  4. Attach time and correspondence records. Include the schedule explanation when time is requested, plus relevant notice, instruction and response references. Keep chronology clear and distinguish a requested effect from an agreed extension. A screenshot of a date is not an analysis of the completion effect.
  5. Index, check and issue. Give attachments stable numbers and readable headings, with bookmarks where the format supports them. Ask a colleague to reproduce the total and locate the key instruction. Retain the exact dated issue, send it through the required channel and identify any remaining evidence due later.

Common mistakes

  • Sending support in several emails without a complete issue reference.
  • Keeping an old quote after revising the total.
  • Adding unrelated correspondence without identifying the passage relied on.

Checklist

Submission check at the coordinator's desk

  • Cover identifies the decision requested.
  • Price and attachment versions reconcile.
  • Current location and revision shown.
  • Time and notice evidence linked.
  • Index lets another person find each record.
  • Exact issued copy retained.

Check your understanding

All the files are present, but a reviewer cannot tell which quote supports the latest price. Is the package ready?

Show the answer
Identify the current quote, remove or clearly label superseded material and reconcile the price references. Completeness includes a usable relationship between records. A reviewer should not have to guess which version the submission relies on.