Using AI as a Construction Contract Administration Co-Pilot
How I’ve been integrating Claude into the daily grind of infrastructure delivery
I work on the Principal side of a major civil infrastructure contract. My role spans quality assurance, specification compliance, variation claim assessment, and contractor management across earthworks, structures, stormwater, paving, and utilities. It’s a broad remit with a lot of moving parts and a lot of documents.
Over the past few weeks, I’ve been going all-in on using AI — specifically Claude — as a genuine working tool, not just a search assistant. What I’ve found has changed how I approach the role. Here’s what I’ve actually been doing.
1. The QA Status Gap — and How AI Helped Map It
One of the most persistent problems in infrastructure contract administration is knowing where you actually are against your QA framework. Hold Points (HPs) and Witness Points (WPs) are submitted against specific chainages or structure elements, but the correspondence register and the physical works progress often exist in completely different systems.
I uploaded two correspondence registers into a session and asked Claude to map HP/WP status against chainage. The contractor uses a structured coding system for submissions:
SUBMISSION REF: [PROJECT].[ALIGN].[ASSET].[DISCIPLINE].[SEQ].[CHAINAGE]
PRJ.N.R.EW.001.CH160-CH410
│ │ │ │ └── Chainage range
│ │ │ └─────── Sequential number
│ │ └──────────── Discipline (EW = Earthworks, SW = Stormwater)
│ └─────────────── Asset type (R = Road)
└─────────────────── Alignment (N = North, S = South)
Claude parsed both CSVs, decoded the location system, and produced a full QA status report — broken into earthworks, stormwater, culverts, and structures — with priority ratings for outstanding items sitting with the Principal.
The output identified three specific chainage gaps with zero HP/WP coverage — sections where earthworks had progressed but no inspection submissions had been raised at all. That’s the kind of gap that disappears into the noise of a busy project and only surfaces painfully later.
| Chainage Zone | Status | Discipline |
|---|---|---|
| CH660 – CH690 | No HP/WP submissions raised | Earthworks |
| CH755 – CH800 | No HP/WP submissions raised | Earthworks |
| CH1050 – CH1080 | No HP/WP submissions raised | Earthworks |
| North Road corridor | No coverage across full section | Earthworks |
| South Verge | No coverage across full section | Earthworks |
This became the basis for a formal action item register — sortable, filterable, and built to document what I’d found and fixed before anyone else noticed.
2. ITP Review — Catching What Gets Missed
Reviewing Inspection and Test Plans is one of those tasks that’s easy to do superficially and hard to do thoroughly. The specification matrix you need to hold in your head is large: mandatory Hold Points, Witness Points, minimum notice periods, submission timing obligations, and linkages to annexure schedules.
I recently reviewed an ITP for concrete works on a pedestrian bridge abutment. I read the ITP myself, flagged some concerns, and then used Claude to do a cross-reference against the applicable specification (TfNSW B80).
The result: two critical findings I had already identified were confirmed, and the clause substantiation was pinned precisely.
ITP REVIEW — B80 CONCRETE WORKS
================================
Activity: Concrete Placement (Bridge Abutment)
ITP Classification: Surveillance
B80 Cl. 7.5.2 Required: HOLD POINT
Finding: NON-COMPLIANT — downgrade from HP to Surveillance not permitted
Activity: Prefabricated Reinforcement Cage Fabrication
ITP Classification: NOT LISTED
B80 Cl. 6.6.2 + Annexure C Required: WITNESS POINT
Finding: MISSING — mandatory WP omitted entirely
Result: ITP NOT RELEASABLE — return for resubmission
The key finding: the contractor had listed concrete placement as Surveillance rather than the mandatory Hold Point required by B80 Cl. 7.5.2. This is a significant difference — a Surveillance item means the Principal may observe; a Hold Point means works cannot commence without Principal written release.
Additionally, the ITP was missing a Witness Point for prefabricated reinforcement cage fabrication entirely. Not a minor formatting issue — a mandatory quality verification step per the specification annexure.
The ITP was returned as non-releasable, with a clause-referenced review note. The AI helped me articulate the precise specification basis for each finding, which matters when a contractor pushes back.
Try this prompt:
I am a Principal’s Representative reviewing an ITP for [ACTIVITY] against [SPEC CODE]. The ITP classifies [ACTIVITY] as [CURRENT CLASSIFICATION]. Please cross-reference [SPEC CODE] Annexure C and identify whether this classification is correct. List any Hold Points or Witness Points that are missing or incorrectly classified, with the relevant clause reference for each finding.
3. Welding — When a Contractor Quotes a Standard to Escape Obligations
A variation claim came in arguing that because a specific specification had been superseded by a designer’s RFI direction (pointing to a different standard), the contractor was no longer required to field a Welding Supervisor or Welding Inspector for structural remediation work.
The argument: “AS 1554.3 doesn’t name those roles explicitly — so only a qualified welder is needed.”
I put the question to Claude cold, with just the standard reference and the contractor’s position. The response was exactly what I needed:
The functions of welding supervision and independent inspection still exist within AS 1554.3 even if the specific job titles aren’t used. A qualified WPS, welder qualification records, and independent inspection of completed welds by a competent person are not discharged by fielding a qualified welder alone.
The response also identified a practical resolution path:
PRINCIPAL RESPONSE STRATEGY — AS 1554.3 WELDING CLAIM
======================================================
Step 1: Acknowledge RFI nominated AS 1554.3 as applicable standard
Step 2: Confirm AS 1554.3 still requires:
→ Qualified WPS (Welding Procedure Specification)
→ Welder qualification records
→ Independent inspection of completed welds
Step 3: Direct contractor to submit BEFORE commencement:
→ Proposed welding methodology
→ WPS documentation
→ Welder qualifications
→ Inspection arrangements
Step 4: No instruction to price a variation — existing obligations only
No variation entitlement. Contractor obligation reinstated. Correspondence drafted and issued the same afternoon.
4. The Personal Issues Register
Over any busy project, a lot of the work a contract administrator does is invisible. You catch things early, fix them quietly, and move on. That’s good practice — but it means when questions arise later, there’s often no record of what you identified and when.
I asked Claude to help me build a personal issues register — an Excel workbook with colour coding, data validation dropdowns, and a formal closure status column. Not for the client. Not for the contractor. For me.
| Field | Purpose |
|---|---|
| Issue Ref | Sequential PIR number |
| Issue Type | HP non-compliance / Spec deviation / Variation dispute |
| Date Identified | When I found it |
| Specification Basis | The exact clause(s) |
| Description | What the issue was |
| Action Taken | What I did |
| Formal System Reference | Was it logged in the contract system? |
| Closure Status | Open / Closed / Pending resubmission |
In two weeks I logged items covering: a variation claim involving double-recovery of a working platform allowance, the ITP concrete abutment findings above, and a specification reading dispute on pile cage fabrication (tied vs welded lap returns — the spec allows tying; no variation required).
Having the register also changes how you find issues — you start documenting as you go rather than retrospectively.
5. Specification Interpretation Under Time Pressure
The pace of site works means questions arrive fast and sometimes decisions need to be made without days of deliberation.
Stormwater pit directly on a culvert barrel
Site flagged a layout that had a drainage pit sitting directly over an existing culvert structure. The question: is separation required?
TECHNICAL ASSESSMENT — PIT ON CULVERT
======================================
Issue 1: Load transfer
→ AS/NZS 4058 + AS 1597 assume uniform cover
→ NOT designed for eccentric pit wall loads on crown
Issue 2: Differential settlement
→ Independent structures, different founding conditions
→ Rigid connection = crack risk at joint
Issue 3: Penetration through top slab
→ Structural integrity impact — requires engineer review
Decision: RELOCATE pit outside culvert footprint
Reason: Engineering complexity not justified; relocation resolves all issues cleanly
Product substitution on drawings
A drawing called out a product “or equivalent.” Claude walked through the correct contractual process:
Step 1: Contractor submits formal substitution proposal — prior to procurement, not after
Step 2: Technical evidence of equivalence — against the performance criteria of the specified product, not just a brochure comparison
Step 3: Principal reviews and responds — the notation does not give unilateral substitution rights
Step 4: Approval recorded before supply — verbal approval is not approval
6. Variation Claim Management
The most commercially significant use of AI in my role has been in variation claim assessment. Claims can be technically complex, involve multiple specification cross-references, and require a precise understanding of where the risk allocation sits under the contract.
The general pattern I’ve found useful:
VARIATION CLAIM WORKFLOW
=========================
1. Claim received
2. AI interrogates specification → identifies relevant clauses
3. AI identifies risk allocation under contract conditions
4. Human makes commercial decision
5. AI drafts clause-referenced response
6. Human reviews, adjusts, issues formally
The key discipline: AI is used to interrogate the specification, not to make the commercial decision. The human retains the decision. The AI makes the analysis faster and more defensible.
A recent example involved a standdown cost claim for additional site investigation boreholes directed under a specification clause. The contractor claimed a separate working platform at a level approximately 500mm below the existing piling working platform allowance already in the contract.
The position: the claimed platform level was within the existing allowance scope. No separate entitlement. The AI helped confirm the specification read, identify the relevant construction contract clauses on investigation obligations, and draft the response.
Try this prompt:
I am assessing a variation claim under [CONTRACT TYPE e.g. GC21 / AS4000 / NZS3910]. The contractor claims [BRIEF CLAIM DESCRIPTION]. The relevant specification clause is [CLAUSE REF]. Please identify: (1) what the clause actually requires, (2) where the risk for this event sits under the contract conditions, and (3) the strongest grounds to reject or accept the claim with clause references.
What I’ve Learned
The AI is only as good as the documents it has access to
On this project I’ve loaded the full specification suite into a project knowledge base. When I ask a question about B80 or NATSPEC or AS 1554.3, the AI searches those actual documents. It’s not working from general knowledge — it’s working from the contract documents. That’s the difference between a useful tool and a hallucination risk.
Push back when it’s wrong
The AI will make mistakes. On one ITP review it raised findings that couldn’t be evidenced on close reading of the document. I pushed back. It retracted. That’s the right dynamic. Treating AI output as a first draft to be verified — not a final answer — is the correct frame.
Correspondence gets faster without getting sloppy
The thing that takes the most time in contract administration is often not knowing what to say — it’s the drafting and refinement cycle. AI has compressed that without reducing quality. If anything, having a first draft to react to forces me to think more clearly about what I actually want to say.
The knowledge base format rewards investment
The more you put in, the more you get out. A spec suite that’s been structured and loaded into a knowledge base becomes a queryable asset. That’s genuinely new.
Frequently Asked Questions
Can AI replace a contract administrator?
No — and it shouldn’t try to. The commercial decisions, the judgment calls under time pressure, and the accountability for the position you take all sit with the human. AI accelerates the analysis and the drafting. The CA still owns the decision.
Which AI tool works best for contract administration?
Claude works well for long-document analysis and specification cross-referencing, particularly when you load the relevant specs directly into the context. ChatGPT is useful for drafting. The best results come from loading your actual contract documents rather than relying on general knowledge.
Do you need to be technically trained to use AI for CA work?
Yes — more so than in other fields. The AI can surface the right clause and draft a response, but you need enough domain knowledge to know when it’s wrong. Treating AI output as a first draft to be verified by a competent practitioner is the correct approach.
Is it safe to use AI for commercially sensitive contract correspondence?
Use judgement. Don’t paste full contract documents into consumer tools if the contract has confidentiality obligations. Purpose-built tools with data isolation, or running models locally, are the appropriate solution for sensitive projects.
Conclusion
If you’re working in infrastructure delivery — principal side, contractor side, or designer side — and you’re not using AI as part of your technical workflow yet, start with your specification suite. Load it. Start asking questions. See what comes back.
The specification didn’t change. Your access to it just got significantly faster.
ITP review for B80 concrete works
GC21 variation claim assessment guide