What to include in a software requirements specification

A software requirements specification is the document that turns an idea into something a team can estimate, build and test. It does not need to be long, but it does need to be clear. A good specification reduces surprises, makes quotes comparable and gives everyone the same picture of what success looks like.

Here are the twelve things it should cover.

A good specification explains what success looks like

Before listing features, describe the outcome. A system that “manages bookings” could mean almost anything. A system that “lets clients book online, matches each booking to an available practitioner and removes manual confirmation calls” gives the team something concrete to design for and to test against.

1. Business objectives

Why are you doing this, and how will you know it worked? Write down the problems you want to solve and, where possible, how you will measure the improvement: time saved, errors reduced, faster responses or new revenue.

2. Users and roles

List everyone who will use the system and what each group needs to do: staff, managers, customers, partners, administrators. Note who can see and change what. Roles and permissions shape almost every screen.

3. Core workflows

Describe the main processes step by step, including what happens when something goes wrong or does not follow the normal path. The exceptions are where most of the complexity lives: cancellations, refunds, partial deliveries, approvals that are rejected.

4. Functional requirements

List what the system must do, ideally grouped by workflow. It helps to prioritise each item as must have, should have, could have or will not have this time. That makes it much easier to agree a first release and to keep the budget under control.

5. Business rules and calculations

Pricing, discounts, tax, allocations, eligibility, deadlines and approval limits should be written down precisely, with examples. A rule that everyone “just knows” is a common source of disputes later.

6. Data and migration

What information will the system hold, where does it come from today and how much of it needs to move across? Note the quality of existing data honestly. Duplicates, missing fields and inconsistent formats all add effort. If duplicates are a known problem, plan for matching and merging records as part of the project.

7. Integrations

List every system the new software must exchange information with, such as accounting, payments, CRM, ERP, email, messaging or government services. For each one, note what information moves, in which direction, how often and whether the other system has an API. Our article on why integration projects get complex explains what to look out for.

8. Security, privacy and compliance

Describe the sensitivity of the data and the rules that apply. Depending on where you operate and what you do, that may include data protection law such as the GDPR in the UK and Europe or the Digital Personal Data Protection Act in India, and sector rules, for example for health records. Note requirements for login, multi-factor authentication, audit trails, data retention and where data must be hosted.

9. Non-functional requirements

These describe how well the system must work rather than what it does: expected numbers of users and transactions, response times, availability, backup and recovery, supported devices and browsers, accessibility, and languages.

10. Testing and acceptance criteria

For each important workflow, describe how you will confirm it works. Clear acceptance criteria, ideally with sample data, turn “it doesn’t feel right” into something that can be checked and fixed. Plan who from your side will take part in user acceptance testing.

11. Assumptions, exclusions and constraints

Write down what is out of scope, what you are assuming and any fixed constraints such as deadlines, budgets or technology that must be used. Unstated assumptions cause many of the most difficult conversations in software projects.

12. Ownership, hosting and support

Note who will own the code and data, where the system will be hosted, who will look after it after launch and what level of support you expect.

How detailed should it be?

Detailed enough that two suppliers would understand the same thing, but not so detailed that it designs every screen. For larger or less certain projects, a short paid discovery phase with your chosen supplier is often the best way to get there. Interviews with users, workshops on the main workflows and a review of existing systems produce a far better specification than one written in isolation.

Using the specification to get quotes

Send the same specification to every supplier you are considering and ask them to list their assumptions and exclusions. That makes quotes comparable and shows you who has really read it. Our guide on how to choose a custom software development company covers the rest of the selection process.

A one-page checklist

  • Objectives and how success will be measured
  • Users, roles and permissions
  • Main workflows, including exceptions
  • Prioritised functional requirements
  • Business rules and calculations, with examples
  • Data sources, quality and migration
  • Integrations and APIs
  • Security, privacy and compliance
  • Performance, availability, devices and accessibility
  • Acceptance criteria and testing
  • Assumptions, exclusions and constraints
  • Ownership, hosting and support

Want help turning an idea into a specification?

Our discovery phase produces a written plan you can use to get comparable quotes, from us or anyone else.

Similar Posts