A PRD (product requirements document) explains what a product or release must do, for whom and why. Include the problem and its evidence, measurable goals, non-goals, users, requirements written as user stories with acceptance criteria, non-functional requirements, data and integrations, and open questions with owners. Leave the technical design out, keep one current version and record every substantive change.
What a PRD is for
A product requirements document (PRD) states what a product or release must do, for whom and why, so that product, design, engineering and stakeholders build the same thing. It describes problems, outcomes and requirements; the technical design belongs elsewhere. A project brief opens a supplier conversation, a PRD guides the team building the product, and a software requirements specification adds detailed, testable system requirements when a contract or regulator needs them.
Where a PRD fits
A PRD sits between the first brief and the documents that bring in a partner. Use it to settle what the product must do before anyone specifies or prices how it will be built.
Each document answers one question, then hands its answer to the next.
Define what you need
- PRDYou are hereProduct requirements document
What must the product do, and how will we know it works?
Hands onGoals, user stories and acceptance criteria
- SRSWhen precision mattersSoftware requirements specification
Exactly how must the system behave?
Hands onTestable, traceable requirements
Choose and agree
- CompareProposal comparison
Which offer is sound, not just cheapest?
Hands onA chosen partner and open risks
- SOWStatement of work
What exactly have we agreed to deliver?
Hands onDeliverables, acceptance and change control
What a product requirements document contains
Keep each part short enough that people read it. A useful PRD covers:
- The problem, who has it, how they cope today and the evidence that it matters.
- Goals and how success will be measured after release.
- Non-goals: what this release deliberately will not do.
- Users and roles, with the main jobs each one needs to complete.
- Requirements written as user stories with acceptance criteria.
- Non-functional requirements: performance, accessibility, security, privacy and availability.
- Data and integrations, each with an owner and test access.
- Dependencies, risks and open questions, each with an owner and a decision date.
- A change log, so readers can see what moved since they last looked.
Copy the PRD template
Paste this into a shared document and replace each heading with a short answer. Keep unanswered items as questions with an owner; do not delete them to make the document look finished.
Write requirements as user needs with acceptance criteria
The UK Government Digital Service recommends a three-part user story: “As a… [who is the user?]”, “I need/want/expect to… [what does the user want to do?]”, “So that… [why?]”. The goal is the most important part, because it shows whether the right problem is being solved. Pair each story with acceptance criteria written as a short checklist that starts “it's done when…”, so that design, build and testing aim at the same result.
A worked example: online appointment booking
Suppose a small clinic wants patients to book appointments without phoning. This is a fictional planning example, not a Scopeivo delivery project. The problem is missed calls during busy hours; the goal is that most routine bookings happen online within three months of release.
| User story | It's done when… | Open question |
|---|---|---|
| As a patient, I need to book an available slot so that I don't have to call during opening hours | Only free slots are offered; a booked slot disappears for others; a confirmation email arrives | Which appointment types may be booked online? |
| As a patient, I need to cancel a booking so that the slot can be offered to someone else | Cancellation works from the confirmation link up to the agreed cut-off; staff see the change | What is the cancellation cut-off? |
| As a receptionist, I need to see today's bookings so that I can prepare for each visit | The list updates without reloading and shows the booking source | Does the practice system need to receive bookings? |
Replace these with your own users and decisions. The example sets no delivery estimate.
Leave solutions out until they are decided
A requirement such as “add a dropdown of time slots” closes off better designs before anyone has tested them. Describe the outcome instead: a customer can choose an available appointment without calling. Record design and technical decisions separately, with a date and an owner, once they are made. This keeps the PRD stable while the solution improves.
Make unknowns visible
Every early PRD contains assumptions. List them as open questions rather than writing them as settled requirements, and give each one an owner and a date by which it must be answered. An honest list of unknowns is what lets a development partner propose discovery work, a prototype or a smaller first release instead of guessing.
Keep one current version
A PRD that nobody updates after kickoff misleads everyone who reads it later. Keep a single shared version, record each substantive change in the change log and say who approved it. When the scope of a release changes, change the document first, then the backlog.
Common PRD problems and their fixes
Most weak PRDs fail in predictable ways. Check a draft against these before sharing it.
| Problem | Why it hurts | Fix |
|---|---|---|
| A feature list with no problem statement | Nobody can judge whether a cheaper design would do | Lead with the problem, evidence and goal |
| Interface designs written as requirements | Better solutions are ruled out before testing | Describe the outcome; record design decisions separately |
| No non-goals | Every reader assumes a different scope | List what this release will not do |
| Assumptions written as facts | Risks stay hidden until they are expensive | Keep them as open questions with owners and dates |
Use the PRD with a development partner
If an external team will build the product, share the PRD with your request for proposal and ask each partner to list the gaps and assumptions they see. Their questions are a good test of the document and of the partner. The Project Scoper turns your answers into a structured brief you can use as a first draft.
Questions buyers ask
What is a PRD?
A product requirements document states what a product or release must do, for whom and why: the problem, goals, non-goals, users, requirements with acceptance criteria and open questions. It guides product, design and engineering; the technical design is documented separately.
What is the difference between a PRD and an SRS?
A PRD describes the product from the user’s and the business’s point of view. A software requirements specification adds precise, testable system requirements, interfaces and quality targets. Many projects need only a PRD; regulated, contracted or multi-supplier work usually needs an SRS as well.
Who writes the PRD?
Usually the product owner or product manager, with input from design, engineering and the people who understand the users and the business. One person should own it, keep a single current version and record each change with who approved it.
How long should a PRD be?
Long enough to answer the questions the team will ask, and short enough that people read it; a focused release often fits in a few pages. Length matters less than measurable goals, explicit non-goals and acceptance criteria for each requirement.
Sources and editorial approach
Scopeivo publishes practical planning guidance. Examples and suggested rubrics are decision aids, not evidence of delivered projects or guaranteed outcomes. Adapt them to your context and verify material assumptions with the people responsible.
Read our research and publication approach. Original publication dates are retained; the update date reflects substantive changes to this guide.
