How to Write a Software Requirements Document (Free Template)
November 18, 2026 · 11 min read

Most software projects that go wrong do not fail because of bad code. They fail because the team built the wrong thing, or because nobody agreed what "done" meant. A clear software requirements document fixes that. It turns ideas, conversations and assumptions into a shared, written description of what the software must do, so that clients, designers, developers and testers are all working towards the same goal.
In this guide, you will learn what a software requirements document is, what to include, how to write requirements that developers can build and testers can verify, and the mistakes to avoid. You will also get a free software requirements specification (SRS) template that you can copy for your next project.
What Is a Software Requirements Document?
A software requirements document, often called a software requirements specification or SRS, describes what a software system should do and the conditions it must meet. It covers the system's purpose, users, features, constraints, integrations and quality standards such as performance and security.
A good SRS answers three questions:
- Why are we building this, and for whom?
- What must the software do (and not do)?
- How well must it do it (speed, security, availability, usability)?
It usually does not say exactly how the software will be built. Technical decisions, such as the tech stack and the architecture, belong in a separate design document.
For formal projects, the international standard ISO/IEC/IEEE 29148 provides guidance on requirements engineering and on the content of requirements documents. Its first edition, in 2011, replaced the older IEEE 830 standard, and the current edition was published in 2018. You can find it on the IEEE Standards website. You do not need to follow it word for word, but it is a useful reference.
Why a Software Requirements Document Matters
- Shared understanding: everyone agrees on what will be built before money is spent.
- Accurate estimates and quotes: developers cannot estimate what has not been defined. A detailed SRS leads to far more reliable time estimates and fixed-price quotes.
- Protection against scope creep: when a new request arrives, you can check it against the agreed scope. The Project Management Institute reported that 52% of projects experienced scope creep in its 2018 Pulse of the Profession survey, up from 43% five years earlier.
- Better testing: testers write test cases directly from the requirements and acceptance criteria.
- Easier handovers: new team members, vendors or support teams can understand the system quickly.
SRS vs BRD vs PRD vs User Stories
You will hear several names for requirements documents. Here is how they differ:
| Document | Focus | Typical Author |
|---|---|---|
| BRD (Business Requirements Document) | Business goals, problems and high-level needs | Business analyst or sponsor |
| PRD (Product Requirements Document) | Product vision, target users, features and success metrics | Product manager |
| SRS (Software Requirements Specification) | Detailed functional and non-functional requirements for the software | Business analyst, product owner or technical lead |
| User stories and backlog | Small, prioritised requirements written from the user's point of view | Product owner with the team |
On smaller projects, one document often covers all of these. In agile projects, the SRS may be lighter, with the detail living in user stories. We explain how this fits each methodology in agile vs waterfall.
Functional vs Non-Functional Requirements
Every software requirements document should separate two types of requirement:
- Functional requirements describe what the system does: features, user actions, business rules and data processing. Example: "Users can reset their password by email."
- Non-functional requirements describe how well the system performs: speed, security, reliability, scalability, usability, accessibility and compliance. Example: "The dashboard loads in under two seconds for 95% of requests."
Non-functional requirements are the ones teams most often forget, and they have a huge impact on architecture and cost. A system for 100 users and a system for 100,000 users can have the same features but very different designs.
How to Write a Software Requirements Document: Step by Step
Step 1: Define the purpose and scope
Start with a short statement of the problem, the goals and the business value. Then define the scope: what is included in this release and, just as important, what is not. An explicit "out of scope" list prevents many arguments later.
Step 2: Identify users and stakeholders
List each type of user (for example, customer, admin and manager) and what they need to achieve. Note who approves the document and who makes the final decision when requirements conflict.
Step 3: Gather requirements
Use interviews, workshops, surveys, reviews of current processes and competitor products. Ask "why" repeatedly to get to the real need behind each request. Watching users do their job often reveals requirements nobody mentions in meetings.
Step 4: Write clear functional requirements
Give each requirement a unique ID (such as FR-001), keep it to one testable statement and use consistent language. Many teams use "must" for mandatory requirements and "should" for desirable ones. User stories are a popular format: "As a [type of user], I want [goal] so that [benefit]."
Step 5: Add acceptance criteria
Acceptance criteria define when a requirement is complete. A common format is Given/When/Then: "Given I am a registered user, when I enter a valid email address on the reset page, then I receive a reset link within two minutes."
Step 6: Specify non-functional requirements
Cover performance, security, availability, scalability, accessibility, browser and device support, data retention and any legal or industry compliance requirements.
Step 7: Document integrations, data and constraints
List third-party systems and APIs (payment gateways, CRMs and email services, for example), data to migrate, hosting constraints, budget and deadline constraints, and any assumptions you are making.
Step 8: Prioritise
Not every requirement is equally important. The MoSCoW method sorts requirements into Must have, Should have, Could have and Won't have this time. This makes it clear what to cut if time or budget runs short, and it is essential when planning an MVP.
Step 9: Review, approve and version-control
Review the document with stakeholders, developers and testers. Developers spot technical risks, and testers spot requirements that cannot be tested. Once the document is approved, keep a change log so that every change is tracked and agreed.
How to Write Good Requirements: Examples
Good requirements are clear, specific, testable and free from ambiguity. ISO/IEC/IEEE 29148 describes characteristics of well-formed requirements, such as being necessary, unambiguous, complete, feasible and verifiable. Compare these examples:
| Weak Requirement | Better Requirement |
|---|---|
| The system should be fast. | Search results must load in under 2 seconds for 95% of requests with up to 500 concurrent users. |
| The app must be secure. | All passwords must be hashed, and admin accounts must use two-factor authentication. |
| Users can manage their orders. | Users can view, filter and cancel orders that have not yet been shipped. |
| The site should work on mobile. | All pages must display correctly on the latest two versions of Chrome and Safari on iOS and Android. |
| The system should be easy to use. | A new user must be able to complete checkout in 5 steps or fewer without help. |
Words such as "fast", "user-friendly", "secure", "flexible" and "etc." are warning signs. Replace them with numbers, conditions or examples.
Free Software Requirements Document Template
Use this SRS template as a starting point. Delete the sections that do not apply and expand the ones that matter most for your project.
| Section | What to Include |
|---|---|
| 1. Introduction | Purpose, scope, goals, definitions and references |
| 2. Overall description | Product overview, users, operating environment, constraints and assumptions |
| 3. Functional requirements | Features grouped by module, each with an ID, priority and acceptance criteria |
| 4. Non-functional requirements | Performance, security, availability, scalability, usability and compliance |
| 5. External interfaces | User interfaces, APIs, third-party integrations and hardware |
| 6. Data requirements | Data entities, data migration, retention and backups |
| 7. Out of scope | Features and work explicitly not included |
| 8. Appendices | Glossary, wireframes, open questions and change log |
Here is the full template in a copy-ready format:
SOFTWARE REQUIREMENTS SPECIFICATION (SRS)
Project name: [Name]
Version: [1.0] Date: [DD/MM/YYYY]
Prepared by: [Name, role]
Approved by: [Name, role]
1. INTRODUCTION
1.1 Purpose - Why this software is being built and the problem it solves
1.2 Scope - What this release includes; goals and success metrics
1.3 Definitions - Terms, acronyms and abbreviations
1.4 References - Related documents, designs, contracts and standards
2. OVERALL DESCRIPTION
2.1 Product overview - New product, replacement or extension of a system
2.2 User classes - Each type of user, their goals and permissions
2.3 Operating environment - Browsers, devices, operating systems, hosting
2.4 Constraints - Budget, deadline, technology, legal or regulatory
2.5 Assumptions and dependencies
3. FUNCTIONAL REQUIREMENTS
Group by module (e.g. Accounts, Orders, Payments, Admin). For each one:
ID: FR-001
Title: Password reset
Description: Registered users can reset their password via an emailed link.
Priority: Must have
Acceptance: Given a registered email address, when the user requests a
reset, then a single-use link valid for 30 minutes is sent
within 2 minutes.
4. NON-FUNCTIONAL REQUIREMENTS
4.1 Performance - e.g. 95% of pages load in under 2 seconds
4.2 Security - authentication, roles, encryption, audit logs
4.3 Availability - uptime target, backups, recovery time
4.4 Scalability - expected users, data volumes and growth
4.5 Usability and accessibility - e.g. WCAG 2.2 level AA
4.6 Compliance - e.g. GDPR, PCI DSS, industry rules
5. EXTERNAL INTERFACES
5.1 User interfaces - links to wireframes or designs
5.2 APIs and integrations - payment gateway, CRM, email, analytics
5.3 Hardware interfaces - if any
6. DATA REQUIREMENTS
Main data entities, data migration, retention periods and backups
7. OUT OF SCOPE
Features and work explicitly NOT included in this release
8. APPENDICES
A. Glossary B. Wireframes C. Open questions D. Change log
How Long Should an SRS Be?
As long as it needs to be, and no longer. For a small website or MVP, 5 to 15 pages is often enough. A large enterprise or regulated system may need far more detail. The test is simple: could a new developer or tester read it and understand what to build and how to check it? If not, add detail. If some sections are never read, cut them.
Tips for Writing a Better SRS
- Use visuals: wireframes, user flows and diagrams often explain more than paragraphs of text.
- Keep one source of truth: store the document in a shared, version-controlled place, not in email attachments.
- Write for your readers: plain language for business stakeholders, precise detail for developers and testers.
- Link requirements to goals: every feature should support a business goal; if it does not, question it.
- Include open questions: listing unknowns is better than hiding them.
- Revisit it: in agile projects, refine requirements as you learn rather than freezing everything on day one.
Common Mistakes to Avoid
- Describing solutions instead of needs: "add a dropdown" is a design decision; "users can choose their country" is a requirement.
- Missing non-functional requirements: performance and security surprises are expensive late in a project.
- No acceptance criteria: without them, "done" becomes a matter of opinion.
- No out-of-scope section: unstated assumptions become disputes.
- Writing it alone: involve developers and testers early to catch gaps and risks.
- Never updating it: an outdated document is worse than none, because people still trust it.
Frequently Asked Questions
What is the difference between an SRS and a functional specification?
The terms are often used interchangeably. Strictly, a functional specification focuses on functional requirements, while an SRS also covers non-functional requirements, interfaces, constraints and assumptions.
Who writes the software requirements document?
Usually a business analyst, product owner or project manager, working closely with stakeholders, developers and testers. On smaller projects, the development agency often writes it with the client during a paid discovery phase.
Do agile projects need an SRS?
They need requirements, but not always a large upfront document. Many agile teams keep a lighter SRS for goals, scope and non-functional requirements, with detailed features captured as user stories in the backlog.
What is the IEEE standard for software requirements?
The current standard is ISO/IEC/IEEE 29148, which replaced IEEE 830. It covers requirements engineering processes and the content of requirements documents.
How detailed should requirements be for a fixed-price project?
Very detailed. A fixed price depends on a fixed scope, so every feature, integration and acceptance criterion should be documented. See our comparison of fixed price vs hourly pricing for more.
What tools can I use to write an SRS?
Google Docs, Microsoft Word, Confluence and Notion are popular for the document itself, while tools such as Jira or Linear manage user stories and backlogs. See our list of the best project management tools for IT teams.
Conclusion
A clear software requirements document is one of the cheapest ways to reduce risk on any software project. It aligns everyone on what to build, makes estimates and quotes more accurate, gives testers something to test against and protects your budget from scope creep. Start with our free template, keep requirements specific and testable, and treat the document as a living reference throughout the software development life cycle.
Need help defining your project? Our team runs discovery workshops that turn your ideas into a clear, prioritised requirements document, with accurate estimates to match. Book a free consultation today.