Product requirements document (PRD) template, with an example
A free product requirements document template for Google Docs, Word, Notion, or Confluence: each section explained, a filled-in example, and mistakes to avoid.
A PRD that took two weeks to write gets one careful read, at the kickoff. Three sprints later, engineering is building from a Jira ticket, design from a Figma comment, and the PRD still describes a version of the feature nobody is building.
The fix is usually a shorter PRD, not a longer one: the parts that stay true, kept current, with links to the detail. This template follows the sections in Atlassian's product requirements guide, checked on 16 November 2026, plus requirements and success metrics.
What a PRD is for
A PRD defines what a team is building, who it's for, and why, so product, design, engineering, and stakeholders work from the same picture. It deliberately leaves out how. Architecture, data models, and APIs belong in a technical design document.
The template
Copy this into Google Docs, Word, Notion, or Confluence:
# [Feature name] PRD
| | |
|---|---|
| Owner | [PM name] |
| Participants | [Eng lead, designer, stakeholders] |
| Status | Draft / In review / Approved / Shipped |
| Target release | [Date or quarter] |
| Last updated | [Date] |
## Goals
- [The outcome this delivers for users]
- [The business objective it supports]
## Success metrics
| Metric | Today | Target | Measured by |
|---|---|---|---|
| [Metric] | [Baseline] | [Target] | [Dashboard or query] |
## Background and strategic fit
[Why now. The problem, the evidence, and how it fits the company's goals.
Link to research and customer interviews.]
## Assumptions
- [Technical, business, or user assumption to validate]
## User stories
| # | As a... | I want to... | So that... | Priority |
|---|---|---|---|---|
| 1 | [User] | [Action] | [Benefit] | Must / Should / Could |
## Requirements
| # | Requirement | Acceptance criteria | Story |
|---|---|---|---|
| R1 | [What the product must do] | [How we'll know it works] | 1 |
## Design
[Links to wireframes, prototypes, and design explorations.]
## Open questions
| Question | Owner | Due | Answer |
|---|---|---|---|
| [Question] | [Name] | [Date] | |
## Not doing
- [Out of scope for this release, and why]
## Decisions
| Date | Decision | Why | Decided by |
|---|---|---|---|
| [Date] | [What was decided] | [Reason] | [Name] |
How to fill in each section
Header. One owner, not a committee. Status and last-updated date tell a reader whether to trust the page.
Goals. Two or three, each an outcome rather than a feature. "Admins can see who has access" is an outcome; "add a permissions page" is a solution.
Success metrics. A baseline and a target for each. Without a baseline, nobody can say later whether it worked.
Background. The problem and the evidence for it: support tickets, interview quotes, usage data. Link rather than paste.
Assumptions. What you believe but haven't confirmed. Each one is a risk; note how you'll check it.
User stories. Who, what, and why, with a priority. Link to the Jira or Linear tickets once they exist.
Requirements. What the product must do, each with acceptance criteria a tester could check. Number them so tickets and reviews can cite R3 rather than "the export thing".
Open questions. Atlassian suggests a table of things to decide or research. Give each an owner and a date, or it stays open forever.
Not doing. The most underused section. Naming what's out of scope ends the same debate in every review.
Decisions. When an open question gets answered, move it here with the reason and who decided. This is the section that keeps the PRD true after kickoff.
A filled-in example
# Team access review PRD
| | |
|---|---|
| Owner | Priya (PM) |
| Participants | Arjun (eng lead), Mei (design), Sam (security) |
| Status | Approved |
| Target release | Q1 |
| Last updated | 16 Nov |
## Goals
- Workspace admins can see and remove stale access in one place.
- Pass enterprise security reviews without a custom export.
## Success metrics
| Metric | Today | Target | Measured by |
|---|---|---|---|
| Security review questions on access | 6 per deal | 1 per deal | Sales tracker |
| Admins running a review per quarter | 0% | 40% | Product analytics |
## Background and strategic fit
Four of the last ten enterprise deals asked for an access report.
Today support exports it by hand. Supports the Q1 enterprise goal.
## Assumptions
- Admins review quarterly, not monthly. Check in 5 interviews.
## User stories
| # | As a... | I want to... | So that... | Priority |
|---|---|---|---|---|
| 1 | Admin | see every member's last activity | I can find stale access | Must |
| 2 | Admin | remove several members at once | the review takes minutes | Must |
| 3 | Admin | export the list as CSV | I can attach it to an audit | Should |
## Requirements
| # | Requirement | Acceptance criteria | Story |
|---|---|---|---|
| R1 | List members with role and last active date | Matches audit log for 10 sampled users | 1 |
| R2 | Bulk remove up to 100 members | Removed members lose access within 1 minute | 2 |
| R3 | CSV export of the list | Opens in Excel and Google Sheets | 3 |
## Open questions
| Question | Owner | Due | Answer |
|---|---|---|---|
| Count API token use as activity? | Arjun | 20 Nov | |
## Not doing
- Scheduled reviews with reminders. Next quarter, if usage hits target.
- Guest accounts. Separate model, separate PRD.
## Decisions
| Date | Decision | Why | Decided by |
|---|---|---|---|
| 12 Nov | Removal is immediate, no grace period | Security reviews require it | Sam |
Mistakes that make PRDs go stale
Atlassian lists anti-patterns, including specifying everything in detail before engineering starts, requiring sign-off from every team before work begins, and requirements that never get updated after sign-off. In practice:
- Writing the solution as the requirement. Leave room for design and engineering.
- No owner for open questions. They resurface in sprint three.
- Decisions made outside the doc. The real answer lives in a Slack thread, and the PRD says something else.
- No "not doing" list. Scope grows one reasonable request at a time.
If AI coding agents will build from the PRD, they read it literally and fill gaps with guesses. See the PRD template for AI coding agents for the stricter version.
Where Lockstep fits
The Decisions section is where most PRDs fall behind, because decisions keep getting made in Slack and in pull requests after the doc is approved. Lockstep captures decisions from PRDs, Slack, and pull requests, routes each to its owner for approval, and briefs the engineers and Claude Code sessions building the feature, so the decision that changed on Thursday reaches the work on Friday.
See Lockstep for product teams.
Sources checked 16 November 2026
Related reading
For logging decisions in Notion or Jira, see the Notion decision log template and the Jira decision log template. For how AI agents fit into product work, see how to use AI agents as a product manager. For how a PRD differs from other requirements documents, see PRD vs BRD vs FRD vs SRS. For the pitch that comes before a PRD, see the product one-pager template. For the plan PRDs fit into, see the product roadmap template. For writing acceptance criteria, see acceptance criteria examples. For writing user stories, see the user story template.
Frequently asked questions
- What is a product requirements document?
- A document that defines what a product or feature should do: its purpose, the users and problems it serves, its requirements, and how success will be measured. Atlassian describes it as a single source of truth that keeps product, design, engineering, and stakeholders aligned.
- What sections should a PRD include?
- A header with participants, status, and target release; goals and business objectives; background and strategic fit; assumptions; user stories; requirements; design links; open questions; and what you're not doing. Add success metrics so the team knows what done means.
- How long should a PRD be?
- As short as it can be while answering what, who, and why. One or two pages, with links to research, designs, and tickets, is common. A PRD that specifies every detail before work starts is an anti-pattern in Atlassian's guidance.
- What is the difference between a PRD and a technical spec?
- A PRD covers what to build and why, from the user's side. A technical design document covers how engineering will build it: architecture, data model, APIs, and trade-offs. Product writes the PRD first; engineering writes the design doc in response.
- Can I use this PRD template in Google Docs, Word, or Notion?
- Yes. The template below is plain headings and tables, so it pastes into Google Docs, Word, Notion, or Confluence. Confluence also has a built-in product requirements template with a similar structure.
Keep reading