Templates

PRD Template for Google Docs (Free, Copy-Ready)

A copy-ready product requirements document template for Google Docs, how to fill it in well, and how to keep PRDs next to the designs and specs they depend on.

Eric Dunaway
Eric Dunaway
Spaceli
4 min read

A product requirements document (PRD) explains what you're building, for whom, and why, so design, engineering and the rest of the team can make good decisions without asking the PM every time. A good PRD is short: problem, goals, scope, requirements, open questions. Below is a copy-ready template for Google Docs, notes on filling it in, and how to keep PRDs next to the designs and specs they depend on.

The PRD template

Copy this into a new Google Doc and use heading styles for each section, so the outline and links to sections work.

PRD template
# [Feature name]

Owner: [PM]  ·  Status: Draft / In review / Approved / Shipped
Team: [design, engineering leads]  ·  Target: [quarter or date]
Last updated: [date]

## Summary
Two or three sentences: what we're building and why now.

## Problem
Who has the problem, how we know (data, quotes, tickets),
and what it costs them today.

## Goals and success metrics
- Goal: ...  ·  Metric: ...  ·  Target: ...

## Non-goals
What this project deliberately won't do.

## Users and use cases
- As a [user], I want to [action] so that [outcome].

## Requirements
| # | Requirement | Priority (Must/Should/Could) | Notes |

## Design
Links to designs, prototypes and flows.

## Open questions
| Question | Owner | Due | Answer |

## Rollout
Phases, feature flags, who's told when.

## Changelog
[date] - what changed and why.

How to fill it in well

  • Start with the problem, not the solution. If the Problem section is weak, the rest will be argued about forever.
  • Make goals measurable. "Improve onboarding" isn't a goal; "cut time to first project from 3 days to 1" is.
  • Write the non-goals. They prevent more scope creep than any requirement.
  • Prioritize requirements. Must, Should, Could. If everything is a Must, nothing is.
  • Link, don't paste. Link designs, research and specs instead of copying screenshots that go stale.
  • Keep open questions visible. Each with an owner and a due date; move the answer into the doc when it's settled.
  • Use comments for discussion, the doc for decisions. Resolve a comment thread by updating the text.
  • Keep it short. Two to five pages for most features. If it's longer, split it.

Where PRDs should live

Keep all PRDs in one Product folder, one subfolder per area, with the status in the doc and shipped PRDs moved to an Archive folder. That way anyone can browse what's planned, in progress and done.

The harder part is that a PRD is only half the story. The designs are in Figma, the flows in Miro, the walkthrough in Loom, the metrics in a Sheet. (More on keeping designs, boards and docs in one place.) Spaceli puts them in one place:

  • Your Product folder becomes a space. Every PRD gets a sidebar, a table of contents and Cmd+K search.
  • Designs next to the PRD. Add a Figma, Miro, Whimsical or Loom embed as a page right next to the PRD in the sidebar, or paste its embed code into the Google Doc to show it inside the page.
  • Sheets and Slides open inside. Metrics sheets and review decks in the folder open right in the space.
  • Link to any section. Link straight to the Requirements or Open questions of another PRD.
  • Edit in place. Open the Google Docs editor right inside Spaceli, with changes synced to Drive.
  • Copy as Markdown. Paste a PRD into an AI tool or a ticket as clean Markdown.

FAQ

What's the difference between a PRD and a spec?

A PRD describes the problem, goals and requirements: what and why. A technical spec or RFC, usually written by engineering, describes how it will be built. For the engineering side, see our engineering documentation templates.

Who writes the PRD?

Usually the product manager, with design and engineering leads reviewing it before work starts.

Do small features need a PRD?

A short one. For small changes, the Summary, Problem and Requirements sections in a single page are enough.

Eric Dunaway
Written by Eric Dunaway

Writes about wikis, documentation and how teams keep their knowledge easy to find.

Share

Your knowledge base is already in Google Drive.

Give your team a better way to organize, find, and share knowledge. Keep your documents right where they are.

Start for Free

Free during the beta. Get started in about a minute.

Spaceli only accesses the folders you choose.