Product requirements document

It is free to fill in online, needs no account, and downloads as a Word document or a PDF. See all IT and projects templates

• Product or feature name

  For example: Saved reports

• Product owner

  For example: Hana Kobayashi, Product manager

• Status

  For example: Draft for review

• Last updated

  For example: 10 June 2030

• The problem

  Say who has the problem and how we know.

  For example: Customers rebuild the same report every week. Support gets 40 requests a month asking how to save one.

• Who it is for

  One group per line.

  For example: Team leads who run weekly reports. Admins who share reports with their team.

• Goals

  One goal per line, with a number where you can.

  For example: Cut the time to produce a weekly report from 15 minutes to 2 Reduce support questions about reports by half

• What this will not do (optional)optional

  Saying no here avoids arguments later.

  For example: No scheduled email delivery in this version No changes to the export format

• Requirements

  One row for each requirement.

  For example: Must | A user can save the current filters as a named report Must | A saved report can be opened in one click Should | A report can be shared with a team Could | A report can be duplicated

• Main user flow

  Describe the main path in a few steps.

  For example: The user sets filters, selects Save, names the report and confirms. The report appears in a list on the reports page.

• Design and content notes (optional)optional

  For example: Designs are in the shared design folder, page 4. Use the existing list style.

• How we will know it worked

  Pick measures and a date to check.

  For example: Time to a weekly report under 3 minutes for 70 percent of users within 60 days. Support questions on reports down by 50 percent.

• Risks and open questions (optional)optional

  One per line.

  For example: Large reports may be slow to open. We need to decide how many saved reports one user may keep.

• Dependencies (optional)optional

  For example: Data team to confirm filter names. Legal to review sharing between teams.

• Launch plan

  For example: Beta with 20 customers in July, everyone in September

1. 11. Problem
2. 22. Who it is for
3. 33. Goals
4. 44. What this will not do
5. 55. Requirements
6. 66. Main user flow
7. 77. Design and content notes
8. 88. Success measures
9. 99. Risks and open questions
10. 1010. Dependencies
11. 1111. Launch plan

1. 01

   Fill in

   Type your details in the form. The document fills itself in as you type; click any gap to jump to its field.

2. 02

   Check

   Read it through. Gaps you have not filled stay marked, so nothing goes out half done.

3. 03

   Download

   Save it as a Word document to edit further, or as a PDF to send or print.

What details does this template ask for?

The form asks for 15 details, starting with Product or feature name, Product owner, Status, Last updated, The problem. 4 more are optional.

Can I download this template as Word or PDF?

Yes. When you have filled in the form, save it as a Word document to keep editing, or as a PDF to send or print. It is free and needs no account.

Is what I type sent anywhere?

No. What you type stays in your browser while you fill in the document. It only goes to nerix if you choose to open the template in the chat.

Are these IT and project templates free?

Most are. Fill in and download them for free as Word or PDF, with no account. A few longer documents are premium: free to fill in, paid once to download, and marked with their price.

Does a security policy make us secure?

No document does that alone. A policy helps when it matches what people really do, so keep it short, explain it to your team and review it every year.

Is a project charter only for large projects?

No. A small project benefits too, because one page that names the goal, the limits and the decision maker prevents most arguments later.

• API integration specificationSpecify how two systems connect: what data moves, how it is secured, how errors are handled and who owns it.IT and projects
• Architecture decision recordRecord a technical decision with its context, options, reasons and consequences, for the team to find later.IT and projects
• Bring your own device policySet the rules for using personal phones and laptops for work: security, privacy, support and leaving.IT and projects
• Bug reportReport a software problem so a developer can repeat it, judge its impact and fix it.IT and projects
• Change management planPlan how people will be told, trained and supported through a big change, and how you will know it worked.IT and projects
• Change requestAsk for a change to a project or system, show its impact and record whether it is approved.IT and projects

See all IT and projects templates