Two documents do most of the work of getting a small business through a bad year: a business plan that tells a lender or investor where the company is and where it's going, and a business continuity plan that tells your own people how to keep operating when something breaks. They are not the same document, they are not written the same way, and the order you draft them in matters. This page walks through both, the decisions each one forces, and what those decisions cost.
Start with the executive summary, and write it last
The executive summary of a business plan is the most important section, according to Rutgers Business School's Small Business Administration–aligned template, which says plainly that it "provides a concise overview of the entire plan along with a history of your company." That's an uncomfortable instruction, because you can't summarize a plan you haven't written. The practical sequence is to draft the body first — operations, market, financials — and write the summary once the numbers are settled, then rewrite it after anyone else reads the plan and tells you what confused them.
The Rutgers template lists what belongs in that summary: a mission statement, the date the business began, the founders and their functions, the number of employees, the business location, a description of facilities, products or services, banking relationships and investor information, a summary of company growth, and a summary of management's future plans. Read that list twice. It is not a pitch. It's a fact sheet with a trajectory attached — where you are now, and where management intends to take the company. Lenders read it to decide whether to keep reading.
What it costs: an afternoon of drafting and probably two rounds of revision, plus the discipline to keep it to a page or two. The failure mode is writing it first, as a kind of aspirational cover letter, and then discovering the body of the plan contradicts it. The other failure mode is treating it as a formality. The common belief that the executive summary is just a brief introduction is contradicted directly by the Rutgers template, which calls it the most important section — the overview decision-makers rely on to understand the entire plan and the company's direction. If your summary is vague, the reader assumes the plan behind it is vague too.
The rest of the business plan is a financial argument in prose
The body of the plan exists to support the numbers in the summary. In practice that means three blocks: what the business does and for whom, how it operates day to day (facilities, staffing, suppliers, equipment), and the financial picture — historical performance if you have it, projections if you don't, and the banking and investor relationships that fund both. The SBA-aligned structure treats these as sections of one document, not separate exercises, and that matters because the sections have to agree with each other. A growth highlight in the summary that isn't visible in the financials is the fastest way to lose a loan officer's confidence.
Write the operations section before the financials, not after. You can't project staffing costs without knowing who does what, and you can't describe facilities without knowing what equipment sits in them. Small businesses typically underestimate the time this takes — it's a few days of real work, longer if you have to dig up old tax returns and bank statements to reconstruct history.
Be honest about the limits here. A business plan is a snapshot, and projections are guesses with arithmetic attached. The plan's job isn't to predict; it's to demonstrate that you know your own operation well enough to be trusted with someone else's money. If you're funding the business entirely from cash flow and have no lender or investor in view, a full formal plan is arguably the wrong tool — a one-page summary of the same facts will serve you better than a document nobody reads.
A continuity plan is a different animal, with a different audience
A business continuity plan is a documented set of procedures that guides an organization to respond, recover, resume, and restore operations following a disruption, per Glocert's reading of ISO 22301. Note the four verbs: respond, recover, resume, restore. They describe a sequence in time, not a set of reassurances. Your audience isn't a lender. It's the person who opens the building at 6 a.m. and finds the server room flooded.
The common belief that a continuity plan only needs high-level statements is wrong on the standard's own terms. ISO 22301-based guidance requires defined purpose and scope, objectives, activation criteria, implementation procedures, roles and responsibilities, communication requirements, interdependencies, required resources, and information flow and documentation. That's a working document, not a policy. "We will maintain operations during disruptions" is not a plan; "the operations lead calls the backup site at this number, in this order, within this window" is.
What it costs: real time, and the willingness to write down things you'd rather not admit, like the fact that one employee holds all the supplier relationships or that your only copy of the customer database lives on a laptop. The trade-off is that a thorough continuity plan for a very small business can be longer than the business's actual complexity warrants. Scale it. A two-person shop doesn't need a fifty-page manual; it needs four pages that name the risks, the triggers, and who does what.
ISO 22301 gives continuity planning a structure — five clauses of it
ISO 22301 treats business continuity as a formal management system, not an ad hoc activity. Five clauses cover the core requirements — planning, support, operation, performance evaluation, and improvement — numbered 6 through 10 as of 2019. That structure is the reason continuity planning isn't optional for organizations that claim alignment with the standard: it's an integrated, systematic requirement that gets evaluated and improved on a cycle, the same way quality or environmental management does.
Clause 8 is the operational clause, and it's where the actual plans and recovery procedures get established — the business impact analysis, the risk assessment, the strategies, the plans themselves, and the exercises that test them. Clause 8.4 is the one that matters most for drafting: it specifies that a continuity plan must define purpose, scope, objectives, activation criteria, implementation procedures, roles and responsibilities, communication requirements, interdependencies, required resources, and information flow. Ten elements. If your draft plan is missing activation criteria or interdependencies, it isn't compliant, and more to the point, it won't work when someone needs it at 3 a.m.
| Clause 8.4 element | What it answers in practice |
|---|---|
| Purpose and scope | Which operations and locations this plan covers, and which it doesn't |
| Objectives | What "recovered" means for each critical function |
| Activation criteria | The specific conditions that trigger the plan, so nobody has to guess |
| Implementation procedures | The step-by-step sequence of who does what, in order |
| Roles and responsibilities | Named people and backups, not job titles alone |
| Communication requirements | Who is told what, by whom, through which channel |
| Interdependencies | Suppliers, systems, and functions this one depends on |
| Required resources | People, equipment, space, and money needed to execute |
| Information flow and documentation | How records move, and where the plan itself is kept |
The honest limitation: certification against ISO 22301 is a substantial undertaking, with audits and ongoing documentation burdens, and most small businesses will never pursue it. That doesn't make the clause structure useless — it makes it a checklist. Borrow the ten elements from Clause 8.4 as a drafting template and skip the certification apparatus. You get most of the operational value at a fraction of the cost.
The order of work: impact analysis, then strategies, then the plan document
Draft the continuity plan after the business impact analysis and risk assessment, never before. The BIA tells you which functions actually matter and how long each can be down before the damage becomes serious; the risk assessment tells you what's likely to interrupt them. Only then can you choose recovery strategies, and only after choosing strategies can you write procedures that make sense. Writing the plan first produces a document full of procedures for the wrong things.
In sequence: list every business function, decide which are critical and in what order they must come back, identify the dependencies each one carries, pick a strategy for each critical function (a backup site, a manual workaround, a cross-trained employee, a supplier with a second location), then write the procedures that put those strategies into motion, then assign named roles, then set the activation criteria. The activation criteria deserve particular care because they are where plans fail. If the threshold for invoking the plan is fuzzy, people wait too long hoping the problem resolves itself, and by the time they act the recovery window has closed.
Then test it. Clause 8 includes exercises among the operational requirements, and this is the part most small businesses skip. A plan that has never been read aloud by the people who would execute it is a hypothesis. A tabletop exercise — an hour, a scenario, the actual named role-holders in a room — will surface gaps in the communication section faster than any amount of rewriting. The cost is an hour or two per exercise, repeated on a schedule. The trade-off is that exercises are disruptive and occasionally embarrassing, which is exactly why they're useful.
Where the two plans touch, and what to keep separate
The two documents share a spine — both describe the business as it actually operates — but they should not be merged. The business plan's audience is external and its purpose is to secure resources; the continuity plan's audience is internal and its purpose is to keep the operation running when resources are gone. Mixing them produces an investor document cluttered with recovery procedures and a continuity plan padded with market analysis, and neither reader gets what they came for.
What should flow between them is facts. The facilities description in the business plan should match the locations named in the continuity plan's scope. The staffing numbers in the executive summary should match the roles and responsibilities section. If the business plan says twelve employees and the continuity plan assigns recovery duties to people who no longer work there, one of the documents is stale — and stale is the default state for both. Build a review cadence into each: the business plan when financials change materially, the continuity plan after every exercise and every significant staffing change.
One more distinction worth holding onto. The business plan's executive summary is explicitly the most important section, per the Rutgers SBA template, because it's what decision-makers read first. The continuity plan has no equivalent single section — its value is distributed across the ten Clause 8.4 elements, and a failure in any one of them shows up as a failure of the whole plan at the worst possible moment. That asymmetry tells you how to allocate your drafting time: compress and polish the summary, but build the continuity plan element by element and test it rather than trusting it.
Cross-training is the cheapest continuity strategy and the first one cut
Name a second person for every critical role in the plan, and write that name into the roles and responsibilities section rather than leaving it as a job title. ISO 22301-based guidance requires named roles and responsibilities under Clause 8.4, and a title is not a person — when the operations lead is unreachable, "operations lead" tells nobody who to call. Cross-training is the strategy that costs almost nothing in cash and a great deal in scheduling: a few hours per employee per quarter, run as a shadowing shift rather than a classroom session.
Write the procedure so it survives the absence of its author. A recovery procedure that only the person who wrote it can follow isn't a procedure, it's a memory. The test is whether someone who has never done the task can execute it from the page — which is why the cross-trained backup, not the primary, should be the one to read the draft aloud. What you give up is depth: a backup who shadows quarterly will be slower and will miss edge cases the primary handles by instinct. Price that into the recovery window instead of pretending it away, and keep the procedures for the highest-impact functions in the hands of the people who do them daily.
Keep the plan where the disruption can't reach it
Store at least one copy of the continuity plan off-site and offline, and put the location in the information flow and documentation element of Clause 8.4. A plan that lives only on the file server in the building that just flooded is not a plan; it's a document with a single point of failure that happens to be the same one the plan was written to address. Print a copy, keep it in a vehicle or a second location, and give the named role-holders their own.
Version control matters more here than in the business plan because the wrong version is actively dangerous. Date every page, name a single owner for revisions, and retire old copies rather than filing them alongside the current one — two undated versions in the same drawer guarantee someone grabs the wrong one at 3 a.m. The cost is administrative friction: someone has to reprint and redistribute after every revision, and that task gets skipped precisely when the plan has just changed for a good reason. Schedule the redistribution with the review, not after it.



