Nonprofit technology roadmap on one page
A one-page technology roadmap you can write in two weeks. Every system with an owner and a renewal date, three moves for the year, a stop list, and a free template.
Template · Technology and Data
A one-page technology roadmap template with a system inventory, three moves, a stop list, five security checks, a budget line, and a sign-off. Docs and Word files.
Nonprofit Strategy Editors. Published .
Get the template
Formats: Google Docs, Word (DOCX). Free. The links work without an email. Licensed CC BY 4.0: use it, adapt it, credit this page.
This is the page described in Nonprofit technology roadmap on one page. It fits on one side of letter paper when printed, and it is meant to be filled in by one person over two weeks, checked with the finance lead, then signed by the executive director. The Word file and the Docs copy are identical. Neither asks for an email.
The page has six blocks, in this order from top to bottom.
The header carries three fields: Organization, Fiscal year, and Prepared by. Prepared by is one name, the person who owns the page.
The system inventory is a table with six columns: System, Purpose, Owner, Annual cost, Renewal date, and Decision. It ships with twelve blank rows. Owner is a person’s name, never a department. Annual cost is all-in, including seats, add-ons, and any consultant who maintains the system. Renewal date is the day auto-renew fires, less the notice period. Decision is one of three words: Keep, Replace, or Retire. A total line under the Annual cost column sums the table.
The three moves block has three numbered rows, each with four fields: Move, Owner, Cost, and Done when. Move is one sentence naming the system and the action. Owner is one name. Cost is written as hours and dollars, for example 60 hours, $3,000 one-time. Done when is a sentence you could check with a yes or no. There is no fourth row on purpose.
The stop list is five short lines, each with a Reconsider on date beside it. Use three to six. Each line names one thing the organization will not buy, pilot, or start this fiscal year.
The security basics checklist has five items, each with a Yes or No box, an Owner, and a Last checked date:
The budget line has four fields: Subscriptions and hardware (the inventory total), One-time costs (from the three moves), Training, and Total, with a fifth field for Total as a share of operating budget.
The sign-off has four fields: Signed by, Title, Date signed, and Review date. Review date is twelve months after Date signed.
Fill it in this order. The order matters because each block depends on the one before it.
The page is reviewed at six months for the three moves only, and rewritten from the top at twelve months. Keep the old page. The inventory changes less than you expect and the renewal dates carry over.
Do not use it during an executive director transition or a merger less than six months out. Fill the inventory only and leave the rest for the incoming leadership.
Do not use it in the middle of a CRM migration. The migration is the year’s only move. Write the page after cutover.
Do not use it if you already have a technology director and a funded multi-year plan of your own. This page adds nothing to that plan except a summary, and the summary can be produced from the plan itself.
Do not stretch it to three years. The Review date is twelve months out, and the renewal column already holds every date beyond that.
A one-page technology roadmap you can write in two weeks. Every system with an owner and a renewal date, three moves for the year, a stop list, and a free template.
Nonprofit Strategy WeeklyOne email every Tuesday: the newest piece, one template, nothing else. No vendor money, unsubscribe in one click. Replies are read and answered.