How to compare draft and executed versions for Construction Subcontracts

Compare the complete executed subcontract package against the last internally approved draft—not simply the last file exchanged. Preserve both versions, reconcile exhibits and incorporated documents, and verify text differences against signed page images. From the general contractor’s perspective, prioritize changes affecting trade scope, upstream obligations, payment, schedule relief, notices, and risk allocation. The deliverable is a source-linked version comparison checklist distinguishing approved changes, unexplained deviations, missing evidence, and administration updates, with an owner and disposition for every material issue.

When to use this workflow

Use this workflow when a signed subcontract returns from a trade contractor, when assembling the execution record, or when operations discovers that its working copy differs from the signed package. It serves general contractor counsel, contract managers, and project teams reconciling negotiated terms with the documents being administered.

The task is execution reconciliation, not a fresh negotiation or complete enforceability opinion. A difference may require explanation, operational action, or corrective documentation; the comparison alone does not determine which version controls.

This guide uses a US practice orientation, with selective federal procurement and Texas illustrations. Confirm location, governing law, project classification, execution date, applicable contract editions, and statutory applicability. Other states’ payment, indemnity, lien-waiver, and contingent-payment rules require separate analysis.

What you need

Assemble the last approved draft, its approval evidence, the returned executed package, and the signing transmittal. Include negotiation redlines and approval messages explaining accepted departures. For electronically signed documents, retain any available completion record alongside the signed files without treating it as proof that every attachment was included.

Construction-specific inputs include scope sheets, exclusions, schedule exhibits, drawing and specification registers, price breakdowns, allowances, unit rates, insurance requirements, and incorporated prime-contract documents. Obtain referenced addenda and amendments rather than assuming their contents from their titles.

Record the trade, original subcontract value, signature dates, project classification, and prime-contract edition. Identify who approves commercial deviations and corrective documentation. Obtain operations’ current working copy: it may differ from both the approved draft and signed package.

Use the template

Use the Construction Subcontracts — Version comparison checklist below. You can copy this table into your working document or spreadsheet. Assign one row to each material difference or package gap. Group formatting changes only after confirming that they do not alter meaning or references.

Use stable document IDs plus section and page citations in both source columns. For substituted exhibits, identify the title and revision. For drawing changes, identify the sheet and revision rather than citing only the incorporation clause.

“Evidence status” distinguishes verified text, uncertain OCR, missing attachments, and conflicting copies. “GC consequence” explains exposure, such as unassigned temporary conditioning or insufficient upstream notice time. “Action/owner” should include the next action and a review date or event. “Disposition” records specific approval evidence, correction status, or an assigned open issue—not merely “reviewed.”

Keep complete clauses in the source documents; use concise summaries or excerpts in the checklist. Cross-reference related rows where one execution change affects several obligations.

Step by step

1. Establish the approved baseline and preserve the signed package

Identify the version actually authorized for signature. A later attachment is not necessarily the approved baseline. Determine whether approval covered the entire package or only the subcontract body, and whether comments remained unresolved.

Preserve original files separately from OCR, comparison, and working copies. Assign document IDs and record filenames, receipt details, page counts, and the evidence supporting each file’s status. If the parties signed different counterparts, retain each and identify any differences before treating them as one package.

Record in the checklist: a baseline row identifying both packages and approval evidence. If authorization cannot be established, assign that uncertainty before labeling differences unauthorized.

2. Reconcile the construction document package

Compare contents before wording. Match every listed exhibit to an attachment; check drawing dates, specification revisions, addenda, schedules, and insurance requirements. Inspect labels, page sequences, and incorporation references for mismatches. A same-named scope sheet with a different revision is a substantive comparison candidate.

Distinguish an absent clause in a complete document, an unavailable incorporated document, and failed extraction. A missing scope exhibit is not evidence that exclusions were deleted. Check whether a substituted drawing register changes which work was priced.

Read order-of-precedence language alongside conflicting attachments. Record the conflict and the relevant hierarchy wording rather than assuming the hierarchy answers every interpretation question.

Record in the checklist: each missing, substituted, or conflicting document, paired references, collection owner, and unresolved question.

3. Generate a comparison and verify execution artifacts

