Late Site Handover in Construction Contracts: 8 Checks

The site was due to be handed over on Monday. By Friday, the contractor still cannot start the planned workfront and five working days of the original programme have been affected. The project manager believes the team can recover the time later. Commercial sees a possible extension-of-time issue. Contract administration asks a different question: what did the contract require the team to do when access was not provided? That last question is usually the right starting point. A late site handover may be an operational problem, but it can also activate contractual processes around site access, possession, delay, extensions of time, notices, mitigation, records and cost. Whether any entitlement exists depends on the actual contract and the facts.

In this article

Direct answer: what happens when site handover is late?

A late site handover in a construction contract does not automatically produce the same legal or commercial result on every project. The team should check the promised access or possession date, any conditions attached to access, the delay and EOT clauses, notice requirements, evidence obligations, mitigation duties and any cost-relief mechanism before assuming time or money is recoverable.

Key takeaways

“Site handover”, “possession of site” and “site access” may describe related but contractually different concepts. Read the defined terms and access provisions first.
Late access may trigger a delay or EOT pathway, but entitlement depends on the contract wording, the event, compliance with notice requirements and demonstrated programme impact.
The fact that the team believes it can recover the lost time later does not remove the need to review the contract when the event occurs.
Notice of delay and an EOT claim may be separate contractual steps.
Project records should show what access was promised, what access was actually available, which activities were affected, what mitigation was attempted and how the programme changed.
Cost consequences should be analysed separately from time entitlement. An EOT does not necessarily mean delay costs are recoverable.
The strongest response is event-driven: identify the event, map it to the relevant clauses, assign contractual actions and preserve evidence while the facts are still fresh.

Why “site handover” needs a contract check, not just a programme discussion

Project teams often use “handover” as shorthand for when the contractor can start work. The contract may instead refer to possession, site access, access to a work area, staged access or satisfaction of preconditions. A principal may be required to provide access by a stated date, while the contractor may first need to provide insurances, security, management plans, permits or other pre-start deliverables. Access may also be non-exclusive or staged. So the first question is not simply, “Was the gate open on Monday?” It is, “What access did the contract require, by when, and subject to what conditions?” NSW Government’s GC21 framework illustrates the importance of contract-specific drafting by dealing separately with site access, extensions of time and delay costs.

The event-to-contract issue map

Project event	Contract area to examine	Questions to ask immediately	Potential risk if ignored
Site not available on the planned date	Site access / possession provisions	Was access contractually due? Were contractor preconditions satisfied?	Disagreement over whether a qualifying event occurred
Planned activities cannot start	Programme / delay provisions	Which activities were due to commence and are they time-critical?	Weak causation or EOT support
Principal or representative advises access will be later	Communications / directions	Is the communication a formal direction, notice or simply information?	Unclear contractual status
Contractor resequences work	Mitigation / programme obligations	Is resequencing required, reasonable and properly recorded?	Later argument that delay could have been avoided
Labour, plant or subcontractors are affected	Cost / delay cost provisions	Are standby, demobilisation, remobilisation or prolongation costs potentially recoverable?	Cost incurred without a preserved contractual pathway
Completion may move	EOT / completion provisions	Does the event qualify and what must be submitted?	Exposure to an unchanged completion date or delay damages
Notice deadline starts running	Notice / claims provisions	What is the trigger, deadline, recipient, method and required content?	Time-bar or procedural compliance risk

The table is a triage tool, not an entitlement test. A late handover can touch several contract mechanisms at once, and each should be checked against the actual wording.

Is late site handover automatically an extension-of-time event?

No. It may be, but the team should not assume it. Late handover is often described as an owner-caused delay that leads to an EOT. That can be too broad for professional contract administration. The better question is whether the specific contract recognises delayed access, an act or omission of the principal, a breach, a qualifying cause of delay, a compensation event, or another defined event that can support time relief. A practical EOT review should test at least five issues:

Contractual trigger: Did the event fall within a recognised cause of delay?
Contractor compliance: Had the contractor satisfied the preconditions to receiving access?
Timing impact: Did the event actually delay an activity that matters to contractual completion or a milestone?
Notice and claim procedure: Were the required notices, particulars and claims submitted correctly and on time?
Mitigation and concurrency: Were there other delays, available workfronts or reasonable steps that affect the assessment?

The NSW Government’s guidance on managing extensions of time emphasises evidence of the alleged delay event and demonstration of its effect on the critical path. That distinction is important. Five days without full access does not necessarily equal a five-day EOT. The programme analysis must show the relevant effect.

Notice of delay is not necessarily the same as an EOT claim

One of the most important issues is the distinction between a delay event, its initial notification and a formal EOT claim. Perfomir’s existing guide on notice of delay in construction contracts explains the broader notice process. For a late site handover, the practical question is narrower: does the access event start one or more contractual clocks? Depending on the contract, the team may need to issue:

an initial notice of delay;
an EOT notice or claim;
an ongoing or updated notice while the delay continues;
particulars showing programme impact;
a separate cost or claim notice; and
notices to subcontractors or suppliers under downstream contracts.

The required sequence can differ. A project team should therefore avoid assuming that a progress-meeting discussion, email chain or programme update has satisfied the formal notice regime. Perfomir’s guide to notice obligations in construction contracts is useful where the team needs to check trigger events, time bars, recipients, service methods and supporting records.

Why “we’ll recover the time later” can be commercially dangerous

Resequencing and recovery planning are sensible project-management responses, but they do not replace contract administration. The forecast may prove wrong, recovery may create additional cost, and an early failure to notify can matter if the impact grows. Resequencing can also make causation harder to reconstruct. If the baseline programme, contemporaneous update and reasons for changing sequence are not preserved, later analysis may become a hindsight debate. The better approach is to run project recovery and contractual review in parallel: pursue mitigation while protecting the relevant contractual pathway.

What records matter when access is late?

A useful evidence file should be built from the first day of the access problem, not months later when a claim is being assembled.

Record	What it helps establish	Practical detail to capture
Contract and access schedule	What access was promised	Dates, areas, stages, conditions and responsible party
Pre-start compliance records	Whether contractor access conditions were satisfied	Insurances, security, plans, approvals, inductions
Baseline and current programme	Planned logic and current status	Activities due to start, float, critical path and milestones
Site diaries	What happened each day	Available workfronts, labour, plant, constraints and instructions
Photos / access logs	Physical availability of the site	Closed areas, incomplete predecessor work, barriers or restrictions
Correspondence	What each party knew and when	Access advice, directions, requests, responses and acknowledgements
Meeting minutes	Decisions and mitigation discussions	Resequencing, partial access, revised handover dates
Labour and plant records	Resource consequences	Standby, redeployment, demobilisation and remobilisation
Subcontractor records	Downstream impact	Mobilisation commitments, delay notices, revised dates
Cost records	Potential financial effect	Preliminaries, disruption, additional supervision, logistics
Notice register	Procedural compliance	Trigger date, due date, recipient, method, status and follow-up

Good records do more than support a future claim. They help the team make better decisions now. For example, a daily access map may reveal that partial possession is enough to keep one critical activity moving even though another workfront remains unavailable.

Time entitlement and cost entitlement should be separated

A common commercial mistake is to treat “we have an EOT” and “we can recover our costs” as the same conclusion. They may be governed by different clauses and different tests. A contract might provide time relief for delayed access but restrict or exclude delay costs. Another may provide an agreed daily delay-cost rate. Another may treat certain principal-caused events as compensation events. A bespoke contract may contain caps, exclusions, notice conditions or specific valuation rules. The project team should therefore run two linked but separate questions: Time: Can the completion date or milestone be adjusted because of this event? Money: Does the contract provide a pathway to recover the financial consequences of the event, and if so, what categories and evidence are required? This distinction also matters for the principal. Granting time does not necessarily concede every claimed cost, and rejecting cost does not necessarily resolve the time question.

