How to Write a Software Requirements Document That Developers Can Build From
November 11, 2026 · 4 min read · Etzal Group Team
Most disputes in custom software projects trace back to one document, or to its absence. The client believed a feature was included. The developer believed it was not. Both are sincere, and neither can point to a sentence that settles it. A good software requirements document is that sentence, written before the work is priced.
This guide describes a structure that business teams can write and developers can build from.
What the document is for
It has three jobs:
- Agreement. Everyone means the same thing by "done".
- Estimation. A vendor can price it without padding for unknowns.
- Testing. At delivery, each requirement can be checked and ticked off.
If a section does not help with one of these, shorten it.
Section 1: background and goals
Two or three paragraphs. What problem is being solved, for whom, and how you will know it was worth doing. State goals as outcomes: "reduce the time to issue a quotation from two days to two hours", not "build a quotation module".
Section 2: users and roles
List every type of user and what each is allowed to do. A simple table works:
- Sales staff: create and edit their own quotations.
- Sales manager: view all quotations, approve discounts above 10%.
- Finance: view approved quotations, convert them to invoices.
- Administrator: manage users, price lists and templates.
Role definitions drive a large share of the build effort. Unclear roles are a common cause of late changes.
Section 3: functional requirements as user stories
Write each requirement from the user's point of view, with conditions that make it testable.
As a sales manager, I want to approve or reject a discount request, so that large discounts are controlled.
>
Acceptance criteria:
- A request above 10% appears in my approval list within one minute.
- I can approve, reject, or return it with a comment.
- The sales staff member is notified of the decision.
- Every decision is recorded with my name and the time.
The acceptance criteria are the important part. "The system shall be user-friendly" cannot be tested. "A new user can create a quotation without training in under five minutes" can.
Number every story. Numbers let you refer to requirements in estimates, test plans and change requests.
Section 4: business rules
Collect the rules that apply across features, so they are stated once:
- How prices, taxes and rounding are calculated.
- Which statuses a record can have and which transitions are allowed.
- Approval thresholds and who can override them.
- What happens at period end, such as month-end locking.
Give examples with real numbers. A worked example removes more ambiguity than a paragraph of description.
Section 5: data
- The main records the system keeps and their important fields.
- Which fields are required, and which must be unique.
- What data will be migrated from the old system, how much, and who cleans it.
- How long records are kept and what may be deleted.
Section 6: integrations
For each system the new software must connect to, state what data moves, in which direction, how often, and what should happen when the other system is unavailable. Name the owner of each system, because the vendor will need access and answers.
Section 7: non-functional requirements
- Performance. Expected number of users and response times for key screens.
- Availability. Working hours or around the clock, and acceptable downtime.
- Security. Login method, password or single sign-on rules, audit trail, encryption.
- Devices. Desktop browser, mobile browser, or native app.
- Language. Interface languages and number and date formats.
- Compliance. Any regulation that applies, such as personal data protection rules.
Section 8: out of scope
List what the project will not include. This section prevents more arguments than any other. If reporting dashboards, a mobile app or integration with a particular system are for a later phase, say so.
Section 9: assumptions and open questions
Write down what you are assuming, and what is still undecided, with a name and date next to each open question. An honest list of unknowns lets a vendor price them separately.
How to produce it
- Run short workshops with the people who do the work today, one process at a time.
- Draft the stories and rules, then walk through them with the same people using real cases.
- Sketch the main screens. Rough wireframes reveal misunderstandings that text hides.
- Ask a developer to review for anything that cannot be estimated.
- Sign off, and from then on change it only through a recorded change request.
Requirements workshops and the resulting document are the first phase of our Enterprise Software projects. If you have a draft and want it reviewed before sending it to vendors, get in touch.
Summary
State the goal, the users, what each can do, the rules, the data, the connections, the quality levels and what is excluded. Make every requirement testable and numbered. A document like this takes a few weeks to write and removes most of the surprises from the months that follow.
Frequently asked questions
How long should a software requirements document be?
Long enough that two different vendors would build the same thing from it. For a typical internal business application that is ten to thirty pages. Length matters less than precision: each requirement should be testable, and anything out of scope should be named.
Who should write the requirements, the client or the vendor?
The client owns the content because only the client knows the business rules. A vendor or analyst can lead the writing through workshops and return a draft for sign-off. A document written entirely by the vendor without client review tends to describe what is easy to build.
What is the difference between functional and non-functional requirements?
Functional requirements describe what the system does, such as creating an invoice or approving leave. Non-functional requirements describe how well it must do it: speed, availability, security, the devices it runs on and how many users it supports.
Related service
Free consultation
Not sure where to start? We will map the right system for your business, free.
