How to Create a Roadmap in SharePoint with Microsoft Lists

You need one place where people can answer three questions without opening five project tools:

• What are we trying to deliver?
• What stage is it at?
• What needs attention next?

SharePoint can do that job well when the roadmap is a lightweight portfolio view, not a disguised project-scheduling system.

The practical pattern is one Microsoft List as the source of truth, several views for different conversations, and a modern SharePoint page that gives the roadmap context. You can build it without pretending JSON formatting calculates dependencies or that every task belongs in the roadmap.

The short answer

SharePoint does not have a special “roadmap” object.

Create a list in SharePoint, give each item an owner, outcome, phase, status and target date, then use:

• Grid view to maintain the data;
• Board view for a phase or status conversation;
• Calendar view for time-based commitments;
• optional formatting to make risks and stale updates visible;
• a modern page to explain decisions, ownership and update rules.

Use Planner for detailed team tasks when that is the real requirement. The Planner web part can show a board or charts on a SharePoint page, but Microsoft limits it to group-connected team sites. A task board and a portfolio roadmap solve different problems.

Also remove Viva Goals from any new design. Microsoft retired Viva Goals on 31 December 2025.

Decide what one roadmap row means

Do this before creating columns.

For most small portfolios, one row should represent an initiative, product change, workstream or meaningful outcome. It should not represent every task.

A useful row might be:

Replace the manual supplier-onboarding spreadsheet with an approved request process.

A weak row would be:

Email Sarah.

The first belongs on a roadmap because a leader can make a priority, funding or risk decision from it. The second belongs in Planner, Microsoft To Do or the delivery team's normal work system.

Use this test: would an owner reasonably report this item at a monthly portfolio meeting? If not, it is probably too small for the roadmap.

Build the list

On the SharePoint site that owns the portfolio, select New > List, then start with a blank list.

Keep the first version small. Add these columns:

Column	Type	Purpose
Title	Single line of text	Short initiative or outcome name
Outcome	Multiple lines of text	What will be observably different when it is done
Owner	Person	One accountable owner
Phase	Choice	For example: Discovery, Approved, Delivery, Adoption
Status	Choice	On track, At risk, Blocked, Complete, Paused
Start	Date	Earliest meaningful start date
Target	Date	Current expected decision or delivery date
Confidence	Choice	High, Medium, Low
Next checkpoint	Date	When the owner must update or decide something
Last update	Multiple lines of text	Short, dated progress note
Delivery link	Hyperlink	Link to the detailed plan, board or evidence

Avoid twenty columns “for later”. Every required field creates maintenance work. Add a field only when someone uses it to filter, group, decide or report.

Use controlled choices

Choice fields make filters and boards reliable. Free-text variations such as In Progress, in progress, Under way and WIP turn reporting into cleanup.

Define each value in plain language. For example:

• On track — no known issue threatens the current target;
• At risk — a credible issue could change the target or outcome;
• Blocked — progress needs a decision or dependency outside the owner's control;
• Paused — the organisation has deliberately stopped work;
• Complete — the agreed outcome and acceptance evidence exist.

Do not calculate a reassuring green status from dates alone. A roadmap needs an accountable judgement, not just arithmetic.

Create the views people actually need

One list can support several conversations without duplicating the underlying items.

1. Portfolio grid

Start with a compact list view showing:

• Title;
• Owner;
• Phase;
• Status;
• Target;
• Confidence;
• Next checkpoint.

Sort by Status and Target, or create separate public views for leaders and delivery owners. Microsoft documents how to create, filter, group and save list views.

Grid view is the maintenance surface. It is faster for updating several items than opening each form.

2. Board by phase or status

Create a Board view and group cards by Phase when the meeting is about flow through the portfolio. Group by Status when the meeting is about intervention.

Keep the card small: Title, Owner, Target and Confidence are normally enough. A crowded card makes the board harder to scan.

Microsoft supports custom Board cards through Board view formatting. Treat that formatting as presentation. Microsoft is explicit that view formatting does not change list data.

It therefore cannot:

• calculate a critical path;
• move dependent dates;
• enforce resource capacity;
• synchronize an external project plan by itself;
• turn a list into a full Gantt engine.

3. Calendar by target date

If the roadmap has meaningful dates, create a Calendar view using Start and Target.

Microsoft's calendar-view guidance explains how a list with date columns can show an item as a point or span on the calendar.

