Standard operating procedure example builder
- Sections in the example
- 9
- Computed on this page from the inputs below
- Controls the department's example carries
- 2
- Computed on this page from the inputs below
- Minutes per run
- 24
- Computed on this page from the inputs below
- Hours the procedure consumes a week
- 2
- Computed on this page from the inputs below
Every figure on this page is computed from the inputs you enter, by the method stated below it. RunbookDesk supplies no constant from outside; the defaults are a worked example to replace with your own.
Email me this result
We will send you these figures and a link back to them. One email, nothing else unless you tick the box.
The figures above start from a worked example (9). Change any input and the answer updates as you type.
Download the Standard operating procedure example builder worked example (CSV)
This builds a worked standard operating procedure example for the department you choose. Pick operations, people and HR, finance, IT and security or sales and customer service, enter the steps in the example procedure, the roles named, the forms, systems or policies it references, how many times it runs a week and the minutes per step, and the page returns the sections the example carries, the controls the department's example needs, the approvals before release, the minutes per run, the hours the procedure consumes a week and a length in words. The department tables are counts for a worked example, not rules from any standard; the figures are yours.
The department decides the controls and the approvals
A finance procedure carries more controls than an operations one, because it moves money: a segregation of duties, an approval threshold, a reconciliation, an audit trail. An IT procedure carries access and change controls. A sales procedure carries one, the CRM record. The page uses a small table of counts per department so the example shows the right shape, and the controls are yours to name.
The example is sized like a real procedure
Eight steps at three minutes is a twenty-four-minute run, five times a week is two hours of the business, and the length in words follows from the steps, the references and the controls. The page prints those figures so the example reads as a procedure that could actually be followed, which is the difference between an example and a template.
Approvals before release are part of the example
A procedure nobody approved is a draft. Finance and HR examples carry two approvals, the owner and a second person, because the procedure binds people other than the writer; operations and sales carry one. The page prints the count so the example's version block has the right number of signature lines.
Standard operating procedure example builder: common questions
Is this a free standard operating procedure example?
Yes: the sections, controls, approvals, run time and length are computed here for free with no account, and you can print the structure. RunbookDesk Pro turns it into the SOP document with your company name on it, filed against the process, with the approvals collected and the review reminder set.
Which department's example should I start with?
The one whose procedure runs most often. Put in the weekly runs and read the hours per week the page prints; the procedure that consumes the most of the business is the one worth writing properly first.
Are the controls and approvals a standard?
No. They are counts for a worked example, chosen so the example has the right shape for its department. Your own controls come from your own risks and your own auditor, and the page says so.