Project Manager Roadmap Sheet Template: 12 Columns and a Filled Example
9 min read ยท 2026-11-15
A good project manager roadmap sheet template has one row per deliverable or milestone and twelve columns: ID, Phase, Workstream, Item, Owner, Start, End, Status, Priority, Depends on, Risk and notes, and Exec view. The first ten run the project day to day. The last two let the same sheet serve your team and your sponsor.
This guide gives you the header row and five filled example rows to paste into Google Sheets or Excel. It explains each column, walks through a 24 week CRM rollout, and shows how to filter one master sheet for leadership, a client or the team.
The roadmap at a glance
Goal: Roll out a new CRM to a sales team, from scope to handover, with a roadmap sheet that the team updates weekly and leadership reads in one page. Duration: 24 weeks
Discovery and scope (Weeks 1-3)
Agree on what the project delivers, who approves it and what is out of scope.
- Interview the sales lead, IT lead and finance owner about current pain points.
- List the processes the CRM must cover at launch and the ones that wait.
- Write the scope statement and get it approved by the sponsor.
- Create the roadmap sheet and fill the first rows for every phase.
Milestone: Scope statement approved by the sponsor.
Design and configuration (Weeks 4-8)
Turn the scope into a configured system that matches how the team sells.
- Map the sales stages, fields and required data for each record.
- Configure pipelines, user roles and permissions.
- Define the email and calendar integrations with IT.
- Hold a design review with two senior sales reps.
Milestone: Design review signed off, configuration frozen.
Data migration (Weeks 9-13)
Move clean data from the old tools into the new CRM.
- Export contacts, accounts and open deals from current sources.
- Remove duplicates and fix missing owners.
- Run a test import, check a sample of records, then fix the mapping.
- Run the final import into the production environment.
Milestone: Data accuracy check passed on the sample agreed with the sales lead.
Pilot (Weeks 14-17)
Prove the system works with a small group before everyone depends on it.
- Pick a pilot group from one sales team.
- Run daily work in the CRM for three weeks.
- Log issues in the sheet's Risk and notes column and fix the blocking ones.
- Decide go or no go with the sponsor.
Milestone: Go decision recorded by the sponsor.
Rollout and training (Weeks 18-22)
Bring every user onto the CRM and retire the old tools.
- Schedule training sessions by team.
- Publish a short how to guide for the most common tasks.
- Switch the remaining teams in two waves.
- Set the old tools to read only.
Milestone: All users active, old tools read only.
Close and handover (Weeks 23-24)
Hand the system to its long term owner and close the project.
- Transfer admin rights and documentation to the operations owner.
- Run a lessons learned session.
- Present the final roadmap status to the sponsor.
Milestone: Handover accepted and project closed.
The columns of a project manager roadmap sheet template
Every column should answer a question someone asks in a status meeting. If nobody asks it, the column is noise. Here is what goes in each of the twelve.
- ID: a short code like R01, R02. It lets you reference dependencies without retyping item names.
- Phase: one of your phases, picked from a dropdown so spelling stays consistent.
- Workstream: the track the item belongs to, such as Data, Integrations, Training or Governance.
- Item: the deliverable or milestone, written as an outcome ("Pipeline stages configured"), not an activity.
- Owner: one named person. Two names means nobody owns it.
- Start and End: real date cells, so you can sort, filter and draw bars.
- Status: a fixed list such as Not started, On track, At risk, Blocked, Done.
- Priority: High, Medium or Low, used to decide what slips first.
- Depends on: the IDs that must finish before this item starts, separated by a space.
- Risk and notes: the one line reason behind any At risk or Blocked status, or behind a date that moved.
- Exec view: a checkbox (TRUE or FALSE) that marks the rows leadership should see, usually milestones and anything at risk.
The header row and example rows, ready to paste
Copy the six lines below. In Google Sheets, paste them into cell A1, then use Data, Split text to columns, with comma as the separator. In Excel, paste them into column A, then use Data, Text to Columns, Delimited, Comma.
The example dates assume week 1 starts on Monday 4 January 2027. Replace them with your own start date and keep the same week spacing.
- ID,Phase,Workstream,Item,Owner,Start,End,Status,Priority,Depends on,Risk and notes,Exec view
- R01,Discovery,Governance,Scope statement approved,Sponsor,2027-01-04,2027-01-22,Done,High,None,None,TRUE
- R02,Design,Configuration,Sales stages and fields mapped,Sales ops lead,2027-01-25,2027-02-05,Done,High,R01,None,FALSE
- R03,Design,Integrations,Email and calendar sync defined,IT lead,2027-02-08,2027-02-19,At risk,High,R02,Waiting for security review,TRUE
- R04,Design,Governance,Design review signed off,Project manager,2027-02-22,2027-02-26,Not started,High,R02 R03,Exposed if R03 slips,TRUE
- R05,Migration,Data,Duplicates removed from contact export,Data analyst,2027-03-01,2027-03-19,Not started,Medium,R04,None,FALSE
How to read the example rows
Read the rows as a chain. R04, the design review, depends on R03. R03 is At risk because the security review has not happened. Because both rows have Exec view set to TRUE, a sponsor who opens the leadership view sees the risk and the milestone it threatens side by side. That link between a working detail and a leadership milestone is why the Depends on and Exec view columns earn their place.
R02 and R05 stay FALSE. They matter to the team, but leadership has no decision to make on them.
Project roadmap template in Google Sheets: setup step by step
Google Sheets works well when several people update the roadmap and the sponsor wants a link instead of an attachment.
For a visual bar per item, add one column per week to the right of Exec view. Use conditional formatting with a custom formula that fills a cell when its week falls between Start and End. Without these bars, the sheet stays a list, which is fine for the team but hard to read in a steering meeting.
- Paste the header row and freeze it (View, Freeze, 1 row).
- Add dropdowns for Phase, Status and Priority with Data, Data validation, so values stay consistent.
- Select the Exec view column and use Insert, Checkbox. Cells that read TRUE become ticked boxes.
- Format Start and End as dates and set data validation to reject anything that is not a valid date.
- Add conditional formatting so At risk turns amber and Blocked turns red.
- Create one filter view per audience: "Leadership" shows rows where Exec view is TRUE, "Team" shows everything.
Roadmap project management template in Excel
Excel suits teams that work offline, need print layouts or already keep budgets in workbooks. Convert the range to a table (Format as Table) so new rows inherit dropdowns and formatting, and use Data Validation for the same lists as in Sheets. Excel also has Insert, Checkbox in current Microsoft 365 versions; in older versions, keep TRUE and FALSE as text and filter on them.
For a timeline, a common approach is a stacked bar chart: the first series is the start date with no fill, the second is the duration in days. It looks like a Gantt chart. Using the table as the chart source means new rows appear in the chart without editing its data range.
Whichever tool you pick, a spreadsheet has the same limits. A sheet is a strong working tool and a weak slide. Plan for that before the first steering meeting.
- No visual layout by default: phases and milestones are rows, not a picture.
- Every change is manual, including moving dependent dates when one item slips.
- Hidden columns and merged cells break easily when someone else edits.
- Exports cut wide sheets across several pages unless you set the print area.
Choosing a time scale for the sheet
The same rows can run on different time scales. Pick the one that matches how certain your dates are, and change the columns to match.
You rarely need several sheets. One master sheet plus a filtered view per audience covers most projects, and nobody has to keep copies in sync.
- Week dates: best for delivery projects with fixed deadlines, like the CRM example. Keep Start and End as dates.
- Quarters: best for a portfolio or a year long program. Replace Start and End with a single Quarter column (Q1, Q2).
- Now, Next, Later: best when scope is still moving. Replace dates with a Horizon column and commit only to Now.
- Phase summary: one row per phase with its milestone, for people who read for two minutes.
Filtering the sheet for leadership, a client or your team
The full sheet is for the people doing the work. Other readers need fewer columns, framed around their decisions.
For leadership, use the Leadership filter view and hide Workstream, Owner and Depends on unless a decision depends on them. What remains is Phase, Item, End, Status and Risk and notes: the milestone, when it lands, and what you need from them.
For a client, duplicate the tab, delete internal rows such as Governance, and show deliverables, approval points and the dates their input is due. Group dates by month rather than week so small internal shifts do not trigger questions.
For your team, keep every column, sort by End, and review the At risk and Blocked rows first in each weekly meeting. For a PMO or portfolio review, add a Project column as column A and stack several roadmaps in one tab, so one filter shows every at risk milestone across projects.
How to export or share the sheet without breaking it
Many roadmap sheets look fine on the author's screen and broken in the reader's inbox. A few settings prevent that.
- In Google Sheets, apply the Leadership filter view, then File, Download, PDF. Choose landscape, Fit to width, and turn on repeat frozen rows.
- In Excel, set the print area, use Page Layout, Print Titles for the header row and scale to one page wide.
- When sharing a link, give view access to readers and keep edit access to owners, so nobody sorts the master sheet by accident.
- Put the date of the last update in the sheet title, so readers know how fresh the status is.
Common mistakes to avoid
- Writing activities like "Work on integrations" as items hides progress, so write outcomes like "Email sync live in test" that you can mark Done.
- Leaving Status as free text breaks filters, so use a fixed dropdown list.
- Assigning two owners to one row leaves nobody accountable, so pick one name and list helpers in notes.
- Sending the full team sheet to leadership buries the decision you need, so send the filtered view.
- Skipping the Depends on column hides knock on delays, so link every row that waits on another.
- Updating dates without noting why erodes trust, so add one line in Risk and notes each time a date moves.
Frequently asked questions
What should a project roadmap template include?
At minimum: item, phase, owner, start and end dates, status and priority. Adding dependencies and a risk note lets you explain delays instead of only reporting them. An Exec view flag makes the same sheet usable in steering meetings.
Is there a project roadmap template for Google Sheets?
Yes. Paste the header row above, split it into columns, then add dropdowns for Phase, Status and Priority, checkboxes for Exec view and a filter view per audience. Conditional formatting on week columns gives you simple timeline bars.
What is the difference between a project roadmap, a project plan and a Gantt chart?
In a sheet, the roadmap is the rows you would show leadership, the plan is every task behind them, and a Gantt chart is one way to draw either as dated bars.
How often should a project manager update the roadmap sheet?
Weekly works for most delivery projects, ideally right before the team meeting. Update status and dates as they change, and refresh the leadership export before each steering review.