SHORT ANSWER TO THE MAIN QUESTION

A Handover Protocol is not one universal contract type with a single statutory content under the Czech Civil Code. Its legal significance depends on what is being handed over, what the main contract says and what the protocol itself confirms.

It may serve only as evidence of physical handover and the condition of the subject matter. However, the parties may also agree in the main contract that signing the protocol is a condition for proper handover of the work, entitlement to the final payment, commencement of a warranty period or another legal consequence.

It is particularly important to record defects and reservations correctly. Under a contract for work, acceptance without reservations may materially weaken the customer’s ability to rely later on rights arising from apparent defects.

The first question should therefore be what the protocol is supposed to mean legally under the particular contract. Only then should you decide what the protocol needs to contain.

YOU MAY BE THINKING…

“Do we have to prepare a handover protocol at all?”

“Is it enough to write that I accepted the item?”

“What if I sign acceptance without reservations and discover a defect later?”

“Do I have to accept work that has defects?”

“What if the other party refuses to sign the protocol?”

“Is an unsigned protocol useless?”

“Can a handover protocol amend the original contract?”

“Do photographs have to be included?”

“What should a protocol contain when an apartment is handed over?”

“Is handing over an apartment the same as handing over a building, machine or software?”

No.

And that is why a universal one-page template does not work equally well in every situation.

FREQUENT PRACTICAL QUESTIONS

Is a Handover Protocol always required?

No.

The Czech Civil Code does not generally require every handover of property or work to be recorded in a separate document called a “Handover Protocol”.

The position changes, however, if the parties have agreed in their contract that handover will take place by protocol.

Then it is necessary to determine whether the protocol is intended:

only to evidence that handover physically occurred,

or whether legally relevant handover is supposed to occur only upon signature of the protocol.

The difference may be fundamental.

What if the contract says that the work is handed over only by signing the protocol?

Then the signed protocol may itself be a condition of handover and acceptance.

The Czech Supreme Court has repeatedly dealt with contracts under which works were to be handed over through a formally specified protocol. If the parties genuinely agree on such a mechanism as a condition of handover, it cannot necessarily be replaced simply by arguing:

“But the customer is already using the work.”

The exact legal effect always depends on the wording of the contract.

The same document may be only evidence of handover under one contract and an actual legal condition of handover under another.

What does “accepted without reservations” mean?

Under a contract for work, this is a significant statement.

The Czech Civil Code expressly distinguishes acceptance of completed work:

with reservations

and

without reservations.

If the customer accepts the work without reservations, they may later lose the ability to successfully enforce rights arising from an apparent defect if the contractor argues that the defect was not notified in time.

It is therefore unwise to sign standard wording such as:

“The Work has been handed over without defects or unfinished works.”

if that does not reflect reality.

Does signing the protocol mean I can no longer claim hidden defects?

Not automatically.

It is necessary to distinguish apparent defects, which could be identified during a proper inspection at handover, from defects that become apparent only later.

Signing a protocol without reservations may be highly problematic in relation to apparent defects.

It does not automatically mean, however, that all rights relating to a defect that could not objectively have been discovered at handover disappear.

Can a Handover Protocol amend the contract?

In some circumstances, yes.

The title of the document is not decisive. Its content and the parties’ actual intention matter.

If both parties clearly agree in the protocol to change a contractual parameter and the requirements for a contractual amendment are otherwise satisfied, the protocol may also operate as an amendment.

It is not safe, however, to assume that every note inserted into a protocol automatically modifies the original contract.

A Handover Protocol may contain contractual arrangements, but an amendment must genuinely be identifiable from its content.

What if one party refuses to sign the protocol?

That depends primarily on the main contract.

If both signatures are contractually agreed as a condition of handover, the absence of one signature may mean that legally relevant handover has not yet occurred.

If the protocol is only evidentiary, the actual handover may still be capable of proof by other means.

So the key question is not merely:

“Do we have a signed protocol?”

The key question is:

“What does our contract say that signing the protocol actually does?”

WHAT THE LAW SAYS VS. WHAT HAPPENS IN PRACTICE

There is no single statutory “Handover Protocol”

That is the starting point.

A protocol serves a different purpose when used for:

• a residential lease,

• a property sale,

• handover of a construction project,

• delivery of machinery,

• software delivery,

• termination of an outsourced service.

The law regulates handover, acceptance, defects and their consequences according to the relevant contractual relationship.

The protocol is the instrument used to record that moment.

Under a contract for work, handover forms part of completion

The Czech Civil Code provides that work is performed when it is completed and handed over.

The customer accepts completed work either with reservations or without reservations.

