Most executives know their planning cycle is slow. Almost none of them can say how slow, in days, with a name next to each delay. That gap is why the cycle survives. A feeling that planning is sluggish loses every argument to a controller with a calendar. A table that shows a rate assumption took eleven weeks to move from public signal to approved change wins the same argument in one meeting. The Cycle Audit produces that table. It takes one afternoon, five or six people, and no software.
Put the right people in the room: the people who actually produce the planning artifacts, not the people who present them. The FP&A lead who builds the budget model. The strategy person who runs the offsite. The treasury analyst who owns the rate assumption. The operations lead who owns the capacity plan. One executive sponsor who can hear the result without getting defensive, because the result is going to make the current process look worse than anyone in the room expected. Three hours, a whiteboard, and a shared spreadsheet are enough.
Step one: list every planning artifact
Write down every document that commits the company to a view of the future. Not just the annual plan. The budget, the capex envelope, the headcount plan, the pricing book, the demand forecast, the treasury model, the board strategy deck, the quarterly reforecast, the supplier contracts with volume commitments, the compensation targets. Most mid-size companies find twelve to twenty of these once they look. Each one is a frozen assumption set with a date on it, and the audit is about to find out how old the ice is.
Step two: record the cadence and the owner
For each artifact, two columns. When is it produced or refreshed, in real terms, not what the process doc says. And who can actually change it. The second column is where the first surprise usually lands. A lot of artifacts have an author but no decision owner. The budget model has an FP&A analyst who maintains it, but the person who can authorize a change to the revenue line is three levels up and meets about it quarterly. Write the name of the person who can say yes, not the person who types.
Step three: name the signal that would change it
This is the column that turns an inventory into a diagnostic. For each artifact, what public or internal signal, if it moved enough, would force a change? The treasury model maps to the Fed funds ceiling and a corporate bond yield. The demand forecast maps to consumer sentiment or orders in your category. The freight line maps to diesel. The hiring plan maps to jobless claims and postings. If nobody can name a signal, write “none” and leave it there. An artifact with no signal attached is an artifact that will be wrong and nobody will know when. The Signal Library has the common public ones with a plain-language note on what each one tests.
Step four: measure the lag
Now pick the last time each signal moved materially and walk the timeline. Four dates. When the move was first visible to anyone in the company. When an executive conversation about it actually started. When the artifact was formally changed. When money or people moved as a result. The span from the first date to the last is that artifact’s decision cycle. Do it from memory and email timestamps; precision to the week is plenty. Then, in the last column, write how often that signal tends to move by that much. That is the environment’s change cycle for that line.
Use this cycle’s rate move as the test case if you are stuck. The Fed raised its target ceiling to 4.00% on September 17. Ask the room: when did the rate line in the 2027 plan change to reflect that, and has it changed at all? Most companies approving budgets this month will find the honest answer is that the line was written in early September and is going to the board as written. That one line is enough to make the whole table legible.
Step five: add the cost line and build the table
The book’s version of the audit, in Chapter 12, counts one more thing: what the cycle costs to run. Senior attention in days per year. Direct spend on consulting and platform integration. Which conversations the cycle owns outright, especially the annual plan approval with the board. And the constituencies whose roles are built around it, because those are the people who will defend the cycle after the table says it should go. Put the attention cost at the bottom of the sheet in days. In most large organizations it comes out near ninety days of senior time a year, and seeing it written down changes the conversation about what the Loop would have to replace.
The output is one table, one row per artifact, seven columns: artifact, cadence, decision owner, signal, decision cycle in weeks, change cycle in weeks, and the ratio between the last two. Sort by the ratio. Anything above one means the environment moves faster than the decision about it, which means that line is being managed by variance reports rather than by decisions. Below the table, three lines: total senior days consumed, total direct spend, and the list of meetings the cycle owns.
That sheet is the whole deliverable. Don’t turn it into a deck. The spreadsheet is more persuasive than any slide you could build from it, because every number in it came from someone in the room.
What a bad result looks like
A bad result has three signatures. First, a lot of “none” in the signal column, which means the plan is not connected to the world in any way that could tell you it broke. Second, decision cycles measured in quarters against change cycles measured in weeks, with the ratio above two on the lines that carry the most money. Third, decision owners who are the same two or three people for every row, meeting on the same quarterly cadence, which means every signal in the company is funneling through one bottleneck that opens four times a year.
A genuinely bad result also has an emotional signature. Someone in the room says the process is fine and the problem is execution. The table says otherwise. The ratio does not care how well the reforecast was run; it measures whether the question being asked was still the right question by the time anyone answered it.
What to do with it
The Cycle Audit does not tell you what to do. It makes the gap impossible to deny, and it is the first step of the 18-Month Sunset, the plan for retiring the annual cycle while Woodring’s Loop stands up beside it. You cannot retire what you have not measured. Once it is measured, the three worst rows on the table are your first three scenarios, and the signals you named for them are the beginning of your Scan.
If you want a read on where your organization sits before you book the afternoon, the Maturity Read takes six minutes. The full audit, with the four passes and the constituency map, is in the book.