Compare text using working copies, then inspect original page images. Check tables, footnotes, strikeouts, initials, handwritten insertions, signature blocks, and dates. Scanned unit-rate schedules and handwritten scope exclusions warrant direct visual review.

Separate formatting noise from meaningful changes. Verify renumbered cross-references and moved clauses against their destinations. Compare amounts both within schedules and against the subcontract’s stated total; a changed allowance may leave the headline price unchanged.

Check entity names and incomplete signature fields. Assign authority, dating, or counterpart questions instead of assuming a signature image resolves them. Request clearer evidence for unreadable marks; do not transcribe a guessed amendment as verified text.

Record in the checklist: wording differences with paired citations, plus separate rows for unresolved visual or execution evidence.

4. Trace scope, schedule, and change consequences

Test each substantive difference against delivery of the trade package. Review exclusions, design responsibility, coordination, temporary works, testing, warranties, acceleration, and backcharges. A deleted obligation can leave the general contractor responsible for work without a corresponding price adjustment.

For changed notices, compare trigger, recipient, delivery method, and period with the actual upstream obligation. Identify time remaining for investigation and transmission. Distinguish a revised milestone from revised entitlement to schedule relief; they require different project decisions.

Changed extra-work language may also require jurisdiction analysis. Texas Property Code §28.0091 permits a contractor or subcontractor to elect not to proceed with owner-directed additional work when specified unsigned-change-order conditions are met and aggregate actual or anticipated value exceeds 10% of its original contract amount. This is not a general right to stop existing work. Check applicability, exclusions, effective-date requirements, and the direction’s origin (Texas Property Code Chapter 28). (tcss.legis.texas.gov)

Record in the checklist: affected upstream obligation, practical consequence, legal dependency where relevant, and project-team decision owner.

5. Test payment and risk-allocation changes together

Compare payment triggers, invoice prerequisites, stored materials, retainage, withholding, interest, and final-payment conditions. Test changed wording using the same sample receipt and allocation in both versions. Keep cash-flow effects separate from enforceability conclusions.

For covered federal prime contracts, FAR 52.232-27(c) requires subcontract provisions addressing payment for satisfactory performance within seven days after receipt of corresponding government funds, late-payment interest, and lower-tier payment and interest requirements. Confirm the incorporated edition, agency supplements, and deviations; this is not a nationwide private-project deadline (FAR 52.232-27). (acquisition.gov)

Review changed indemnity and insurance together. Where Texas Insurance Code Subchapter C applies, §151.102 invalidates specified transfers of claims caused by the indemnitee’s or designated related persons’ fault or breaches; §151.104 addresses corresponding additional-insured requirements and coverage. Check §151.101 applicability, employee-claim exceptions, project exclusions, and the consolidated-program named-insured exception. Do not assume an endorsement cures prohibited indemnity wording (Texas Insurance Code Chapter 151). (tcss.legis.texas.gov)

Record in the checklist: commercial effects, interacting clauses, and separately assigned legal questions.

6. Reconcile differences with approval evidence

Classify differences as approved, unexplained, clerical, or unresolved. Match approval to the actual wording and exhibit revision. Permission to close the deal does not, by itself, explain a specific scope concession.

Prioritize potential cost, schedule impact, likelihood, and controllability. An unexplained payment change may require immediate legal review; an approved exclusion may require procurement action rather than corrective drafting. Neither should disappear because the package is signed.

Prepare any proposed correction in a separate working document. Obtain instructions on the appropriate instrument and necessary approvals. Keep the comparison redline clearly identified as an analytical work product, not an amendment, and never silently replace a signed page.

Record in the checklist: approval reference, rationale, proposed response, decision owner, and status for each material deviation.

7. Update only the affected administration records

Update payment instructions, scope assignments, notice registers, insurance follow-up, and schedule records affected by verified execution changes. Re-extract the relevant obligations instead of carrying draft-based entries forward. Confirm that the project team knows which source copy supports each update.

For event-triggered duties, record the trigger, required evidence, day-count convention, recipient, and responsible person. Do not invent a calendar date while the trigger remains unknown. Assign manual follow-up and escalation for unresolved items.

