Skip to content
Free template

Software requirements document template and generator.

A requirements document sets out what your software must do before any vendor writes a quote. This template walks you through the parts that matter, in order: goals, roles, features, integrations, data protection and acceptance. You end up with a clean document to copy, print or download as a Word file.

What happens to what you type

Nothing, unless you send it. The generator runs in your browser, stores nothing and asks for no email address. The finished document works for any vendor, not just us.

Definition

What is a requirements document?

A requirements document is where the client writes down what the software has to do and why: goals, users, features, integrations and constraints. It covers the what, not the how. The vendor answers it with a specification of how they will build it, which German-speaking teams call the Pflichtenheft.

Our view: you don't need a requirements document to make a first enquiry. One page is enough. It earns its place once several vendors have to quote against the same scope, or someone inside your company has to sign off. And it doesn't need to be long. Five clear pages beat forty that nobody reads to the end.

Requirements document and specification: the difference
Requirements documentSpecification
Who writes it?The client, which means youThe vendor who builds it
Which question does it answer?What must the software do, and what for?How will it be built?
When is it written?Before the enquiry or tenderAfter the requirements, before the build
What is in it?Goals, roles, requirements, acceptance criteriaArchitecture, technology, approach, test plan
In German-speaking projects the two are the Lastenheft and the Pflichtenheft, both defined in DIN 69901-5. In French it is the cahier des charges.
The generator

Answer the questions, take the document with you.

Jump to the document
Project

What are you building? Pick the closest type and we tick the features that usually go with it.

Two or three sentences: how does it work today, and what gets in the way?

Goals

One goal per line. What should be better once it is live?

Users and roles

One role per line, with what it does in the system.

Features

Ticked for your project type. Untick what you don't need.

The basics
Payments
Messaging and real time
Running the business
AI, voice and devices
Integrations

Which existing systems does the solution have to exchange data with?

Data and data protection

What applies to the data? It lets a vendor plan data protection in from the start.

Quality and operations

The non-functional requirements: languages, devices, availability.

Acceptance

The generator writes one acceptance criterion for each feature you picked. Add your own, one per line.

Scope and constraints

What is explicitly not included, and anything else that applies.

A real example

Requirements document example: a supplier portal, shortened

This is what a software requirements document looks like in practice. The example comes from a supplier portal CODT Technologies built for a Swiss food company. Through it, the company orders ingredients, fruit and vegetables from its suppliers, keeps its stock and generates purchase orders. We have shortened it and anonymised it heavily.

Shortened and simplified. No client data, no quantities, no prices.

Requirements: supplier portal

  • Client: a Swiss food company
  • Project type: web application
  • Excerpt

This document describes what the solution must do. How it will be built is for the vendor to set out in their specification.

1. Background and goals

The company cooks in its own kitchen and buys ingredients, fruit and vegetables from several suppliers.

  • G-01Orders, stock and purchase orders live in one system.
  • G-02Before every order, it is clear what is in stock.

2. Users and roles

  • Purchasing: places orders with the suppliers
  • Kitchen and stores: book deliveries in, see the stock
  • Admin: maintains suppliers, items and users

3. Functional requirements (excerpt)

  • F-01An item list holds ingredients, fruit and vegetables, each with its supplier and unit.
  • F-02Purchasing creates orders per supplier. The system turns each one into a purchase order.
  • F-03The system keeps the stock level per item.
  • F-04A booked delivery raises the stock of the items delivered.

7. Acceptance criteria (excerpt)

  • A-01An order for three items from one supplier produces exactly one purchase order with three lines.
  • A-02After a delivery is booked in, the stock shows the quantity delivered.

8. Scope

  • Which dishes get cooked is planned in a separate kitchen system. That planning is not part of this contract.
FAQ

Questions about requirements documents

Anything we missed?

Put it in a brief. A senior engineer reads it and replies within one business day.

How do I write a software requirements document?

Start with the background and two or three goals you can check later. Then list the roles, the must-have features, the integrations with systems you already run, what applies to data and data protection, and finally the acceptance criteria. The generator on this page asks exactly those questions and puts the answers together into a finished document.

Is there an example of a software requirements document?

Yes, on this page: a shortened requirements document for a supplier portal CODT Technologies built for a Swiss food company. It shows how goals, roles, must-haves and acceptance criteria fit together. You can also make your own example in seconds: pick a project type in the generator and a full draft appears.

Do agile teams still need a requirements document?

Yes, as long as it stays short. An agile team does not need a document that describes every screen. It needs goals, roles, boundaries and acceptance criteria to judge each sprint against. The detail grows later as user stories in the backlog, worked out with the people who will use the software.

What is the difference between a requirements document and an SRS?

The terms overlap. A business requirements document says what the business needs and why. A software requirements specification (SRS) goes further into how the system must behave, often following ISO/IEC/IEEE 29148, which replaced IEEE 830. This generator produces the first kind: what a vendor needs in order to understand the job and quote for it.

Should the document include a budget and deadlines?

Fixed dates, yes, such as a trade fair or a season start, because they change the approach. Whether to name a budget is your call; some clients only share it in a meeting. The free field “Dates and other constraints” is there for both. The generator itself never writes in an amount or a deadline.

Is anything I type stored?

No. The generator runs entirely in your browser. We store nothing you type, and you need no account and no email address. Only if you choose to send the document to us do we receive your name, your email address and the document, so that we can reply.

Can I send the document to other vendors?

Yes, that's what it is for. The requirements name no vendor, and the document works for any request for proposal or tender. At the very bottom there is a short line saying which template made it. You can delete it in the Word file.

Ready to build

Have a problem worth
solving well?

Tell us what you are building and the deadline it has to meet. You will get a clear read on whether we fit and what the work would take.