How to review a construction change order before sending it to counsel

Pin the baseline before describing the change

Start by naming the agreement, amendment set, project document, and approved version the team treats as the current baseline. Preserve the proposed change order as a separate source file and record who sent it, when it arrived, and which project event prompted the review.

Add the supporting field record only as context: a request, drawing reference, meeting note, estimate, schedule update, or correspondence that helps explain why the change is being discussed. Do not merge those materials into the contract summary or assume they carry the same status.

• Identify the exact contract and change-order versions under review.
• Record the project, counterparty, sender, and business deadline.
• Keep source files intact and label supporting context.
• Flag any missing baseline document or referenced attachment.

Write the operational delta in four columns

Before interpreting contract language, describe the proposed change as an operating comparison. Use four columns: work or materials, price or payment event, schedule or sequencing, and approval or responsibility. For each column, record the current project assumption and the proposed change beside it.

Leave an entry open when the project team cannot verify it. A blank cost, an uncertain completion effect, or an unnamed approver should remain visible. The purpose of the map is to reveal the decisions still needed, not to make an incomplete proposal look settled.

• Describe added, removed, or revised work in plain language.
• Separate a quoted amount from an internal cost assumption.
• Record stated schedule effects and unresolved dependencies.
• Name the person expected to confirm each operational fact.

Connect each delta to the contract record

Locate the source sections the team needs counsel to inspect: the baseline scope, change process, notice or approval language, pricing method, payment timing, schedule provisions, and any document the proposed change incorporates. Capture short excerpts and exact source locations rather than paraphrasing them into a conclusion.

When the change order and baseline appear to address the same subject differently, preserve both passages. Explain the project scenario affected by the difference and keep the interpretation open for counsel. The source pair is more useful than an internal note that says only “does not match contract.”

• Pair every review note with its document and source location.
• Keep the baseline passage beside the proposed language.
• Mark a referenced item that is absent from the review set.
• Do not turn a source comparison into a legal conclusion.

Route each open item to the right decision lane

Classify the remaining items by owner. The project team confirms field facts and sequencing. Finance or leadership confirms price and commercial authority. The contract administrator collects versions, notices, and approvals. Counsel addresses interpretation, drafting, and legal risk.

Some questions will need more than one owner, but the handoff should still state the next action. This prevents counsel from receiving a technical unknown as though it were a legal question, and it prevents the business from answering a legal question as though it were only project administration.

• Technical: what work or project fact must be confirmed?
• Commercial: who can approve the price or schedule decision?
• Administrative: which file, notice, or sign-off must be collected?
• Legal: what source-backed interpretation or drafting question needs counsel?

Give counsel one verifiable change map

The packet should include the baseline inventory, proposed change order, four-column delta, paired source excerpts, missing items, decision owners, and a prioritized question list. Keep superseded drafts available but clearly separated from the versions counsel is being asked to review.

For each uploaded contract document, CounselOS can preserve source-linked clause extracts, surface playbook deviations, capture questions beside the relevant finding, and export selected material in a review packet. The cross-document change map remains a human-reviewed project artifact; CounselOS provides traceable contract evidence for the business and attorney making the next decisions.