Ask a senior leader how many plans their organization is tracking right now. The answer rarely comes on the first try.
You count them out loud. The strategic plan. The annual business plan that flows from it. The sustainability plan. The digital transformation plan. The workforce plan. The multi-year accessibility plan. And every department's work plan, which does not always carry the word plan but is one.
Then each sector adds its own. A municipality has its asset management plan and its capital forecast. A school board has its student achievement plan. A health organization has its quality improvement plans. A nonprofit has the plans its funders require. A company has its sales plan and its succession plan.
You reach eight or ten without trying. It takes a minute, and it surprises people every time.
This is not a management failure. It is the normal state of an organization in 2026, public sector and private sector alike. The number worth looking at is not how many plans you have. It is how many times the same action gets entered.
One action, four documents
Take a concrete action: setting up a continuing education program for staff. Nothing exotic, the kind of project you find in every organization, whatever its size and sector.
In the sustainability plan, that action sits under the social pillar, with a target in training hours per person.
In the digital transformation plan, it is a precondition for rolling out the new tools, with a deadline tied to the systems timeline.
In the workforce plan, it is a retention lever, with a budget and a target number of participants.
And in the strategic plan, it supports a direction on organizational capacity, sometimes through a skills development objective.
Four documents. Four files. Four places where someone is supposed to record that the program is 60 per cent rolled out.
That is what a cross-cutting action looks like. It belongs to none of the four plans, and all four need it.
What the fourth entry costs
The cost is not the data entry. Four times thirty seconds, nobody complains about that. The cost shows up elsewhere, and it is more serious.
First effect: the numbers diverge. The sustainability file says 60 per cent, the workforce plan says 40 per cent, and neither is wrong. One measures the design of the program, the other measures how many teams have actually been through it. Both are defensible. But when both numbers reach the same body, in two different reports, what takes the hit is the credibility of the tracking, not of the project.
Second effect: updates happen once a year. Updating four places every month does not fit into a normal work week. So people wait. They wait for the year-end report, and at that point they reconstruct twelve months from memory and email threads.
Third effect, the most expensive one: the governing body, whether that is a board, a council or an executive committee, receives several portraits of the same project at different points in the year, and eventually loses track of which one is current. In the end, it stops asking.
Why the stack is not a mistake
This needs to be said plainly, because the reflex is usually to blame the organization. Nobody woke up one morning and decided to have ten plans.
Some plans are required by legislation or by a ministry. Others are the condition of funding: no plan, no money. Others were asked for by staff, by a union, by a board or by the community, and it is usually good news when someone gets an organization to write down what it intends to do.
Each plan was adopted for a sound reason, often by a different body, years apart. The stack is not a lack of rigour. It is the accumulation of reasonable decisions made separately.
Which means no cleanup exercise is going to settle the question. The number of plans is not yours to set.
Separating the plan from the action
The way out runs through a distinction that sounds theoretical and is anything but.
A plan is a document. It has to exist in as many versions as your obligations require, with its own directions, its own vocabulary, its own adoption date. That part does not merge.
An action is real work, done by a real person, on a real date. It exists once, even when it serves four plans.
As long as the action lives inside each document, it duplicates. The moment it exists once and the plans point to it, the divergence disappears on its own. There is only one place to write 60 per cent, and that figure shows up everywhere the action is attached.
Three conditions make this work.
- A vocabulary adopted by the whole organization, not one per plan. If a direction in the strategic plan and a pillar in the sustainability plan name the same level of decision, say so once and for all.
- An action that can attach to more than one element, in more than one plan, with the same progress everywhere. Our continuing education program stays one project, with one accountable lead, visible in all four plans it serves.
- An indicator that can serve several elements while holding a single value. Training hours per person is one number, even if three plans watch it.
An hour-long exercise
Before changing anything, there is a test that costs almost nothing.
Pick a mid-sized project, under way for at least a year, attached to more than one plan. Cross-cutting projects are the best candidates, precisely because they show up everywhere: staff training, a process redesign, a system rollout, an energy consumption reduction.
Pull the last three documents where the project appears: a report to the governing body, a sectoral plan update, a department work plan.
Compare the progress recorded in each one. Then find the date each figure was last updated.
In most organizations the three numbers differ, and at least one is more than six months old. That is not a verdict of failure. It is the exact measure of what multiple entry costs you, in one hour of work.
For a council or a board starting a new term, this is also the cheapest way to see the state of the tracking it has inherited, before deciding anything about the next plan.
What changes, and what does not
Let us be honest about the scope of all this. The exercise will not reduce the number of your plans, and neither will Planivore. That number comes from your obligations and your funders, not from how you organize the work.
What does shrink is the number of places an action lives. From four to one. It is less dramatic than a redesign, and it is what makes tracking last twelve months instead of three.
The day a senior leader can answer a question about a project without opening three files, the question gets asked again the following quarter. That is about the only reliable sign that a plan is alive.
Keeping your plans in one place
See how a strategic plan, sectoral plans and department work plans hold together in a single environment, with cross-cutting actions attached to several plans at once.
Schedule a Personalized 30-Minute Demo
Our strategic execution trilogy covers plan structure, reporting cadence and indicators.