In practice, the protocol may therefore be the document in which the customer states:

“Yes, I accept the Work, subject to these specific defects.”

or:

“Yes, I accept it without reservations.”

Or, alternatively, that the conditions for acceptance have not yet been satisfied at all.

In construction projects, not every minor defect allows refusal of acceptance

Czech law contains a specific rule for construction works.

The customer may not refuse acceptance merely because of isolated minor defects that, individually or together, do not prevent or materially restrict functional or aesthetic use of the construction.

That does not mean:

“Minor defects do not need to be recorded.”

Quite the opposite.

If the construction is accepted, apparent defects should be recorded specifically and the protocol should also deal with how and by when they will be remedied.

In a residential lease, the protocol primarily evidences condition

At the end of a lease, the tenant must return the apartment in the condition in which it was received, allowing for ordinary wear and tear and for defects for which the landlord is responsible.

The Czech Civil Code expressly recognises that if a written record describing the property was prepared when the tenant took possession, that record is relevant when the property is later returned.

In practice, the initial protocol answers:

“What condition was the apartment in before the tenant started using it?”

The exit protocol answers:

“In what condition is it actually being returned?”

Without the first, comparing the second becomes considerably harder.

Keys matter as well

Under Czech residential lease law, making the apartment available to the tenant is connected, among other things, with handing over the keys and ensuring that nothing prevents access and use.

At the end of the lease, the apartment is considered returned if the landlord receives the keys and nothing prevents access and use.

An entry such as:

“3 apartment keys, 2 building access chips and 1 mailbox key handed over”

is therefore not merely an inventory note.

It may help prove the actual moment of handover or return.

In a property sale, the protocol does not transfer title

The purchase agreement and the Handover Protocol perform different functions.

For real estate, the protocol will typically record:

• physical handover,

• keys,

• condition of the property,

• fixtures and equipment,

• meter readings,

• documentation,

• identified defects.

It does not replace the purchase agreement or registration of ownership in the Land Register.

It is therefore important not to confuse:

legal transfer of ownership

with

physical handover of the property.

In software projects, handover does not necessarily mean “we sent the ZIP file”

For technology projects, the handover process may be much more complex.

What may need to be delivered includes:

• the production version of the software,

• source code,

• documentation,

• administrator accounts,

• access credentials,

• repositories,

• API documentation,

• databases,

• configuration files,

• licences,

• test reports.

The contract may also provide for:

acceptance testing.

In that case, it is important to distinguish:

delivery → testing → acceptance → remedying defects → final acceptance.

One sentence stating that “the software has been handed over” may be far too vague for a larger project.

BIGGEST RISKS AND COMMON MISTAKES

❌ Mistake: preparing the Handover Protocol only on site without reviewing the main contract

Consequence

The protocol uses terminology that differs from the contract.

For example, the contract distinguishes between:

completion, handover, acceptance and remedying defects,

while the protocol simply states:

“The Customer has accepted the deliverable.”

It then becomes unclear what the signature actually meant.

Better approach

Draft the protocol as a document that directly follows the structure of the main contract.

❌ Mistake: pre-printed wording “without defects and reservations”

The property has a crack.

The software has three open bugs.

The renovation still lacks several finishing items.

Yet the receiving party signs a form stating:

“Accepted without defects or unfinished works.”

Consequence

This creates evidence directly contradicting what the receiving party may later want to argue.

Under a contract for work, the consequences concerning apparent defects may be even more significant.

Better approach

Record reality, not the template.

❌ Mistake: “There are defects” without describing them

Consequence

It later becomes unclear:

• which defect was identified at handover,

• how serious it was,

• whether it is the same defect later claimed.

Better approach

Describe the defect specifically.

Not:

“damaged floor”

but, for example:

“approximately 20 cm scratch in the wooden floor next to the balcony door in the living room”.

❌ Mistake: photographs exist, but nobody knows which protocol they belong to

Consequence

Six months later, there are hundreds of photographs on someone’s phone.

It is unclear:

• when they were taken,

• whether they show the condition at handover,

• whether the other party saw them.

Better approach

Identify and date the photographic documentation and expressly attach it to the protocol.

❌ Mistake: no deadline for remedying defects

The protocol lists ten defects.

The contractor confirms awareness of them.

But nowhere does it say:

when they will be remedied.

Consequence

The protocol records the problem but does not create a practical mechanism for resolving it.

Better approach

For outstanding defects, address:

• who will remedy them,

• by when,

• how remedy will be verified,

• whether a follow-up protocol will be prepared.

❌ Mistake: it is unclear whether the signature means acceptance or only participation in an inspection

