How to compare draft and executed versions for Construction Contracts

Compare the complete executed construction contract package against the owner’s final approved draft, including incorporated conditions, scope documents, and commercial schedules. Preserve both sets, verify comparison results against the signed pages, and reconcile substantive differences with approval evidence. Review price, scope, schedule, change authority, notices, and risk allocation together rather than as isolated clauses. The deliverable is a source-linked version comparison checklist recording confirmed changes, missing evidence, owner consequences, approval status, and assigned responses before affected contract administration records are updated.

When to use this workflow

Use this workflow when owner’s counsel receives signed construction documents, inherits an executed project agreement, or discovers that construction administrators are using a different package from legal’s approved version. It serves in-house and outside counsel working with procurement, project executives, and design and construction administrators.

The task is execution reconciliation, not renegotiating the entire agreement. Establish what changed, whether the change received approval, and what corrective or operational response is needed. Keep later amendments and change orders separately identified so they do not obscure differences introduced at execution.

This is a US-oriented workflow recommendation, not advice for a particular project. Resolve governing-law questions separately, especially indemnity, payment, liens, and notice enforcement. For federal procurement, check the incorporated clause and award version rather than applying private-contract assumptions; the federal Changes clause assigns specified functions to the contracting officer (FAR 52.243-4). (acquisition.gov)

What you need

Collect the following inputs before assigning conclusions:

• Approved baseline: the final approved agreement, conditions, exhibits, and approval evidence identifying the precise revisions and any conditions on approval.
• Executed package: signed agreement, attachments, counterparts, handwritten alterations, and available signing and delivery records.
• Technical scope: drawing and specification indexes, issue dates, addenda, accepted alternates, and incorporated clarifications or exclusions.
• Commercial schedules: contract sum or guaranteed maximum price (GMP), allowances, contingency, payment provisions, milestones, completion requirements, and delay terms.
• Supporting documents: referenced bonds, insurance requirements, warranties, authority schedules, and incorporated amendments.
• Decision evidence: concession approvals, negotiation correspondence, delegated authority limits, and any applicable lender-consent requirements.

Ask which package the project team actually received and uses. Distinguish a document missing from the review folder from one demonstrably omitted from the execution package.

Use the template

The Construction Contracts — Version comparison checklist records the comparison and its disposition. Copy this table into your working document or spreadsheet. Use one row per material difference, missing component, or unresolved approval question.

Assign stable document IDs. Source cells should identify the revision, section, and PDF page; distinguish printed pagination where different. For technical documents, include sheet or specification number and revision.

Preserve operative wording or a precise description in Evidence / difference. Explain cost, schedule, administrative, or legal consequences in Owner effect without collapsing uncertainty into a risk label. Approval / uncertainty should identify the approval record or missing evidence. Put the responsible person and target resolution date in Action / assignee. Useful statuses include approved difference, open evidence gap, escalated interpretation, and correction pending.

Maintain a coverage record alongside the exception rows so reviewers can distinguish provisions checked and unchanged from provisions not reviewed. Record package IDs, reviewer, and review date in the working document’s header.

Step by step

1. Establish the approved baseline and preserve execution evidence

Identify who approved which agreement and attachments, and whether approval was conditional. Do not assume the last draft emailed to the contractor was the approved baseline. If the signature-ready draft differs, preserve it as an intermediate version that may explain the discrepancy.

Keep original executed files unchanged. Use copies for OCR, annotation, and comparison. Label incomplete counterparts and unreadable pages; do not reconstruct signed wording from the draft without flagging that reconstruction as unverified.

Record: baseline and execution package IDs, approval evidence, and an evidence-gap row for competing baselines. Obtain decision-maker confirmation before treating either competing draft as definitive.

2. Reconcile incorporated documents and revisions

Match exhibit titles, revision dates, drawing indexes, specification sections, addenda, and referenced schedules. Check document precedence and inconsistent references. An unsigned exhibit is not necessarily excluded merely because it lacks a signature; investigate its identification and incorporation rather than using signature presence as the sole test.