What about the prevention principle?

The prevention principle can arise in discussions about principal-caused delay. In broad terms, it concerns circumstances where one party’s conduct prevents the other from meeting a contractual time obligation. Its interaction with EOT machinery, time bars and liquidated damages is contract- and fact-sensitive. Gaymark Investments Pty Ltd v Walter Construction Group Ltd is frequently discussed in this area, but project teams should not treat the principle as a fallback for a missed contractual process. The practical lesson is simpler: identify and comply with the available delay mechanism promptly. If disputed time bars, termination or significant liquidated damages are involved, appropriately qualified legal advice may be required.

A practical response framework for late site handover

When the planned handover date is missed, use the following eight-step process.

Verify the contractual access obligation. Confirm the date, area, level of access, conditions precedent and any right to defer or stage access.
Confirm contractor readiness. Record whether the contractor had satisfied its own pre-start obligations and was genuinely ready to perform the affected work.
Define the event precisely. Record what was unavailable, from when, why, who communicated it and whether partial access existed.
Map the relevant clauses. Review access, delay, EOT, notice, claims, cost, mitigation, communications and completion provisions together.
Protect notice requirements. Identify the trigger date, deadline, recipient, service method, content and follow-up particulars. Do not wait for the full impact to be known if the contract requires earlier notice.
Assess programme impact. Compare the event with the contemporaneous programme and identify affected activities, logic, float, milestones and potential critical-path effect.
Mitigate and document. Consider partial possession, alternative workfronts, resequencing or resource changes, while recording why each step was reasonable and what it cost.
Escalate the commercial position. Keep the project director and commercial leadership informed if the event may affect completion, delay damages, subcontractor exposure, acceleration or material cost.

This framework deliberately separates recognition of the event from proof of entitlement. The project team’s first job is to keep the relevant options visible while the facts develop.

Who should do what?

Role	Immediate question	Primary action
Project manager	What work cannot proceed and what can be resequenced?	Protect delivery, confirm actual access and document mitigation
Site / construction manager	What physical workfronts are available?	Maintain daily records of access, labour, plant and constraints
Planner	What does the current programme show?	Assess affected logic, float, milestones and critical path
Contract administrator	What does the contract require now?	Identify clauses, notices, deadlines, recipients and formal steps
Commercial manager	What time and cost exposure is developing?	Separate EOT, delay-cost, subcontract and claim pathways
Project director	Does the issue threaten key milestones or commercial position?	Set escalation, client engagement and decision priorities
Document control	Can we prove what was sent and received?	Preserve correspondence, transmittals, notices and receipt evidence

The responsibility should not sit with one person. Late access is a good example of why project controls, delivery and commercial teams need a shared event-to-contract workflow.

Common mistakes after a late handover

Common failure points include waiting until the final delay is quantifiable before checking notice obligations; treating meeting minutes as automatically satisfying formal notice requirements; assuming five days without access equals five days of EOT; failing to prove the contractor was ready to start; recording the principal’s delay but not mitigation efforts; treating time relief and monetary recovery as the same entitlement; and overlooking downstream subcontract notices or claims. Each mistake has the same underlying cause: the project event was not connected to the contract early enough.

From project event to commercial risk

A late site handover becomes easier to manage when the team follows an explicit chain: Project Event → Relevant Clause → Contractual Obligation → Notice Requirement → Potential Entitlement → Commercial Risk Project event: contracted access is not available when expected. Relevant clauses: access or possession, EOT, notice, programme, mitigation, delay costs and communications. Contractual obligation: determine what each party had to do and whether any preconditions applied. Notice requirement: identify the trigger, timing, recipient, format and supporting particulars. Potential entitlement: assess possible time or cost relief without assuming it exists. Commercial risk: consider completion exposure, delay damages, resource cost, subcontractor claims, acceleration pressure and dispute escalation. This event-driven approach is also the logic behind contract risk intelligence: risk becomes more useful when clauses and obligations are connected to what is actually happening on the project.

