Process documentation

Turn a walkthrough into an SOP someone can use

Record the decisions, checks, and approvals that a walkthrough may leave unexplained.

· About 3 minutes

A walkthrough shows how one person completes a task. A usable standard operating procedure should also explain when to start, what information is needed, who can make decisions, and what happens when something goes wrong. The aim is a procedure another authorized teammate can follow and check.

1. Define the beginning and the finish

Choose one process with a clear trigger and result. “Handle an order discrepancy” is easier to document when the trigger is a reported mismatch and the finish is an approved solution, carried out and recorded.

Identify the process owner, intended user, required access, and inputs. State what is outside the procedure. If the workflow touches refunds, inventory adjustments, or customer commitments, name the role authorized to approve those actions.

2. Capture the decisions behind the clicks

Ask the person demonstrating the process to explain what they check before choosing the next step. Useful prompts include: “What would make you stop here?”, “Which record do you trust?”, and “Who decides if these values disagree?”

Write down unresolved questions rather than inventing a policy. Separate what the walkthrough demonstrated from what the team still needs to confirm. Use redacted screenshots or public-source records wherever real customer details are unnecessary.

3. Give each step an action and a check

Use numbered steps with a clear verb, the relevant system or record, and the expected result. Replace “deal with the issue” with a specific action such as “Compare the order quantity with the packing record and any remaining shipments.”

Add branches where the path changes. If a shipment is still due, verify its status. If records conflict, name someone to investigate. If a remedy needs approval, pause at the approval point. A checklist should summarize the procedure's essential checks without introducing new instructions.

See a procedure built from real guidance

The shared-drive handover example starts with official NARA guidance and turns it into an ordered procedure, review checkpoints, and a handover record.

The source register separates what the guidance establishes from practical steps added by Cleargrain Docs. It does not invent a completed handover or approved local policy. The organization must assign owners and confirm its own retention, access, and approval rules before using it.

4. Test it with someone else

Have an authorized teammate walk through the draft using a safe example. Note where they need the original demonstrator to explain a missing step. Check the normal path and at least one exception. Where a step affects live records or money, use a test environment or a read-through rather than executing it without approval.

  • Are the trigger, owner, and required inputs clear?
  • Can the reader find the right record or system?
  • Are decisions, stop points, and approvers explicit?
  • Can the reader check that the task is complete?
  • Does the document identify its version and maintenance owner?

Common failures are transcribing every click without explaining decisions, using outdated screenshots, and leaving exception handling to “common sense.” Update the SOP when the actual workflow changes.

Document the process you already have

The five-SOP package is $399 USD for client-provided walkthroughs totaling up to 100 minutes. It includes five procedures, five checklists, an index, and one combined round of changes within the agreed scope. Scope and timing are confirmed after review. Your team validates the procedures before use; documentation does not establish legal, safety, or regulatory compliance.

Use these checks with your own records, systems, and approved policies. Linked portfolio examples identify their public sources and limits.

Have a task in mind?

Start with the result you need.

Tell us what you need
Need help using this site?

New here? You do not need to know the service name. Tell us what you have now and what a useful finished result would look like.

  1. Start a short inquiry. A few sentences are enough, and no account or files are needed.
  2. Compare services, package prices, and quote options, or see complete public-source examples before you ask.
  3. Already working with Cleargrain? Use Client Login for private requests, files, messages, and project review.

Still unsure? Describe the result you need, including technical detail if useful. Larger spreadsheets and custom work are welcome; we’ll review the task before agreeing on the work and price.

What do the file types and technical terms mean?
PDF
A document you can read in a browser or PDF reader.
XLSX
An Excel workbook. Open it in a spreadsheet app to inspect the full example.
DOCX
An editable Word document. Open it in Word or another compatible document app.
CSV
A plain spreadsheet file. Open it in a spreadsheet app to see rows and columns.
TXT
A plain-text checklist or template. Open it in a text editor or copy its text.
SOP (standard operating procedure)
A step-by-step guide for a recurring task.
CRM (customer relationship management)
A system used to organize customer or contact records.
Workflow
The steps that move a task from start to finish.
Flat file
One table of rows and columns, with one header row.
Exception list
Records that need a decision or more information, with references to the original rows.
Source-ready procedure
A procedure written from approved material you already have, rather than from a supplied walkthrough.
Preference revision
One collected round of requested adjustments within the agreed work. Correcting work that fails the written scope is separate.
White-label support
Work prepared for your agency to review and present in its own branding.

To download a file, select its download link. It may open in your browser or appear in Downloads. If the browser asks, choose where to save it. Downloading an example does not place an order.