Planning in Pencil: Contingency Planning for the Unknown

Most organizational plans are written in ink, meaning there is no expectation of changes or edits. They assume one budget, one set of priorities, and one version of next year, and they are built to be executed as is.

That works in a static environment. However, a leadership transition, delayed budget, regulatory shift, acquisition, major customer walking away, or priority-shifting election can all redraw the map in a matter of weeks. When that happens, a plan built around a single forecast doesn’t bend; it breaks. Then, leaders end up making high-stakes decisions under a time crunch with no laid groundwork.

The alternative is to build a contingency plan in pencil that anticipates several possible futures. This requires clear direction regarding which moves are safe now, which should wait, and what scenarios will trigger action. It isn’t necessary (or possible) to predict exactly what will happen. It is possible, though, to be prepared for more than one answer.

Why Single-Forecast Plans Break

Planning tends to focus on one question: what will we need next year? Leaders estimate demand, compare it to current headcount and skills, and close the gap. The logic is sound on its face, but it relies on an assumption that collapses during instability: that next year is knowable.

When the future doesn’t pan out as expected, one of three things usually happens. First, some organizations freeze. Every decision gets deferred “until we know more,” and critical hires, promotions, and projects stall for months. Meanwhile, other organizations do the opposite and lunge, making large, hard-to-reverse commitments based on their best guess, which then forces them to scramble when the guess is wrong. Third, and most commonly, there are organizations that do both at once: they delay the decisions that could safely move forward while rushing the ones that should wait.

Despite the different outcomes, the root problem in all three is the same. The plan written in ink offers no way to tell which decisions are sensitive to the uncertainty and which aren’t. Contingency planning, however, fills that gap. The four steps below can serve as a guide to assess the situation and identify which items can proceed, which ones can begin preparation, and which require waiting for a trigger event to move forward.

Step 1: Build Two or Three Scenarios

Start by naming the forces that could change your organizational needs. For most organizations, these fall into a few categories: funding or revenue, priorities and mandates, regulatory or policy requirements, and access to talent. Pick the one or two forces that are both highly uncertain and highly consequential for your organization. Those become the axes of your scenarios.

Then describe two or three plausible futures. Keep them limited in number and neutral. Three scenarios are enough to stretch your thinking without turning planning into a research project. Describe each one by its effect on your organization, not by its cause. “Budget holds flat and priorities stay the same” is more useful than a scenario named after a market event or an election outcome, because it keeps the conversation on what you can prepare for rather than on predictions.

For each scenario, answer four questions:

• Which roles become more critical, and which become less critical?
• Which skills would we need that we don’t have today?
• What happens to headcount, hiring, and contractor support?
• Which teams or programs would be most disrupted?

The goal is to see where the scenarios agree and where they diverge, then use that comparison to drive every step that follows.

Step 2: Sort Every Move Into Three Tiers

With your scenarios side by side, list the actions you’re considering and sort each into one of three tiers. This is where the plan goes from being an exercise to actually guiding decisions. Below is an example with a workforce angle.

There are two patterns that commonly emerge here. First, the no-regret list is longer than leaders expect, which means much of the work that felt frozen can actually move forward. Second, many big bets can be broken into an option plus a smaller commitment. Instead of approving a hiring surge, for example, you might approve the job descriptions and recruiting partner now and hold the requisitions until conditions are clearer.

The point of options is to buy speed. An option should cut the time between “we know” and “we’ve acted” from months to weeks.

Step 3: Set Tripwires and Assign Decision Rights in Advance

A tripwire is a specific, observable signal that tells you a scenario is becoming real and triggers an option to be activated. Good tripwires are concrete enough that two people looking at the same facts would agree whether one has been crossed. “If the budget situation looks bad…” is not a tripwire. “If our funding is not finalized by March 1…” is.

For each option and big bet, write down three things:

1. The trigger: The event, date, or threshold that sets the action in motion.
2. The action: Exactly what gets activated, and how far it goes. A first trigger might start recruiting, while a second, stronger trigger approves the offers.
3. The owner: The person authorized to act when the trigger is hit without waiting for another round of approvals.

