In this article
ToggleWhy a Contract Review Checklist Matters
A contract review checklist helps project teams avoid reviewing contracts in an inconsistent or overly informal way. Without a checklist, teams may focus on obvious commercial items such as price, scope, and completion date. However, the clauses that create real delivery risk are often less obvious. These may include notice provisions, time bars, variation procedures, payment claim rules, delay claim requirements, indemnities, liability caps, latent condition clauses, design obligations, and termination rights. In construction and infrastructure projects, small drafting details can have major commercial consequences. A missed notice can affect entitlement. An unclear scope boundary can create a variation dispute. A poorly understood delay clause can affect programme recovery. Incomplete records can also weaken a claim. For that reason, strong risk management construction practice should include a structured contract review process before the project starts and during delivery. Perfomir explains this broader approach in its guide to construction contract risk management, where contract risk is treated as something that must be identified, monitored, and escalated throughout the project lifecycle.Contract Review Should Not Stop at Signature
Many teams complete a contract review before award, then file the contract away until a problem arises. That approach creates risk. A contract continues to matter every day during delivery. It matters when the scope changes, when access is delayed, when the principal issues an instruction, when subcontractor costs increase, when a payment claim is disputed, and when a notice period starts running. Modern contract management construction should therefore treat contract review as a live process, not a one-off exercise. Perfomir has written further on why contract review should not stop at signature. The key point is simple: contract review should move from static document review to continuous contract risk intelligence. That is where contract risk intelligence becomes useful. It helps project teams connect clauses, obligations, notices, project events, claim pathways, and executive exposure.How to Use This Contract Review Checklist
To create an effective construction contract review checklist, start by confirming the contract documents and scope, then review the main contractual risk categories, record the risk and required action, assign clear ownership, transfer important findings into project controls, and keep the checklist updated during delivery. A practical approach is to follow these six steps:- Confirm the contract documents and scope. Identify the documents that form the contract, their order of precedence, the agreed scope, exclusions, assumptions, interfaces, and key delivery requirements.
- Review the main contractual risk categories. Work systematically through scope, design, programme, delay, notices, variations, payment, claims, liability, insurance, termination, disputes, governance, and other relevant risk areas.
- Record the risk and required action. For each checklist item, note whether it has been reviewed, whether the risk is acceptable, and whether action is required before signing or during delivery.
- Assign ownership and identify contractual requirements. Record who is responsible for managing the issue and identify any relevant notice requirements, evidence requirements, approval processes, claim procedures, or other contractual actions.
- Transfer important findings into project controls. Move significant obligations and risks into the appropriate contract obligation register, notice register, variation register, claim register, risk register, or other project control used by the delivery team.
- Review and maintain the checklist during delivery. Revisit the checklist when project events, scope, programme, instructions, variations, payment issues, or other circumstances change so that the review remains connected to the live project.
- Has this been reviewed?
- Is the risk acceptable?
- Is action required before signing or during delivery?
- Who owns the action?
- What evidence or records may be required?
- Does the issue need to be monitored as the project progresses?
Before Signing and During Delivery: How the Review Changes
| Review stage | Main objective | Priority actions | Typical output |
|---|---|---|---|
| Tender and before signing | Understand the proposed allocation of risk and decide what must be priced, clarified, negotiated, transferred, or accepted. | Confirm contract documents, test scope and assumptions, review amendments, identify departures, assess programme feasibility, and check downstream alignment. | Risk schedule, qualifications, clarifications, pricing allowances, negotiation points, and approval record. |
| Handover and mobilisation | Convert the signed contract into practical responsibilities and controls. | Extract notices, obligations, approvals, reporting dates, securities, payment requirements, and delegated authority. | Obligation register, notice calendar, responsibility matrix, and project controls. |
| During delivery | Keep entitlement, compliance, evidence, and emerging exposure visible as events occur. | Track instructions, variations, delay, access, RFIs, payment, records, mitigation, and escalation triggers. | Updated registers, notices, evidence files, forecasts, and executive risk reporting. |
| Close-out | Resolve outstanding commercial matters and confirm surviving obligations. | Reconcile claims, variations, security, retention, defects, warranties, releases, and final account. | Close-out plan, evidence audit, final-account position, and obligations handover. |
Who Should Review Each Part of the Contract?
The review should be coordinated, but it should not depend on one person reading every clause in isolation. Each material issue needs a named owner and, where necessary, input from the appropriate specialist.| Role | Primary review focus |
|---|---|
| Principal or asset owner | Project outcomes, scope completeness, governance, approvals, funding, interfaces, performance requirements, security, and remedies. |
| Head contractor | Scope and price alignment, programme feasibility, design responsibility, notice and variation pathways, payment, risk transfer, and subcontract flow-down. |
| Subcontractor or supplier | Scope boundaries, access and dependencies, programme, payment, variations, notices, liability, insurance, termination, and alignment with upstream obligations. |
| Commercial and contracts team | Risk allocation, qualifications, time bars, entitlement, security, payment, change control, claims, records, and escalation. |
| Project and delivery team | Operational obligations, sequencing, approvals, reporting, instructions, evidence, programme updates, and day-to-day compliance. |
| Legal, insurance, tax, and technical advisers | Issues requiring specialist interpretation or advice beyond the delivery team’s authority or expertise. |
How to Prioritise Checklist Findings
Not every departure deserves the same response. A simple priority model helps teams focus attention without losing lower-level issues:- Critical: the issue could materially affect project viability, uncapped liability, insurability, payment, completion, termination, or a major entitlement. It requires decision-maker review before commitment or immediate escalation during delivery.
- High: the issue could materially affect margin, cash flow, programme, claim rights, or delivery control. Assign an owner, treatment, and deadline.
- Monitor: the risk is currently manageable but depends on an assumption, interface, future event, or continuing compliance. Record the trigger and review date.
Practical Contract Review Checklist
The checklist has been divided into smaller sections so project teams can review each risk area more easily.Contract Documents and Scope Checklist
| No. | Review Area | Checklist Item | Why It Matters | Status / Action |
|---|---|---|---|---|
| 1 | Contract documents | Confirm all contract documents are listed, including general conditions, special conditions, scope, drawings, specifications, schedules, addenda, clarifications, and letters of acceptance. | Missing or inconsistent documents can create uncertainty during delivery. | ☐ Reviewed ☐ Action required |
| 2 | Order of precedence | Check which document prevails if there is a conflict between drawings, specifications, schedules, scope, or conditions. | A conflict between documents can create variation, design, or delivery disputes. | ☐ Reviewed ☐ Action required |
| 3 | Scope of works | Confirm the scope is clear, complete, and aligned with the price and programme. | Unclear scope is one of the most common sources of construction disputes. | ☐ Reviewed ☐ Action required |
| 4 | Exclusions and assumptions | Check whether exclusions, assumptions, qualifications, and departures are clearly recorded and accepted. | If assumptions are not captured, the project team may inherit unintended risk. | ☐ Reviewed ☐ Action required |
Design, Programme, and Delay Checklist
| No. | Review Area | Checklist Item | Why It Matters | Status / Action |
|---|---|---|---|---|
| 5 | Design responsibility | Identify who is responsible for design, design development, coordination, review, errors, omissions, and performance outcomes. | Design responsibility can significantly increase commercial and professional exposure. | ☐ Reviewed ☐ Action required |
| 6 | Fitness for purpose | Check whether the contract includes fitness-for-purpose obligations or performance guarantees. | These obligations may create higher exposure than ordinary skill and care obligations. | ☐ Reviewed ☐ Action required |
| 7 | Programme and milestones | Review practical completion dates, sectional completion, key dates, access dates, interface dates, and handover obligations. | Time obligations drive delay risk, liquidated damages exposure, and extension of time claims. | ☐ Reviewed ☐ Action required |
| 8 | Delay and extensions of time | Check what events give entitlement to time relief and what notice or claim process applies. | Delay claims may fail if notices, records, or claim submissions are not managed correctly. | ☐ Reviewed ☐ Action required |
| 9 | Liquidated damages | Identify whether liquidated damages apply, when they start, how they are calculated, and whether caps apply. | Delay damages can create significant executive and commercial exposure. | ☐ Reviewed ☐ Action required |
Notice, Time Bar, and Variation Checklist
| No. | Review Area | Checklist Item | Why It Matters | Status / Action |
|---|---|---|---|---|
| 10 | Notice obligations | Extract every notice obligation, including notices for delay, variations, claims, latent conditions, force majeure, disputes, and payment issues. | Missed notices can affect entitlement and increase claim exposure. | ☐ Reviewed ☐ Action required |
| 11 | Time bars | Identify any clause where entitlement may be lost if notice is not given within a specified timeframe. | Time bars are one of the most important risks for project delivery teams to monitor. | ☐ Reviewed ☐ Action required |
| 12 | Variations | Review how variations must be directed, claimed, priced, assessed, disputed, and recorded. | Variation claims often become disputed when the contractual process is not followed. | ☐ Reviewed ☐ Action required |
| 13 | Oral instructions | Check whether oral instructions can create entitlement or whether written direction is required. | Site teams may proceed with work without understanding whether entitlement is protected. | ☐ Reviewed ☐ Action required |
Payment, Security, and Claims Checklist
| No. | Review Area | Checklist Item | Why It Matters | Status / Action |
|---|---|---|---|---|
| 14 | Payment claims | Review payment claim dates, supporting documents, certification process, payment timing, and set-off rights. | Payment process errors can create cash-flow and commercial administration issues. | ☐ Reviewed ☐ Action required |
| 15 | Security and retention | Check bank guarantees, bonds, retention amounts, release triggers, and expiry requirements. | Security and retention affect working capital, risk exposure, and close-out. | ☐ Reviewed ☐ Action required |
| 16 | Claims process | Identify all claim pathways, including time, cost, disruption, prolongation, latent conditions, and disputed variations. | For teams managing Contract Claims construction risk, early understanding of claim pathways is critical. | ☐ Reviewed ☐ Action required |
| 17 | Records and evidence | Confirm what records are required to support claims, including daily records, cost records, programmes, photos, correspondence, and instructions. | Claims are often weakened by incomplete or inconsistent records. | ☐ Reviewed ☐ Action required |
External Events and Risk Allocation Checklist
| No. | Review Area | Checklist Item | Why It Matters | Status / Action |
|---|---|---|---|---|
| 18 | Latent conditions | Review how latent conditions are defined, what notice is required, and what relief is available. | Site condition risk can create major time and cost exposure. | ☐ Reviewed ☐ Action required |
| 19 | Force majeure and external events | Check force majeure, frustration, change in law, supply chain disruption, extreme weather, and external event clauses. | External events may affect time, cost, termination rights, or relief mechanisms. | ☐ Reviewed ☐ Action required |
| 20 | Price escalation | Check whether the contract allows price adjustment for material, labour, foreign exchange, or supply chain increases. | Fixed-price contracts may create exposure if escalation risk is not understood. | ☐ Reviewed ☐ Action required |
| 21 | Liability and indemnities | Review indemnities, liability caps, exclusions, carve-outs, consequential loss, and third-party liability. | Risk allocation should be understood before the contract is accepted. | ☐ Reviewed ☐ Action required |
| 22 | Insurance | Confirm required insurance policies, limits, deductibles, duration, and subcontractor insurance obligations. | Insurance requirements must align with the risk profile and project obligations. | ☐ Reviewed ☐ Action required |
Close-Out, Disputes, and Delivery Monitoring Checklist
| No. | Review Area | Checklist Item | Why It Matters | Status / Action |
|---|---|---|---|---|
| 23 | Defects and warranties | Review defects liability periods, warranty obligations, rectification rights, and access after completion. | Defects obligations can extend exposure beyond practical completion. | ☐ Reviewed ☐ Action required |
| 24 | Termination | Check termination for default, termination for convenience, cure periods, payment on termination, and demobilisation rights. | Termination clauses define the consequences if the contract relationship breaks down. | ☐ Reviewed ☐ Action required |
| 25 | Suspension | Review when work can be suspended, by whom, and what entitlement follows. | Suspension rights affect programme, cost recovery, and project control. | ☐ Reviewed ☐ Action required |
| 26 | Dispute resolution | Review negotiation, executive escalation, adjudication, expert determination, arbitration, litigation, governing law, and jurisdiction. | Dispute process requirements should be known before a dispute arises. | ☐ Reviewed ☐ Action required |
| 27 | Reporting obligations | Check progress reports, programme updates, safety reports, quality reports, risk registers, meeting minutes, and audit obligations. | Reporting records often become evidence during claims or disputes. | ☐ Reviewed ☐ Action required |
| 28 | Governance and approvals | Identify required approvals, delegations, superintendent decisions, principal approvals, and internal authority limits. | Unclear authority can delay decisions and create disputed instructions. | ☐ Reviewed ☐ Action required |
| 29 | Subcontract flow-down | Check whether subcontract obligations align with the head contract. | Gaps between head contract and subcontract terms can create unrecovered exposure. | ☐ Reviewed ☐ Action required |
| 30 | Delivery-stage monitoring | Convert key risks into a live obligation register, notice register, claim register, and executive risk dashboard. | Contract review only creates value if risks are monitored during delivery. | ☐ Reviewed ☐ Action required |
Key Areas to Review in More Detail
The checklist table gives users a practical starting point. Several review areas deserve deeper attention because they often create major commercial exposure during construction and infrastructure delivery.Contract Documents and Order of Precedence
The first step is to confirm exactly what documents form part of the contract. Construction contracts often contain multiple documents prepared at different stages of tendering and negotiation. The final contract may include drawings, specifications, schedules, addenda, tender clarifications, departures, correspondence, pricing documents, and technical requirements. When contract documents are inconsistent, the order of precedence clause becomes critical. A strong contract review checklist should confirm whether the order of precedence is clear and whether it properly reflects the commercial deal. For example, if the scope document says one thing and the technical specification says another, the team should understand which document controls the obligation. Where possible, these issues should be resolved before signing.Scope, Exclusions, and Assumptions
Scope clarity is central to risk management in construction. Many disputes begin because one party believes work is included, while the other believes it is a variation. This often happens when scope documents are broad, qualifications are not incorporated, or assumptions are not clearly recorded. A practical checklist should test whether the scope aligns with the price, programme, drawings, technical requirements, and delivery methodology. Clear exclusions are also important. When a contractor has priced on the basis that certain work is excluded, that exclusion should be captured clearly. Important assumptions should not be left only in informal tender correspondence. Perfomir has discussed this type of commercial exposure in its article on top contract risks and how to avoid them.Notices, Time Bars, and Contract Administration
Notice obligations are one of the most important parts of a contract review checklist. A notice clause can look administrative, but it may control entitlement. In many contracts, a party may need to issue notice within a specific number of days after becoming aware of an event. Late notices may reduce, complicate, or dispute entitlement depending on the contract terms and applicable circumstances. The practical commercial point is that project teams need visibility of notice obligations before issues arise. Notice obligations should be extracted into a live register. The register should include the event, clause reference, trigger date, deadline, required content, recipient, delivery method, and owner. Perfomir has a dedicated resource on notice obligations in construction contracts and a practical article explaining why notice provisions can cost millions.Variations and Change Control
Variations are one of the most common sources of construction claims. A contract review checklist should clearly identify how a variation is instructed, assessed, priced, submitted, certified, disputed, and recorded. The project team should understand whether written instruction is required, whether oral directions are recognised, whether notice must be issued, whether a quotation must be submitted before work proceeds, and how time impact is assessed. When the variation process is unclear, changed work may be carried out without properly protecting entitlement. Perfomir has written further on variation claims and construction contract risk, including how delivery events can become commercial exposure if not managed early.Delay, Extensions of Time, and Claim Exposure
Delay risk is not just a programme issue. It is also a contract issue. A delay event may require notice, particulars, updated programme information, causation evidence, mitigation records, and formal assessment under the contract. A good checklist should identify the events that may give rise to an extension of time. It should also identify the required notice period, whether concurrent delay is addressed, whether acceleration can be directed, and whether delay damages apply. For executives, delay exposure can become significant because it may affect revenue, liquidated damages, project margin, client relationships, and downstream subcontractor claims. Perfomir’s guide to claim exposure prediction explains how early identification of claim pathways can help teams understand risk before it crystallises into a dispute. Perfomir has also written on contract risk intelligence and claim exposure.Payment, Security, and Cash Flow Controls
Payment clauses should be reviewed carefully because they affect project cash flow and commercial control. The checklist should identify payment claim dates, required supporting documents, assessment periods, payment due dates, set-off rights, retention, bank guarantees, milestone payment triggers, and release conditions for security. From a contract management perspective, the practical issue is process compliance. A project team should know exactly what must be submitted, when it must be submitted, who must certify it, and what records are required to support payment claims.Liability, Indemnities, Insurance, and Defects
Risk allocation clauses should be reviewed carefully with the appropriate professional advisers. From a commercial management perspective, the team should understand what risks the organisation is accepting, whether liability is capped, whether any exclusions apply, whether indemnities are broad or limited, and whether insurance requirements align with the risk profile. Defects and warranty obligations should also be reviewed before signing. These obligations can continue after practical completion and may affect project close-out, security release, maintenance, and long-term exposure. Perfomir has published further guidance on managing contract risk in construction, including the importance of identifying risk early rather than waiting until a dispute has already developed.External Events, Force Majeure, and Price Escalation
Construction projects can be affected by events outside the direct control of the parties. These may include supply chain disruption, extreme weather, change in law, industrial action, geopolitical disruption, force majeure events, or market escalation. The checklist should identify whether the contract provides time relief, cost relief, termination rights, notice obligations, or no relief at all for these events. This is particularly important for fixed-price contracts, where price escalation risk may sit heavily with one party unless the contract provides a clear adjustment mechanism. Perfomir has explored these issues in its articles on force majeure, frustration, and termination and Middle East crisis and fixed-price contract risks.Dispute Resolution and Executive Escalation
A dispute clause should not be reviewed only after a dispute occurs. The project team should understand the required process for dispute notices, negotiation, executive escalation, adjudication, expert determination, arbitration, or litigation. Teams should also understand whether work must continue during a dispute and what records must be maintained. A clear dispute pathway helps project teams respond quickly and consistently when issues arise. For commercial leaders, the important question is not only “what happens if there is a dispute?” A better question is: “what early warning signs show that a dispute may be forming?” Live contract risk monitoring can help answer that question earlier.How Contriqo by Perfomir Supports the Checklist During Delivery
Manual contract review has several common limitations. Important clauses can be missed. Notice obligations may remain buried in long documents. Project teams may not know which clauses are relevant when events occur during delivery, and emerging commercial exposure may not become visible until an issue has already developed. Contriqo by Perfomir helps address these challenges through AI-assisted contract intelligence that connects project events with relevant contractual clauses and obligations. Rather than treating a contract review as a one-off document exercise, Contriqo helps construction and infrastructure teams understand how contract requirements relate to what is actually happening on the project. For example, Contriqo can help teams:- Identify relevant and high-risk clauses in construction contracts.
- Surface contractual obligations and notice requirements.
- Connect project events with relevant contract clauses.
- Identify variation, delay, payment, and potential claim pathways.
- Support earlier visibility of contractual risk and potential entitlement.
- Highlight commercial risk and potential claim exposure.
- Reduce reliance on manual contract searching.
- Support a more consistent contract review and risk-analysis process.
- Keep contract intelligence connected to live project events during delivery.
Turning the Checklist into a Live Risk Register
The checklist should not sit in a folder after contract award. Once the contract is live, the checklist should be converted into practical registers and controls, including:- A contract obligation register.
- A notice obligation register.
- A variation register.
- A delay and extension of time register.
- A claim exposure register.
- A payment and security register.
- A risk escalation dashboard.
Frequently Asked Questions
What should be included in a construction contract review checklist?
A construction contract review checklist should cover the contract documents and order of precedence; scope, exclusions, and interfaces; design responsibility; price and payment; programme and delay; notices and time bars; variations; site conditions; security and insurance; liability and indemnities; defects and warranties; suspension and termination; disputes; records; governance; and subcontract flow-down. Each material finding should identify the risk, required action, owner, deadline, and delivery-stage control.What are the biggest red flags when reviewing a construction contract?
Common red flags include unclear scope, conflicting documents, broad fitness-for-purpose obligations, unrealistic programmes, strict time bars, unapproved oral-instruction risk, uncertain variation valuation, extensive set-off rights, uncapped or uninsured liability, one-sided termination rights, and head-contract obligations that are not passed through to subcontractors.Should a contract checklist be used after the contract is signed?
Yes. Before signing, the checklist supports pricing, clarification, negotiation, and acceptance decisions. After signing, its material findings should become live obligation, notice, variation, payment, delay, claim, security, and risk controls. The checklist should be revisited when scope, programme, instructions, access, payment, or other project conditions change.Who should complete a construction contract review?
The review is usually coordinated by commercial or contracts personnel with input from project delivery, estimating, planning, design, procurement, finance, insurance, technical specialists, and legal advisers where appropriate. Responsibility depends on the organisation and contract, but every material finding should have one named owner and a defined approval or escalation route.Australian References and Further Reading
These public sources provide useful Australian context. Their application depends on the project type, contract, jurisdiction, and circumstances:- Australian Government — National Guidelines for Infrastructure Project Delivery, covering delivery approaches and the balance of project cost, risk, objectives, and outcomes.
- NSW Government — Checklist for home owners signing a building contract worth more than $20,000, a residential NSW checklist addressing licensing, scope, price, variations, insurance, payments, approvals, and termination.
- NSW Government — Guide to providing home building contracts, explaining requirements and supporting materials for NSW residential building contracts.
- NSW legislation — Building and Construction Industry Security of Payment Act 1999, the current official text for NSW security-of-payment legislation.
Final Thoughts
A practical contract review checklist helps construction and infrastructure teams identify risk before it becomes a claim, dispute, delay, or margin issue. The checklist should cover contract documents, scope, design responsibility, notices, time bars, variations, delay, payment, claims, records, liability, insurance, termination, dispute resolution, and delivery-stage monitoring. However, the checklist is only the starting point. The real value comes when the checklist is converted into live contract management actions. Notices need owners. Time bars need deadlines. Variations need records. Claims need evidence. Executives need visibility. Project teams need practical tools to connect daily events back to contract obligations. That is why contract review should not stop at signature. With the right checklist, strong commercial discipline, and tools such as Perfomir, construction and infrastructure teams can improve visibility, reduce surprises, and manage contract risk more proactively. General information only. This article does not provide contractual, legal, or financial advice. Project-specific issues should be reviewed with the appropriate professional advisers.
Author: Perfomir Contract Risk Intelligence Team
Perfomir provides contractual risk intelligence for businesses. Through Contriqo by Perfomir, the team helps organisations identify contract risk, claims exposure, commercial strategy issues, project delivery challenges, and executive-level insights.
