Section

After Writing Your Plan

The plan is not the deliverable. The executive summary is what a lender or investor actually reads, and the continuity plan is what your staff actually execute at 3 a.m. when the freezer fails or the payment processor goes down. Everything that matters after the writing is distribution, testing, and maintenance — getting the executive summary in front of the right reader with the right numbers, and getting the continuity plan out of the binder and into a drill. A business plan that sits in a drawer and a BCP nobody has read are the same failure: a document that describes a company rather than running one.

3 articles

After Writing Your Plan

After Writing Your Plan

By reference
What an entrepreneur must do after writing a business plan
After Writing Your Plan

What an entrepreneur must do after writing a business plan

“What must I actually do after writing this detailed business plan?”…

29 AugOpen
Next steps for entrepreneurs after creating a business plan
After Writing Your Plan

Next steps for entrepreneurs after creating a business plan

The most critical next step after finalizing a business plan is not to polish the document for potential investors, but to use its framework to build out your operational resilience and prove…

24 AugOpen
Steps an entrepreneur takes after creating a business plan
After Writing Your Plan

Steps an entrepreneur takes after creating a business plan

After writing a business plan, the next critical step an entrepreneur takes is transforming the conceptual document into two parallel systems: a rigorously refined narrative for external…

23 AugOpen

The plan is not the deliverable. The executive summary is what a lender or investor actually reads, and the continuity plan is what your staff actually execute at 3 a.m. when the freezer fails or the payment processor goes down. Everything that matters after the writing is distribution, testing, and maintenance — getting the executive summary in front of the right reader with the right numbers, and getting the continuity plan out of the binder and into a drill. A business plan that sits in a drawer and a BCP nobody has read are the same failure: a document that describes a company rather than running one.

The executive summary is the plan for most of your readers

Assume the executive summary is the only page a decision-maker reads. Rutgers Business School's Small Business Administration–aligned business plan template calls it "the most important section" outright, and describes its job as telling the reader where the company is now and where management wants to take it. That framing should change how you write it. It is not a warm-up to the real plan; it is the compressed version of the whole thing, and it has to stand alone.

The same template lists what belongs in it: a mission statement, the date the business began, the founders and their functions, the number of employees, the business location, a description of the facilities, the products or services, banking relationships and investor information, a summary of company growth, and a summary of management's future plans. That is a lot of specifics for a section people usually draft last and trim first. The practical sequence that works is to write the full plan, then build the summary by pulling one sentence from each section — which forces you to notice when a section has no sentence worth pulling.

The common belief that the summary is just a brief introduction is the expensive one. A banker reading a loan package is triaging; if the summary does not establish the business's history, its current position, and its direction, the rest of the document does not get read. The cost of getting this right is time — the summary is usually the slowest page in the plan to write, because it cannot contain anything the plan does not support. The limit of the advice is that a summary written for a bank and a summary written for an equity investor are not the same document. Banking relationships and investor information both belong in the template's list, but the weight you give each depends on who is holding the paper.

What changes when the summary leaves your hands

Write a second version of the executive summary for every audience you send it to, and keep the facts identical across all of them. The plan itself can stay fixed; the cover note, the emphasis, and the length should not. A lender wants the history, the banking relationships, and the growth record. An investor wants the future plans and the management functions. A potential partner or a large customer doing vendor due diligence wants the facilities, the location, and the ownership structure. Same company, same numbers, different lead.

Keep a master version with every figure sourced to the section of the plan it came from. When a number in the summary drifts from the number in the financials — a stale employee count, an old facility description after a move — the reader who catches it stops trusting the rest. That is the specific failure mode to watch for: not a badly written summary, but a summary that was accurate when drafted and was never revised after the business changed.

The honest trade-off is that maintaining multiple versions costs you a version-control problem. Small businesses lose track of which summary went to which bank. Date every version, keep one folder, and retire old ones rather than editing them in place. If you cannot sustain that discipline, write one version and accept that it will read as slightly generic to everyone.

A continuity plan is a procedure document, not a statement of intent

ISO 22301, the international standard for business continuity management systems, treats the plan as an operational document with mandatory contents. Clause 8.4, as of 2019, specifies that business continuity plans must define purpose, scope, objectives, activation criteria, implementation procedures, roles and responsibilities, communication requirements, interdependencies, required resources, and information flow. Read that list as a checklist and grade your own plan against it; most first drafts fail on activation criteria and interdependencies.

Activation criteria are where plans break in practice. Someone has to be able to answer "is this an incident or not" without calling the owner at midnight. Write the trigger in observable terms — a system down past a stated window, a facility unavailable, a key supplier unable to deliver — and name who has the authority to declare it. Without that, staff either over-react to routine outages or wait too long because nobody wants to be the one who escalated.

Interdependencies are the other gap. Glocert's ISO 22301-based guidance defines a business continuity plan as "a documented set of procedures" that guide an organization to "respond, recover, resume, and restore operations" after a disruption — four distinct phases, and most plans only really cover the first two. Recovery and restoration depend on things outside your building: the single supplier, the payroll processor, the one person who knows the scheduling system. The standard's structure reflects that continuity is a management system rather than an ad hoc activity, with Clause 8 as the operational clause requiring plans and recovery procedures to be established, including business impact analysis, risk assessment, strategies, plans, and exercises.

Writing the plan is the small part; exercising it is the work

