The Handover Report at Project End: Acceptance Without Disputes

Why do disputes arise precisely at project end?

At the end of a project, two interests collide. The company wants to issue the final invoice and move the team to the next order. The customer wants to be sure they get what they pay for and now has the strongest leverage, because the money is still with them. At this moment, open points that nobody raised during the project suddenly become important.

Without an orderly handover, a gray zone arises. The company considers the project finished; the customer does not. Invoices go unpaid, rework is done without an order, and the relationship suffers exactly when a follow-up order would be possible. This leads to the guiding question of this guide: How does a small company design acceptance and the handover report so that a project ends without disputes and both sides know where they stand?

To answer it, we first clarify what acceptance does legally and distinguish it from the handover report. Then we introduce the expectation-confirmation model as a thinking model, weigh whether a formal report strengthens or weakens trust, and describe a nine-field report and the handover process. This article is not legal advice.

A project is not finished when the work is done but when both sides have put that in writing.

What does acceptance do, and what is a handover report?

Under a contract for work in German law, that is, when a company owes a specific result such as an installation, a renovation, or software, acceptance is a central step. It is the customer’s declaration that they approve the work as essentially compliant with the contract (Section 640 of the German Civil Code, BGB). The customer may not refuse it because of insignificant defects. With acceptance, payment falls due under Section 641 BGB, the limitation period for defect claims begins under Section 634a BGB, and according to established case law, it is generally the customer who must then prove that a defect exists.

Two rules are particularly important in practice. If the company sets a reasonable deadline for acceptance after completion and the customer does not refuse it by naming at least one defect, the work is deemed accepted under Section 640(2) BGB. And if the customer accepts the work despite knowing of a defect, they lose certain rights regarding that defect unless they reserve them at acceptance (Section 640(3) BGB). A sales contract has no acceptance in this sense. Between merchants, the duty to inspect goods and report defects without delay applies there instead (Section 377 of the German Commercial Code, HGB).

The handover report is the document in which the handover and acceptance are recorded: what was checked, which defects remain and by when they will be fixed, which documents and access credentials were handed over, and whether the customer accepts, with or without reservation. It is not required by law, but it turns a declaration people can argue about later into a signature.

The thinking model: expectation and confirmation

In 1980, the marketing researcher Richard Oliver explained with a simple model why customers are satisfied or dissatisfied with the same result (Oliver 1980). According to it, satisfaction arises from two quantities: the expectation with which someone approaches a service, and the confirmation or disconfirmation of that expectation, that is, whether the service exceeds, meets, or falls short of it. Oliver supported the model with a two-stage field study in which he measured expectations before and satisfaction after a flu vaccination.

One detail makes the model especially useful for projects. Oliver describes the expectation as a kind of reference point against which everything later is measured. It is shaped by the product itself and previous experience, by the context, explicitly including what salespeople say, and by the person themselves. Whoever says “we’ll include all of that” in a sales conversation sets a reference point against which acceptance will later be measured.

For the end of a project, it follows that disputes at acceptance are usually not a problem of acceptance but an expectation violation laid down at the start. As with handing back an apartment when moving out, the move-in report decides whether the scratch in the parquet is a new defect or an old one. In a project, the order confirmation and the kickoff take on this role. The guide to the order confirmation explains why contracts always remain incomplete according to Williamson’s (1985) transaction cost theory, and the guide to the project kickoff describes how success criteria and the item “not included” are set at the start.

What is known about project closeout

Project research considers the closeout phase difficult and little studied. Using the example of a large construction company in Iran, Mirzaee and Martek (2025) describe it as particularly prone to conflict: several issues come together, including possibly unfulfilled contractual obligations, claims and counterclaims, and relationships between the parties deteriorate as a result. This leads to poorer outcomes, especially where there is no structured handling of claims. The case comes from a different scale and industry, but the pattern carries over to small projects.

For small companies, an idea from project controlling is important. Scope creep arises where agreements are not recorded, as the guide to project controlling for small businesses shows. The remedy is a change log during the project. At the end, it serves as the basis for acceptance: whatever is on the log was agreed and is part of the inspection scope; whatever is not on it was not agreed.