The parties meet.

They prepare a list of defects.

The document is titled “Handover Protocol”.

But nowhere does it say whether the customer:

accepts the work

or

refuses to accept it.

Consequence

The document itself creates a dispute about what it was supposed to prove.

Better approach

State the outcome of the handover expressly.

❌ Mistake: nobody checks whether the person signing is authorised to make the statements in the protocol

A technician attends the construction site.

A project manager signs for one company.

A site manager signs for the other.

A dispute later arises over whether they were authorised:

• merely to confirm factual condition,

• to accept the work,

• to acknowledge defects,

• or even to amend contractual obligations.

Better approach

For important handovers, verify who is authorised to make the particular statements contained in the protocol.

HOW TO APPROACH IT – REALITY, NOT THEORY

1. Start with the main contract

Not with the Handover Protocol.

Check:

• when handover is supposed to take place,

• what must be handed over,

• how it must be handed over,

• who should participate,

• whether a protocol is mandatory,

• what legal effect its signature has,

• how the contract deals with defects,

• whether handover is linked to payment,

• whether a warranty or another period starts running from handover.

Only then can you draft a protocol that makes sense within the contract.

2. Identify the subject matter precisely

For an apartment, this may be simple.

For complex work, it is not.

It may not be enough to write:

“the Work under the Agreement has been handed over”.

Depending on the project, it may be necessary to identify:

• a specific stage,

• a particular part of the construction,

• a software version,

• serial number of equipment,

• documentation,

• accessories,

• data,

• licences,

• access credentials.

3. Record the actual condition

The protocol should not create a better version of reality.

It should record reality.

For a property, this may include:

• condition of individual rooms,

• defects,

• equipment,

• meters,

• keys,

• documentation.

For work:

• level of completion,

• test results,

• defects and unfinished items,

• documentation,

• deadlines for remedy.

For software:

• delivered version,

• functions,

• open bugs,

• test results,

• access details,

• documentation.

4. Distinguish defects, unfinished items and outstanding administrative tasks

Not everything left open is necessarily the same legal issue.

For example:

defect – completed performance does not comply with the contract,

unfinished item – part of the performance is still missing,

outstanding administrative task – for example, a required document has not yet been delivered.

It is useful to know what exactly the protocol is recording.

5. For each reservation, determine the next step

A list alone does not finish the process.

It may be useful to specify:

• the required remedy,

• responsible party,

• deadline,

• method of verification,

• any follow-up handover.

6. Record documents and access credentials handed over

Attention is often focused on the main item while everything surrounding it is forgotten.

But the following may be critical:

• manuals,

• inspection reports,

• certificates,

• service documentation,

• licences,

• passwords,

• access cards,

• keys,

• source code,

• backups,

• databases.

7. Before signing, review the wording of the final statement

Pay particular attention to wording such as:

“without reservations”

“without defects”

“properly completed”

“all obligations have been fulfilled”

“the parties have no further claims against each other”

Such wording may have a much broader effect than a simple statement:

“the receiving party received the keys today”.

PRACTICAL EXAMPLES

The following examples are illustrative.

👉 Apartment renovation is almost complete

The customer sees:

• unfinished silicone sealing in the bathroom,

• scratched doors,

• one non-functioning electrical socket.

The customer wants to start using the apartment.

The protocol contains the pre-printed statement:

“The Work is accepted without defects or unfinished works.”

The customer signs it because:

“We agreed orally that they would fix it.”

A month later, a dispute arises.

The protocol and oral understanding contradict each other.

It would have been much safer to list the defects specifically and set a remedy deadline.

👉 A tenant returns an apartment after five years

The landlord says the damaged kitchen worktop was new when the tenant moved in.

The tenant says it was already damaged.

The initial protocol states only:

“Apartment accepted in good condition.”

There is no photograph and no description of the kitchen.

The document exists, but it does little to resolve exactly the dispute it was supposed to prevent.

👉 A buyer takes possession of a house

Ownership has already been registered in the Land Register.

During physical handover, the buyer discovers damp in the basement.

The seller presents a protocol containing the statement:

“The Buyer accepts the Property without defects and has no reservations regarding its condition.”

Signing that statement is not the same as simply confirming:

“I received six keys today.”

The protocol should not mechanically deny reality just because the purchase agreement has already been signed.

👉 Software has been deployed, but acceptance has not yet taken place

The supplier deploys the system into production.

The customer starts using it.

But the contract provides:

delivery → acceptance tests → acceptance protocol → final payment.

Mere use of the system does not necessarily mean that the contractual milestone linked to successful acceptance has occurred.

