IT Advisory

A One-Page IT Roadmap Template That Survives Budget Season

Last updated 2 October 2026

An IT roadmap template that survives budget season ties every line to a business outcome and gives it a named owner, a cost range and a stated dependency, and it costs the whole plan at a floor, a base and a stretch budget so the cuts are decided before the meeting. The one-page structure below is built from those parts.

Most of what follows, including this IT roadmap template, is practitioner judgement, not a published standard. Where a framework such as COBIT or TOGAF says something specific, the text names it and the Sources list links to it. Everything else is opinion about what tends to hold up when finance and business leaders go through an IT plan line by line during IT budget planning, so test it against how your own organisation decides.

Why roadmaps fail in the budget meeting

A roadmap that is a list of projects is easy to cut. Finance sees costs with no outcome attached. Business leaders see IT items they did not ask for. Nobody can say what stops working if a line goes, so the cut lands on whatever is newest or largest. Four patterns sit behind most of this.

Initiatives described by technology. “Migrate the file servers” starts a cost debate. “Retire storage before vendor support ends” starts a risk debate, which IT is better placed to win.
No split between run, mandatory and discretionary spend. When everything sits in one pile, a regulatory deadline competes with a nice-to-have.
One figure for work nobody has scoped. The figure becomes a promise, and the first revision looks like an overrun.
Hidden dependencies. An AI pilot is funded while the data clean-up it needs sits on another line and gets cut. Both are then wasted.

The IT roadmap template below is built to answer each of these patterns.

The one-page IT roadmap template

Keep it to one page on purpose. A roadmap that needs a deck to explain it will be discussed like a deck, and decks get debated rather than approved. Each block below has a test, which is the question a sceptical finance director would ask. Treat the table as an IT roadmap template to adapt, not a form to complete, and work down it in order, starting with outcomes, because every initiative has to link to one.

Block	What goes in it	Test it must pass
Outcomes	Three to five business outcomes for the period, in the business’s own words, each with a measure	A non-IT executive recognises them as their goals
Initiatives	Each one linked to an outcome, with a named business owner, a delivery owner, a cost range and a start window	Every row maps to an outcome or is labelled mandatory
Run, mandatory, change	Spend split into keeping services running, items you cannot avoid (a regulatory date, end of vendor support, a contract expiry) and discretionary change	Mandatory items are visible before discretionary ones are debated
Horizons	Now (funded or in flight), Next (approved in principle and sequenced), Later (direction only, no dates)	Only Now carries a firm date and budget
Dependencies	What each item needs from data, other projects, contracts, skills or approvals	Nothing on the page relies on something that is not on the page
Funding cases	The same roadmap at a floor, a base and a stretch budget, showing what starts, slips or drops at each	Leadership can pick a case without redrawing the plan
Cost of cutting	One sentence per at-risk item on what the organisation loses or carries as risk if it is not funded	A cut is a decision, not an accident
Decisions needed	The approvals, owners and trade-offs required this cycle, with dates	The page ends with asks, not status
Review rhythm	When the roadmap is revisited, and what triggers a change between reviews	Someone owns the next revision

Use cost ranges in your IT roadmap template until an item is scoped

Until work is scoped, it has a cost range and not a cost. Show it in the IT roadmap template as a band that you define once on the page, for example four bands with a riyal range each and a note on how firm the estimate is. Replace the band with a quote when the item moves from Next to Now. A single figure invites an argument about the arithmetic. A range invites the argument you actually want, which is whether the outcome is worth the money. Do not let anyone round a band into a promise.

Cost the same roadmap three ways

Use the IT roadmap template to draw one roadmap at three budgets. The floor funds run costs, mandatory items and anything already contracted. The base is the budget you expect to receive. The stretch adds what would be funded if more money appeared. For each case, show which initiatives start, which slip a quarter and which drop.

Then agree the order of cuts with your sponsor before the meeting. In our judgement this habit does more for a roadmap’s survival than any choice of IT roadmap template, because the meeting chooses between prepared options instead of improvising cuts under pressure. Pair it with the cost-of-cutting sentence, so that dropping an item is a visible trade.

Put contract renewals on the page

Add a renewals list to the IT roadmap template, covering every contract and licence above a threshold you set, with its renewal date and notice period, for the next 18 months. Renewals are where money leaves quietly. A contract that rolls over because the notice date passed is a budget decision nobody made. Dates on the roadmap also show when a replacement project has to start if it is to finish before the old arrangement ends.

Where COBIT and TOGAF fit

COBIT is published by ISACA as a framework for the governance and management of enterprise information and technology. COBIT 2019, the edition ISACA’s COBIT page describes as current, has 40 governance and management objectives in five domains. These are Evaluate, Direct and Monitor (EDM); Align, Plan and Organize (APO); Build, Acquire and Implement (BAI); Deliver, Service and Support (DSS); and Monitor, Evaluate and Assess (MEA). ISACA’s basic distinction is useful for roadmap work. Governance determines who makes decisions, and management directs and implements them. The “decisions needed” block on the page is where governance shows up.

TOGAF, from The Open Group, is an enterprise architecture standard now in its 10th Edition. In Phase E of its architecture development method (Opportunities and Solutions), an Architecture Roadmap is a timeline of the progression from the baseline architecture to the target architecture. It is built from work packages, which are logical groups of the changes needed to reach the target, and transition architectures, which are interim states that deliver measurable business value. The Now, Next and Later horizons in the IT roadmap template above are in the same spirit, since each stage is meant to deliver something on its own.

You do not need an enterprise architecture practice to use this IT roadmap template. Neither framework will write the roadmap or secure its funding. What they give you is shared vocabulary, which helps when IT, finance and risk need to talk about the same plan.

Getting the baseline right

The part of any IT roadmap template that most often goes missing is the baseline. Before any line can have an honest range, you need a current-state view of applications, infrastructure, data, contracts and team, and a cost baseline by system and vendor. Without it, any IT strategy roadmap is built on guesses. WASNA Digital Solutions offers IT strategy and technology roadmap development as a standalone engagement, and your own team can do the same baseline work if it has the time.

Once the roadmap is approved, every funded item needs a governed project behind it, which the PMO setup checklist covers. AI and automation items need their data and process prerequisites checked first, and AI in Saudi Arabia sets out what to settle before a project starts.