Skip to main content

From burden to duty


The terms specification sheet and requirement specification are often not clearly distinguished from each other in common parlance. This can lead to irritations, especially in the delicate tendering and planning phase. The result: avoidable misunderstandings, project delays and budget overruns.

By definition, the client specifies in the specifications what is expected from the solution, in this case the ERP software. The requirement specification is thus a kind of "wish list" with specific, but usually more general requirements for the later solution. It is where the current and future requirements are summarized. The question "What is to be achieved?" is the central point.

The contractor's specifications, on the other hand, represent something like the answer to the specifications. The question "How can the objectives be achieved?" is summarized with concrete, technical solutions and proposals for the client. In doing so, the contractor either includes or excludes concrete cases and situations in the overall concept in order to form a measurable basis for further action.

Understanding the difference between specifications and requirements is essential for the entire project communication and affects all dimensions of cooperation, from contract conclusion to budgeting and project management. The clear separation of terms is not only the basis for a smooth project without misunderstandings, but also opens up opportunities for optimizing the project in the concept phase.

In the run-up to a cooperation (e.g. for tenders) we would be pleased to provide you with the most important content points for the requirement and functional specifications in connection with ERP solutions.

Scroll to top