The end of a project is also the best moment to learn. Structured debriefs improve performance by about 25 percent on average, as the meta-analysis by Tannenbaum and Cerasoli (2013) across 46 samples shows. The handover to the customer and the internal review are, however, two separate meetings, as the guide to project closure and lessons learned describes.

Distrust or protection? Two perspectives on the report

The first view says: a formal report with signatures looks like distrust. With regular customers you have worked with for years, it disturbs the relationship. A handshake and a short email are enough. This view has a true core, because tone and timing determine how a report is received.

The second view says: the report protects both sides. The customer gets a list of open points with deadlines and the assurance that defects are taken seriously. The company gets clarity about when payment is due and what counts as done. Without a report, one memory stands against another.

I consider the second view right, especially in good relationships. A report harms a relationship only if it comes as a surprise. Whoever explains in the kickoff how the handover will work and sets up the report as a joint inspection rather than a form to sign strengthens trust. Transparency at the end is the continuation of transparency at the start.

The handover report: nine fields

Field 5 determines what happens next. Each defect is described so that a third party could find it again, ideally with a photo. The rating as significant or insignificant should be made jointly, because it bears on whether acceptance may be refused. In case of disagreement, this is noted in the report rather than left open.

How does a handover without disputes work?

1. Internal pre-inspection

   One or two days before the meeting, someone from the team who did not work on the project checks the result against the success criteria. Whatever they find is fixed before the customer meeting or prepared as an open point.

2. Announce the meeting in good time

   The customer receives the date, the process, and the prepared report two weeks in advance. That way they know who from their side should attend and sign.

3. Inspect together

   Company and customer go through the work together using fields 3 and 4. Each defect is entered in field 5 immediately.

4. Sign on site

   At the end of the meeting, both sides sign the report, and each receives a copy. Whoever does not want to accept names in the report the defects that speak against it.

5. Fix and confirm defects

   Each fixed defect is checked off with a date and briefly confirmed to the customer. Once all points are done, the final invoice follows with a reference to the report.

If a customer declines the meeting or lets it pass, the rule from Section 640(2) BGB comes into play: a reasonable deadline for acceptance, set in writing, creates clarity. Whether and how this works in an individual case, for example with consumers who must receive specific notice, is something to clarify with your legal advisor.

What follows beyond the single project

A good handover is the start of the next phase of the customer relationship. Customers remember the end of a project more strongly than the middle. Whoever hands over clearly, completely, and reliably at the end creates the best starting point for maintenance, extensions, and referrals, as the guide to growing existing customers describes.

The report is also a mirror of one’s own work. Whoever lays the defect lists of several projects side by side sees which types of errors keep recurring and can fix them in checklists and templates. Defects that appear after acceptance go through the process described in the guide to handling complaints.

The limits are clear. The legal rules on acceptance apply to contracts for work, not to every order, and they are complex in detail, for example for construction contracts or consumers. Research on project closeout is thin and comes mostly from large projects. And no report repairs an expectation that was set wrongly at the start.

Conclusion: how does a project end without disputes?

The question was
a small company designs acceptance and the handover report so that a project ends without disputes. The answer has two parts. The first lies at the start: according to the expectation-confirmation model, satisfaction is measured against the expectation, and that arises in sales, in the order confirmation, and in the kickoff. Whoever records success criteria and the limits of scope there has a yardstick at the end.

The second part is the handover itself: a prepared nine-field report, a joint inspection, a defect list with deadlines, and signatures on site. Acceptance is more than a formality, because it makes payment due and starts deadlines running. The sober observation is: disputes at project end are rarely about the work and almost always about what was agreed.

How to get started

1. Take the project that ends next and set up the handover report with the nine fields.
2. Pre-fill fields 1 to 3 and 7 from the order confirmation, change log, and project documents.
3. Announce the handover meeting with process and report to the customer two weeks in advance.
4. Plan an internal pre-inspection by someone who did not work on the project.
5. Add the handover process to your kickoff template so that customers know it from the start.