Guides

How to write a business procedure: template and worked example

Updated on 5 min
Two colleagues review a printed procedure and checklist beside a computer.

A business procedure should help someone do a task. It tells them where to start, which steps to follow and how to tell when the work is complete.

Start with one clearly defined recurring task. Write down the instructions, then give them to a colleague who has the access and skills the task requires. During the trial, note where they need to stop or ask for help.

Here is a template you can copy, a completed example and a form for recording the trial. You can use them in the document or wiki your team already uses.

Start with a task that has a clear beginning and end

“Manage projects” is too broad for this exercise. “Set up the folder for an approved project” gives you a starting point and an outcome you can verify.

Before writing, clarify the following.

  • What triggers the work
  • Which information and access must be available
  • Who performs the task and answers questions
  • What should be in place when the work is complete

If a decision is still open, mark it for confirmation. Have the person responsible check any new team rules before adding them to the procedure.

A business procedure template to copy

Copy the outline and replace the fields in square brackets. Give each step an observable action and an outcome to check.

PROCEDURE TITLE
[Verb + specific task]

STATUS, VERSION AND DATE
[To review / In trial / Approved / Retired]
[Version and date of the last revision]

OBJECTIVE AND FINAL OUTCOME
[What must be completed]
[How to check the result]

WHEN TO USE IT
[Event that triggers the work]
[Cases in and out of scope]

RESPONSIBILITIES
Performs the work: [Role]
Reviews and approves the procedure: [Owner]
Contact if blocked: [Internal contact]

PREREQUISITES
[Information, materials, skills and access needed]
[How to obtain missing access]

SOURCES
[Document or guidance behind these instructions]
[Link, version or date]

STEPS
1. [Who] performs [action] using [input].
   Expected result: [...]
   Check: [...]

2. [...]

EXCEPTIONS AND WHEN TO STOP
If [data/access] is missing: [...]
If [result] already exists: [...]
If [error] occurs: [...]
Resume when: [...]

RECORD OF THE WORK
[Where to record the outcome, result and issues]

UPDATES
Who updates it: [...]
When to review it: [...]
Where to find the current version: [...]

The objective says what you need to achieve. The steps explain how to get there. The exceptions explain what to do when the usual route is unavailable.

In the sources section, name the exact reference behind the instructions. In the prerequisites, explain how to request access. Keep passwords and keys out of the document.

Worked example for setting up a project folder

This example is entirely fictional. Names, folders and conventions illustrate how to fill in the template.

Title. Set up the folder for an approved project.

Status and version. In trial, version 0.1 dated November 16, 2026.

Objective. Set up the project folder with the required subfolders and the approved brief.

When to use it. After the Operations lead has confirmed the project, when the project code, name and brief are available. This procedure covers document setup.

Who does the work. An Operations team member authorized to work in the test area.

Who checks the work and handles blockers. The Operations lead.

Prerequisites. Write access to the “Test projects” folder, project code PR-024, project name “Demo catalog” and an approved fictional brief.

Source. The convention agreed for the exercise. Name the folder “code - project name” and include “01-Brief”, “02-Materials” and “03-Deliverables”.

Steps for the sample procedure
StepActionResult to verify
1Check that the code, name and brief are available and match the request.The details identify the same project.
2Search for PR-024 in “Test projects”.You know whether a folder already exists for this code.
3If it does not exist, create “PR-024 - Demo catalog”.The name follows the agreed convention.
4Create “01-Brief”, “02-Materials” and “03-Deliverables”.All required subfolders are present.
5Put the approved brief in “01-Brief”.The document is present and opens correctly.
6Record the folder path and result on the trial form.The owner can find and review the work.

Exceptions

  • If the code or approved brief is missing, stop and ask the owner for it.
  • If a folder already exists for that code, record its path and ask the owner to check it before creating another.
  • If you lack write access, report the blocker and resume when authorized access is available.
  • If the brief will not open, identify the file you used and request a valid copy.

The work is complete when the structure, name and brief match the instructions and the path has been recorded. Record any blocker explicitly.

Have a colleague test the procedure

Choose someone other than the author who meets the prerequisites. Ask them to follow the procedure with dummy data or in a suitable test environment.

The EPA's guidance on preparing standard operating procedures recommends having someone other than the author try the draft. We apply that method here to a simple organizational exercise. EPA, Guidance for Preparing Standard Operating Procedures, section 2.2.

Before the trial, check the following.

  • The colleague can find the correct version.
  • The materials and access are available.
  • The expected result is clear.
  • They know when to stop and who to contact.

Ask the colleague to record each point of confusion during the trial. If you have to step in, record what you explained. The procedure may need that information.

Try a boundary case and an error as well. In the example, provide an existing folder and a missing brief. Check whether the instructions help the colleague recognize the issue and choose the next step.

A form for recording the result

PROCEDURE AND VERSION
DATE
PERSON RUNNING THE TRIAL
CASE TESTED

OUTCOME
[Completed / Completed with help / Blocked]

RESULT
[Description and a reference that can be checked]

UNCLEAR STEPS
[Step number and difficulty encountered]

HELP RECEIVED
[Explanation or intervention needed]

MISSING INFORMATION
[...]

CHANGES TO MAKE
[...]

REVIEW OWNER
[...]

RETEST NEEDED
[Yes/no and reason]

If the colleague completes the task thanks to a verbal explanation missing from the document, record that help. The trial has identified something to fix.

A successful trial shows that the procedure worked for that task, those prerequisites and that case. More sensitive or variable activities need checks suited to their risks and possible exceptions.

Keep the procedure usable

After the trial, clarify ambiguous steps and have the owner review the new version. Give the team a clear place to find the current document and identify superseded versions.

Review the procedure when tools, responsibilities, sources or ways of working change. Use the issues the team reports to spot instructions that need attention.

At the end of this exercise, you should have a completed procedure, a trial result and a list of changes to make.

If you have many scattered procedures, you can organize the collection as a whole. The guide to a company knowledge base explains how to connect documents, ownership and updates.

If you want to start with one department, LuCz's company knowledge base and internal assistant service begins by organizing sources into a hub the team can find and maintain. An assistant can be considered when it helps.

Sources

Sources were consulted on November 16, 2026. Adapt the template and example to your own work and test them before use.

Tags

#knowledge base#documentation#organization

Written by

Matteo Lucrezio

Matteo Lucrezio

Startupper | Lead Software Engineer

Book 30 minutes with Matteo

Leave your contact details, then choose a day and time for a free 30-minute initial conversation. Any technical assessment and subsequent work are agreed separately.

How can we help?

Enter your contact details to continue to the calendar.

We use it to follow up on your request and manage the booking. This does not subscribe you to promotional messages.

We save your details immediately to handle your request. They also stay in this browser for 24 hours, so you do not have to type them again if you reload the page.

No suitable time or prefer to write? Email me at matteo.lucrezio@lucz.dev.