# Product requirements document template

Replace bracketed placeholders with your evidence and decisions. Keep unresolved items explicit.

## Problem and evidence

[Your answer] Name the affected user, observed problem, source and date. Separate measured evidence from assumptions.

## Outcome and measurement

[Your answer] Define the intended outcome, baseline, target, denominator and measurement owner. Mark unknown baselines for investigation.

## Scope and non-goals

[Your answer] Define the first usable slice and explicitly deferred work. Record the tradeoff behind each boundary.

## Users and permissions

[Your answer] Describe who may perform the action and what data each role may access. Include denied-access behavior.

## Requirements and acceptance criteria

[Your answer] Assign stable IDs and write observable behavior for the happy path, boundary and failure cases.

## Experience and edge cases

[Your answer] Show the entry point, loading state, successful outcome and recovery actions. Define empty and oversized requests.

## Dependencies and feasibility

[Your answer] Identify upstream systems, owners, constraints and the questions that could change scope.

## Risks and mitigations

[Your answer] Record risks, evidence, mitigation owners and the condition that blocks release.

## Rollout and release decision

[Your answer] Define test evidence, pilot users, monitoring, pause conditions and the accountable release owner.

## Open questions and change history

[Your answer] List unresolved decisions with an owner and due point. Record what changed, why and affected requirements.

## Acceptance review

### R-01
[Observable behavior]
[Given / when / then, including a boundary or failure case]
[Rationale or source]

## Reading and review
Adapt this original teaching template to your team. Guidance checked November 9, 2026.
https://www.atlassian.com/agile/product-management/requirements
https://owasp.org/www-community/attacks/CSV_Injection