IT roadmap template
An IT roadmap answers the question every department eventually asks the IT team: "When will you get to our thing?" Laid out well, it also shows leadership why the team is busy, which projects compete for the same people, and what quietly keeps the business running.
This template splits a year of IT work into four lanes and four quarters. It is small on purpose. A roadmap that fits on one screen gets read; one that needs scrolling in two directions gets ignored.
The template
Fernhill Freight is a fictional regional delivery company with a four-person IT team; every project below is made up for the example.
| Lane | Q1 2027 | Q2 2027 | Q3 2027 | Q4 2027 |
|---|---|---|---|---|
| Infrastructure | Replace the depot network switches
Swap the aging switches at both depots so scanners stop dropping off the network at shift change. network depots | Backup restore drill
Restore one full day of dispatch data to a spare machine and time how long it takes. backup | Move file shares to managed cloud storage
Retire the office file server and keep shared folders backed up off site. storage backup | |
| Apps | New driver route app on company phones
Roll out the new route app to every driver phone, one depot at a time. drivers rollout | Retire the old timesheet system
Move the last two teams onto the payroll tool's own timesheets and switch the old system off. retirement payroll | Customer delivery tracking page
Give customers a page that shows where their parcel is, fed by the dispatch system. customers | |
| Security | Multi-factor sign-in for all staff accounts
Require a second step at sign-in for office and depot staff, starting with finance. accounts | Laptop disk encryption
Turn on full-disk encryption for every company laptop and record the recovery keys centrally. devices | Phishing awareness session
A short session for every team on spotting fake invoices and delivery scams. training | |
| Support | One place to ask for IT help
Replace calls and hallway requests with a single help request form and a queue the whole IT team can see. helpdesk | New starter checklist
A laptop, accounts and app access ready on a new hire's first morning, every time. onboarding | Self-service password reset
Staff reset a forgotten password themselves instead of waiting for the IT team. accounts helpdesk |
The example belongs to Fernhill Freight, a fictional delivery company with a four-person IT team. Every project in it is invented.
That button copies the roadmap, lanes and all, into a free Votelantern account, ready to edit.
The four lanes
Infrastructure. Networks, servers, storage, backups: the work nobody notices until it fails. Put the restore drill here as well as the hardware. A backup that has never been restored is a hope, not a plan.
Apps. New tools going in and old ones coming out. Retirements belong on the roadmap as much as rollouts do, because switching a system off takes real effort and frees time later.
Security. Account protection, device encryption, training. Spread this lane across the year rather than bunching it into one quarter, so it doesn't become the thing that always slips.
Support. How staff get help: the request queue, new starter setup, self-service fixes. This lane is where staff feel the roadmap most directly, so it earns its own row.
You might add a fifth lane for data or reporting. We suggest stopping at five. Beyond that, the lanes stop helping people find their own work.
How to fill it in
- List everything, then cut. Write every project people have asked for on a scratch list. Keep the ones that fix a real problem this year; park the rest.
- Place each item in the quarter you expect to finish it. People read a roadmap as a promise about when things arrive, not when work begins.
- Check each quarter against your people. If one quarter holds three large projects for a two-person team, move one. The roadmap should be believable before it is ambitious.
- Write descriptions for the people affected. "Scanners stop dropping off the network at shift change" means more to a depot manager than "replace core switches".
- Mark dependencies in the description. If the delivery tracking page needs the new route app first, say so in a few words.
Spreadsheet, slide or live page?
A spreadsheet is a fine place to start: one row per lane, one column per quarter, a project in each cell. That works for planning. The same grid pasted onto a slide works for a leadership meeting.
The trouble starts after the meeting. The file gets copied, edited in two places, and nobody knows which version is current. A live roadmap page has one address that is always up to date, and you can change an item between meetings without sending anything around.
Votelantern adds one more thing: a board where staff post requests and vote on them. A request like "let me reset my own password" can collect votes from across the company. Votes don't decide the roadmap for you, but they show you what people feel most.
Internal or public?
Decide who the roadmap is for before you share it. In Votelantern, boards are public by default; private boards come with the Business plan, and private pages are kept out of search engines. If your roadmap names systems or security work you would rather not publish, put it on a private board.
A small company might still choose a public roadmap for customer-facing items, like the delivery tracking page in the example, and keep the rest private.
Keeping it current
Review the roadmap once a month in a short meeting. Move finished items out, push slipped ones to the next quarter with a word of explanation, and add anything urgent that arrived. At the end of each quarter, roll the columns forward so the roadmap always shows the year ahead.
Related templates: the technology roadmap template for the technology behind the product you sell (the layout is similar), and the project roadmap template for a single project by month.
Plans (draft prices)
Our prices are drafts and may change before launch. Free is $0 with one public board, roadmap, changelog and widget for one admin. Team (price not set yet) covers up to three admins and up to five boards. Business (price not set yet) adds private boards, up to ten admins and unlimited boards, which suits an internal IT roadmap.
FAQ
How far ahead should an IT roadmap look? A year is a common choice for a small team. Further out than that, items become guesses, and people still read them as promises.
Should routine maintenance go on the roadmap? Only the parts that take planned effort, like a restore drill or a hardware swap. Daily upkeep belongs in the support queue, not on the roadmap.
What if leadership wants dates, not quarters? Give a date only for items with a fixed outside deadline. For the rest, a quarter is honest about the uncertainty.
Can staff suggest projects for the roadmap? Yes. Staff post on the board, vote on each other's ideas and follow the ones they care about. You decide what moves onto the roadmap.