How Contriqo can support the review

Contriqo by Perfomir is an AI contract intelligence and decision-support platform for construction and infrastructure. In a late-site-handover scenario, it can help teams connect a reported access event with relevant contract clauses, obligations, notice requirements and potential claim-exposure pathways. The practical value is not that software decides whether an EOT or cost claim is legally valid. It does not replace the planner’s delay analysis, the commercial manager’s judgement, the contract administrator’s process or professional legal advice. Its role is earlier visibility. A project event that might otherwise remain in a meeting minute or email can be reviewed against the contract while the notice window, records and mitigation options still matter. Perfomir’s contract administration risk intelligence resource explains this event-to-clause approach in more detail, while claim exposure prediction shows how access constraints can become an early signal of a wider claim pathway.

Questions project teams should ask on day one

Before closing the first internal review, confirm:

What contractual access or possession was due, and had contractor preconditions been satisfied?
Was access completely unavailable, or partial or restricted?
Which planned activities and milestones were affected?
Is the event potentially a qualifying cause of delay?
What notice, EOT or cost-claim steps are required, by when and to whom?
What programme, site and correspondence records exist?
What mitigation or alternative workfronts are genuinely available?
Are subcontractors, suppliers or material costs affected?
When should the issue be escalated to project leadership?

These questions turn a vague “late handover” problem into a manageable set of contractual and project controls.

Frequently asked questions

What is late site handover in a construction contract?

It generally refers to the contractor not receiving the level of site access or possession required by the contract at the time expected. The precise meaning depends on the contract, which may distinguish between possession, access, partial access, staged access or access subject to preconditions.

Does late site access always entitle a contractor to an EOT?

No. The event may support an EOT under many contracts, but the outcome depends on the relevant delay clause, contractor compliance, programme impact, notice requirements, mitigation and any concurrent delay.

Should a contractor issue notice even if it expects to recover the delay?

The contract should be checked immediately. If it requires notice when an event occurs or may cause delay, a belief that time can later be recovered may not remove that procedural requirement.

Can a contractor claim costs for delayed site handover?

Possibly, depending on the contract. Time and money should be analysed separately because an EOT provision may not provide an equivalent right to delay costs, prolongation or disruption recovery.

What evidence is most important for a late site handover?

The contract access provisions, proof of contractor readiness, contemporaneous programmes, daily site records, access logs, correspondence, notices, mitigation records, subcontractor impacts and cost records are commonly important.

What if only part of the site is handed over?

Partial access should be assessed against the contract and the programme. The team should record exactly which areas were available, whether planned activities could proceed, what resequencing was possible and whether the remaining restriction affected contractual completion or milestones.

Key conclusion

The project manager, commercial manager and contract administrator are each seeing part of the same problem: recovery may be possible, an EOT pathway may exist, and notice may be required. A late site handover should trigger coordinated project and contract review. Confirm the promised access, identify the relevant clauses, protect notice requirements, preserve programme and cost records, test mitigation and keep time and cost questions separate. The project event is the trigger. The contract determines what happens next. This article provides general educational information only and does not constitute legal, contractual or financial advice. Contract terms and project circumstances vary. Obtain appropriately qualified advice for your specific contract and situation. Have a contract? See how Contriqo analyses project events against your contractual obligations.

References

NSW Government — GC21 Edition 2 — standard-form construction contract resources covering site access, extensions of time and contract administration.
NSW Government — Construction procurement guide: managing extensions of time — guidance on assessing delay, programme impact, mitigation, notices and EOT claims.
King & Wood Mallesons — Australian Construction Law: Frequently Asked Questions — Australian construction-law guidance covering qualifying causes of delay, EOT mechanisms and principal-caused delay.
Supreme Court of the Northern Territory — Gaymark Investments Pty Ltd & Anor v Walter Construction Group Ltd [1999] NTSC 143 — judgment relevant to discussion of the prevention principle and contractual delay mechanisms.

Late Site Handover in a Construction Contract: What Project Teams Should Check