Skip to main content
Product Management9 min

Quarterly Roadmap Google Sheets Template (Q1-Q4)

Free Google Sheets quarterly roadmap template covering Q1-Q4 planning. Includes theme columns, dependency tracking, and color-coded status formulas.

Published 2026-05-07
Share:
TL;DR: Free Google Sheets quarterly roadmap template covering Q1-Q4 planning. Includes theme columns, dependency tracking, and color-coded status formulas.
Free PDF

Get the Product Ops Setup Checklist

A printable 1-page checklist you can pin to your desk or share with your team. Distilled from the key takeaways in this article.

or use email

Join 10,000+ product leaders. Instant PDF download.

Want full SaaS idea playbooks with market research?

Explore Ideas Pro →

Why a Quarterly Roadmap Format

Quarterly is the right altitude for most product roadmaps. Monthly is too granular. The plan changes faster than you can publish it. Annual is too vague. By the time you commit to a year of work, the second half is fiction. Quarterly hits the middle. Long enough to plan a meaningful chunk of work, short enough that the plan still resembles reality at the end.

This guide shows how to build a Q1-Q4 roadmap in Google Sheets with theme columns, dependency tracking, and color-coded status. If you are coming from a different format, the Google Sheets roadmap template guide covers the foundational setup, and the agile roadmap in Google Sheets walkthrough covers sprint-based variations. You can browse Google Sheets roadmap templates for ready-made versions to copy.

For the underlying methodology of quarterly planning, see the guide to building a product roadmap and the features timeline roadmap type.


Step 1: Set Up the Spreadsheet Layout

Create a single tab called "Quarterly Roadmap." Add a second tab called "Backlog" for items not yet promoted to a quarter. A third tab called "Snapshot" gets duplicated at the end of each quarter to preserve history.

The Quarterly Roadmap tab uses a wide format. Each initiative is a row. Each quarter is a column block. Themes get their own column for filtering.

Set the year context at the top. Cell A1: "Product Roadmap 2026." Freeze row 1 (View > Freeze > 1 row) and the first column (View > Freeze > 1 column) so headers stay visible as you scroll.


Step 2: Define the Core Columns

Before the quarter blocks, you need metadata columns that describe each initiative.

ColumnPurposeExample
InitiativeName of the work"Self-serve onboarding redesign"
OwnerWho drives it"Alex (PM)"
ThemeStrategic bucket"Activation"
StatusCurrent state"In Progress"
PriorityTier"P0"
Effort (T-shirt)Size estimate"L"
ImpactExpected business value"High"
DependencyBlocking initiative"Auth refactor (Q1)"
NotesContext, linksFree text

Set up dropdown menus for Theme, Status, Priority, Effort, and Impact (Data > Data validation > Add rule > Dropdown). This keeps filtering reliable and prevents the "In Progress" vs "In progress" vs "WIP" inconsistencies that break formulas later.

For the Theme column, define the categories at the start of the year and keep them stable. Common themes: Activation, Retention, Growth, Platform, Tech Debt, Compliance. The strategy roadmap type covers how to choose themes that align with company strategy.


Step 3: Build the Quarter Columns

Add four column blocks after the metadata columns: Q1, Q2, Q3, Q4. Each block can be one column (just an X marker) or four sub-columns (one per month) if you need finer granularity.

Simpler to read and maintain. Each cell takes one of:

  • Empty (nothing planned)
  • "X" (planned)
  • "In Progress"
  • "Shipped"
  • "Slipped" (planned but did not happen)

Apply conditional formatting to color-code:

  • X (Planned) → Light blue
  • In Progress → Yellow
  • Shipped → Green
  • Slipped → Red

This gives you a one-glance read across the year. An initiative that spans multiple quarters has the same status marker in each quarter cell until it ships.

Four sub-columns per quarter (advanced)

Use if your team needs month-level granularity. Each quarter becomes Jan/Feb/Mar columns. Same status values, same conditional formatting. The trade-off is the sheet gets wide fast (12 quarter columns + 9 metadata = 21 columns) and stops fitting on a laptop screen.

Most teams start with single-column quarters and add granularity only if they need it.


Step 4: Add Theme-Based Grouping

Themes are the reason quarterly roadmaps exist at the strategic level. Without themes, a quarterly roadmap is just a feature list with quarter columns.

Create a theme summary section

Above the data rows, add a 5-row summary block:

ThemeQ1 ItemsQ2 ItemsQ3 ItemsQ4 Items
Activation4322
Retention2433
Growth3345
Platform2222

The formula in the Q1 Items column:

=COUNTIFS(ThemeColumn, "Activation", Q1Column, "<>")

This shows how investment is distributed across themes per quarter. If "Tech Debt" has 0 items in 4 consecutive quarters, that is a signal. If "Activation" gets 80% of Q1 and 0% of Q3, that is also a signal.

Sort and filter by theme

Use a filter view (Data > Create a filter view) for each theme. Save the filter as "Activation Roadmap" or "Platform Roadmap" so the engineering lead for that theme has a clean view without seeing the rest. Multiple people can use different filter views simultaneously without affecting the underlying sheet. This is one of Google Sheets' best features for shared roadmaps.

For more on theme-based planning, see 50 product roadmap best practices and the strategy guide.


Step 5: Track Dependencies

Dependency tracking is where most quarterly roadmaps fail. The fix is structural: make dependencies explicit, in their own column, with a check formula.

The Dependency column

Each row's Dependency column lists the initiative that must ship before this one can start. Most rows will be empty. The ones that are not are the most important rows on the sheet.

Add a Dependency Status column with this formula:

