What is a goal cascade?

The handoff of a company goal down through the organisation: to each facility, then to departments or teams, then to people, each level writing the goal in terms it can act on and keeping the link to the goal above. Cascading on its own is top-down; the catchball reply at each step makes it two-way.

The back-and-forth between the level that sets a goal and the level that has to deliver it. In this template it is one of three replies by a date: adopt as written, write own version, or not applicable with the reason. The reply becomes the lower level's goal, with the company goal as its parent.

What is the difference between cascading and aligning goals?

Cascading sends a goal down and asks for a version at each level. Aligning starts from the work already under way, kaizens, projects and personal goals, and marks the company goal each one serves. This template does both: the tree is the cascade; the initiatives list with its Other bucket is the alignment.

How many levels should a cascade have?

Company, facility and department is enough for most plants; a fourth level, the person, is worth it where a named person owns a change, such as a setter owning the internal changeover steps on one press. Beyond four levels the cards outnumber the people reading them.

What should happen with initiatives that serve no goal?

List them in Other and count them. Some work has to be done whatever the strategy says, so Other is never empty. What the review needs is its size: a share aligned well below three quarters says the plan and the work have drifted apart, and leadership decides which one to change.

Free template

Updated November 1, 2026

Goal cascade and alignment template

A goal cascade template carries a company's goals down to each facility, then to departments and people, and records the catchball reply at every step: adopt the goal as written, write an own version with the company goal as its parent, or not applicable with the reason. Cascading is the top-down handoff; the reply is what makes it two-way, and the reply-by date is what makes it happen. Page 1 of the PDF is the cascade tree on one page, with a card per goal at each level and the reply circled on each card. Page 2 holds the three replies, the steps, the rules and a list of the initiatives under way with the goal each one serves, or Other, and an alignment tally. Pages 3 and 4 are a worked example. The Excel version takes forty goals at any level, finds the company goal at the root of each one from the parent ids, draws the tree as an indented list, flags replies that are pending past the reply-by date and replies that came late, counts the three reply types and the average days to reply, and resolves every initiative to its company goal to give the alignment %.

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Page 1 of the goal cascade template — One-page cascade treeCompany, facility, department, personParent id on every goalCatchball replyReply-by and replied datesPending and overdue flagsInitiatives listAligned to, with OtherAlignment %Reply counts

Filled-in Goal cascade and alignment template: two company goals cascaded to three plants — The same sheet filled in with the worked example (page 3 of the PDF, illustrative numbers). Open full size (opens the picture in a new tab)

When to use it

When to use a goal cascade template

In the first weeks of the year, when the company goals are set and each plant has to say what it will do about them.
When goals are sent down by email and nobody knows who has replied, who has not, and who disagreed.
When a plant has twenty initiatives running and the leadership team cannot say which goal each one serves.
When a department or person is asked to set objectives and needs to see the line from their goal back to the company's.
At the monthly review, to read who is overdue on a reply and how much of the work sits in Other.

How to fill it in

1
Write the company goals
Three to five for the year, each with a pillar, an owner, the KPI it is measured by and the target. Give each one an id (G1, G2) so the tree can refer to it.
2
Cascade with a reply-by date
Send each goal to the facilities with a message and a date two to three weeks out. Write the date on the card. It is never moved: a late reply shows its days late.
3
Each facility replies
Adopt as written, write own version, or not applicable with the reason. The reply becomes the facility goal, with the company goal as its parent (From). Not applicable is a reply, as long as the card says why and what the site will do for that pillar instead.
4
Cascade again, to departments and people
Facilities send their goals to departments and teams the same way, and departments to people where it helps. Every card keeps the id of the goal it came from, so the tree reads from any person back to the company goal. Three levels is usually enough; four is the most.
5
List the initiatives
Every kaizen, project and improvement under way, with the id of the goal it serves at any level, or Other. The sheet finds the company goal at the root and counts how much work serves each one.
6
Read the summary monthly
Requests pending past their date, replies that came late, the mix of adopt, own version and not applicable, and the share of initiatives aligned to a company goal. A large Other is information for the review, not a failure.

