Requirements spec and functional spec templates for Word, free
Six templates as Word files (.docx), free and with no sign-up: a requirements specification (German: Lastenheft), a functional specification (German: Pflichtenheft), a checklist for reviewing the requirements spec, ten questions for the first call, a test case and an indicative quote. Grey notes in every section say what belongs there. The functional spec template also uses sample sentences to show how precise it should be.
Step by step
Which template helps when.
The client writes the requirements spec, the service provider writes the functional spec. Both sides need the checklist and the test case. If you are learning about the topic and just want to see the structure, the functional spec template with its sample sentences is the best place to start.
You are the client
- You describe what you need.Requirements spec
- You check it before sending it to providers.Checklist
- You accept the finished result.Test case
You are the service provider
- You have the first call with the client.Ten questions
- The requirements spec arrives and you check how solid it is.Checklist
- The client wants a price before everything is clear.Indicative quote
- Once you have won the contract, you clarify the gaps and write down what you will deliver.Functional spec
- You define what acceptance is measured against.Test case
To take away
Six templates, no sign-up.
Each template opens in Word and in other common programs that read .docx. There is space for your logo at the top; a small line at the bottom says where the template comes from.
-
Requirements specification
Work through the sections from top to bottom and delete the grey notes. In the table, add for every requirement how you will know it is met, and give quantities. Check the result against the checklist before you send it.
Word (.docx) -
Functional specification
First break the requirements spec down into epics (big themes) and work packages (parts with a testable result that get estimated) and enter them in the table in the scope section. Clarify the gaps with the client and give each package a status: firm, based on assumptions, range or open. The grey sample sentences from the fictional case in the book (the insurance group Auenhof commissions the service provider Hanselink to build a broker portal) show how precise it should be. Delete them afterwards.
Word (.docx) -
Checklist: is the requirements spec solid enough?
Go through the ten questions with the requirements spec next to you and tick yes or no. Every no goes into the quote as an assumption, or into the indicative quote as an open item. Clients use the same list before they send out their requirements spec.
Word (.docx) -
Ten questions for the first call
Print the questions or keep the file open next to the video call. Write the answers into the boxes while the client is talking. Whatever stays open goes into the table at the end, with who will clarify it and by when.
Word (.docx) -
Test case
Write test cases for every work package, ideally in the functional spec itself. Each step describes exactly one action, so that someone without prior knowledge can run the test. At acceptance, tick one of three results: passed, passed with limitations or failed.
Word (.docx) -
Indicative quote
Enter the epics as items and give each one a status. Show the total of the firm items and the total including ranges separately. Adapt the cover letter to your needs. The withdrawal clause in it is an example, not legal advice. Agree the wording with your lawyer.
Word (.docx)
The templates follow chapters 5 to 10, chapter 20 and appendix A of the book “Projects that pay off.” The Auenhof case is fictional. About the book →

Frequently asked questions
What people often ask.
Is there a requirements spec template for Excel?
No, the templates are only available as Word files. But you can select the table of functional requirements in the requirements spec template, copy it and paste it into Excel. Columns and rows are kept, so you can sort and filter there. A table is a good place to start anyway, and the specialist literature recommends it: every requirement gets its own row with fixed columns, such as number, requirement, acceptance criterion, quantity and priority. That forces more structure than running text.
Do I need two separate documents for a small project?
Not necessarily. Christof Ebert recommends that smaller companies in particular let the requirements spec, the functional spec and the test cases grow as one document, with separate chapters and an owner for each. Misunderstandings come to light early, and less gets built that nobody needs. With our templates, that means placing the sections of the functional spec template and the test cases after the requirements spec template, and noting which side writes which chapter.
What should I add to the templates?
A glossary. Specialist literature recommends recording in one place, from the start, what technical terms, abbreviations and everyday words with a special meaning stand for in the project, agreed with the client and kept up to date until the end. In the broker portal example, “company” would be such a word: if the glossary says it means every firm in the group, including the subsidiaries in Austria and Switzerland, nobody reads anything else into it.
May I change the templates and pass them on?
Yes, that is what they are for. You may use, adapt and pass on the templates free of charge, including for client projects. Add your logo and adapt the sections to your projects. We are pleased if the small note in the footer stays. The templates are working aids without any warranty and are not legal advice. Agree anything that is meant to be contractually binding with your lawyer.
Is there a DIN template for requirements specs and functional specs?
There is no mandatory DIN template. The German standard DIN 69901-5:2009 (project management, project management systems, part 5: terms) defines Lastenheft and Pflichtenheft, but it does not prescribe an outline to fill in. For automation projects, the guideline VDI/VDE 3694 covers both documents in more detail. Our templates follow the structure from the book “Projects that pay off.” They are not a standard template.
Do the templates cost anything?
No. You download them without signing up and without giving an email address.
What is the difference between the two spec templates?
The requirements spec template is for the client: it asks for goals, requirements and constraints, in other words the what. The functional spec template is for the service provider: it breaks the work down into epics and work packages and has sections for exclusions, assumptions, client responsibilities and acceptance, in other words the how. More on the difference
Are the templates available as PDF?
For filling in, they are only available as Word files. If you want to send a completed template, save it as a PDF from Word.
Read on
Where to go next.
Next step
Got a requirements spec from a client? Turn it into a functional spec.
Upload the requirements spec and answer ten questions at most, only the ones that change the effort. You get a structured draft functional spec with your logo, as Word and PDF. Anything still unclear is marked as open. You estimate the hours yourself.
- Freeno account, email address optional
- 10 questions at mosteverything else is marked as open in the spec
- Word and PDFwith your logo and colour
