Skip to content
← All articlesProduct

How to Write a Software Requirements Document (PRD)

Learn how to write a software requirements document that outsourced teams can build from: structure, user stories, acceptance criteria and a ready checklist.

Most outsourced projects that go wrong do not fail because of bad code. They fail because the team built something slightly different from what the business had in mind. A clear software requirements document, often called a product requirements document or PRD, is the cheapest way to prevent that gap. It does not need to be long. It needs to be specific, testable and agreed by everyone who will build, test and sign off the work.

This guide shows how to write one that works for a distributed team, including an offshore one, where you cannot lean over a desk to clarify what you meant.

What a requirements document is for

A good document does four jobs:

  • Aligns people. Founders, product managers, designers, developers and testers read the same description of the goal.
  • Supports estimation. A team cannot give a dependable estimate from a paragraph of ideas. See our software project estimation guide for how estimates are built from this material.
  • Defines “done”. Acceptance criteria turn opinions into checks that can be passed or failed.
  • Controls change. When something new comes up, you can see whether it is in scope or a change request.

It is not a legal contract and it is not a design file. It sits between the business goal and the technical specification.

A practical structure

Keep the document to the sections below. Skip any that genuinely do not apply.

Section What to put in it
Background and goal The problem, who has it, and what success looks like in plain words
Users and roles Who uses the product and what each role is allowed to do
Scope What is in this release, and what is explicitly out
Functional requirements Features written as user stories with acceptance criteria
Non-functional requirements Performance, security, accessibility, browser and device support, data retention
Integrations Third-party systems, APIs, payment or identity providers
Assumptions and risks Things you believe to be true but have not confirmed
Open questions Decisions still needed, with an owner and a date

Start with the problem, not the feature list

Open with two or three sentences on the problem and the outcome you want. For example: “Field engineers lose time re-entering job notes. We want them to log a job once on a phone, even without signal.” A team that understands the reason can make sensible small decisions without asking you every time.

Write user stories that can be tested

A common format is: As a [role], I want [capability], so that [benefit]. It keeps attention on the user. But a story alone is vague, so attach acceptance criteria.

A weak requirement: “Users can reset their password.”

A testable version:

  • A user can request a reset link from the login page using their registered email address.
  • The link expires after a stated period, agreed with the business.
  • A used or expired link shows a clear message and offers to send a new one.
  • The screen never reveals whether an email address is registered.
  • Every reset request is recorded in the audit log.

Each line can be tested by a QA engineer. If you cannot imagine how to test a sentence, it is not yet a requirement.

Do not forget the non-functional requirements

Teams usually remember features and forget qualities. These are often where the real cost and risk sit. Cover at least:

  • Performance: for example, target page load behaviour using Core Web Vitals thresholds, and expected concurrent users.
  • Security and privacy: authentication method, roles, data encryption, and any regulation that applies to your users, such as GDPR.
  • Accessibility: the WCAG level you expect.
  • Compatibility: which browsers, operating system versions and devices you must support.
  • Availability and support: expected uptime, backup needs and who responds to incidents.

If you do not state these, the team will assume something, and the assumption may not match yours.

Say what is out of scope

An “out of scope” list is one of the most useful parts of a document. List the things people might reasonably expect but are not included in this release: admin reporting, a second language, an iOS version, data migration from the old system. This single list prevents many awkward conversations later and supports the discipline described in managing scope creep in outsourced projects.

Make it easy to review and keep it alive

  • Use visuals where words struggle. A simple flow diagram or wireframe often replaces a page of text. Link to designs rather than pasting them.
  • Keep one source of truth. Store the document where everyone can see the latest version, and record changes with dates.
  • Review it with the whole team. Developers spot technical risks, testers spot untestable statements, and designers spot missing states. Hold a short walkthrough before development starts.
  • Resolve open questions early. Give each one an owner and a due date.
  • Treat it as living. Requirements will change. That is fine if changes are visible and agreed.

A quick quality checklist

Before you hand the document over, check that:

  • The goal and target users are stated clearly.
  • Every feature has acceptance criteria that can be tested.
  • Non-functional requirements are written down.
  • Out-of-scope items are listed.
  • Integrations and data sources are named.
  • Assumptions and open questions have owners.
  • Someone other than the author has read it and understood it.

Not sure where to start?

If your idea is still forming, a short discovery phase can produce the first draft of this document with you. Our product discovery workshop guide explains how that works. Once the scope is clear, a dedicated development team can build against it and keep the requirements current as the product grows. To talk through your project, contact us and we will help you shape a clear brief.

Let’s build what’s next.

Tell us about your platform, your product idea or the systems you want to modernise. Someone from our Chennai engineering team will get back to you personally.