Most disputes in external software delivery do not start with bad code. They start with a Leistungsbeschreibung that describes activities instead of results, leaves scope boundaries implicit and says nothing about how acceptance works. Such a document satisfies procurement but fails engineering, because nobody can decide on its basis whether a sprint was delivered. The fix is a sprint-level Leistungsbeschreibung with a fixed structure: objective, scope, explicit exclusions, testable acceptance criteria, cooperation duties of the client and a change procedure. This guide sets out that structure, with phrasing patterns that work for engineers and stand up when the contract is read by a lawyer.
The numbers: why scope documents matter more now
More software is being delivered by external teams and with AI assistance, which raises the value of a precise scope. The pressure to externalise is structural: Bitkom counted around 79,000 unfilled IT positions in Germany in 2026, after 109,000 in 2025 and 149,000 in 2023, and its 2025 survey found an average of 7.7 months to fill an IT vacancy. The way code is produced is changing too. Google's DORA 2025 report found that 90% of technology professionals use AI at work and concluded that AI amplifies whatever system it meets, good or bad. Stack Overflow's 2025 Developer Survey of more than 49,000 developers reported that 46% do not trust the accuracy of AI output and 45% find debugging AI-generated code time-consuming. When output is faster and less predictable, a Leistungsbeschreibung with testable acceptance criteria is the control that keeps both sides aligned.
Why the Leistungsbeschreibung carries so much weight
Under a Werkvertrag (BGB §631), the contractor owes a result, not effort. Payment generally becomes due on acceptance (BGB §641), and acceptance (BGB §640) is assessed against what was agreed. If the agreed result is vague, every one of these mechanisms becomes contestable. Under a Dienstvertrag (BGB §611), the provider owes a service rather than a result, but a precise description of the service, its scope and its deliverables is just as important for steering the engagement.
There is a second reason. A Leistungsbeschreibung that describes the work as tasks to be performed according to the client's day-to-day instructions can, together with how the engagement is lived, point toward Arbeitnehmerüberlassung under §1 Abs. 1 Satz 3 AÜG. A description of defined results that the provider organises and delivers on its own responsibility points the other way. The document alone does not decide the classification, because the actual practice matters, but it sets the frame for that practice.
The two layers: framework and sprint
A workable setup separates two layers. The framework agreement fixes what does not change every two weeks: contract type, fees, liability, rights of use, data protection, the acceptance procedure and the change procedure. The sprint-level Leistungsbeschreibung is a short, structured document, typically two to four pages, that defines the concrete result of one sprint or one release increment. It references the framework and does not repeat it.
This separation keeps the legal text stable and the delivery text current. It also means that the people who write sprint documents are the people who understand the system, not the people who negotiate liability caps.
A seven-part structure for each sprint
- Objective. One or two sentences on the business purpose of the increment. Engineers make better trade-offs when they know why something is needed.
- Scope. The items to be delivered, each with an identifier that matches the issue tracker, so that the document and the backlog cannot drift apart.
- Explicit exclusions. What is deliberately not part of this sprint. This is the section most often missing and most often argued about later.
- Acceptance criteria. Per item, testable statements that a third person can verify. See the patterns below.
- Non-functional requirements. Performance, security, compatibility, documentation and test coverage expectations that apply to the increment.
- Cooperation duties of the client. Inputs, decisions, access and test data the client must provide, with dates.
- Delivery and acceptance. Delivery form (merged to a named branch, deployed to staging, tagged release), demo date, acceptance window and the person authorised to accept.
Acceptance criteria: patterns that work
Acceptance criteria are the core of the document. They must be specific enough to verify and stable enough not to change during the sprint. The given, when, then format from behaviour-driven development works well because it forces a precondition, an action and an observable outcome.
| Weak phrasing | Deliverable phrasing |
|---|---|
| Improve the performance of the search. | Given the staging dataset, when a user submits a search with up to three filters, then the API returns results within the agreed latency threshold for 95 percent of requests in the load test defined in the test plan. |
| Support for SSO. | Users of the client's identity provider can log in via OIDC. Local accounts remain available for administrators. Logout terminates the session in the application. |
| Refactor the export module. | The export module is split into the components listed in ADR 014. All existing export tests pass unchanged. No change to the public API. |
| Write documentation. | README covers local setup, configuration variables and deployment. A new team member can complete setup by following it without additional help. |
A useful test for every criterion: could two engineers who did not write it disagree about whether it is met? If yes, rewrite it.
Cooperation duties are part of the scope
Software delivery depends on input from the client: access, test data, decisions on open design questions, feedback on drafts. Under the Werkvertrag, BGB §642 addresses the case in which the client fails to provide necessary cooperation, and the contractor may then be entitled to reasonable compensation. In practice, the more important effect is operational. When cooperation duties are written down with dates, a delay becomes visible and attributable, instead of turning into a silent slip in the sprint.
- Access to repositories, environments and tools by a named date.
- Representative, anonymised or synthetic test data where personal data would otherwise be needed.
- Decisions on listed open questions by a named date.
- Availability of the accepting person for the demo and acceptance window.
Change control without bureaucracy
Requirements change. A good Leistungsbeschreibung does not try to prevent that but defines how change is handled. A lightweight pattern: changes requested during a sprint are recorded as change requests with a short impact note (effort, affected items, risk). The client decides whether the change replaces an existing item of similar size, moves to the next sprint, or extends the current scope under the framework's commercial terms. What should not happen is a change that is agreed verbally in a call and never written down. That is how scope disputes begin.
A checklist before you sign off a sprint document
- Does every scope item have a tracker identifier and at least one testable acceptance criterion?
- Are exclusions explicit?
- Are non-functional requirements stated, or explicitly referenced from the framework?
- Are client cooperation duties listed with dates and owners?
- Is the delivery form defined, including the target branch or environment?
- Is the person authorised to accept named, along with the acceptance window?
- Does the document describe results the provider organises itself, rather than tasks assigned to individual engineers?
Whichever provider you work with, insisting on this structure is the cheapest form of dispute prevention available.
This article is general information, not legal advice.
A Werkvertrag succeeds or fails on the quality of its Leistungsbeschreibung. In niogod™ engagements, the Projektleiter drafts each sprint document together with your product owner, and the Senior Consultant checks every acceptance criterion for testability before the sprint begins. If sprint-based external delivery is part of your plan for next year, it is a conversation worth having early.
Talk to niogod™
Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.
Book consultation