How to write a PRD: a practical template with a worked example
Write a product requirements document around the problem, user flow, testable behavior, release boundaries and decisions still open.
A product requirements document, or PRD, explains the problem, intended users and behaviour a product or feature should deliver. It should connect the reason for building something to requirements the team can discuss and test. A long list of screens is not enough if nobody knows what outcome those screens are meant to produce.
Atlassian's PRD template includes objectives, success metrics, assumptions, user stories, supporting designs, open questions and exclusions. The structure below is our own compact starting point based on those planning needs. You can use it in an ordinary document; no specific project-management product is required.
A reusable PRD structure
1. Context and ownership
Name the feature or release, document owner, current status and people who make product and technical decisions. Distinguish a target date from a committed delivery date. Record when a consequential decision changes.
2. Problem and evidence
Describe who has the problem, when it occurs and how they handle it now. Link to research or operational evidence where you have it. Label assumptions rather than turning them into statements such as "all customers need this."
3. Goal and success measures
State the improvement you seek and how you will observe it. Separate a target from a result already achieved. If no baseline exists, say how you plan to establish one.
4. Users and permissions
List the relevant user types and their jobs. Explain who may view, create, change or approve important records. Avoid relying on a role name such as "staff" without describing its scope.
5. Release boundaries
List the first-release requirements, later ideas and explicit exclusions. The first release should form a coherent workflow, not an arbitrary collection of partially connected features.
6. Main flow and exceptions
Write the normal sequence in numbered steps. Then describe important failures and alternative paths: unavailable item, conflicting update, missing permission or interrupted external service. A screen design can support this section but should not replace the explanation.
7. Testable requirements
Give important requirements stable identifiers. State the conditions, expected behaviour and observable result. Atlassian's product-specification guide also describes functional specifications through workflow, inputs, outputs and how users know they succeeded.
8. Dependencies, constraints and open questions
Name the platforms, integrations, data sources and decisions the work depends on. Give each unresolved question an owner. A statement such as "payment provider to be decided" is a dependency, not a completed payment requirement.
9. Release and review plan
Describe who receives the first release, how feedback will be collected and who decides what happens next. Keep this proportionate: a small internal pilot may need a different plan from a broad consumer release.
A worked example: equipment reservations
The following example is fictional and deliberately limited. It illustrates document structure, not a production architecture.
Problem. Workshop members coordinate shared equipment through messages, leaving uncertainty about which requests are confirmed.
Goal. Make the confirmation state visible to members and staff. Establish a baseline for unresolved requests, then choose a realistic improvement target before the pilot.
Users. A member requests or cancels their own reservation. A coordinator manages availability and resolves exceptions for the workshop they support.
First release. Members see published availability, submit a request and receive a confirmed or declined outcome. The coordinator can review the reservation list.
Excluded. Payments, public reviews, cross-workshop sharing and automated demand forecasting.
Main flow. The member chooses equipment and an interval, reviews the request, submits it and sees the server's result. A conflict does not produce a false confirmation.
Requirement R-01. When two otherwise valid requests would create conflicting confirmed reservations for the same item, the server permits only one conflicting confirmation and returns a clear outcome to the other requester. Define the booking and approval model with the technical team before implementation.
Requirement R-02. A member cannot change another member's reservation merely by submitting its identifier. The coordinator's access is limited to the agreed workshop scope.
Open question. Does confirmation happen immediately or after coordinator approval? Product owner to decide before the booking flow is estimated as final.
Pilot review. Review observed request outcomes and user feedback before adding automation or more locations.
Replace vague requirements with observable ones
"The app should be easy" does not tell a tester what to check. Nor does "use modern technology" explain the outcome the business needs.
Prefer statements about a concrete action and result. If the requirement concerns performance, define the operation, test conditions and threshold with the team. If it concerns usability, identify the task and how the team will evaluate it. Do not invent a universal tap count because it looks precise.
A requirement can still leave a technical design choice open. The PRD should make that decision visible rather than disguising uncertainty as finished specification.
Review the document before requesting a final estimate
Ask the designer, developer and relevant operational owner to mark each section clear, unclear or dependent on another decision. Resolve the consequential gaps or state how the quote treats them.
Keep the PRD current when approved scope changes. A polished document that no longer describes the agreed release is less useful than a short record everyone can trust.
By Omnistu. Reviewed 16 November 2026. Template, identifiers and equipment example are illustrative; no delivery outcome or customer result is claimed.