What is Acceptance Protocol?
Updated: 6 March 2026
An acceptance protocol is a written document completed at the conclusion of a project or delivery that records what was delivered, whether it meets the agreed specifications, what defects or outstanding items were identified, and what the agreed remediation commitments are. Signing the acceptance protocol by both parties marks the formal moment of handover, from which the warranty period begins and responsibility transfers from supplier to buyer.
How does acceptance protocol work?
An acceptance protocol is a critical document for projects, fit-outs, installations, and bespoke solutions. It gives formal legal weight to the moment of transfer: the supplier declares the work complete, the buyer inspects and accepts — or accepts conditionally, or rejects.
A complete acceptance protocol includes: a description of what has been delivered (scope and specifications), the outcome of the inspection (accepted, conditionally accepted, or rejected), a snagging list of identified defects or outstanding items, the agreed remediation plan for those items (deadlines and responsibilities), and the signatures of both parties.
The date of acceptance is legally significant for several reasons. First, the warranty period begins on the acceptance date. Second, the defect notification period — the window within which you can report defects — starts running. Third, risk in the delivered goods or works typically transfers from supplier to buyer at acceptance.
A common mistake is implied acceptance: if the buyer takes the delivered work into use without formally completing an acceptance protocol, this may be interpreted as tacit acceptance. Defects reported later become harder to enforce because the supplier can argue that the buyer accepted the delivery in its current state.
For larger projects such as IT implementations, construction works, or equipment installations, it is common practice to precede final acceptance with a formal acceptance test. The acceptance protocol then documents the outcome of that test and the buyer's sign-off.
Why does this matter for SMBs?
Without an acceptance protocol, the buyer's position in disputes about subsequent defects is weak. If there is no written record of the condition at delivery, it is difficult to prove after the fact whether a defect existed at handover or arose later.
A well-drafted acceptance protocol protects both parties: the supplier can demonstrate compliant delivery; the buyer can demonstrate which defects were identified at acceptance and need to be rectified. It is the contractual close of a project and the starting point of the warranty period.
How to manage this correctly
- 1Always produce a written acceptance protocol, even for smaller projects or partial deliveries
- 2Include a specific snagging list: each identified defect with a description and the agreed remediation deadline
- 3Sign the protocol only after a genuine inspection of what has been delivered — a signed protocol implies acceptance
- 4Specify whether the acceptance is final or conditional and what timeline applies for resolving outstanding items
- 5Keep the signed protocol as part of the contract file — it is evidence in any future warranty or liability claim
Manage all your contract deadlines automatically
Tracking Contracts alerts you well ahead of every notice deadline — no spreadsheets, no missed renewals.
Start free monthRelated terms
Acceptance Test
An acceptance test is a structured testing process in which the buyer verifies whether a delivered s…
Contract ManagementWarranty
A warranty is a contractual commitment that a product or service will conform to agreed specificatio…
Core TermsNotice of Defect
A notice of defect is a written notification from the buyer to the supplier that delivered goods or…
Core Terms