The third item is the one most often skipped, yet it matters the most. Instability tends to arrive with time pressure. If every activated option requires a new meeting, a new business case, and sign-off from three levels of leadership, the speed you bought in Step 2 disappears. Pre-assigning decision rights also keeps decisions consistent. Leaders aren’t relitigating the plan under stress; they already agreed on it when the stakes felt lower.

Tripwires can also run in the other direction. Set a “stand-down” signal for options that are no longer needed so that prepared work doesn’t linger indefinitely and drain attention.

Step 4: Find and Fix Single Points of Failure

Every scenario carries one shared risk: losing the wrong person at the wrong moment. Instability raises that risk because people may be reassigned, step away, or leave. A single-point-of-failure audit identifies where your organization depends on a single individual to keep a critical function running.

Work through each critical function and ask:

• If this person were unavailable for 30 days, what would stop?
• Is the knowledge they hold written down anywhere, or does it live only in their head?
• Is there at least one other person who could step in, even at reduced capacity?
• Do any relationships with key partners, customers, or stakeholders run entirely through this person?

Rate each function by how much damage a gap would cause and how hard the role would be to backfill. Address the highest-rated gaps first with no-regret moves, such as pair the person with a backup, capture their knowledge in a short operating guide, and/or introduce a second contact to their key relationships.

This is also a natural place to update succession plans. Many organizations have succession plans only for the top few executives. During instability, the more urgent gaps are often a level or two down, found in the specialist or manager who holds a critical process together behind the scenes.

Putting It to Work: An Election Transition: Example

Elections are a useful example because they come with a fixed calendar and an uncertain outcome. The 2026 midterms take place on November 3, and the new Congress is sworn in on January 3, with many state offices changing hands in the same window. Organizations whose work depends on public funding, contracts, or regulation can’t know in October what their priorities will be in February. Yet, they can still be ready.

Consider a mid-sized organization that delivers programs funded partly through government grants and contracts. Below is an outline of how the four steps might play out.

• Scenarios: Leaders choose funding level and program priorities as their two forces. Their three scenarios are: funding and priorities hold steady; funding holds but priorities shift toward a different program area; and funding tightens, with a delayed budget.
• No-regret moves: Every scenario rewards cross-training staff across program areas and documenting how each program runs, so those start immediately.
• Options: They draft job descriptions for skills a priority shift would require, line up a staffing partner, and sketch a consolidated team structure in case funding tightens. None of it is activated yet.
• Big bets: A planned expansion of one program is held. Rather than cancel it, leaders turn it into an option by keeping the business case current and ready to approve.
• Tripwires: If budget guidance for the coming year isn’t final by a set date, the consolidation option is reviewed. If a priority shift is formally announced, the new job descriptions are posted. The chief operating officer owns both decisions.
• Single points of failure: The audit shows that one program director holds every key relationship with funding agencies. A deputy is introduced to those contacts before the transition.

Nothing in this plan depends on predicting who wins or what they will do. It depends only on knowing which kinds of change would matter most, and deciding ahead of time how to respond to each.

The same structure applies to non-political instability as well, such as a pending merger, a leadership change, or a shift in a major customer’s strategy. Only the forces and tripwires change.

Keeping the Plan in Pencil

A contingency plan only works if it stays current. Set a short, regular review schedule. This can look like a monthly review during stable periods while tightening to every two weeks when conditions are actively shifting. Each review should cover four questions:

• Has any tripwire been crossed?
• Have any scenarios become more or less likely?
• Are the options still ready to activate?
• Have new single points of failure appeared?

Keep the plan short. A one-page summary of scenarios, tiers, tripwires, and owners will be used far more than a long document that’s revised once a year.

Finally, remember what this kind of plan does and doesn’t do. It won’t remove uncertainty, and it won’t tell you what the future holds. What it does is turn uncertainty from a reason to freeze into a set of decisions you’ve already thought through. When the ground shifts, you’re not starting from scratch. You’re filling in and adjusting the plan you wrote in pencil.

How have you handled a contingency scenario? Did things work out as anticipated, or did you have to plan on the fly? Leave a comment below, send us an email, or follow us on LinkedIn.