Create a product requirements document

Use this template as a starting point. Add, remove, or change sections to fit your project.

The online editor needs JavaScript, but the blank files are available below.

Or start with a blank file

0 of 12 sections completed

Checking this browser for a saved draft.

Your draft stays in this browser unless you download it.

Document title Optional

1. Product summary and desired outcome Optional

Summarize the product, who it is for, and the outcome this work should produce.

What will exist when this work is complete?
What change should the product create for its users?

2. Context and problem Optional

Describe the current situation, the problem to solve, and the evidence or assumptions that explain why it matters now.

What happens today?
What pain, risk, or opportunity makes this work worthwhile?

3. Goals and success measures Optional

State the goals and the observable measures that will show whether the product achieved them.

Which outcomes should improve?
What signals, targets, or timeframes define success?

4. Users and important use cases Optional

Identify the users who matter for this work and the important tasks or journeys each needs to complete.

Who uses, administers, or is affected by the product?
Which use cases must work at launch?

5. Scope and non-goals Optional

Define what this work includes, what it deliberately excludes, and where its boundaries sit.

Which capabilities belong in this release?
Which plausible additions should not be built?

6. User experience Optional

Describe the screens, interactions, states, responsive behavior, and accessibility decisions users should experience.

What do users see and do from start to finish?
How should loading, empty, error, success, and small-screen states behave?

7. Functional requirements Optional

List observable product behavior, using exact labels, values, ordering, limits, and fallback rules where those details matter.

What can a person or automated test observe?
Which strings, numbers, precedence rules, or edge cases must be exact?

8. Data, APIs, and external integrations Optional

Specify the data the product reads or writes, its API contracts, and each external system interaction.

What data is stored, generated, imported, or shared?
How should integration failures, limits, and retries behave?

9. Constraints and fixed implementation decisions Optional

Record the constraints and implementation choices that are fixed, plus alternatives that remain open or are ruled out.

Which technology, compatibility, budget, timing, or operating constraints apply?
Which decisions must not drift during implementation?

10. Security, privacy, identity, and permissions Optional

Define applicable security, privacy, identity, permission, and trust-boundary decisions, including how untrusted input is handled.

Who may see or change each resource?
Where does trusted data end and untrusted data begin?

11. Acceptance criteria and failure recovery Optional

Write pass-or-fail acceptance criteria and define expected behavior when operations fail, time out, or need recovery.

What must be true for this work to be accepted?
What should users see and do after a failure?

12. Validation plan and definition of done Optional

Name the runnable commands, end-to-end journeys, and other evidence that define a complete and validated result.

Which checks prove individual requirements?
Which complete journeys, environments, or restart checks must pass?

Download your PRD

Current draft

Include blank sections

Files are generated in this browser.

Or start with a blank file

Draft controls

A JSON backup reopens your editable draft with all 13 fields preserved exactly, here or in another browser. Downloads and imports stay on your device. Import limit: 5 MiB.

Convert finished Markdown

Markdown import converts a finished document that uses the 12 section headings into editable fields. Use JSON when you need an exact backup. Import limit: 5 MiB.

Portable references

Includes the Guide, handoff checklist, Walkthrough, Template guidance, and blank template.

Download reference bundle (.zip)

1. Product summary and desired outcome Optional

2. Context and problem Optional

3. Goals and success measures Optional

4. Users and important use cases Optional

5. Scope and non-goals Optional

6. User experience Optional

7. Functional requirements Optional

8. Data, APIs, and external integrations Optional

9. Constraints and fixed implementation decisions Optional

10. Security, privacy, identity, and permissions Optional

11. Acceptance criteria and failure recovery Optional

12. Validation plan and definition of done Optional

Product requirements document

Product summary and desired outcome

Context and problem

Goals and success measures

Users and important use cases

Scope and non-goals

User experience

Functional requirements

Data, APIs, and external integrations

Constraints and fixed implementation decisions

Security, privacy, identity, and permissions

Acceptance criteria and failure recovery

Validation plan and definition of done

Portable references