Process documentation: a usable template for a small team

Process documentation: a usable template for a small team

5 min read

If a routine only works when you are there to explain it, the routine is still in your head. A useful process description lets someone else complete the work and recognise when to stop.

One account instead of four tools?

SavePaper.work brings together specialised software for salons, garages, weddings and schools. One login, clean handover, export whenever you want.

See the products

You do not need to describe the whole business before improving one task. Start with something that regularly causes questions: changing an appointment, checking an incoming invoice or handing an unfinished job to a colleague. Record the steps people actually follow, then test the description with someone who did not write it.

The template below is a practical working document, not an ISO certification package or a substitute for trade-specific safety instructions. Its purpose is narrower: one trigger, a clear result, an owner and a route for exceptions. Keep customer details in the authorised business record; the procedure explains where to find them.

Choose a process with a visible beginning and end

“Customer service” is too large for a first page. “Handle a request to move an existing appointment” has a recognisable starting point and an outcome you can check. Name the person responsible for keeping the instructions current separately from the person carrying out today's task.

Watch one real run before writing. Note the information needed, where work pauses and which decision needs someone else's approval. If two people work differently, settle which method is intended before turning either version into instructions. Otherwise you document the disagreement.

Separate the business decision from the software clicks. The decision might be to confirm available time and the right staff member; the clicks depend on the system. This also gives you concrete workflows to take into a software demonstration.

A procedure is ready when another person can use it without having to guess the next step.

Copy this seven-part process template

Use these fields in a shared document. Write actions as verbs and give each step one observable result. A screenshot can clarify a difficult control, but it should not replace the instruction or contain real customer information.

FieldWhat to record
Purpose and scopeWhich task this covers, and which similar tasks it excludes.
Trigger and inputsWhat starts the work; which record, information and permissions are needed.
ResponsibilityWho carries out the task, who covers absence and who may approve exceptions.
StepsNumbered actions, including decision points and the place to record the result.
Completion checkEvidence that the requested outcome has actually been reached.
ExceptionsWhen to stop, whom to contact and how to keep the unfinished work visible.
Document controlOwner, version, effective date, review trigger and location of the current copy.

A role can be sufficient where staff change frequently, provided the team can find the person currently holding it. Never put passwords or recovery codes in an ordinary procedure.

Worked example: moving an appointment

Fictional example: a customer asks to move an agreed appointment. The person handling bookings may offer an available slot for the same service; changes to scope or price need the designated decision-maker. The procedure begins when the request arrives and ends when the agreed change is recorded and communicated.

  1. Find the correct booking and check that the request concerns the right customer and service.
  2. Check duration, staff, resources and buffers for the proposed replacement slot.
  3. Offer the available option and obtain the customer's agreement before replacing the original booking.
  4. Update the authoritative calendar once. Check that the old slot has been released and no duplicate appointment remains.
  5. Communicate the agreed date, time and any preparation through the agreed contact channel. Check the system's sending result instead of assuming that a message was sent.
  6. Record completion or the outstanding response in the booking record, with the next responsible person if further action is needed.

If there is no suitable slot or the customer has not agreed, keep the original booking and mark the request as pending. A changed service or disputed charge goes to the designated approver. The separate guide to reminder channels and timing covers how messages fit the appointment.

Test the ordinary case and one exception

Give a colleague the document and a fictional booking in a suitable test environment. Do not prompt them through the steps. Ask them to show the resulting booking, the released old slot and the communication status. Then repeat with no suitable replacement slot.

Record each point where they hesitate: missing input, unclear responsibility, inaccessible screen or undefined decision. Repair that instruction and repeat the affected step. Test with the device used at work and the permissions the role actually has; an administrator account can hide an access problem.

Collect only information needed for the task. The process page does not need a second customer file, private contact lists or copies of sensitive notes. Use the existing guide to customer data and its purpose when deciding what belongs in the business record.

Publish one current copy and give changes an owner

After the test, agree who approves the procedure and where staff find it. Mark earlier copies as superseded so an old printout cannot silently compete with the current instructions. Keep a short change note: what changed, why and from which date it applies.

Review after a software change, a repeated mistake, a new service or a change in responsibilities. A calendar reminder is useful too, but a scheduled review should not postpone a known correction. Show the revised step to the people affected and confirm they can perform it.

Measure whether the recurring question has become less frequent and whether the completion check is met. A shorter document is not automatically a better process, and time saved is not established until you observe comparable work before and after.

Choose one recurring task, complete the seven fields and have your cover work through an ordinary case and an exception. Correct the unclear steps before declaring the page finished. The result is a usable work instruction you can improve as the business changes.

If the process will run in new software, take the same cases into the trial. The workflow remains your test; the product has to show how it supports it.

One account instead of four tools?

SavePaper.work brings together specialised software for salons, garages, weddings and schools. One login, clean handover, export whenever you want.