Skip to main content

Contracts & Claims

Every obligation tracked. Every claim backed by the record.

Connect contracts, site events, and correspondence to see what needs action, where a claim may have a basis, and which evidence is still missing.

Winning the work is the beginning. Protect its value through delivery.

A drawing arrives late. Access stays blocked. An instruction changes the sequence. The facts live in site diaries, inboxes, and someone’s memory, while the contract keeps counting.

Bring the obligations and the project record together. Know what needs action today, preserve the evidence as work progresses, and assess a claim before the team starts assembling it.

From award to final account

One connected record. Six places to act.

01

The governing contract

Read the agreement, conditions, specifications, and amendments together. Trace each obligation to its clause and version. Flag conflicting provisions for your team to resolve.

02

Obligations on both sides

Know what your team, the employer, engineer, and subcontractors owe. Assign owners, confirm triggers, and track due dates with evidence of submission, receipt, and completion.

03

Hindrances as they happen

Record delayed access, drawings, instructions, and disrupted work. Connect each event to its location, affected activities, resources, mitigation, and contemporary site records.

04

Correspondence with a next action

Connect letters, emails, RFIs, and meeting minutes. Surface commitments, unanswered requests, instructions, and possible notice requirements without losing the original thread.

05

A basis you can examine

Review the applicable clauses, notice history, causation, and supporting records. See what supports the claim, what contradicts it, and what still needs a planner or commercial manager’s judgment.

06

Evidence ready for review

Build a chronology and indexed exhibits alongside the claim narrative and calculations. Keep originals, revisions, delivery records, and reviewer decisions connected to the submission.

Examine the basis

A possible claim. The reasons. The gaps.

Follow delayed access from a site event to a reviewable position. Each part of the assessment stands on its own evidence.

Illustrative workflow · Sample records

Hindrance H-014

The event

Access to the workfront remains blocked.

The team records the obstruction, identifies the affected work, and links the access obligation. A notice is prepared and its delivery recorded.

  1. 01Site report and photographs recorded
  2. 02Access obligation linked for review
  3. 03Notice and delivery receipt attached
  4. 04Programme and cost evidence requested

Next action · Planning team

Link the affected activities and assess the effect on the completion milestone.

Assessment · Open each finding

Contractual basisPotential basis

The access obligation and handover record support further assessment. Confirm the applicable amendments and qualifications.

Contract access provision · Handover record

Notice procedureDelivery recorded

The notice and delivery receipt are linked. Confirm the trigger date, recipient, and delivery method against the governing contract.

Notice N-014 · Delivery receipt

Time entitlementAnalysis needed

The site record establishes blocked access. The effect on the completion milestone still needs programme analysis, including overlapping delays and mitigation.

Daily reports · Programme update required

Additional paymentEvidence missing

Standby costs are proposed, but resource allocation and cost records are incomplete. An extension of time alone does not substantiate additional payment.

Cost worksheet · Plant and labour records missing

Illustrative assessment, not a determination. Your team reviews the applicable contract, analysis, and source evidence.

Submission readiness

Know what is missing before you file.

A folder full of documents is only the start. Connect every assertion to an exhibit, identify gaps in substantiation, and give reviewers the complete chain of reasoning.

Keep the chronology, clauses, notices, calculations, and counterarguments together. Preserve the submitted version and track later additions separately.

The next missing record should be an action with an owner.

Claim pack · H-014

Illustrative exhibit index

Review required
  • 01Contractual basis & amendmentsLinked
  • 02Event chronology & site recordsLinked
  • 03Notices & delivery evidenceLinked
  • 04Correspondence & instructionsLinked
  • 05Programme & impact analysisNeeds review
  • 06Costs & supporting recordsIncomplete
  • 07Mitigation & counterargumentsNeeds review

Linked evidence still needs review. Readiness depends on what this claim must establish, not how many files are attached.

Built on Vault

The original record behind every conclusion.

Your contracts, correspondence, and site evidence belong to your firm. Vault connects the facts to their source documents, while your team confirms interpretations and approves the next action.

Explore your firm’s record in Vault →

The questions that matter.

Does a hindrance automatically become a claim?

No. An event is a starting point. The assessment connects the governing contract, procedural requirements, responsibility, impact, and evidence. A recorded delay alone does not establish an extension of time or additional payment.

Which notice deadline applies?

The requirement in your applicable contract and amendments. Trigger dates, calendar rules, recipients, and delivery methods need confirmation. Unresolved wording or dates stay visible for review instead of becoming a definitive deadline.

Can we see weaknesses in our position?

Yes. The assessment surfaces conflicting records, possible exclusions, overlapping causes, missing substantiation, and amounts already addressed elsewhere. Each conclusion should be examined alongside its sources.

What happens to the original evidence?

Original documents remain connected to extracted facts and annotations. Review the exhibits, preserve the submitted version, and track later additions separately so the record of what was submitted remains clear.

Who approves a notice or claim?

Your authorised team. Drafting, approval, sending, delivery, and acknowledgement are distinct steps. A prepared document is not treated as a served notice, and a potential claim is not treated as an agreed entitlement.

Contracts & Claims

Start with one contract. Follow the evidence.

Talk through a project contract, a hindrance, and the records behind it. See where obligations, notices, and claim preparation fit into your team’s work.

Discuss your contracts and claims