A historical SEC-filed construction agreement expressly includes listed and incorporated documents within the contract and states its own precedence arrangement. That wording illustrates why package reconciliation requires reading the actual incorporation provisions (Article 1). (sec.gov)

Record: each matched component and each unavailable or conflicting revision. State whether the issue is missing review evidence, uncertain delivery, or confirmed omission. Keep subsequent modifications separate from the execution comparison.

3. Locate differences and verify the signed text

Compare each matched document, then inspect signed page images for handwriting, filled blanks, initials, deleted text, replaced pages, and table changes. Verify OCR-generated differences against the image, particularly prices, dates, percentages, negatives, and exception language.

Separate formatting from operative changes, but test dependencies before dismissing renumbering. A moved notice clause can leave an authorization provision pointing to the wrong section. A changed drawing-index date may alter scope while the agreement body remains unchanged.

Record: both source locations and the verified difference. Keep unresolved image-quality issues visible. Mark unchanged reviewed provisions in the coverage record; an exception-only checklist does not establish complete review coverage.

4. Assess construction-specific consequences and dependencies

Read each difference with its related provisions. Compare scope exclusions against GMP inclusions, allowances, and contingency; completion changes against milestones and delay remedies; payment changes against certification and supporting-document requirements. Include owner duties such as access, design information, approvals, and coordination.

The November 27, 2007 SEC-filed agreement’s GMP Addendum §1.1, rather than its general incorporation clause, includes reasonably inferable work within the GMP and requires written change orders for GMP adjustments under referenced conditions. This is a wording example, not a market benchmark (GMP Addendum). (sec.gov)

Prioritize changed pricing, change authority, indemnity, insurance, bonds, warranties, liability limitations, and termination terms. Refer enforceability questions for project-specific analysis rather than resolving them from comparison alone.

Record: the affected dependency, owner consequence, and evidence needed to determine the effect. Do not estimate additional cost without supporting scope or pricing evidence.

5. Compare notice and change mechanisms word by word

Check the actor, action, trigger, period, day-count convention, recipient, delivery method, required content, exceptions, and consequence. Knowledge, occurrence, receipt, and delivery are distinct triggers. Compare authorization, pricing evidence, disputed directions, and final approval separately.

The historical PNK Baton Rouge agreement illustrates the distinction: §11.6.7 requires specified delay notice after contractor knowledge, including where the owner knows of the cause. Section 18.4.4 makes failure to communicate agreement or disagreement with proposed adjustments within ten days after directive delivery a deemed-approval mechanism. These are negotiated terms, not universal rules (§§11.6.7 and 18.4.4). (sec.gov)

For an award incorporating FAR 52.243-4, distinguish paragraph (a) written change orders from paragraph (b) other contracting-officer orders accompanied by contractor notice. Confirm the controlling version and any applicable deviations before comparison (paragraphs (a)–(b)). (acquisition.gov)

Record: the altered mechanism and required administrative response. Calculate an event-specific deadline only after verifying its trigger evidence.

6. Reconcile approvals, signatures, and proposed corrections

Match substantive departures to approval correspondence, concession records, and authority limits. Distinguish internal approval compliance from the separate question of contractual effect. Absence of an internal approval record is not, by itself, a conclusion that executed wording is ineffective.

Check party identities, signature capacities, dates, counterpart completeness, and apparent post-signature alterations. Escalate their legal significance rather than assuming that initials cure every alteration or that a missing date invalidates execution.

Record: documented approval, explanation required, accepted residual risk, or proposed correction, with decision-maker and evidence. If correction is needed, prepare a separately identified corrective instrument through the authorized approval process. Never replace signed pages and describe the archive as reconciled.

7. Issue the comparison result and control operational updates

Prepare an exception summary linked to checklist IDs. Explain confirmed findings, unresolved interpretations, and immediate administrative consequences. If project activity cannot wait, ask counsel and the authorized owner representative to give an interim instruction that identifies the uncertainty rather than presenting it as resolved.

Update affected obligation records from verified executed wording, retaining open interpretations. Do not withhold a confirmed owner response obligation simply because an unrelated scope exhibit remains unavailable.

