Template

Product Requirements Document (PRD) Template

A lean PRD that aligns product, design and engineering on the problem, goals, users, requirements, scope and how success will be measured.

Updated November 19, 2026In Web & DevelopmentFree download: Word, Markdown, PDF

Download this template free

No sign-up needed. Word and Excel files also open in Google Docs, Google Sheets and Apple Pages/Numbers. Letter size (8.5 × 11 in).

PRD: [Feature or Product Name]

Author
Status[Draft / In review / Approved]
Last updated
Target release
Stakeholders
Links[design, tickets, research]

1. Problem

[What problem are we solving, for whom, and how do we know it's a problem? Include data or user quotes.]

2. Goals and non-goals

Goals

  • [Measurable outcome]
  • [Measurable outcome]

Non-goals

  • [Explicitly out of scope]
  • [Explicitly out of scope]

3. Users and use cases

User typeUser story (As a … I want … so that …)

4. Requirements

#RequirementPriority (Must / Should / Could)Acceptance criteria
R1
R2
R3
R4
R5

5. User experience

[Key flows, wireframes or design links, edge cases and empty, error and loading states.]

6. Success metrics

MetricBaselineTargetBy when

7. Dependencies, risks and open questions

  • [Dependency on another team or system]
  • [Risk and mitigation]
  • [Open question, with owner]

8. Launch plan

[Rollout approach (beta, percentage rollout, feature flag), support and documentation, announcement.]

Preview of the template. Highlighted [brackets] show text to replace.

How to write a PRD

  1. Start with the problem, not the solution. Back it up with data, research or customer feedback.
  2. Set goals and non-goals. Non-goals prevent scope creep and endless debates.
  3. Describe users and use cases with simple user stories.
  4. List requirements with priorities. MoSCoW (Must, Should, Could, Won’t) is a common method. Add acceptance criteria so everyone knows when a requirement is met.
  5. Link to design rather than describing every screen in words.
  6. Define success metrics with a baseline and target.
  7. Call out risks, dependencies and open questions, each with an owner.
  8. Plan the launch.

Example user story and acceptance criteria

User story: As a returning customer, I want to reorder a previous purchase in one click, so that I can restock quickly.

Acceptance criteria:

  • A “Reorder” button appears on each past order.
  • Clicking it adds all in-stock items to the cart at current prices.
  • Out-of-stock items are listed with a message.

Tips

  • Keep it a living document and update it as decisions are made.
  • Write for skimmers, with headings, tables and bullets.
  • Get sign-off from engineering and design leads before development starts.
  • Use the Markdown version in GitHub, GitLab, Notion or Confluence.

Frequently asked questions

What is a product requirements document?

A PRD describes what a product or feature should do and why. It defines the problem, goals, target users, requirements and success metrics, so product, design and engineering share the same understanding before building.

How long should a PRD be?

As short as possible. Many teams use one- to three-page PRDs for features, and link to designs and tickets for detail. Large products may need longer documents.

Who writes the PRD?

Usually the product manager, with input from design, engineering, data and stakeholders. It should be reviewed and agreed before significant development begins.

Related templates and guides