Whitepaper
Requirements & functional specification template
No more blank page: this template gives you the complete structure for a Lastenheft (requirements specification) and Pflichtenheft (functional specification) – as a fillable Word document with a requirements table, must/should/could prioritisation and acceptance criteria. Describe your software project precisely enough that vendors can quote realistically and comparably.
Get the template now
Leave your details and you’ll get the template straight away as a Word document.
What you'll take away
A complete structure instead of a blank page
Every chapter from starting situation through requirements to acceptance criteria, pre-structured, with guidance notes and sample wording.
Requirements table with prioritisation
Capture functional and non-functional requirements properly and prioritise them as must/should/could: the basis for comparable quotes.
Both documents covered
The template explains the difference and covers both: what you need (requirements specification) and how it will be implemented (functional specification).
Ready to use as a Word document
Download, fill in, hand over to vendors: the template arrives in your inbox as a .docx file.
What Requirements specification template (Lastenheft & Pflichtenheft) is about
What this is about
Without a requirements specification, every quote is a gamble
If you put a software project out to tender without describing the requirements properly, you get quotes that cannot be compared – and you pay for the vagueness later through change requests. The Lastenheft (requirements specification) describes what you need and why; the Pflichtenheft (functional specification) answers how the vendor will implement it. Together, both documents are the basis for realistic budgets, reliable schedules and a clean acceptance.
Part A (requirements specification) walks you through every chapter: starting point, goals and non-goals, current processes and systems, user roles, functional and non-functional requirements with must/should/could prioritisation, interfaces, data protection, constraints and acceptance criteria. Part B (functional specification) gives your vendor the structure for their answer: solution concept per requirement, architecture, data migration, milestones, testing and acceptance, operations and SLA, change requests. On top of that you get a checklist to run through before sending and a mini glossary. Each chapter includes guidance notes and example rows that show you the level to aim for.
What to expect
A fillable Word document with a prepared requirements table, prioritisation columns and sample texts – written from more than ten years of practice in custom software development. It lets you talk to any vendor on equal terms, whether you build with us or elsewhere.