Schedule the first exercise before the plan is finished, and make it small. A tabletop walkthrough — the core team in a room, a written scenario, a facilitator reading out injects — takes a couple of hours and surfaces more problems than any amount of editing. Run it against the activation criteria first: read the scenario, ask who declares, and see whether the answer is unambiguous. Then walk the communication requirements and watch how long it takes the group to find a current phone number for a key supplier. That exercise alone usually produces a list of corrections longer than the plan's revision history to date.

ISO 22301's requirements span five clauses — 6 through 10, covering planning, support, operation, performance evaluation, and improvement, as of 2019. The last two are the ones small businesses skip, and they are the ones that keep the plan alive. Performance evaluation means you check whether the plan works; improvement means you act on what the exercise found. A plan that has never been exercised has an unknown failure rate, and the failures tend to be mundane: an out-of-date contact list, a backup that was never restored in testing, a role assigned to someone who left.

The cost is real. Exercises take staff hours away from revenue work, and for a business of a few people that is the whole argument against doing them. The counter-argument is that the exercise is where you find out the plan is wrong, and finding out during a real disruption is more expensive. If full exercises are out of reach, exercise one component at a time — a call tree, a backup restore, a supplier contact — rather than nothing. What you should not do is treat the written plan as evidence that you are prepared.

Who owns the documents after they are written

Name one owner for each document and one backup for that owner. The executive summary belongs to whoever is closest to the financials and the strategy — usually the owner or a senior manager — because it has to be revised whenever the numbers or the direction change. The continuity plan belongs to whoever would actually run the response, not necessarily the most senior person. Assigning the BCP to the owner is the most common structural mistake: the owner is often the person unreachable or incapacitated in the scenario you are planning for.

Roles and responsibilities are a required element under Clause 8.4 for exactly this reason. Write them as named positions with named backups, and check that the person in each role knows it. The quiet failure is a plan with a role matrix that nobody outside the drafting room has seen. A short briefing — walking each named person through their role and the activation criteria — costs an hour and converts a document into a capability.

Review cadence matters more than review depth. Pick a fixed interval and a trigger list: a change of premises, a change of key supplier, a change in ownership, a new system that operations depend on. Trigger-based review catches the changes that matter between scheduled reviews, and it is cheaper than a full rewrite. The trade-off is administrative overhead — someone has to hold the trigger list and act on it. Without that, the review interval passes, the plan is skimmed, and the stale sections survive another cycle.

Where the two documents overlap, and why that matters

Your business plan and your continuity plan should agree on the facts, and they usually do not. The business plan describes facilities, location, employees, and key relationships; the continuity plan depends on all of those being current. When the business plan's executive summary says one thing about the facility and the continuity plan's resource list says another, one of them is wrong, and you will discover which at the worst moment. Reconcile them at each review — it takes minutes if both owners are in the same conversation.

Business plan executive summaryBusiness continuity plan
Primary readerLenders, investors, partnersThe response team, at the moment of disruption
Core contentMission, history, founders and functions, employees, location, facilities, products or services, banking and investor information, growth, future plansPurpose and scope, objectives, activation criteria, implementation procedures, roles and responsibilities, communication requirements, interdependencies, required resources, information flow and documentation
Standard or template behind itRutgers SBA-aligned business plan templateISO 22301, Clause 8.4
How you know it worksA reader can restate where the company is and where it is goingAn exercise produces corrections, and the corrections are made
Typical failureSummary drifts out of date or contradicts the financialsNo activation criteria, no exercise, roles assigned to people who have left

The two documents share a discipline rather than a format: both are judged by whether someone else can act on them. The executive summary is tested when a lender decides whether to keep reading. The continuity plan is tested when a disruption happens and someone has to decide, in the first few minutes, whether to activate it and who to call. Neither test cares how long the document is. Both care whether the specifics are current and whether the person holding it knows what to do next.

Version control is the maintenance job nobody assigns

Give each document a version number and a date on the cover, and keep one master copy in a place the whole response team can reach. The failure this prevents is specific: two people holding two different copies of the continuity plan, one of which still lists a supplier you dropped or a phone number that no longer rings. When the plan lives in three inboxes and a printed binder, nobody can say which one is current. A dated cover page and a single master folder solve it. The cost is that someone has to be the person who files the new version and marks the old one superseded, and that job gets dropped first when things are busy. If nobody owns it, version control quietly stops working and you will not notice until an exercise turns up the stale copy.

The same discipline applies to the executive summary. The Rutgers template's contents — banking relationships, employee count, facilities — are exactly the facts that change without anyone updating the document. A summary that was accurate at the last loan application and was never revised is a liability, not an asset.

What to check before you call either document done

Test both documents against a reader who was not in the room when they were written. For the continuity plan, that means handing the activation criteria to someone who would be on call and asking them to decide, from the written criteria alone, whether a given situation triggers the plan. If they hesitate, the criteria are not written in observable terms yet. Clause 8.4, as of 2019, requires activation criteria and implementation procedures as named contents precisely because a plan that assumes the reader already knows is not a procedure document.

For the executive summary, the test is whether a reader can restate where the company is and where management intends to take it after one pass. The Rutgers template frames the summary's job in exactly those terms, which makes it a checkable claim rather than a matter of taste. If the reader cannot restate it, the summary is describing the business rather than orienting the reader.

The limit of both tests is that they measure comprehension, not accuracy. A clearly written plan built on an out-of-date supplier list still reads well and still fails. Comprehension checks catch the unclear document; only the review triggers and the exercise catch the stale one. You need both, and the cheap one is the read-through — so do it first, before you spend staff hours on a drill.