Section

Industry Spotlights

Every industry spotlight on this site comes down to the same handful of documents and the same handful of decisions, and the two that matter most are the business plan and the business continuity plan. One gets you money; the other keeps you operating when something breaks. Both are routinely done badly for the same reason: owners treat them as paperwork to satisfy someone else rather than as working tools they will actually use. The sections below take the mechanics of each seriously — what the standard or template actually requires, in what order you build it, what it costs you in time and money, and where the approach stops being worth it.

7 articles

Industry Spotlights

Industry Spotlights

By reference
Starting a successful landscaping service business plan
Industry Spotlights

Starting a successful landscaping service business plan

The single biggest mistake new landscaping service owners make is treating their business plan as a binder full of documents for the bank, and then filing it away once they get the loan.

12 SepOpen
A detailed small business plan for laundromat operations
Industry Spotlights

A detailed small business plan for laundromat operations

When approaching a small business plan for laundromat operations, you have two usual paths: creating a highly detailed document aimed solely at securing investment capital, or building an internal…

11 SepOpen
Developing a profitable salon business plan
Industry Spotlights

Developing a profitable salon business plan

When drafting your salon's business plan, remember that stakeholders—be they lenders, investors, or bank representatives—will spend most of their time reading the Executive Summary; this section must…

8 SepOpen
Creating a successful bakery business plan
Industry Spotlights

Creating a successful bakery business plan

When presenting a plan to potential investors, do not start with your mission statement; begin by providing an executive summary that immediately summarizes where the bakery currently stands…

6 SepOpen
Creating a robust business plan for restaurants
Industry Spotlights

Creating a robust business plan for restaurants

“Is a business plan just something I have to make for the bank?” No; it is fundamentally an operational roadmap that forces you, the owner, to think through every potential failure point in your…

4 SepOpen
Developing a strong business plan for a food truck
Industry Spotlights

Developing a strong business plan for a food truck

A strong business plan for your food truck must prioritize its executive summary as the most important section because it provides decision-makers with a concise overview of your entire venture…

1 SepOpen
Developing a food truck business plan
Industry Spotlights

Developing a food truck business plan

“What do I do after I write down my dream menu and estimate some startup costs?”…

27 AugOpen

Every industry spotlight on this site comes down to the same handful of documents and the same handful of decisions, and the two that matter most are the business plan and the business continuity plan. One gets you money; the other keeps you operating when something breaks. Both are routinely done badly for the same reason: owners treat them as paperwork to satisfy someone else rather than as working tools they will actually use. The sections below take the mechanics of each seriously — what the standard or template actually requires, in what order you build it, what it costs you in time and money, and where the approach stops being worth it.

Why the executive summary decides whether your business plan gets read

The executive summary is the most important section of a business plan, and it is the last thing you should write. Rutgers Business School's Small Business Administration–aligned business plan template says so outright, calling it "the most important section" and describing its job as providing "a concise overview of the entire plan along with a history of your company" — where the company is now and where you want to take it. Write it first and you will rewrite it three times, because the numbers in your financial projections will move and the summary has to match them.

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 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 long list for a section that runs one to two pages. The compression is the point. A lender or investor reads the summary to decide whether to read anything else, and the summary has to survive that skim on its own.

Two practical consequences follow. First, the summary must contain real figures, not adjectives — the same revenue, margin and headcount numbers that appear later in the plan, so a reader who checks finds them consistent. Second, it must name the ask. A summary that describes a healthy company but never states how much capital is being sought, on what terms, and what it will be spent on forces the reader to hunt, and most readers won't. The common belief that the executive summary is just a brief introduction is wrong on the template's own terms; it is the section decision-makers rely on to understand the entire plan and the company's trajectory.

The honest limitation: for a solo owner-builder funding the business from savings and a credit card, a full SBA-style plan is often overkill. The summary still earns its place if you ever apply for a commercial lease, a line of credit or a supplier account, because someone will ask for it. But don't spend a week polishing prose when the underlying projections are guesses. The summary can only be as good as the plan behind it.

What a lender or investor is actually looking for in the plan

A business plan is a formal written document presenting the mission, history, operations, products or services, facilities, ownership, financial relationships, growth highlights and management's future plans, written to inform lenders, investors and other stakeholders. The order of those elements is not arbitrary. Readers move from who you are, to what you sell, to whether the numbers work, to what could go wrong — and they abandon the document at the first section that feels thin.

The section owners underestimate most is the one on ownership and financial relationships. The Rutgers template folds banking relationships and investor information into the executive summary itself, which tells you how much weight readers put on knowing exactly who owns what and who already has a claim on the business. If you have a partner, a family loan or an existing credit line, it goes in early. A lender who discovers a second lienholder late in the process stops trusting the rest of the document.

Growth highlights deserve the same treatment. A plan that says the business is growing is worth less than one that shows the growth and explains what produced it — a new location, a contract, a price change. Management's future plans then have to connect to that history. The failure mode is a plan whose past and future read like two different companies: three pages of steady, careful history followed by a hockey-stick projection with no mechanism behind it.

Where this approach costs you: a full plan takes real hours, and if you are pre-revenue with no trading history, several sections will be thin no matter how well you write them. In that case a shorter document with strong financial assumptions and an honest account of what you don't yet know beats a padded one. Lenders have read thousands of these; they can tell the difference between a plan that has been thought through and one that has been formatted.

How ISO 22301 structures a business continuity plan

A business continuity plan is a documented set of procedures that guides an organization to respond, recover, resume and restore operations following a disruption, and ISO 22301 — the international standard for business continuity management systems — treats it as a formal requirement rather than a good idea. Under the standard as structured in 2019, five clauses (6 through 10) cover the core planning requirements: planning, support, operation, performance evaluation and improvement. Continuity planning is therefore an integrated, systematic requirement inside a management system, not an ad hoc activity you get to when things are quiet.

The operational weight sits in Clause 8, which requires business continuity plans and recovery procedures to be established, including the business impact analysis, risk assessment, strategy selection, plan development and exercises. Clause 8.4 is the one that governs the document itself. It specifies that a compliant plan must define its purpose and scope, objectives, activation criteria, implementation procedures, roles and responsibilities, communication requirements, interdependencies, required resources, and information flow and documentation. Read that list again: activation criteria and roles and responsibilities are in it. A plan that says "in the event of a disruption, senior management will coordinate the response" fails on both counts.

The sequence inside Clause 8 matters more than the clause numbering. You do the business impact analysis first, because it tells you which activities are time-critical and how long they can be down. The risk assessment tells you what is likely to interrupt them. Only then do you choose strategies — a second site, a backup supplier, cross-training, a generator — and only then do you write the plan and exercise it. Skipping to the plan is the single most common failure. You end up with a document that describes a response to a disruption nobody has ranked, staffed or funded.

The trade-off is real. A management-system approach to continuity is heavier than most small businesses need: documented processes, internal audit, management review, corrective action. If you run a five-person shop, the full ISO 22301 apparatus is probably the wrong tool. What transfers is the content of Clause 8.4 — purpose, scope, activation criteria, roles, communications, interdependencies, resources — because that is what you actually reach for at two in the morning when the power is out and the phone is ringing.

Building the continuity plan in the order that works

Start with the impact analysis, not the document. List every activity the business performs, then for each one ask how long it can stop before the damage becomes serious — lost customers, missed contractual deadlines, spoiled stock, regulatory breach. The answers sort themselves into tiers quickly, and the tiers tell you where to spend money. For most businesses a handful of activities carry almost all the risk: order intake, the one system everyone works in, the physical premises, and the two or three people who know how everything fits together.

Then write the activation criteria. The standard requires them, and they are the part owners most often skip. Criteria should be observable and specific: who declares an incident, at what point, and who has authority to invoke the plan in that person's absence. The failure mode is a disruption where everyone waits for a decision from someone who is unreachable, and the recovery starts hours late because nobody was authorized to start it. Name a primary and a backup, and write down how they reach each other when the usual channels are down.

Roles and responsibilities come next, assigned to positions rather than names where you can. A plan that says "Maria will contact customers" becomes obsolete the week Maria leaves. Communication requirements deserve their own page: staff, customers, suppliers, insurers, landlord, bank, and any regulator that applies to your sector. For each, note what they need to hear, who tells them, and through which channel — and have a channel that doesn't depend on the system that just failed. Interdependencies and required resources are the practical inventory: which suppliers you cannot substitute, which equipment you would need to rent, what it would cost and how quickly it could arrive.

Finally, exercise it. A plan that has never been run is a hypothesis. A tabletop exercise — a couple of hours, a plausible scenario, the key people in a room — surfaces the gaps cheaply: the phone list with a disconnected number, the backup that has never been restored, the assumption that someone else holds the building keys. Then revise. The standard's improvement clause exists because the first version is always wrong somewhere.

What each plan costs you, in money and in time

Neither document is expensive in cash for a small business; both are expensive in attention, and that is the real budget. A business plan built from a free template like the Rutgers SBA one costs nothing but the hours, and the hours are substantial — the research, the projections, the rewriting. A continuity plan built to the content of Clause 8.4 costs little beyond the time to do the impact analysis properly and the discipline to run an exercise once a year. Where money does enter is in the mitigation: the backup generator, the second supplier, the cloud failover, the cross-training that costs you productivity while it happens.

DecisionWhat it buys youWhat it costsWhen it is the wrong call
Full SBA-style business planA document lenders and investors expect; forces the numbers to be coherentSignificant writing time; needs revisiting as figures changeSelf-funded business with no external stakeholder asking for it
Full ISO 22301 management systemCertifiable, auditable continuity across the whole organizationDocumented processes, internal audit, management reviewSmall teams without a customer or regulator demanding certification
Clause 8.4 content onlyThe working plan: activation criteria, roles, communications, resourcesTime for impact analysis and a yearly exerciseNever, for an operating business — this is the minimum useful version
Annual tabletop exerciseFinds the broken phone numbers and false assumptions before a real event doesA few hours of key people's timeOnly if the plan is never going to be used, which defeats the purpose

The comparison that matters is not business plan versus continuity plan. It is doing either one properly versus doing it to tick a box. A plan written for a loan application and never opened again has bought you the loan and nothing else. A continuity document that lives in a drawer has bought you nothing at all, because the moment you need it is the moment you cannot calmly read it for the first time.

Where the standard advice goes wrong

Three beliefs cause most of the damage. The first is that the executive summary is a formality — a short introduction before the real content. The Rutgers SBA template contradicts that directly by naming it the most important section, and the practical test is simple: hand someone only the summary and see whether they understand the business, the numbers and the ask. If they can't, the summary isn't finished.

The second is that a continuity plan can stay at the level of high-level statements. ISO 22301-based guidance shows the opposite: purpose and scope, objectives, activation criteria, implementation procedures, roles and responsibilities, communication requirements, interdependencies, required resources, and information flow and documentation are all required content. Detailed operational material is the requirement, not an optional extra. A plan without named roles and trigger points is a statement of intent, and intent does not restore operations.

The third is that continuity planning is optional and separate from how the business is run. ISO 22301 makes it a formal management system with specific clauses for planning, support, operation, performance evaluation and improvement — a systematic requirement rather than an ad hoc activity. Even if you never seek certification, the discipline of reviewing the plan after every exercise and every near-miss is what keeps it from going stale.

The limits are worth stating plainly. Standards and templates describe the shape of a good document; they cannot supply your judgment about which activities matter most or how much downtime your customers will tolerate. That judgment is the actual work, and it is not delegable to a template. The documents are only as good as the thinking behind them — and the thinking is the part you can't outsource.