That is why the protocol must reflect the mechanism agreed in the main contract.

👉 Only one party signs the protocol

The contractor prepares a Handover Protocol and signs it.

The customer refuses because of defects.

If the contract provides that handover occurs only through a protocol signed by both parties, a document signed only by the contractor may not satisfy that contractual requirement.

That may subsequently affect:

whether the Work was performed and whether the final price has become due.

WHY YOU SHOULD BE CAREFUL WITH “I’LL DO IT MYSELF”

A Handover Protocol looks like an ideal document for a universal template.

You only need fields for:

• transferring party,

• receiving party,

• date,

• condition,

• defects,

• signatures.

And for a simple handover, that may sometimes be enough.

The problem begins when the main contract says, for example:

“Entitlement to the final payment arises upon signing a Handover Protocol without defects or unfinished works.”

Or:

“The warranty period begins on the date of proper handover.”

Or:

“Software acceptance occurs upon signing the Acceptance Protocol.”

A generic protocol does not know:

• which contractual milestone it is supposed to confirm,

• whether acceptance with reservations is permitted,

• what should trigger invoicing,

• what the acceptance test covers,

• how defects are classified,

• whether signature starts the warranty period,

• whether the protocol also amends the main contract.

A Handover Protocol should therefore not be drafted in isolation. It should be the final link in a mechanism already created in the main contract.

LAWYER’S RECOMMENDATION + CHECKLIST

With a Handover Protocol, I would start with one question:

What exactly is signing this document supposed to confirm or trigger under the main contract?

Then I would check:

• whether the protocol correctly identifies the main contract,

• who is handing over and who is receiving,

• whether the signatories have sufficient authority,

• what exactly is being handed over,

• whether it is the entire performance or only part of it,

• the date and, where relevant, time of handover,

• the actual condition of the subject matter,

• all apparent defects and unfinished items,

• whether the defects are described with sufficient specificity,

• whether photographic documentation is attached and identified,

• how and when defects are to be remedied,

• who will confirm that they have been remedied,

• whether further testing or follow-up handover will take place,

• which documents have been delivered,

• which keys, chips or access devices have been delivered,

• meter readings and meter identification where relevant,

• delivered equipment and accessories,

• test results where relevant,

• whether acceptance is with or without reservations,

• whether the text contains broader declarations than intended,

• whether signature affects payment due dates,

• whether signature starts a warranty or another period,

• whether the protocol unintentionally amends the original contract,

• whether both parties have the same final version of the document and its attachments.

FAQ

What is a Handover Protocol?

A Handover Protocol is a document recording the handover and acceptance of property, real estate, work or another deliverable and usually also its condition at the time of handover.

Its exact legal significance depends on the main contract and on the wording of the protocol itself.

Is a Handover Protocol mandatory?

Not generally.

For many contracts, the law does not require a separate Handover Protocol in every case.

But if the parties agree on formal handover through a protocol, its signature may become critical to the contractual mechanism.

What should a Handover Protocol contain?

There is no single mandatory content applicable to all situations.

Typically, it should accurately record:

• the parties,

• the subject matter,

• the date,

• the condition,

• defects and reservations,

• delivered documents and accessories,

• the outcome of the handover,

• signatures.

Additional content depends on the type of performance and the main contract.

What does acceptance of work without reservations mean?

The customer confirms acceptance without raising reservations at that time.

For apparent defects, this may have significant consequences. If the customer accepts work without reservations, the court may under statutory conditions refuse to uphold a later claim relating to an apparent defect if the contractor raises late notification as a defence.

Can I accept work that has defects?

Yes. Czech law expressly recognises acceptance with reservations.

In construction contracts, the customer may also be unable to refuse acceptance merely because of isolated minor defects that do not prevent or materially restrict use.

The exact regime may also be influenced by the contract itself.

What if the other party refuses to sign the Handover Protocol?

It depends on the contractual handover mechanism.

If a protocol signed by both parties is a contractual condition of handover, the absence of a signature may be critical.

If the protocol serves only as evidence, the actual handover may still be capable of proof by other means.

Should photographs be included?

The law does not generally require photographs to be attached to every Handover Protocol.

For real estate, construction or other assets whose condition may later be disputed, photographs are highly useful evidence.

They should be clearly linked to the particular protocol and the date of handover.

Can the Handover Protocol amend the original contract?

Potentially, yes, if the document clearly shows an agreement to amend the contract and all applicable requirements for that amendment are satisfied.

The title “Handover Protocol” does not prevent the document from containing legally binding contractual changes.

But it is not advisable to hide an unintended contractual amendment inside what appears to be a purely technical handover record.