Putting a real process behind operations plans

Most operations sections are written last, in an afternoon, by someone who has stopped caring. That is where more plans fail than anywhere else.

The operations section is the only part of the document that can be checked against physical reality. A reader testing whether you thought about the business rather than the document goes there first.

This is a working day, split into seven sittings. Do them in this order. Each one produces something you can put on the page, and each one feeds the next.

What to take away

Before you start: what to have on the table

Gather these first, because hunting for them mid-draft is how a day becomes a week.

Bring any quote or written price from a supplier, landlord, installer, or contractor, plus a floor plan or sketch of the space, even rough. Add the specification of your largest equipment.

Write down your intended opening hours or service window, and list every permission, license, inspection, or registration you think applies. Bring a blank sheet for what you do not know; that sheet is the day's most valuable artifact.

Sitting one: trace one unit, forty-five minutes

Take one order, job, patient, cover, delivery, or subscription. If you have not yet settled what one of those is, stop and settle it in the product and service section first, because everything below is counted in that unit.

Write down every step from customer commitment to payment, in order, skipping nothing and merging nothing.

Write it as verbs. Someone answers. Someone quotes. Someone schedules. Someone buys the material. Someone does the work. Someone checks it. Someone invoices. Someone chases.

Then annotate each step with three things: who does it, how long it takes, and what happens when it goes wrong. Steps with no name attached are steps you have not staffed. Steps with no duration are steps you cannot cost. Steps with no failure mode have not been thought about.

Sitting two: find the ceiling, thirty minutes

Look at the list and ask what runs out first when demand doubles. It is usually one of five things: floor space, a machine, a licensed or skilled person, delivery vehicles, or the founder's own hours.

Name it in one sentence, then quantify it in the unit your business actually uses. Covers per service. Jobs per week. Installations per crew per day. Tickets one person can close in a shift.

That number is the ceiling on your revenue line, and the projections section has to live under it. A forecast that exceeds capacity without saying what was added, when, and at what cost is the single easiest thing for a reader to break, and they will.

Sitting three: premises, equipment and the cost of standing still

Write what you occupy, what you own, what you rent, and what stays available whether or not a customer arrives. Rent, insurance, connectivity, licenses, minimum staffing and equipment finance carry on during a quiet week, and the plan should say what a quiet week costs.

If you have a lease or a quote, say so and give the date. If you do not, say the figure is a quote you have requested and not yet received. Both are fine. A figure with no origin is not.

Sitting four: suppliers and inputs, thirty minutes

For each input you cannot make yourself, write the lead time, the minimum order, the payment terms, and whether a second source exists. Then mark the ones where the answer is no second source, because that is a risk paragraph you owe the reader later.

Payment terms belong here rather than in the financial section, because this is where you discover them. Paying a supplier in fourteen days while a customer pays you in forty-five is an operational fact that turns into a cash problem two sections later.

Sitting five: people and the shape of demand, forty-five minutes

Demand is rarely flat. Plot your week or your year in the roughest possible terms: which days, which months, which hours carry the load. Then staff the shape rather than the average, because staffing the average leaves you short at the peak and paying for idle time at the trough.

Say which roles must be filled by someone qualified, licensed or certified, and what you do when that person is unavailable. That is the same question the team section answers from the other side, and the two should agree on names, start dates and hours.

Sitting six: permissions, records and safety, forty-five minutes

List every approval that stands between you and opening, with the authority that grants it and the current status of your application. Do not state fees, processing times or requirements from memory. Name the authority and say what you have asked them.

Workplace safety obligations depend on what you do and where you do it. The practical starting point is the federal guidance on how a small business builds a safety program from scratch, at the Occupational Safety and Health Administration's small business pages.

Record retention is a separate obligation with its own rules. The requirements for what a business keeps and for how long are set out in the Internal Revenue Service guidance on recordkeeping.

Write what you record for each job, where it lives, and who can retrieve it. A business that cannot produce last month's job records is a business that cannot answer a complaint, a claim or an audit.

Sitting seven: turn the day into numbers, thirty minutes

Close the notebook and write down only these, on one page.

That page is the operations section's real deliverable. The prose exists to explain it.

Writing it up

Draft in the same order you worked. A reader follows a process better than a set of categories, so describe the flow first, then the constraint, then premises and inputs, then people, then permissions, then what breaks.

Keep it under three pages and put the floor plan, the equipment list and the supplier quotes in an appendix. Then read the operations pillar once more against your draft and check that every claim you made about capacity survives contact with the arithmetic you did in sitting seven.

When the day ends with more questions than answers

That is normal, and that is the point. Your sheet of unknowns is a to-do list with names: call a supplier, question a licensing authority, spend an hour with an installer.

Work through it before you circulate the plan. If a question stays open, state that in the document and say what you are doing about it.

A plan does not predict. It records what you currently believe and what would change your mind, and an operations section written this way makes both of those visible.

Common questions

Can I write the operations section before I have signed a lease or bought equipment?

Yes, and most people have to. Describe the requirement rather than the specific asset: the square footage and the features you need, the capacity of the machine, the crew size. Mark each as a requirement rather than a commitment, and say what the shortlist looks like.

How much detail is too much?

Stop when more detail would not change a reader's decision. A lender does not need your shift handover procedure. They need to know that the work can be done at the volume you claim, by people you have, and that the cash timing works.

What if my operations are genuinely simple?

Then say so in a page and spend the space elsewhere. A short honest operations section beats a padded one. But check first: businesses that look simple usually have one hidden constraint, most often the founder's own available hours.

Do I need process diagrams?

Only if a diagram is faster to read than the sentence. One flow diagram of the order path often is. A wall of swimlanes is not, and it signals effort spent on the document rather than on the business.

Should the internal version and the submitted version differ?

Yes. Keep the full timings, the failure modes and the unresolved questions in the version you use to run the business, and send a shorter one arranged for the reader in front of you. The difference is resolution, never substance.