Maintenance
Part of What to Include in Operations Plans for a Business Plan
Operations plans format: laying out for a two-minute read
Operations plans format for a skimming reader: a process order, the constraint in its own block, tables for repeating fields and at most one diagram.
This section is read by people looking for one specific answer: can the work be done at the volume claimed. A layout either lets them find it in two minutes or hides it in six pages of resource description. Layout changes nothing the section says, only whether the constraint, the timing and the failure modes are visible.
What to take away
- Order the section as a process, then as categories. Readers follow a flow more easily than a taxonomy.
- Put the constraint in its own short block near the top, not buried in a paragraph about equipment.
- Anything with the same fields repeated belongs in a table.
- One diagram at most, and only where it is faster to read than the sentence.
- Detail a reader would not act on belongs in an appendix.
Order the section as a process
Order the section as a process, then as categories. Readers follow a flow more easily than a taxonomy. Resource-first layouts, which start with premises and work outward, are the common alternative, and they read as an inventory. The reader has to build the process themselves, and most will not.
Five blocks in order
- The floworder arrival to payment
- The constraintwhat limits volume
- Inputs and premisessuppliers, lead times, space
- People against demandroster shape
- What breaksfailures and responses
| Block | What the reader checks | Space |
|---|---|---|
| The flow | One order from arrival to payment, as steps with owners and durations | Half a page |
| The constraint | What limits volume, stated in the unit you sell | A short paragraph |
| Inputs and premises | Suppliers, lead times, terms, space and equipment | Half a page |
| People against demand | The shape of the week or year, with a roster that matches the team section | A third of a page |
| What breaks | Single points of failure, permissions, and the response to each | A third of a page |
The section follows the product and marketing material and comes before the team and the numbers. A reader arrives knowing what is sold and how it is bought, and this section answers how it gets delivered. Writing the flow itself is covered in the process guide.
Give the constraint its own block
Set it apart visually: a short paragraph under its own subheading, or a two-line callout. It is the sentence a lender is looking for, and how a lender reads capacity starts from it. Nothing else in the section deserves that prominence.
Constraint. Volume is limited by one named resource, measured in the unit you sell. Realistic throughput is lower than the rated figure, and the next constraint appears when that one is lifted.
State it in the unit you sell, give the realistic throughput rather than the rated one, and say what becomes the constraint next as the business grows. Three sentences is enough, and putting them where they can be found is worth more than another page of description.
Tables for anything with the same shape repeated
Suppliers, equipment, licenses and process steps all have repeating fields, and a table beats prose for each of them.
Table columns that earn their place
Suppliers
- First field
- Input
- Second field
- Supplier type
- Third field
- Lead time
- Fourth field
- Payment terms
- Fifth field
- Second source
Permissions
- First field
- Permit
- Second field
- Issuing authority
- Third field
- Status
- Fourth field
- Date
- Fifth field
- —
Table / Columns
- Suppliers
- Input, supplier type, lead time, payment terms, second source
- Permissions
- The permit, the issuing authority, the status, the date
Keep one header row and no merged cells, and keep column order the same between plan versions. Use real headings rather than bold text so the structure survives a screen reader. Section508.gov explains how to create accessible word processing documents that conform to the Section 508 Standards.
A status column with "applied 14 March" does more for a reader's confidence than a compliance promise. The SBA notes that most businesses need to file for the appropriate licenses and permits, so list each one with its authority and its status, including any application still pending.
One diagram, or none
One flow diagram of the order path is often faster to read than the paragraph describing it. Beyond that, restraint. A wall of swimlanes signals effort spent on the document rather than on the business, and a floor plan belongs in the appendix unless the layout is itself the argument.
Does this diagram earn its place?
Is it the order path or the layout itself the argument?
one flow diagram, captioned and readable in black and white
move it to the appendix or cut it
Whatever you include, make it readable in black and white and give it a caption that states what it shows. Then check that the diagram and the text agree, because they drift apart at the first revision.
Print the section at the size the reader will see. Print reveals a supplier table running off the margin, a diagram reduced to unreadable boxes, and type set small to fit a page limit.
Send the detail to the appendix
Keep in the section anything that changes a reader's judgment of whether the volume is possible. Move anything that only proves you have it. If unsure, ask whether removing the paragraph would change a decision, the test the plan guide applies to every section.
In the section or behind it
Keep in section
- Test
- Changes a judgment
- Volume
- Three pages generous
- Equipment
- What limits throughput
- Space
- Layout is the argument
- People
- Roster shape
- Compliance
- Status and date
Move to appendix
- Test
- Only proves you have it
- Volume
- Full supplier quotes
- Equipment
- Schedule with model numbers
- Space
- Floor plan
- People
- Shift rosters
- Compliance
- Inspection certificates
Number the appendix items and reference them by number from the section, so a reader can find the quote or the floor plan without hunting. Photographs of the premises or equipment go there too, where they answer questions faster than paragraphs. The section stays readable without them.
Common questions
How much of the process should be written as steps?
Enough that a competent stranger could follow one order through. The full procedure manual is a different document and belongs on the wall or in the appendix.
What if the application gives me short fields instead?
Get the field list before drafting, write to the shortest field first, and keep your own full version, because you will need it for the next reader. Where a limit will not fit the truth, write the essential clause and point to an attachment.
My business is online and has almost no physical operations. What does the section look like?
Shorter, and organized the same way. The flow is still an order from arrival to settlement, the constraint is usually support or one person who can fix the platform, and the permissions block still exists.
Can I merge this with the team section?
Better not. Readers look for capacity in one place and people in another, and merging them makes both harder to check against the model.
