General
Lastenheft and Pflichtenheft: the difference — and what belongs in a good requirements specification for your product
Lastenheft and Pflichtenheft explained simply: who writes what, how DIN 69901-5 defines them, and what a verifiable requirements specification for a product looks like.

“Please send us your Lastenheft.” Anyone having a product developed for the first time can easily stall at this point. You have an idea, perhaps a sketch, but no document with that name. And shortly afterwards a second term often appears: the Pflichtenheft.
In this post I explain what distinguishes the two documents, who writes them, and what a Lastenheft for a technical product can look like, even if you have never written one.
The difference in one sentence
The Lastenheft describes what is needed and what for. The Pflichtenheft describes how and with what it will be implemented.
DIN 69901-5:2009-01 (Project management — Project management systems — Part 5: Concepts) defines both documents as follows (translated from the German wording):
Lastenheft: “the complete set of demands, specified by the client, on the deliveries and services of a contractor within an order”
Pflichtenheft: “the implementation specifications prepared by the contractor on the basis of implementing the Lastenheft specified by the client”
DIN 69901-5:2009-01, quoted from the REFA lexicon: Lastenheft and Pflichtenheft (retrieved 19 November 2026).
VDI guideline 2519 Part 1 (“Procedures for the compilation of tender and performance specifications”) describes the Pflichtenheft, according to REFA, correspondingly as a description of the realisation of all customer requirements demanded in the Lastenheft.
| Lastenheft | Pflichtenheft | |
|---|---|---|
| Question | What, and what for? | How, and with what? |
| Who writes it? | The client | The contractor |
| Content | Requirements, constraints, acceptance criteria | Solution path and implementation specifications for each requirement |
| Timing | before the enquiry or invitation to tender | after the Lastenheft, before implementation |
Why the terms so often get mixed up
In practice, Lastenheft, Pflichtenheft, Leistungsbeschreibung (service description) and Spezifikation (specification) are often not kept cleanly apart, or are even used as synonyms. On top of that come many other names such as requirements specification, requirements catalogue or functional specification.
This is more than a question of wording. If “what” and “how” are mixed in one document, it is often later unclear whether a solution was prescribed or only a goal. Misunderstandings between client and contractor arise from exactly that.
How the two documents work together
The usual sequence looks like this:
- The client writes the Lastenheft and sends it to one or more possible contractors.
- In a clarification phase the requirements are discussed, contradictions are resolved and points are, where needed, made more precise.
- The contractor prepares the Pflichtenheft. In it, one or more services can be assigned to each requirement from the Lastenheft.
- The client reviews and confirms the Pflichtenheft. Only then should the actual development begin.
Together with the quote, the documents often form the contractual basis. In a contract for work (Werkvertrag), the Lastenheft describes the verifiable services and deliveries against which acceptance is judged. How that is to be assessed legally in your case belongs in legal advice, not in this post.
A principle for the Lastenheft is: word requirements as generally as possible and as detailed as necessary. Anyone who already fixes the solution in the Lastenheft takes away the developer’s chance to find a better one.
What belongs in a Lastenheft for a technical product
There is no fixed outline. Typical contents are:
- Starting point: Which problem is to be solved? How is it solved today?
- Goal: What should the product do, and for whom?
- Functional requirements: What must it be able to do? Which load, which stroke, which operation?
- Non-functional requirements: for example reliability, usability, efficiency, changeability.
- Conditions of use: indoors or outdoors, temperature range, humidity, dust, operable with gloves?
- Interfaces: What is the product mounted on, what is it connected to?
- Scope of delivery: What exactly is to be handed over at the end: prototype, drawings, data?
- Acceptance criteria: How do both sides recognise that a requirement has been met?
For physical products it is worth including three points explicitly: the planned quantity, because it determines the manufacturing process; a target price per unit; and the temperature range. What happens if that is missing is in the post Thermal expansion in design.
Verifiable rather than vague
A good Lastenheft is short and verifiable. “Robust” is not a requirement. “Survives a drop from hip height onto concrete” is one. Three examples of how a wish list becomes requirements:
| Vague | Verifiable |
|---|---|
| robust | survives a drop from hip height onto concrete without loss of function |
| light | weighs at most 500 g |
| easy to assemble | can be assembled by one person without special tools in 10 minutes |
The figures in the right-hand column are examples. Which values are right for your product depends on the application. It also helps to mark each requirement as a must or a wish. Then, in case of conflicting goals, it is clear what may give way.
Lastenheft in English
There is no single fixed English equivalent. VDI 2519 Part 1 has the English title “Procedures for the compilation of tender and performance specifications”: Lastenheft is called “tender specification” there, Pflichtenheft “performance specification”. Also common are “requirements specification” for the Lastenheft and terms such as “functional specification” or “system specification” for the Pflichtenheft. In software engineering, the “Software Requirements Specification” according to IEEE often combines both documents. In an international project it is therefore worth defining in the contract which document contains what.
No Lastenheft? A normal starting point
If you do not yet have a Lastenheft, that is not a problem. At KANID the Lastenheft is the first result of phase 1, concept & feasibility. We clarify the problem, the application and the requirements: what must the product be able to do, for whom, under which conditions? After that I sketch solution paths and assess feasibility and risks.
Phase 1 costs 1,450 € incl. 19% VAT as a fixed price and takes about 3–4 weeks. You receive a Lastenheft, a solution concept with sketches, a parts list with sources of supply, a short report on risks and a binding fixed-price quote for phase 2. Phase 2 through to the pre-series prototype starts, as a guide, from about 5,000 € net plus VAT; the exact fixed price is set after phase 1. More under Services, the process step by step in the post From the idea to the product.
If you would like to prepare: on the Services page there is the free checklist “From the product idea to a prototype that can be manufactured”, with twelve questions, without giving an email address. The checklist is a German PDF. You do not have to be able to answer everything. Each open question is a point that the concept phase can settle.
In brief
What is the difference between a Lastenheft and a Pflichtenheft?
The Lastenheft describes what the client needs and what for. The Pflichtenheft describes how and with what the contractor will implement those requirements. DIN 69901-5 defines both documents accordingly.
Who writes the Lastenheft, and who writes the Pflichtenheft?
The client writes the Lastenheft, the contractor writes the Pflichtenheft on the basis of the Lastenheft. Ideally the client confirms the Pflichtenheft before implementation begins.
What belongs in a Lastenheft?
Typical contents are the starting point, the goal, functional and non-functional requirements, conditions of use, interfaces, scope of delivery and acceptance criteria. Each requirement should be worded so that it can be verified.
As an inventor, do I need a Lastenheft before I commission a developer?
It helps, but it is not a prerequisite. At KANID the Lastenheft is produced in phase 1, concept & feasibility, at a fixed price of 1,450 € incl. 19% VAT.
What is Lastenheft called in English?
There is no single fixed equivalent. VDI 2519 Part 1 uses “tender specification” for the Lastenheft and “performance specification” for the Pflichtenheft. Also common are “requirements specification” for the Lastenheft and “functional specification” or “system specification” for the Pflichtenheft.
Sources
All retrieved on 19 November 2026.
- REFA lexicon: Lastenheft and Pflichtenheft (definitions according to DIN 69901-5:2009-01, VDI 2519 Part 1, contract for work and acceptance)
- DIN Media: DIN 69901-5:2009-01, Project management — Project management systems — Part 5: Concepts
- VDI: VDI 2519 Blatt 1, Vorgehensweise bei der Erstellung von Lasten-/Pflichtenheften (English title)
- Wikipedia: Lastenheft and Pflichtenheft (process, typical outline, variety of terms, English designations)
Lastenheft Pflichtenheft differenceLastenheftPflichtenheftLastenheft product developmentLastenheft contentsLastenheft in Englishproduct development
