Skip to content

Cookie Settings

We use necessary cookies and Google reCAPTCHA to protect our forms from spam. You can find details in our privacy policy.

Privacy Policy
FragonStudios

By Danijel Balog, Founder, Fragon Studios · Last updated: 2026-11-13

Template for a software requirements document (Lastenheft)

Updated: By Danijel Balog, founder of Fragon Studios in Linz

The template as a Word file, an outline with guiding questions, a filled-in example, and how a vague requirement becomes a testable one.

  1. Starting point and goal

    What is the problem today, and what should be different after the project?

  2. Users and roles

    Who works with the software, and who may see, change and approve what?

  3. Current processes

    How does the process work today, and where do errors occur?

  4. Functional requirements

    What must the software do, as a must, should or could?

  5. Data and interfaces

    Which data, and which systems does the software exchange it with?

  6. Quality requirements

    Which devices, how many users at the same time, offline as well?

  7. Data protection and hosting

    Which data is personal, and where may the servers be located?

  8. Constraints

    What budget, what deadline, is funding planned?

  9. Acceptance and success criteria

    When is a requirement met, and who signs it off?

  10. Operation and further development

    Who runs the software after go-live?

In short

  1. The template is available as a Word file, free and without sign-up (in German). It has ten sections, from the starting point to operation.
  2. The client writes the requirements document. It says what the software should do and why. The contractor writes the functional specification (Pflichtenheft). It says how.
  3. Describe problems and goals, not finished solutions, and write every requirement so that someone can check whether it is met.
  4. A requirements document is what makes quotes from different providers comparable. With us it also works without one: a workshop from €1,500 then takes its place.
  5. With us, the requirements document is followed by an analysis of two to ten days at a day rate of €1,100, then a written quote, usually at a fixed price.

What is a requirements document, and how is it different from a functional specification?

The requirements document describes, from the client's point of view, what the software should do and why. The functional specification describes, from the contractor's point of view, how this will be implemented.

Written by the client

Requirements document

  • What, and what for?
  • goals, processes, requirements, constraints
  • before you approach a service provider
  • to get comparable quotes
Written by the contractor

Functional specification

  • How, and with what?
  • technical solution, architecture, interfaces in detail
  • after the analysis, before implementation
  • basis for implementation and acceptance, often part of the contract

A good requirements document describes problems and goals, not finished solutions.

“We need an app” is a solution. “Our technicians record jobs on paper and type them up in the evening” is a problem a service provider can work with.

There is no prescribed form.

Both terms are defined in the standard DIN 69901-5, and the guideline VDI 2519 Part 1 describes how to draw up a requirements document. Both terms are common in Austria and Germany. In agile projects people tend to speak of requirements or a backlog. The idea stays the same: first clarify what is needed, then talk about technology.

How is a software requirements document structured?

In ten sections, from the starting point to operation. Adopt the outline and answer the guiding questions in full sentences.

Template to fill in

Download the template as a Word file (.docx, free, no sign-up). The file is in German. It contains the same sections and guiding questions as the table.

The ten sections with all guiding questions.
SectionGuiding questions
1. Starting point and goalWhat is the problem today? What should be different after the project? How will you know in a year that it was worth it? Which off-the-shelf solutions have you looked at, and why do they not fit?
2. Users and rolesWho works with the software, for example employees, customers, partners? How many people per role? Who may see, change and approve what?
3. Current processesHow does the process work today, step by step? Where do double entry, waiting times or errors occur? Which Excel lists, forms or emails are involved?
4. Functional requirementsWhat must the software do? Classify each requirement as a must, should or could. What is explicitly not included?
5. Data and interfacesWhich data is processed, and where does it come from? Which systems must the software exchange data with, for example ERP, accounting or Microsoft 365? Is there existing data that will be migrated?
6. Quality requirementsWhich devices and browsers must it run on? Does it have to work offline? How many users at the same time? Are there accessibility requirements?
7. Data protection and hostingIs personal or particularly sensitive data processed? Where may the servers be located? Are there internal requirements from IT or the data protection officer?
8. ConstraintsRoughly what budget is available? Is there a fixed deadline, and why? Is funding planned that sets deadlines or content? What is funded in Upper Austria is covered in the guide Funding for software projects in Upper Austria.
9. Acceptance and success criteriaWhen is a requirement considered met? Who signs it off? With which test cases or real sample data?
10. Operation and further developmentWho runs the software after go-live? Who takes care of updates and bugs? Who should own the source code and the access credentials?

The question in section 1 about the off-the-shelf solutions you have looked at pays off when you apply for funding. DIGITAL.PLUS 26 in Upper Austria only funded custom software if its advantage over existing solutions was set out convincingly. According to the programme page, applications closed on 2 November 2026.

Incomplete is better than nothing

Leave questions you cannot answer open and mark them. We clarify open points in the analysis. An honest “we don't know yet” helps more than a guessed answer.

What does a filled-in requirements document look like?

Much like this shortened example from an installation company that wants to move its jobs from paper to the phone. It fits on two pages and still answers every guiding question.

A service provider rarely needs more for a first estimate.