Record: disposition, supporting evidence location, assignee, target date, and any operational update. Close the review when material differences are resolved or expressly assigned and review coverage is documented—not merely when comparison software finds no further changes.

Worked example

Fictional scenario: Harbor Lantern Properties and contractor Alder Quay Builders sign a warehouse construction agreement stating an $18.4 million GMP. Counsel’s approved package D-07 includes Scope Exhibit B revision 4 and Authority Schedule C, reserving price-adjustment approval to the owner’s project director. Signed agreement E-01 references Exhibit B revision 5, but only revision 4 is available for review.

E-01 also adds wording about field directions and shortens the owner’s submittal response period. Approval email A-03 expressly approves the shorter period but does not address field directions. Every party, document, amount, and clause below is fictional.

V01 prevents a verified scope comparison but does not establish whether revision 5 changes the work. Procurement must obtain the document and delivery evidence; counsel should not invent a scope description from the revised reference.

V02 concerns evidence supporting a request, not express authority to approve an adjustment. The unchanged authority schedule matters. Counsel must reconcile both provisions and approval history before characterizing the addition as a price entitlement or an unauthorized concession.

V03 supports an immediate routing update because both the change and approval are verified. These separate dispositions let the owner implement confirmed duties while preserving the unresolved scope and authority questions.

Common mistakes

• Using the last emailed draft: identify the approved package and preserve any intervening signature draft.
• Comparing only agreement text: reconcile conditions, technical revisions, exclusions, and commercial schedules individually.
• Trusting OCR as execution evidence: verify material differences against signed page images.
• Calling every unexplained change ineffective: separate missing internal approval from contractual effect and escalate the latter.
• Repairing the archive instead of the agreement: preserve originals and document any authorized corrective instrument separately.

Final quality check

• Approved and executed package IDs are stable; original files are preserved.
• Incorporated components are matched or specifically identified as unavailable.
• Review coverage distinguishes unchanged, changed, and unreviewed material.
• Material differences have source citations checked against original pages.
• Scope, pricing, schedule, and authority dependencies are addressed.
• Notice changes capture triggers, content, recipients, and delivery requirements.
• Approval conclusions identify evidence and the decision-maker.
• Open issues have assignees and target dates; confirmed operational changes are communicated.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review capabilities can support owner-side review of identified departures. In Word, choose the represented party or neither and provide deal-specific instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present. Lawyers can edit or insert suggestions as ordinary tracked changes under the signed-in Word user’s name, or dismiss findings with reasons. Tabular review supports work across multiple documents. Keep corrective drafts separate from signed originals; counsel retains package verification, approval reconciliation, and legal judgment. Book a demo to discuss this workflow.

Frequently asked questions

Which draft is the correct baseline?

Use the package tied to final owner approval, including identified exhibits and approval conditions. Preserve and compare a different signature-ready draft as an intermediate version; it may locate where a discrepancy arose but does not replace approval evidence.

What if an executed exhibit is unavailable?

Identify exactly what is missing and assign retrieval. Continue reviewing available material, but qualify conclusions dependent on the exhibit. A similarly named draft is not a verified substitute, and unavailability does not prove omission from the contract.

Does every substantive difference need an amendment?

No. Reconcile approval and effect first. The authorized owner decision-maker and counsel should determine whether to accept the difference, seek clarification, or pursue a corrective instrument. Document accepted differences and communicate resulting administrative duties.

Can the checklist replace the obligation register?

No. The checklist records comparison evidence and decisions; the register records performance responsibilities. Transfer verified changes with source citations, retain unresolved interpretations visibly, and preserve comparison history so later administrators can trace each update.

Sources

• SEC-filed construction agreement dated November 27, 2007, Article 1 and GMP Addendum §1.1: incorporation, precedence, and historical GMP wording examples.
• PNK Baton Rouge GMP Construction Services Agreement, §§11.6.7 and 18.4.4: historical delay-notice and change-directive wording examples.
• FAR 52.243-4, Changes: federal clause text; confirm incorporation and the controlling award version.

The historical filed agreements illustrate wording, not market standards or current enforceability.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.