even
← Back to glossary

Lastenheft

Also: Anforderungskatalog, Anforderungsdokument, Anforderungsspezifikation, LH, Requirements Specification, User Requirements Specification, URS

AI-generated

In brief

A requirements specification (Lastenheft) describes all of a client's requirements for a planned system or project from their perspective. It forms the binding basis for tendering, comparison of bids, and subsequent contract negotiations.

Key facts

What is a Requirements Specification (Lastenheft)?

The requirements specification is a structured document in which a client — such as a warehouse manager or IT department — describes their requirements for a system, facility, or service to be procured in a complete and comprehensible manner. It addresses the what level: What should the future system do, which processes must it support, and what conditions apply? The answer to the how question is provided by the vendor in the functional specification (Pflichtenheft).

In intralogistics, a requirements specification typically covers the following content:

  • Project objectives and strategic context
  • Description of existing and planned processes
  • Volume frameworks: throughput rates, number of SKUs, storage capacities, order peaks
  • Functional requirements for control systems, interfaces, and data exchange
  • Quality, availability, and safety requirements
  • Compliance and operational requirements
  • Acceptance criteria and verification obligations

How does a requirements specification work in practice?

The requirements specification is created before the tendering process begins and is typically developed in an interdisciplinary manner: logistics planning provides the process requirements, IT defines interface standards and system boundaries, and procurement adds commercial framework conditions and compliance requirements. The more concretely and measurably the requirements are formulated, the better bids can be compared and subsequent acceptance tests conducted.

A key aspect is the distinction between mandatory and optional requirements. Mandatory requirements are non-negotiable and feed directly into the evaluation matrix. Optional requirements signal wishes that can be addressed on an optional basis in the bid. This prioritization prevents projects from becoming unmanageable due to extensive special requests.

What matters when creating a requirements specification?

Completeness and measurability are the most important quality criteria. Vague formulations such as "high availability"

Frequently asked questions

The requirements specification describes what the system should do and comes from the client. The functional specification describes how the vendor intends to implement these requirements. Both documents complement each other and together form the contractual basis.

Related terms

Matching categories