Two documents do most of the work of keeping a small business alive through a crisis and through a loan application: the business continuity plan, which tells you and your staff how to respond, recover, resume, and restore operations after a disruption, and the business plan, whose executive summary is described by Rutgers Business School's SBA-aligned template as "the most important section." Both are shorter than owners expect, both fail for the same reason — they get written for the file cabinet rather than for the person who has to use them at 6 a.m. on a bad day — and both are judged by a standard you can read in advance. What follows is how each one is actually structured, which decisions come first, what the formal standards require, and where the honest trade-offs sit.
What a business continuity plan has to contain, and why the standard is stricter than most owners assume
If you want a plan that would survive scrutiny under ISO 22301, the international standard for business continuity management systems, the content list is not optional and it is not high-level. Clause 8.4 of the standard 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. That is a long list, and the item most small plans skip is activation criteria — the written trigger that tells a manager whether this is a real disruption or a bad morning.
The reason activation criteria matter more than the rest is that every other section depends on someone deciding to invoke the plan. Without a written threshold, invocation becomes a judgment call made under stress by whoever happens to be on shift, and the common outcome is that the plan is activated late or not at all. Write the trigger as a condition, not a feeling: "no access to the primary site for more than one business day," "payment processing unavailable during business hours," "the only person who runs payroll is unreachable." The standard's language about roles and responsibilities exists for the same reason — a plan that says "management will coordinate" has assigned the work to nobody.
ISO 22301 treats continuity as a formal management system rather than an ad hoc activity, structured across five core clauses (6 through 10) covering planning, support, operation, performance evaluation, and improvement, as of 2019. Clause 8 is the operational clause that requires business continuity plans and recovery procedures to be established, including the business impact analysis, risk assessment, strategy selection, plans, and exercises. That sequence is the part owners get backwards. The impact analysis and risk assessment come first because they determine what the plan is protecting; a plan written before that work is a generic template with your logo on it, and it will not match your actual dependencies.
The cost is time, and it is real. A first pass at the impact analysis means sitting down with each function of the business and asking what stops if it goes dark for a day, then a week — and the answer is often a supplier, a single credential, or one employee's knowledge rather than a building. The limit of the standard is that certification is a heavier lift than most small firms need; you can borrow ISO 22301's structure without pursuing certification, and for many businesses that is the right trade. What you should not do is skip the structure entirely and write a page of reassuring sentences, because the standard's content list is essentially a checklist of what will actually be missing when you need it.
The order of work: impact analysis, risk assessment, strategy, then the written plan
Build the plan in four stages and resist the urge to start with the document. Stage one is the business impact analysis: for each function, identify how long the business can tolerate it being down and what it depends on. Stage two is the risk assessment, which looks at what could cause that downtime — a failed HVAC unit over a server closet, a key supplier's bankruptcy, a flood plain, a ransomware event. Stage three is strategy: for each critical function, choose between accepting the risk, reducing it, transferring it (insurance), or building a workaround. Stage four is writing the plan that Clause 8.4 describes, mapping each strategy to procedures, roles, and resources.
The practical reason to keep that order is that strategies are where the money goes, and they should be chosen deliberately rather than implied by whatever the plan happens to say. A restaurant that discovers its single walk-in cooler is a critical dependency can choose to buy a backup compressor, to hold a standing agreement with a refrigerated truck service, or to accept a multi-day closure — three very different costs. The plan then records the choice and the activation criteria that trigger it, rather than leaving staff to improvise.
Where this breaks down is in businesses with no slack. If you are a two-person operation, a full impact analysis across every function is overkill; scope it to the functions whose failure would end the business within a month, and write a plan for those only. A narrow plan that gets exercised beats a comprehensive one that sits unread. The trade-off is coverage: the functions you exclude are genuinely unprotected, and you should say so in the plan's scope section rather than pretending otherwise.
Exercises are what turn a written plan into a usable one
A continuity plan is a draft until it has been exercised, and ISO 22301's Clause 8 includes exercises alongside the plans and procedures for exactly that reason. The first exercise is almost always humbling in the same specific ways: the contact list is out of date, the person who holds the building key is on vacation, the backup system restores data but not the configuration that makes it usable, and nobody knows who is authorized to spend money on an emergency repair. None of those problems show up on paper.
Start with a tabletop exercise — a couple of hours, a scenario, and the people named in the plan, walking through the first twenty-four hours against the written procedures. Then, once the plan survives that, test one technical recovery for real: restore a backup to a spare machine and confirm the business could actually run on it. The cadence matters less than the habit; an annual tabletop plus a periodic restore test catches most of what goes stale.
The honest cost here is staff time and the discomfort of finding failures on purpose. Owners sometimes skip exercises because a failed test feels like bad news, but the failure is cheaper to discover in a scheduled exercise than during an actual outage. The limit of tabletop exercises is that they test decision-making and communication, not infrastructure; they will not tell you whether your backup is corrupt. Only a restore test does that.
What the executive summary of a business plan must contain, and the mistake that sinks it
The executive summary is not a warm-up paragraph. Rutgers Business School's SBA-aligned template calls it "the most important section" and says it "provides a concise overview of the entire plan along with a history of your company," telling the reader where the company is and where management wants to take it. Lenders and investors frequently read it first and sometimes read nothing else, which is why it has to stand alone.
The template's contents list is specific: mission statement, the date the business began, founders and their functions, number of employees, business location, description of facilities, products or services, banking relationships and investor information, a summary of company growth, and a summary of management's future plans. Notice how much of that is factual rather than persuasive — dates, headcount, banking relationships. A summary that opens with an aspirational sentence about passion and never states when the business started or who runs it has failed the reader who is deciding whether to keep reading.
The common belief that the executive summary is just a brief introduction is contradicted directly by the template's own language: it is the section decision-makers rely on to understand the entire plan and the company's trajectory. The practical consequence is that you should write it last, after the financials and operations sections are settled, so that the numbers it quotes match the body. The trade-off is length. "Concise overview" is doing real work in that description — a summary that runs several pages has stopped summarizing, and one that runs a few paragraphs without the required contents has stopped informing.
Where the two documents overlap, and why continuity belongs in the business plan
The business plan's executive summary and the continuity plan's scope section answer the same underlying question — what does this business depend on, and what happens if it loses it — and putting a continuity sentence in the business plan is cheap insurance. Lenders increasingly ask what happens to repayment if operations stop; a business plan that names its critical dependencies and its continuity arrangements answers that before it is asked. The Rutgers template's growth summary and management future plans sections are natural places to note that a continuity plan exists and has been exercised.
The overlap runs the other way too. The continuity plan benefits from work you did for the business plan: the facilities description, the list of key personnel and their functions, and the banking relationships are all inputs to a business impact analysis. If you have already written a business plan, you are further into continuity planning than you think, and the remaining work is mostly the risk assessment and the activation criteria.
What does not transfer is the audience. The business plan is written for an outside reader who will judge it; the continuity plan is written for your own staff, under pressure, possibly without you. That difference should show in the prose. The continuity plan can be blunt and procedural — "call this number, then this one, then open the secondary site" — where the business plan needs to be persuasive. Reusing the same polished paragraphs in both is a sign that neither was written for its actual reader.
Choosing what to formalize, and what a lighter version costs you
Not every business needs ISO 22301 certification, and not every business needs a fifty-page business plan, but the decision about how much to formalize should be made on the basis of who will read the document and what they will do with it. A business seeking a bank loan or outside investment needs a business plan with a complete executive summary because that is what the reader expects. A business whose main risk is a single point of failure in operations needs a continuity plan scoped to that failure, with activation criteria and named roles, whether or not it ever pursues certification.
| Decision | What it gets you | What it costs |
|---|---|---|
| Full ISO 22301-aligned continuity program | Coverage across the five core clauses (6–10) — planning, support, operation, performance evaluation, improvement — and a plan meeting the Clause 8.4 content list | Substantial staff time for impact analysis, risk assessment, exercises, and review; certification adds audit cost on top |
| Scoped continuity plan for critical functions | Activation criteria, roles, and procedures for the failures that would end the business | Excluded functions are unprotected; the plan's scope section should say so |
| SBA-aligned business plan with full executive summary | A document that stands up to lender and investor reading, with the contents the template specifies | Time to write it last and keep it consistent with the financials; must be revised as the business changes |
| Minimal or informal versions of either | Lower upfront effort | Continuity becomes an ad hoc activity rather than a systematic requirement; the business plan's most important section is left thin |
The pattern across both documents is the same: the formal version is not harder to write than the informal one, it is just harder to fake. A continuity plan that names its activation criteria, its roles, and its interdependencies takes an afternoon or two once the analysis is done, and the analysis is the part that actually protects the business. An executive summary that covers the template's list takes less time than the rest of the business plan and carries more weight with the reader. The failure mode in both cases is writing something that sounds complete without doing the thinking behind it — and the way you find out which one you have is to exercise the plan, or to hand the summary to someone who will decide something based on it.