Keep uncertain interpretations visible and separate from confirmed instructions. Preserve the original packages, comparison output, approval evidence, and final checklist together.

Record in the checklist: updated work product, responsible person, communication evidence, and any remaining dependency.

Worked example

Fictional scenario: Northbank Construction is reconciling a $640,000 mechanical subcontract with Willow Ventilation for a privately owned warehouse. All parties, documents, amounts, and wording are fictional. D-12 was approved with Scope S-4 and Schedule T-2. Returned package E-01 includes Scope S-5, changed payment wording, and a reference to unavailable Schedule T-3. No governing-law conclusion is assumed.

Both versions define the relevant payment interval in calendar days. A finance approval email specifically accepts seven days after owner receipt. No corresponding approval for the conditioning exclusion has been located.

The entries produce different decisions. V1 requires investigation and a coverage plan, not an immediate assumption that Northbank must accept the exclusion. For V2, a hypothetical $40,000 allocation of owner funds creates an earlier payment-planning requirement, assuming unchanged prerequisites and no withholding issue; approval does not establish legal compliance. V3 supports only a changed reference. The team cannot conclude that milestones changed—or remained unchanged—until T-3 is obtained.

Common mistakes

• Comparing against the latest filename. Establish the authorized baseline through approval evidence and package contents.
• Ignoring exhibit substitutions. Compare revisions of scope sheets, drawing registers, schedules, and insurance attachments even when titles match.
• Treating accepted redlines as execution proof. Inspect signed pages for restored wording, handwritten changes, and altered schedules.
• Equating commercial approval with legal compliance. Record the approval while separately assigning applicable-law questions.
• Fixing the execution record directly. Preserve originals and route corrections through an authorized documentation process.

Final quality check

• Both packages have stable IDs, with evidence supporting the approved baseline.
• Listed exhibits and incorporated versions are matched or assigned for collection.
• Material differences are verified against original pages, including handwritten edits.
• Amounts, cross-references, entity names, and signature-page discrepancies are checked.
• Consequences cite clauses, exhibits, or actual upstream obligations.
• Legal conclusions remain within the cited sources’ applicability and scope.
• Approval evidence matches each specific concession; open issues have owners and review triggers.
• Affected administration records and team communications reflect verified changes or expressly unresolved dependencies.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. In its contract review workflow, choose the general contractor as the represented party and provide project-specific instructions. Findings quote clauses, rank severity, locate text, and identify missing language as not present. Lawyers control suggestions inserted as ordinary tracked changes under the signed-in Word user’s name. Use separate working copies for proposed corrections, not the preserved signed package. (decover.ai) Tabular review supports work across documents; the checklist, verification, and approval decisions remain team work products. To assess fit for subcontract reconciliation, book a demo.

Frequently asked questions

Which draft should we compare with the executed subcontract?

Use the last internally approved package with supporting evidence. Preserve a different last-exchanged draft as an intermediate version to locate where changes entered the sequence. If approval covered only the body, identify exhibit approval as a separate gap.

What if an executed exhibit is missing?

Record its incorporation reference and collection owner. Continue comparing available materials, but leave dependent conclusions open. Do not substitute the draft exhibit without evidence that it belongs to the execution package.

Should every execution difference produce a new redline?

No. Approved differences may require reconciliation and operational updates only. Material unexplained differences may justify proposed corrective wording. Keep that proposal separate from the signed record while counsel determines the appropriate response and documentation.

Can the team keep using its draft-based notice register?

Check changed triggers, periods, recipients, delivery methods, and incorporated schedules first. Update affected entries from verified sources. Mark unavailable evidence and unresolved interpretations so a draft assumption is not presented as a confirmed instruction.

Sources

• FAR 52.232-27 — Prompt Payment for Construction Contracts, paragraph (c).
• Texas Property Code Chapter 28 — Prompt Payment to Contractors and Subcontractors, §28.0091 and applicability provisions.
• Texas Insurance Code Chapter 151 — Consolidated Insurance Programs, §§151.101–151.105.

Scope: General professional workflow guidance using the supplied research cutoff of October 13, 2026. Contract conclusions depend on actual language, governing law, facts, and deal context.

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.