# Prime Contract

> The master agreement between owner and contractor that fixes scope, price, schedule, and risk allocation — and governs every subordinate document on the project.

- Source: https://briq.ai/acu/object/prime-contract
- Department: Contracts, Compliance & Risk (https://briq.ai/acu/department/contracts)
- Catalog code: CON 101 · Level: Foundation · Track: Foundations · 12 min read
- Also known as: Owner Contract, General Contract, Main Contract, Owner-Contractor Agreement

## Definition

A prime contract is the binding agreement between the project owner and the general contractor (or construction manager) that establishes the scope of work, the contract sum, the time for completion, and the allocation of risk between the two parties. It is the top of the contractual hierarchy on a project: every subcontract, purchase order, and change order flows down from its terms, and no lower-tier agreement can grant rights the prime does not. It is typically assembled from a standard base agreement (AIA A101/A102, ConsensusDocs 200-series, EJCDC, or an owner's custom form) plus incorporated general conditions (such as AIA A201), the drawings and specifications, and any addenda. It is not merely a price and a signature — the general conditions and the order-of-precedence clause do most of the work of resolving disputes, and reading only the cover agreement is a common and costly mistake.

## Why it matters

The prime contract allocates risk, and risk allocation is where projects are won or lost long before the first shovel. Who owns differing site conditions, who carries the risk of design errors, whether delay damages are liquidated or actual, and whether consequential damages are waived are all decided in the general conditions. A contractor who prices the work but never reads the indemnity, insurance, and no-damages-for-delay clauses has priced only half the deal.

It is the source of every dollar the contractor can collect. Payment terms, the schedule of values, retainage percentage, the pay-application process, and the conditions for final payment all originate here and flow down. When an owner disputes a billing, the argument is settled by reference to the prime, not to the invoice.

It governs time. The contract sets the completion date, defines what counts as an excusable or compensable delay, specifies the notice a contractor must give to preserve a time-extension claim, and states the daily rate of liquidated damages. Missing a contractual notice deadline can forfeit an otherwise valid delay claim regardless of merit.

It is the evidentiary spine of any dispute. The order-of-precedence clause decides which document controls when the drawings and specifications conflict; the dispute-resolution clause decides whether a fight goes to mediation, arbitration, or litigation and in which venue. In claims, everything is read back against the prime, which is why the executed contract and every incorporated exhibit must be complete, current, and retrievable.

## Lifecycle

1. **Award and letter of intent** — The owner selects the contractor and often issues a notice of award or letter of intent so mobilization can begin before the full agreement is executed. Working under an LOI without a defined scope-and-price cap is a frequent source of early exposure.
2. **Negotiation and redlining** — The base agreement and general conditions are marked up. The contested clauses are almost always the same: indemnity, insurance and additional-insured obligations, delay and liquidated damages, differing site conditions, warranty duration, and dispute resolution.
3. **Assembly and incorporation** — Exhibits are attached and incorporated by reference — drawings, specifications, the schedule of values, the project schedule, the list of drawings, and any addenda. Incomplete or mismatched exhibit lists are a leading cause of later scope arguments.
4. **Execution** — Both parties sign, and the effective date is set. Bonds and certificates of insurance are typically conditions precedent to execution or to the first payment, so they must be in hand.
5. **Flow-down and buyout** — Key terms cascade into subcontracts and purchase orders during buyout. Failing to flow down insurance, indemnity, schedule, and notice requirements leaves the general contractor holding obligations it cannot pass to the responsible trade.
6. **Administration** — The contract governs day-to-day life: pay applications, change orders, RFIs, and notices all cite it. The order-of-precedence and notice clauses are consulted constantly, whether or not the team realizes it.
7. **Modification** — Change orders and construction change directives amend the contract sum and time. Each executed change becomes part of the contract, and the running total of changes must reconcile to the revised contract value.
8. **Closeout and final payment** — Substantial and final completion are certified, punch is resolved, closeout deliverables and final lien waivers are exchanged, retainage is released, and warranties commence. Final payment usually operates as a waiver of claims not expressly reserved.

## Anatomy

- **Parties and effective date** — The exact legal entities and the date obligations begin. A contract signed by the wrong entity or an unregistered DBA can be unenforceable or uninsurable.
- **Scope of work** — Defined by reference to the drawings, specifications, and exhibits — not restated in prose. What is excluded matters as much as what is included.
- **Contract sum and type** — Lump sum, cost-plus with or without a guaranteed maximum price (GMP), or unit price. The contract type dictates who carries cost overrun risk.
- **Schedule and completion dates** — Contract time, milestones, substantial and final completion. The dates that liquidated damages attach to.
- **Liquidated damages** — A fixed daily rate for late completion, meant to be a genuine estimate of the owner's loss rather than a penalty. An unenforceable penalty rate can be struck entirely.
- **Retainage terms** — Percentage withheld from each payment, whether it reduces at a completion threshold, and the conditions for release. Commonly 5 to 10 percent.
- **Payment terms and process** — Pay-application cycle, review and payment windows, and whether payment to the GC is contingent on the owner's payment (pay-when-paid versus pay-if-paid).
- **General conditions** — The incorporated document (e.g., AIA A201) that governs claims, changes, notices, warranties, and termination. It is where most of the real terms live.
- **Indemnity clause** — Who defends and holds harmless whom, and to what extent. Anti-indemnity statutes in many states limit how far this can be pushed.
- **Insurance and bonding requirements** — Required coverages, limits, additional-insured and waiver-of-subrogation obligations, and payment/performance bonds.
- **Order of precedence** — Which document controls when documents conflict — typically addenda over drawings over specifications, but it varies and must be read.
- **Notice provisions** — How and within what window a party must give notice of a claim, change, or delay. Missed notice is the most common way valid claims die.
- **Dispute resolution and governing law** — Mediation, arbitration, or litigation; venue; and the governing state law, which determines lien rights and anti-indemnity limits.
- **Termination clauses** — For cause and for convenience, including the compensation owed on a convenience termination. Different remedies flow from each.

## Failure modes

- **Signing the cover agreement without reading the general conditions** — Teams focus on price and dates and skim the A201 or equivalent. The indemnity, no-damages-for-delay, and notice clauses that decide every future dispute go unnegotiated and unread until they bite.
- **Terms that do not flow down** — The prime imposes obligations — schedule, insurance limits, indemnity, notice windows — that never make it into the subcontracts. The GC is contractually exposed to the owner but cannot pass the obligation to the trade actually responsible.
- **Incomplete or mismatched exhibits** — The drawing list attached does not match the set the price was based on, or an addendum is omitted. The scope the contractor priced and the scope the contract obligates diverge, and the gap becomes a change-order fight.
- **Missed contractual notice** — A delay or changed condition occurs but written notice is not given within the contractual window in the required form. The claim is time-barred regardless of merit, and the cost lands on the contractor.
- **Pay-if-paid mistaken for pay-when-paid** — A pay-if-paid clause shifts owner-nonpayment risk to the GC and down to subs; a pay-when-paid clause only delays timing. Confusing the two during buyout mis-prices risk that can wipe out a project's margin.
- **Unenforced liquidated-damages exposure** — The team never models the daily LD rate against realistic completion scenarios. A schedule slip that felt minor turns into a six-figure withholding because nobody quantified the exposure while there was still time to recover.
- **Change total that never reconciles** — Executed change orders are tracked in one system and the contract sum in another. The revised contract value on the pay application does not equal the original sum plus approved changes, and the discrepancy surfaces at closeout.

## Metrics

- **Contract cycle time** — Days from award to full execution. Long cycles delay bonding, insurance, and buyout, and push mobilization into risky LOI territory.
- **Flow-down completeness** — Share of key prime terms (insurance, indemnity, schedule, notice) reflected in executed subcontracts. Measures how much risk the GC actually transferred.
- **Change order value as percent of contract** — Cumulative approved changes over the original sum. Benchmarks scope stability and design completeness.
- **Notice compliance rate** — Share of claims and delays where required notice was given on time and in the correct form. A direct predictor of claim recovery.
- **Liquidated-damages exposure** — Daily LD rate multiplied by projected days of slip. Turns schedule risk into a dollar figure executives can act on.
- **Retainage outstanding** — Dollars withheld and days aged since the release condition was met. Ties directly to cash flow and closeout velocity.
- **Days to final payment** — From substantial completion to release of final payment and retainage. Measures closeout discipline and dispute drag.

## The AI shift

- **Conversational** — The contract stops being a PDF you scroll and becomes something you question. You can ask what the notice window is for a differing site condition, whether consequential damages are waived, what triggers retainage reduction, and how the order-of-precedence clause resolves a specific drawing-versus-spec conflict — with the governing clause quoted and cited rather than paraphrased from memory.
- **Generative** — Redline and comparison work compresses. Given an owner's custom form, a model can compare it against a standard base agreement, surface every material deviation, and draft fallback language for the indemnity, delay, and insurance clauses in the contractor's standard position — producing a negotiation memo a reviewer edits rather than a blank markup.
- **Orchestrated** — The prime becomes the anchor other objects check against. Flow-down obligations are matched against executed subcontracts to find gaps; insurance and bonding requirements are checked against certificates and bonds on file; notice deadlines are tied to the events that trigger them; and the revised contract sum is reconciled continuously against the executed change-order log.
- **Autonomous** — The compliance perimeter runs itself: certificates and bonds tracked against contractual requirements with expirations escalated before they lapse, notice clocks started automatically when a triggering event is logged, flow-down gaps flagged during buyout, and change totals reconciled every billing cycle — while a human negotiates terms, decides risk positions, and signs anything that binds the company.

## Prompts

### Conversational — You inherited a project and need to know what the contract actually says about a live issue.

```text
Read our prime contract and its incorporated general conditions. We just discovered rock during excavation that was not indicated in the geotechnical report. Tell me exactly how this contract handles a differing site condition: is it a Type 1 or Type 2 clause, what written notice must we give and within how many days, who bears the cost, and does any exculpatory language (such as a site-investigation disclaimer) undercut our position. Quote the controlling clauses verbatim and cite the section numbers, and flag anything ambiguous rather than resolving it in our favor.
```

**Expected output:** A clause-cited answer that states the notice window, the cost-allocation rule, and the risk from any disclaimer language — with verbatim quotes and section numbers, not a paraphrase.

**Follow-ups:**

- Draft the differing-site-condition notice in the exact form the contract requires.
- What is our deadline, and what happens to the claim if we miss it?
- Does the general conditions cap our delay recovery for this event?

### Generative — An owner sent a custom agreement and you need a negotiation position fast.

```text
Compare this owner-drafted agreement against a standard AIA A101 with A201 general conditions and produce a negotiation memo. Identify every material deviation from the standard, grouped by risk theme: indemnity and additional-insured scope, delay and liquidated damages, consequential-damages waiver, differing site conditions, payment timing and pay-if-paid language, warranty duration, and termination for convenience. For each deviation, state the owner's position, why it is riskier than the standard, our recommended fallback language, and whether it is a walk-away issue or a tradeable one. Write it for a principal who has ten minutes.
```

**Expected output:** A prioritized deviation memo with recommended fallback language per issue and a clear walk-away-versus-tradeable classification, not a generic list of clause types.

**Follow-ups:**

- Draft clean redline language for the three walk-away issues.
- Which of these deviations do our insurance and bonding partners need to review?
- Summarize the residual risk if the owner rejects all of our redlines.

### Orchestrated — Buyout is underway and you need to know the prime is fully flowed down.

```text
Cross-check our prime contract against every executed subcontract and purchase order on this project. For each key obligation — insurance limits and additional-insured requirements, indemnity, the project schedule and milestone dates, notice provisions, warranty duration, and lien-waiver requirements — tell me which lower-tier agreements carry it, which are missing it, and where the lower-tier terms are weaker than what the prime obligates us to deliver. Return a flow-down gap matrix by subcontractor, tie each gap to the specific prime clause it fails to satisfy, and flag any gap that leaves us exposed to the owner with no ability to pass it through.
```

**Expected output:** A flow-down gap matrix mapping each prime obligation to the subcontracts that satisfy or fail it, with the unpassable exposures flagged and tied to specific clauses.

**Follow-ups:**

- Draft the subcontract amendment language to close the insurance and indemnity gaps.
- Which subs have COIs that do not meet the prime's required limits?
- Rank the gaps by dollar exposure to us.

### Autonomous — Standing policy for how contract compliance should run itself across a portfolio.

```text
Monitor prime-contract compliance across all active projects under these rules. Track every certificate of insurance and bond against the coverages, limits, and additional-insured requirements the governing prime demands, and escalate any deficiency or upcoming expiration to the project manager 30 days out and the risk manager 15 days out. When a triggering event is logged (differing site condition, owner-directed change, delay, force majeure), start the contractual notice clock and alert the responsible manager with the required form and deadline. Reconcile the revised contract sum against the executed change-order log every billing cycle and flag any discrepancy. Never draft or send a notice, never accept or waive a contract term, and never certify a pay application — route each of those to a named human with your supporting analysis.
```

**Expected output:** A continuously maintained compliance state with a short exception and deadline queue, where the human handles all notices, term decisions, and certifications and the audit trail is complete.

**Follow-ups:**

- Show me every notice clock currently running and its deadline.
- Which projects have insurance or bond deficiencies right now?
- List every contract-sum reconciliation exception from this cycle.

## Maturity ladder

- **Level 0 — Level 0 — Filed and forgotten** — The signed contract sits in a folder. Terms are recalled from memory, exhibits are incomplete, and notice deadlines are missed because no one is tracking them.
- **Level 1 — Level 1 — Cataloged** — Contracts are stored centrally with key terms (sum, dates, retainage, LD rate) abstracted into a register. Compliance is still a manual, periodic review.
- **Level 2 — Level 2 — Linked** — Prime terms are connected to subcontracts, insurance certificates, bonds, and the change log. Flow-down gaps and reconciliation breaks are visible rather than discovered late.
- **Level 3 — Level 3 — Assisted** — Redline comparison, deviation memos, and notice drafts are model-generated for review, and compliance gaps are surfaced proactively against the governing clauses.
- **Level 4 — Level 4 — Operated** — The compliance perimeter runs unattended — insurance and bond tracking, notice-clock triggering, flow-down and reconciliation checks — while humans negotiate, decide risk, and sign.

## FAQ

### What is the difference between pay-when-paid and pay-if-paid?

Pay-when-paid is a timing provision: it delays the general contractor's obligation to pay a subcontractor until the GC is paid, but only for a reasonable time, after which payment is due regardless. Pay-if-paid is a condition-precedent provision: it makes the owner's payment an actual precondition to the sub's right to be paid, shifting the risk of owner nonpayment down the chain. Pay-if-paid clauses are strictly construed and unenforceable in several states, so the exact wording and the governing law both matter.

### Which controls when the drawings and specifications conflict?

The order-of-precedence clause in the contract decides. A common hierarchy places addenda over the agreement, the agreement over the general conditions, specifications over drawings, and figured dimensions over scaled dimensions — but there is no universal rule, and some contracts invert the drawing-versus-spec order. When the contract is silent, resolution falls to interpretation principles and often an RFI, which is slower and riskier than having read the clause up front.

### Are liquidated damages the same as a penalty?

No, and the distinction is legally decisive. Liquidated damages must be a reasonable pre-estimate of the owner's actual loss from late completion, agreed when the harm would be hard to quantify. If a court finds the rate is really a penalty meant to punish rather than compensate, it can refuse to enforce it entirely, leaving the owner to prove actual damages. That is why a defensible LD rate is tied to real carrying costs, lost revenue, or extended-supervision expense.

## Related objects

- [Subcontract](https://briq.ai/acu/object/subcontract)
- [Certificate of Insurance (COI)](https://briq.ai/acu/object/certificate-of-insurance)
- [Surety Bond](https://briq.ai/acu/object/surety-bond)
- [Retainage](https://briq.ai/acu/object/retainage)
- [Owner Change Order (OCO)](https://briq.ai/acu/object/owner-change-order)
- [Closeout Package](https://briq.ai/acu/object/closeout-package)