The strategic plan is adopted. It has been laid out, approved by council or by the board, posted as a PDF on the organization's website. And that is often where it stops. Tracking starts somewhere else: one spreadsheet per department, columns that do not line up, and one person consolidating everything twice a year.
The document is not the problem. A strategic plan needs an official version that people can read and quote. The problem is asking that same document to work as a tracking tool, which no document can do.
What gets lost between the document and execution
When a plan moves from document to tracking spreadsheet, three things almost always disappear.
1. The hierarchy
In the document, an action sits under an objective, which sits under a strategic direction. In the spreadsheet, all that remains is a flat list of actions. You can no longer answer the question that matters at the senior leadership table: is this direction moving, and because of what ?
2. Accountability
The document names responsible departments. A department is not a person. Six months later, nobody knows who was supposed to update what, and the follow-up is done by guesswork.
3. History
The spreadsheet is overwritten at every update. You keep today's value and lose the trajectory. At reporting time, you reconstruct from memory what happened, which is exactly the work you were trying to avoid.
Four steps from a document to living tracking
1. Rebuild the hierarchy before entering anything
Before any data entry, decide how many levels the plan has. Two levels (directions and objectives) are enough for many organizations. Three levels add strategic means. Four levels insert strategic intents between objectives and means. The right number is the one in the adopted document, not the one that looks most complete.
The second decision is just as structural: the vocabulary. If the plan speaks of pillars, themes or priorities, the tracking must speak of pillars, themes and priorities. Renaming the vocabulary during migration is the surest way to lose the teams.
2. Attach the action plan to the right level
The action plan is not a level of the strategic plan. It is the operational floor, the projects, and it attaches to one specific strategic element. An action attached to the direction rather than to the objective produces tracking that looks complete but supports no trade-off decision.
This is also the moment to clean house. Some actions in the spreadsheet are finished, abandoned or replaced. They do not need to be migrated.
3. Name an owner per element, not per department
Every element gets one accountable owner and a set of contributors. The distinction looks administrative. It is what decides the update rate six months later.
4. Choose the starting point for indicators
Two options, and you have to pick. Either you restart from the current value and accept losing the history, which is fast. Or you re-enter whatever history exists, which takes longer but lets you show a trend in the very first report. For a plan adopted more than a year ago, the second option is almost always worth the effort.
Doing it yourself, or getting help
Most organizations handle the migration themselves, and that is entirely workable. One person who knows the plan well, two or three half days, and the essentials are in place.
Three situations change the calculation. When the plan was adopted more than two years ago and has drifted, migration becomes an update exercise, which calls for decisions rather than data entry. When several departments use different vocabularies, the arbitration has to happen before entry, otherwise each department reproduces its own spreadsheet inside the new tool. And when a reporting deadline falls within the following weeks, there is no room to learn and migrate at the same time.
In those cases, an implementation service earns its cost. What it brings is not the data entry, which is the fastest part. It is facilitating the structural decisions, carrying over the vocabulary of the adopted plan, setting up the indicators, and training the people who will keep the plan current afterwards. A migrated plan nobody knows how to maintain has solved nothing.
One caution, whichever route you take. The structural decisions belong to the organization. A provider can propose, build and accelerate, but the number of levels, the vocabulary and the name of the accountable owner for each element are settled internally. Those decisions are what keep the plan alive afterwards.
What if the plan is halfway through ?
Many migrations happen mid-cycle, not the day after adoption. That is in fact the common case: the plan is two or three years old, some actions are delivered, others have drifted, and the official document no longer tells the whole truth.
In that case, migration doubles as an update exercise. Sort everything into three buckets: what is done and gets recorded as such, what is under way and carries over as is, and what never started. The third bucket is the most useful. An action that has not moved in two years is not missing a tool, it is missing a decision. Migration is the right moment to settle it: either it restarts with an owner and a deadline, or it is formally dropped.
Recording a drop is not an admission of failure. It is what makes honest reporting possible, and it holds up far better in front of a council than an action left at zero per cent across three consecutive reports.
Three common pitfalls
- Migrating the tracking spreadsheet instead of the adopted plan. The spreadsheet carries the habits of whoever maintained it, not the official structure. Start from the adopted document, then reconcile.
- Migrating everything at once, across all departments. One pilot department over two or three weeks surfaces vocabulary problems before they multiply.
- Starting the migration without setting the first reporting deadline. With no date, data entry drags on. With a date, it ends.
The real sign that a migration worked
It is not the number of rows transferred. It is the moment a department opens the plan to answer a question of its own, rather than to satisfy a request from above. From then on, the plan is no longer a document to update. It is where the work becomes visible.
Getting ready to migrate your plan
Our guides on strategic plan execution cover structure, governance cadence and measurement.
Free Guides to Execute Your Strategic Plan
To see what a migrated plan looks like inside a tracking platform, book a 30 minute demo.