Use this to spot clusters and collisions, not to imply precise task scheduling. A monthly target date is often honest; a 09:00 deadline six months away often is not.

4. Attention view

Create a filtered view for:

• Status is At risk or Blocked;
• Confidence is Low;
• Next checkpoint is overdue;
• Owner is blank;
• Last update is missing.

This is usually more valuable than a decorative timeline. It tells the portfolio owner what needs a decision.

Put the roadmap on a SharePoint page

Create a modern page with a simple order:

1. Purpose — what belongs on this roadmap and what does not;
2. Decision cadence — who reviews it and when;
3. List web part — show the default portfolio or attention view;
4. Key links — detailed plans, decision log, risk process and archive;
5. Owner and contact — one person accountable for the roadmap's health.

Do not bury the list below a long mission statement. The page should help someone understand and use the roadmap in under a minute.

If a group-connected delivery team already uses Planner, add the Planner web part beneath the portfolio summary. Keep the distinction visible:

• roadmap list: initiatives, outcomes, decisions and dates;
• Planner: assigned delivery tasks;
• document library: specifications, evidence and decisions.

Add automation carefully

Automation should protect the update process, not invent progress.

Useful Power Automate flows include:

• remind an owner when the next checkpoint is due;
• notify the portfolio lead when Status changes to Blocked;
• record a completed item's archive date;
• request an update when Last update is older than the agreed cadence.

Avoid automatically marking something On track because the target is still in the future. A dependency can be broken while the date remains green.

Also avoid two-way synchronization until you can name the authoritative system for every field. If both Jira and SharePoint can overwrite Status, the roadmap will eventually lie.

Governance that keeps the roadmap alive

Most roadmaps fail because nobody owns the data contract.

Set these rules:

• every item has one accountable Owner;
• Status has a written definition;
• every active item has a next checkpoint;
• changes to target or outcome include a dated explanation;
• completed and cancelled items move to an archive view instead of disappearing;
• the portfolio owner reviews stale and ownerless rows;
• detailed delivery stays in the delivery system and links back to the roadmap.

Use SharePoint permissions at the list or site level wherever possible. Avoid creating unique permissions on every roadmap item unless the confidentiality requirement genuinely demands it.

When SharePoint is the wrong tool

Choose a more capable planning product when you need:

• automatic dependency scheduling;
• resource capacity and levelling;
• baselines and variance analysis;
• detailed portfolio finance;
• hundreds of linked tasks across programmes;
• sophisticated scenario planning;
• guaranteed synchronization with several delivery platforms.

SharePoint remains useful as the governed communication layer, even when another system performs the scheduling. Show the approved summary and link to the authoritative plan rather than copying every task.

A sensible first release

Start with ten real initiatives and one monthly review.

Then check:

1. Can a leader identify the blocked items in thirty seconds?
2. Can every active item be traced to a named owner?
3. Does each target have an outcome rather than just an activity?
4. Can delivery teams reach their detailed work from the roadmap?
5. Can the portfolio owner see stale updates without manual detective work?

If those answers are yes, the roadmap is doing its job. Add complexity only when a real decision requires it.

Frequently asked questions

Does SharePoint have a native roadmap feature?

No dedicated SharePoint roadmap object exists. A practical lightweight roadmap uses a Microsoft List as the source of truth and presents it through Grid, Board, Calendar and filtered views.

Can SharePoint JSON formatting create a Gantt chart?

Formatting can make list data look more timeline-like, but Microsoft says view formatting changes only how items are displayed. It does not calculate dependencies, move dates or provide a project-scheduling engine.

Should I use Microsoft Lists or Planner for a roadmap?

Use a list for portfolio initiatives, outcomes, owners, status and decision dates. Use Planner for assigned team tasks. On a group-connected team site, the Planner web part can surface the task board alongside the roadmap.

What happened to Viva Goals?

Microsoft retired Viva Goals on 31 December 2025. Do not make it part of a new SharePoint roadmap design.

How often should roadmap owners update their items?

Set a cadence that matches the decisions being made. Weekly may suit active delivery; monthly may suit a slower portfolio. Give every active item a next-checkpoint date so stale updates are visible.

If you are turning a messy portfolio spreadsheet into a governed SharePoint view, join the SharePoint & Teams Admins Space. Bring the decisions the roadmap must support and a redacted sample row.