A reference to UAV or UAV-GC does not resolve a construction dispute by itself. First establish which terms the parties agreed, which version applies and where the contract departs from it. Then examine the particular notification, variation or delay. This guide helps business clients and contractors organise their file for a Dutch construction lawyer. The outcome remains dependent on their own contractual documents and facts.
Sources (3)
On this page
1. Establish whether the terms were actually agreed
PIANOo states that UAV and UAV-GC do not apply automatically and must be expressly declared applicable. Find the reference in the signed contract, appointment confirmation and tender documents. Collect your quotation and any reservations as well. A document sent only with a later invoice does not automatically have the same significance as terms agreed at contract formation.
Then examine whether the parties mentioned different sets of terms and how they responded. Record which documents were available before acceptance and what the parties expressly accepted or rejected. A dispute about applicability requires different arguments from one about interpreting a provision. Have your lawyer assess those questions separately. A model name used for years provides useful background, but does not replace proof of the specific agreements for this project.
2. Compare versions, appendices and deviations
Write down the full name and year of the agreed terms. UAV 2012, UAV-GC 2005 and UAV-GC 2025 may occur in different files in practice. Introducing a new version does not automatically rewrite an earlier contract. Rijkswaterstaat, for example, describes its own implementation choices for integrated design-and-build appointments; that does not automatically amend every construction contract.
List deviations in the specifications, basic agreement, requirements specification and other contract documents. Include any document hierarchy and tender clarification notices. Keep dated original versions so a subsequently changed project folder does not obscure the starting point. Discuss inconsistencies using your own hierarchy and context. A provision from an online example may be correct in substance yet unusable for your contract version or differing agreement.
3. Allocate design, execution and information specifically
Tasks may be allocated differently under traditional and integrated contracts. Avoid assuming that the UAV-GC label places every design and information risk on the contractor. Read which performance, data and investigations each party must provide. PIANOo describes attention to information and cooperation in the UAV-GC revision; precise application requires the chosen text and project agreements.
Connect the problem to that task allocation. For unexpected ground conditions, for example, the investigation supplied, access for further investigation and earlier questions matter. An unworkable detail raises issues about design, apparent inconsistency and warnings exchanged. Also collect what the parties actually knew when setting price and schedule. Merely identifying afterwards who uploaded a drawing is often too narrow to determine contractual responsibility.
4. Record notifications without inventing universal deadlines
Contractual notification requirements may apply to claims for time, money or circumstances. Investigate for each claim which provision matters, whom a message must address and what information is needed. Do not use a general deadline from another project. Create a timeline of discovery, discussions, written notification and receipt. Include original attachments; a short email may refer to an extensive report that is subsequently missing.
If a potentially relevant period is still running, have the position assessed immediately. An informal conversation with the site manager is not automatically valid notice to the representative designated in the contract. Conversely, the absence of a particular heading alone does not decide every substantive question. Preserve all communication and record the consequence announced. A lawyer can compare the applicable rule, any deviation and the significance of actual events.
5. Separate the variation instruction, price effect and schedule
A changed requirement may demand different execution and extra time. Record who initiated the change, the instruction given and whether the authorised person agreed. Keep the technical description separate from cost and schedule estimates. Approval of a new solution need not mean agreement on all financial consequences. The procedure for reaching that agreement may also be contractually regulated.
Create a file for each variation containing the original situation, request, response, design adjustment, hours and equipment use. State which activities could not wait and why. If the parties proceed before agreement, they must record what this does and does not decide. Also discuss substantiation of delay effects. A higher final invoice or shifted completion date does not itself show which part this variation caused and which part arose from other project problems.
6. Fictional scenario: different information during execution
Suppose a contractor on an integrated project finds a cable in a different position from the supplied data. They report this at a site meeting, choose a diversion and later request extra payment and time. The client points to investigation obligations and a written notification procedure. This invented example contains separate questions about information, risk, authority, variation and demonstrable consequences for the works.
The file begins with the agreed version and deviations, followed by original information and investigation opportunities. The notification, instruction and chosen solution are then examined. A programme shows which activities actually had to wait and which could continue. The lawyer can then advise specifically on the claim and defence. The conclusion does not follow solely from UAV-GC appearing on the cover or the client having supplied new data.
7. Give your lawyer a searchable contract file
Assemble the signed contract, terms, deviations, document hierarchy and relevant appendices in their original versions. Add a register of variations and notifications showing date, sender, recipient and location. Describe the desired outcome and associated amount or time effect for each dispute point. Include an overview of outstanding decisions too. This allows the initial assessment to focus on the provisions that actually affect the next decision.
Also ask about the dispute clause and any steps preceding proceedings. The proper forum, response points and opportunities for interim measures must emerge from the specific file. Meanwhile continue recording necessary project information and avoid unclear oral commitments. A settlement must identify the variation, period and claim it settles. Otherwise a practical payment may later prompt disagreement about relinquishing other rights not yet assessed.
Frequently asked questions
Does UAV-GC 2025 automatically apply to an ongoing project?
No. Check the agreed version and any later contractual amendment. A new publication does not rewrite your contract automatically.
Must every claim be notified within the same fixed period?
No. The relevant provision, contract version, deviations and nature of the claim determine which notification requirements need investigation.
Does the contractor always bear every design risk under UAV-GC?
That is too general. Read the specific task allocation, information supplied, design contributions and deviations before attributing a risk to a party.
Sources
These sources relate to this page. For a specific case, check current rules and your own documents.
- PIANOo — uniforme administratieve voorwaarden Accessed: 2026-10-23
- Rijkswaterstaat — implementeert UAV-GC 2025 Accessed: 2026-10-23
- PIANOo — terugblik impact UAV-GC 2025 voor inkoper Accessed: 2026-10-23
Legal review
Not legally reviewed yetThis version has not been reviewed by a lawyer or legal professional. Checking sources or editing text is not legal approval.
Editorial team Construction law in the Netherlands
We connect explanations to sources and record targeted changes. Legal review is attributed only to the actual reviewed version, with a real reviewer, date and scope. Human legal review of these articles remains open.
Ricardo van der Spoel
Editorial responsibility · Editorial organisation and technology