PRODUCT REQUIREMENTS DOCUMENT — BLANK TEMPLATE
Original planning resource, 2026-10-27.
Keep detail proportional to the change and its uncertainty.

DOCUMENT CONTROL
Title / owner / status / version / review date:
Decision participants and responsibilities:
Links to related roadmap outcome and technical notes:

PURPOSE
Who is the intended user?
What situation or task is difficult today?
Why is this worth addressing now?
What change in the user's outcome do we hope to observe?

EVIDENCE
Permitted source / date / context:
Observed behavior or need:
Interpretation:
What remains unknown?
Avoid invented quotes, unsupported prevalence claims, or unlabelled examples.

GOALS
Result this release should make possible:
How the later customer outcome will be investigated:

NON-GOALS
Explicitly excluded behavior:
Why each boundary matters:
What would justify revisiting it?

USER STORY
As [relevant role in a situation], I want [capability] so I can [result].
Starting state:
Main sequence:
Expected result:

BEHAVIOR AND EDGE CASES
Eligibility / server-side authorization:
Input and selection validation:
Empty state:
Unavailable dependency:
Failure and retry:
Account switching or lost access:
Data retention / logging exclusions:
Accessibility requirements relevant to the workflow:

ACCEPTANCE CRITERIA
AC1: given [state], when [action], then [observable result].
AC2: forbidden or invalid request and expected result.
AC3: empty or missing-data case and expected result.
AC4: failure and recovery case.
AC5: retry or duplicate request case, if relevant.
Synthetic fixture and exact expected values:
Reviewer / evidence location / intended environment:

CONSTRAINTS AND OPEN QUESTIONS
Platforms / supported formats / scale boundary:
Question / responsible owner / decision date:
Do not bury unresolved product behavior in implementation assumptions.

RELEASE CONTROLS
Owner / approver / pilot audience:
Checks before exposure:
Observation definitions / excluded payloads:
Stop conditions:
Recovery for actions that already happened:
Compatibility with the existing path:
Temporary flag cleanup condition, if relevant:

REVIEW
How will we investigate whether the change helps?
Which observations are acceptance evidence versus later outcome evidence?
Decision log: date / decision / reason / affected criteria / owner.
Final reviewer record and remaining limitations: