Small business ownership comes down to two documents most owners never write properly: a business plan that convinces someone else to fund you, and a continuity plan that keeps you trading when something breaks. Everything else — entity choice, insurance, payroll, tax elections — hangs off those two. The order matters more than most people expect, because the second document is often what a lender or insurer asks for after the first one gets you in the room.
The business plan exists to answer one question: where is this going
The executive summary is the part of a business plan that gets read, and it is the part most owners write last and worst. The Small Business Administration–aligned template published by Rutgers Business School calls it "the most important section" and describes its job plainly: it "provides a concise overview of the entire plan along with a history of your company," covering where the company is now and where you want to take it.
That framing is worth sitting with, because it kills the common assumption that the summary is a throat-clearing paragraph before the real content. It is the only section a loan officer or an angel investor is guaranteed to finish. If the summary does not tell them the trajectory, the rest of the document does not get read.
The same template lists what belongs in it: mission statement, 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. That is a lot to compress, and the compression is the point — each item gets a sentence or two, not a page.
Two items on that list catch owners out. Banking relationships and investor information is a line most first-time writers skip because they think it is private; lenders read its absence as a sign the owner has not thought about how money moves through the business. Founders and their functions is the other — naming a founder without saying what they actually do day to day reads as a hobby, not a company.
The honest trade-off: a business plan built to a template like this one is not a strategy document. It will not tell you whether to open a second location. What it does is force you to state, in writing, the number of employees, the facilities, and the growth you are claiming, which is exactly the material a bank wants and exactly the material that becomes uncomfortable when it stops being true. Plan to rewrite the summary every time a material fact changes, not annually.
The business continuity plan is a different document with a different job
A business continuity plan is a documented set of procedures that guides an organization to respond, recover, resume, and restore operations following a disruption. The definition comes from ISO 22301 guidance as interpreted by Glocert, and the four verbs matter: responding is not the same as recovering, and resuming operations is not the same as restoring them. A plan that only covers the first two leaves a business running at partial capacity with no route back.
ISO 22301 is an international standard for business continuity management systems, and it treats continuity as a formal management system rather than an ad hoc activity — with requirements spanning planning, support, operation, performance evaluation, and improvement. As of 2019, five clauses (6 through 10) carry the core requirements, and Clause 8 is the operational one: it requires that business continuity plans and recovery procedures actually be established, including the business impact analysis, risk assessment, strategies, plans, and exercises.
Clause 8.4 is where the standard gets specific about what the document must contain. A compliant plan defines purpose and scope, objectives, activation criteria, implementation procedures, roles and responsibilities, communication requirements, interdependencies, required resources, and information flow and documentation. That list is the single most useful checklist in this whole subject, and it is the reason the common belief that a continuity plan can be a few high-level statements is wrong — detailed operational content is required, not optional.
Activation criteria deserve their own mention because they are the item most small plans omit. Without a written threshold, nobody knows who declares an incident or when, so the decision gets made late, informally, and by whoever is closest to the problem. Name the person, name the trigger, and write down who they call first.
The cost is real: a plan built to Clause 8.4 takes weeks, not an afternoon, and the business impact analysis — the step where you work out which functions and systems actually keep revenue moving — is tedious. It is also the step that produces the useful output. Owners who skip it end up with a plan that protects the wrong things.
Insurance, entity, and tax decisions come after, not before
Entity choice and coverage get decided in the first weeks of a business and then quietly constrain everything afterward. The sequence that causes the fewest problems is: form the entity, open the business bank account the plan's executive summary will reference, then buy coverage against the risks the continuity plan just identified. Doing it in the reverse order — buying a package policy before you know which functions are critical — usually produces coverage that duplicates itself and misses the actual exposure.
The continuity work feeds directly into the insurance conversation. Once you have written down your interdependencies and required resources, you know which suppliers, systems, and premises need to appear on a policy. Insurers and lenders increasingly ask for continuity documentation alongside financial statements, and a plan that names activation criteria and roles reads very differently to an underwriter than a one-page assurance that the owner "has a plan."
Tax elections are the decision most often made by default rather than on purpose. The choice of how a multi-member LLC is taxed, and the payroll setup that follows from it, changes the compliance calendar for years. This is the point to get an accountant involved rather than a template — the rules differ by structure and by state, and the cost of getting it wrong shows up as penalties rather than a clean bill.
What this ordering costs: time before you are trading, and professional fees before you have revenue. What the reverse ordering costs: an entity that does not match how you actually operate, insurance that covers the wrong risks, and a continuity plan written to satisfy a template instead of your business.
Hiring and payroll: the first genuinely irreversible commitment
Adding the first employee is the decision that turns a sole proprietorship into an operation, and it is the one most owners underestimate. The business plan's executive summary will state a number of employees — that figure becomes a commitment you report to lenders and carry on your books, and it drives payroll tax registration, workers' compensation, and in most states an unemployment insurance account.
The continuity plan and the hiring decision meet in an uncomfortable place: the Clause 8.4 requirement to define roles and responsibilities. In a one-person business, that section is short and slightly absurd. With staff, it becomes the document that tells you who covers what when the person who normally does it is unavailable. Write the roles section before you hire, not after, and you will find out whether the role you are about to fill actually has a defined function or is a reaction to being busy.
The trade-off here is between hiring ahead of demand to protect capacity and hiring behind demand to protect cash. Both are defensible. What is not defensible is hiring without having written down what the new person is responsible for, because that is the gap a continuity plan exposes and the gap that turns a single absence into a bad month.
Cash, credit, and the numbers a lender will actually check
Lenders and investors read the executive summary for the trajectory and then verify it against the financials, and the verification is where applications fail. The summary lists banking relationships and investor information for a reason: a bank wants to see that the account exists, has history, and matches the revenue you are claiming.
Three things get checked most often. First, whether the growth highlights in the summary are consistent with the numbers in the statements — a summary claiming rapid growth against flat deposits ends the conversation. Second, whether the ownership and founders section matches the entity documents on file. Third, whether the facilities described match a real lease or a real address.
Continuity planning belongs in this section too, because a lender's real question is what happens to repayment if the business is disrupted. A plan that names interdependencies and required resources, and that has been exercised at least once, answers that question in a way a verbal assurance cannot. The exercise is the part owners skip; it is also the only part that proves the plan works.
Where this approach is the wrong choice: if you are funding the business entirely from retained earnings with no lender or investor involved, the SBA-aligned template's emphasis on banking relationships and investor information is mostly overhead. Write the mission, the operations, and the growth plan for your own use and skip the sections aimed at external readers.
Continuity is a management system, not a binder on a shelf
ISO 22301's structure is the argument against treating continuity as a one-time document. The standard sets requirements across planning, support, operation, performance evaluation, and improvement — five clauses as of 2019 — which means the plan is supposed to be reviewed, tested, and revised, not filed.
The practical shape of that for a small business is a short cycle. Once a year, revisit the business impact analysis: have your critical functions changed, has a supplier been replaced, has a key person left? Once a year, run an exercise against the activation criteria and see whether the named person actually made the call. Then update the plan and record what changed. That record is what distinguishes a management system from a binder.
| Document | Primary reader | What it must contain | When it goes stale |
| Business plan (executive summary) | Lender, investor, sometimes a partner | Mission, history, founders and functions, employees, location, facilities, products, banking and investor information, growth, future plans | Any material change in ownership, headcount, facilities, or financial position |
| Business continuity plan | Owner, staff, insurer, lender | Purpose and scope, objectives, activation criteria, implementation procedures, roles and responsibilities, communication, interdependencies, resources, information flow | Any change in critical functions, suppliers, systems, or key people — reviewed at least annually and after every exercise |
The two documents share a spine: both force you to state where the company is and what it depends on. The business plan says where you are going; the continuity plan says what you will do when the route closes. An owner who has written both, and revised both after something went wrong, is in a materially better position than one who has a plan in a drawer and a policy in a folder — because the first owner knows which of the two to open, and when.
Writing activation criteria that actually get used
Activation criteria work when they name a person and a condition, and fail when they describe a mood. "When operations are significantly disrupted" is not a criterion — it invites an argument at the worst possible moment. A usable trigger reads like an instruction: a named role declares activation, a backup is named in case that person is unreachable, and the condition is something observable rather than debatable. ISO 22301-based guidance treats activation criteria as mandatory content under Clause 8.4, alongside implementation procedures and roles, so this is not a nicety you add once the rest is done.
The common failure mode is a plan with detailed recovery procedures and no front door. You notice it in an exercise: the scenario starts, everyone looks at the owner, and the owner says they weren't sure it was serious enough to invoke. Write the criteria before the procedures, test them in the exercise, and revise whichever one broke.
The exercise is the only proof the plan works
An untested continuity plan is a claim, not a capability, and the exercise is where Clause 8's requirement for plans and recovery procedures gets validated rather than asserted. You do not need a full simulation. Walk the activation criteria with the people named in them, have them place the calls they would place, and time how long it takes to reach the person who can authorize the spend. What goes wrong is usually mundane: a supplier contact list that is months out of date, a phone tree that assumes everyone checks email, a backup site nobody has visited.
Run it annually and after any change to critical functions, suppliers, systems, or key people, then record what changed in the plan. That record is the difference between a management system and a binder, and it is what an insurer or lender is actually reading when they ask whether the plan has been exercised. The cost is a half-day and some discomfort; the alternative is discovering the gaps during the disruption itself.