# [Feature name]: product requirements

**Owner:** [name] · **Status:** Draft · **Last updated:** [date]
**Reviewers:** [product] · [engineering] · [design] · [area owners]

> Free PRD template from SprintProof: https://sprintproof.com/templates/prd-template
> Replace everything in [brackets]. Delete the guidance lines (starting with ">") when you are done.

## 1. Summary

> What you are building, for whom, and why now, in three sentences or fewer. Write it last.

[Summary]

## 2. Problem

> The situation today, without the solution. Who has the problem and how often, what they do instead, and the evidence. Link sources rather than summarising them.

- **Who:** [who has the problem]
- **Today they:** [what they do instead]
- **Evidence:** [links to tickets, interviews, usage data]

## 3. Users and roles

> Everyone the feature touches, including the people on the receiving end. Name the permission rules here.

| Who | What they can do | What they must not be able to do |
| --- | --- | --- |
| [role] | [actions] | [limits] |

## 4. Done when

> Outcomes a tester can check. This is what the plan is reviewed and signed off against.

- [ ] [A user can ...]
- [ ] [... still works when ...]

**Measured after launch:** [metric], baseline today: [value or "no baseline yet"]

## 5. Not now

> What is deliberately out of scope for this release, each with a reason. Anything not listed here will be asked for in review.

- [Out of scope item]: [reason]

## 6. Requirements

> What has to exist, grouped by layer. Describe behaviour, not implementation. Include the empty, loading, error and no-access states for every screen.

| # | Requirement | Layer | Priority | Best (days) | Likely (days) | Worst (days) |
| --- | --- | --- | --- | --- | --- | --- |
| R1 | [requirement] | Frontend / Backend / Data / Cross-cutting | Must / Should / Could | | | |

## 7. Edge cases and open questions

> What you do not know yet. Every question needs an owner and a date to decide by.

| Question | Owner | Decide by | Answer |
| --- | --- | --- | --- |
| [question] | [name] | [date] | |

## 8. Risks and dependencies

> Other teams, vendors, migrations, security, legal or privacy reviews. Put the riskiest part first and spike it.

- **Risk:** [what could go wrong] · **Mitigation:** [what you will do] · **Owner:** [name]
- **Depends on:** [team or system] for [what], by [date]

## 9. Estimate

> A range, never one number. Sum the parts, then say which ones have the widest spread and why.

- **Total:** [best] to [worst] days, likely [likely]
- **Widest spread:** [requirement]: [why it is uncertain]
- **Date at 80% confidence:** [date]

## 10. Sign-off

> Product, engineering, design, and the owners of every area the feature touches.

| Role | Name | Decision | Conditions |
| --- | --- | --- | --- |
| Product | [name] | Approved / Changes requested / Pending | |
| Engineering | [name] | | |
| Design | [name] | | |
| [Area owner] | [name] | | |