=IF(H2 = "", "None", IFERROR(VLOOKUP(H2, A:E, 5, FALSE), "Missing"))

Where H2 is the Dependency column and the VLOOKUP pulls the Status of the parent initiative from column A and E. The result tells you, for each dependent initiative, whether the blocker is "Shipped" (proceed), "In Progress" (at risk), or "Missing" (typo or wrong reference).

For complex dependency graphs, see the dependency management glossary entry for the underlying methodology.

Use a separate dependencies tab if needed

If your roadmap has more than 10 dependencies, build a separate Dependencies tab with two columns: Initiative, Blocked By. Use this tab as the lookup source for the Dependency Status formula. The Dependencies tab also makes it possible to model dependencies that involve cross-team work, which the flat Dependency column cannot.


Step 6: Color-Code by Status

Conditional formatting turns the wall of text into a heat map. Apply formatting in this order so the rules layer correctly.

Status (highest priority)

Select the four quarter columns. Format > Conditional formatting > Add rule.

  • Shipped → Green background, white text
  • In Progress → Yellow background, black text
  • Planned (X) → Light blue background, black text
  • Slipped → Red background, white text

Priority (apply to Priority column only)

  • P0 → Red text, bold
  • P1 → Orange text
  • P2 → Default text
  • P3 → Gray text

Theme (optional, apply to row)

If your team thinks in themes more than priorities, apply a faint background color to each row based on Theme. Use the "Custom formula is" option:

=$C2 = "Activation"

Apply to A2:Z2 (the full row), not just the Theme column. Repeat for each theme with a different pastel color. Pastel matters. Saturated colors compete with the status colors and create noise.


Step 7: Run the Quarterly Cadence

The roadmap is only as useful as the cadence around it.

  • Weekly (15 min): Update Status on in-progress items. Move Shipped items. Flag blockers.
  • Monthly (30 min): Review the theme summary. Are themes drifting from the plan? Have new dependencies emerged?
  • Quarterly (90 min): Lock the snapshot. Move shipped items to a "Done" tab. Re-rank backlog items. Commit the next quarter.

Quarterly planning workflow

At the end of each quarter, before locking the snapshot:

  1. Review what shipped vs what was planned: For each initiative marked "X" in the closing quarter, was it Shipped, In Progress, or Slipped?
  2. Calculate hit rate: What percent of planned items shipped? Most teams average 60-75%.
  3. Snapshot: Right-click the Quarterly Roadmap tab > Duplicate. Rename "2026 Q1 Snapshot." This freezes the plan as it was at quarter close.
  4. Promote backlog items: Move next quarter's items from the Backlog tab into the active roadmap.
  5. Reset the cycle: Update the year context if needed. Confirm themes are still right.

This cadence is the same one we cover in 50 product roadmap best practices. The snapshot ritual is the part most teams skip and the part that pays the most dividends a year later when someone asks "when did we deprioritize feature X?"


When This Format Stops Working

A quarterly Google Sheets roadmap works for teams up to about 50 people managing one product. Beyond that, you will hit:

  • Cross-team dependencies that flat columns cannot model
  • Multiple product lines that need separate quarterly views
  • Stakeholders who need filtered, role-specific views

If those frictions are real, the PM Tool Picker helps match your team to a dedicated tool. Most teams that switch keep the spreadsheet for executive presentations because the quarterly grid pastes cleanly into a slide deck. Dedicated tools rarely export that well.

For other formats, see the Now/Next/Later roadmap type (better for teams that want to avoid date commitments) and the portfolio roadmap type (for multi-product organizations).

Sources

  • Google Sheets formula reference (Google Workspace Learning Center)
  • "Escaping the Build Trap" by Melissa Perri (O'Reilly, 2018)
  • Atlassian Agile Coach: Roadmaps

Frequently Asked Questions

Should I plan all four quarters or just the next one?+
Plan the next two quarters in detail. Sketch the third and fourth quarters at the theme level. Anything more specific than "Activation work in Q3" for Q3 and Q4 is fiction. The point of a quarterly roadmap is to commit to what you can see clearly. Q1 and Q2 should have specific initiatives. Q3 and Q4 should have theme bets.
How do I handle initiatives that span multiple quarters?+
Mark the same initiative in every quarter it spans. The Status column reflects the overall state. The quarter cells reflect which quarter the work is happening in. An initiative that runs Q1 to Q3 has "X" or "In Progress" in all three quarter columns until it ships, then "Shipped" in the quarter it shipped and the previous quarters keep their planning marker for historical context.
What is the right number of initiatives per quarter?+
5-10 initiatives per quarter for a team of 8-15 people. Less than 5 means the initiatives are too big and progress will not be visible. More than 10 means you are tracking work that should live in the [Sprint Planning Template](/templates/sprint-planning-template) instead. Quarterly roadmap items should be initiative-sized, not story-sized.
How do I share the roadmap with executives without confusing them?+
Create a separate filter view called "Executive Summary" that hides the Backlog tab, hides the metadata columns (Owner, Effort, Notes), and shows only Initiative, Theme, Q1, Q2, Q3, Q4. Apply heavy conditional formatting so the view is mostly color blocks. Executives consume colors and headlines, not metadata. Save the filter view and share the URL with the filter parameter pre-applied.
Free PDF

Get the Product Ops Setup Checklist

A printable 1-page checklist you can pin to your desk or share with your team. Distilled from the key takeaways in this article.

or use email

Join 10,000+ product leaders. Instant PDF download.

Want full SaaS idea playbooks with market research?

Explore Ideas Pro →

Recommended for you

Keep Reading

Explore more product management guides and templates