Catchball

The three replies to a cascaded goal

Every site, department or person a goal is sent to gives one of three replies by the reply-by date. All three are valid; silence is the only wrong answer.

Reply	What it means
Adopt as written	The goal applies here as it stands. The site takes the wording and sets its own baseline and target for the same KPI.
Write own version	The goal applies, but the site writes it in its own terms: a different KPI, a different scope or a different target, with the company goal as its parent. Usually the best reply.
Not applicable	The goal does not fit this site, and the reply says why and what the site will do instead. A valid answer, as long as it is written down.

Adopt as written
What it means
The goal applies here as it stands. The site takes the wording and sets its own baseline and target for the same KPI.
Write own version
What it means
The goal applies, but the site writes it in its own terms: a different KPI, a different scope or a different target, with the company goal as its parent. Usually the best reply.
Not applicable
What it means
The goal does not fit this site, and the reply says why and what the site will do instead. A valid answer, as long as it is written down.

A filled-in example

Illustrative, not a benchmark

An example: a three-plant metal components group cascades two company goals on 12 January, read on 10 February (illustrative, the same as the Excel example sheets and PDF pages 3 and 4).

G1 Safety: cut the recordable injury rate in half, TRIR 2.4 to 1.2. Plant North and Plant East adopt it as written with their own targets; Plant South writes its own version, TRIR 3.1 to 1.5 with zero hand injuries on the press lines, because six of its nine recordables were hand injuries.
G2 Delivery: cut average changeover time from 52 to 30 minutes. Plant North writes its own version for the press lines (58 to 30 minutes); Plant South adopts it, two days after the reply-by date; Plant East replies not applicable, a continuous casting line has no product changeovers, and takes OTIF 90% to 97% as its delivery goal instead.
The facilities cascade on 26 January with a 9 February reply-by date: maintenance and planning at North adopt, press line 2 at North and the machining cells at South write their own versions, and the press shop at South has not replied, one day overdue. Press line 2 cascades to its team leader (adopts) and its setter (own version: internal changeover steps 31 to 12 minutes); the maintenance technician's reply is not due until 19 February.
Twelve initiatives are under way. Ten serve a company goal, five behind G1 and five behind G2, found through the tree (SMED workshops serve F4, which serves G2). Two serve neither: new canteen furniture and a lobby refurbishment, both in Other.

Fourteen requests sent, twelve answered, two pending of which one is overdue, one answered late. Replies: 6 adopt as written, 5 write own version, 1 not applicable. Average days to reply: 107 days across 12 replies = 8.9. Initiatives aligned to a company goal: 10 of 12 = 83%.

Common mistakes

Cascading without a date
A goal sent down with no reply-by date is a memo. Write the date on the card, and chase the people who have not replied; a pending reply is the sender's problem.
Treating not applicable as refusal
A plant that says a goal does not fit, and says why and what it will do instead, has done its job. Forcing a changeover goal on a continuous process produces a number nobody owns.
Four levels for everything
Cascading every goal to every person produces hundreds of cards and no ownership. Three levels is usually enough; go to a person only where it helps that person act.
Losing the parent
A department goal with no From id is an orphan: nobody can say which company goal it serves. Every card below company level names the goal it came from.
Leaving initiatives off the list
The alignment % is only honest when every project under way is on the list, including the ones that serve no goal. Other is where they go, and its size is the finding.

Download the template

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Run this template in LeanSuite

In LeanSuite, a company goal is cascaded to chosen facilities with a message and a reply-by date; each facility replies under My goals with adopt as written, write own version, which creates a facility goal with the company goal as its parent, or not applicable with the reason, and requests show as pending or answered.

See it in a 45-minute demo

In the lean glossary

Free tools

All free lean calculators

Guides

FAQ