An installation company with 12 technicians: fictional, not a client project, all numbers invented.
Fictional example, not a client project. All numbers are invented.
SectionExample text
1. Starting point and goalOur 12 technicians write up jobs on paper, and the office types them into the ERP in the evening. The goal is to invoice no later than the day after the job. We tested two off-the-shelf apps for tradespeople, and neither connects to our ERP.
2. Users and roles12 technicians record jobs and see only their own. 2 people in the office plan and check. Management sees reports.
3. Current processesThe office plans by phone and with an Excel list. Technicians fill in a paper form. Errors come from illegible material details and forgotten working hours.
4. Functional requirementsA must is the job record with working time, material, photos and customer signature. A should is the daily schedule on the phone, a could is the report by email to the customer. Stock management is not in scope.
5. Data and interfacesCustomers and items come from the ERP, and completed jobs go back to it. Around 4,000 existing customers are migrated.
6. Quality requirementsAndroid company phones, usable with work gloves on, recording without signal in the basement, up to 15 users at the same time.
7. Data protection and hostingCustomer data and signatures are personal data. Servers in the EU, data processing agreement (DPA) under Art. 28 GDPR.
8. ConstraintsBudget range €30,000 to €40,000 net. In use before the main season in March, because after that we have no time for training.
9. Acceptance and success criteriaMet when three technicians record all their jobs only in the app for a week and the office no longer types anything up. The office manager carries out acceptance with 20 real jobs from the previous month.
10. Operation and further developmentThe service provider runs the software, and updates come through a maintenance contract. Source code and access credentials belong to us.

How do you write good requirements?

Testable and from the users' point of view. A good requirement says who can do what, and how you can tell that it works.

Examples for orientation. The values on the right are placeholders; put in your own.
VagueTestable
The software should be user-friendly.After one training session, a new field service employee creates a job without help.
The software should be fast.The job list loads in under two seconds on a company phone on the mobile network.
Connection to our ERP.New customers from the ERP appear in the portal after 15 minutes at the latest, and changes in the portal flow back.
Customers should see invoices.Logged-in customers see their invoices from the last three years and download them as PDFs.
It should also work offline.Technicians record jobs without signal, and the data is transferred automatically the next time there is reception.
Secure and GDPR-compliant.Servers in the EU, data processing agreement under Art. 28 GDPR, access by role only.

The test for each row is whether an outsider could say without doubt after the project that it has been met. If not, a number, a role or an example is missing.

How long should a requirements document be?

Short enough that someone reads all of it, and long enough that all ten sections are answered. There is no required length.

For an internal tool that replaces Excel for a team, a few pages are often enough. A customer portal with several roles and an ERP connection needs more, especially on interfaces and acceptance.

Most of the extra length comes from proposed solutions, screen sketches down to the last detail or copied boilerplate. These are the parts you can most easily cut. Sketches are still welcome when they explain a process.

What are the most common mistakes in a requirements document?

The most common mistake is describing a solution instead of a problem. Missing acceptance criteria come right after.

  • prescribing technology before the problem is clear
  • every requirement classed as a must
  • interfaces to existing systems forgotten
  • data protection only considered after the quote
  • no acceptance criteria
  • only management asked, not the people who will use the software
  • boilerplate copied from someone else's project

How do we work with your requirements document?

We use it as the basis for an analysis that translates your requirements into effort. After that you get a written quote, usually at a fixed price.

  • 1 working dayuntil you have a price and time range. In the no-obligation 30-minute initial consultation we go through the requirements document with you and ask follow-up questions.
  • 2-10 daysis how long the analysis takes, at a day rate of €1,100, so €2,200 to €11,000 net.
  • €5,000Below this, we do not take on custom software or apps.

In the analysis we clarify open points, check interfaces and put in writing what will be built. The quote is a fixed price for the agreed scope. If the work is genuinely open, we say so and bill by effort, with a cap on the number of weeks.

It also works without a requirements document. Then a workshop from €1,500 takes its place, or a feasibility analysis from €3,000 if there are bigger question marks. After that comes the analysis as above.

You can send us your requirements document in advance, by email to office@fragonstudios.com. What projects of different sizes cost is shown in the guide What software costs in Austria.

Frequently asked questions

Do I need a requirements document to get a quote?

No.

For a first price and time range, a 30-minute conversation is enough, and for the binding quote, the analysis. But a requirements document is what makes quotes from different providers comparable.

Who writes the functional specification?

The contractor, based on your requirements document.

With us, the analysis before the quote translates your requirements into scope and effort, and the agreed scope is then set out in the quote.

Is a requirements document legally binding?

Not on its own.

What the contract names as part of it is binding. That is usually the quote with scope and acceptance criteria, and often also the functional specification or your requirements document if the quote refers to it.

What does the analysis of a requirements document cost?

With us, €2,200 to €11,000 net.

The analysis takes two to ten days at a day rate of €1,100. The clearer the requirements document, the shorter the analysis.

Further reading

Requirements document finished, or half finished?

Send it to office@fragonstudios.com or tell us about it in the initial consultation. Within one working day you get a price and time range.