How do I create and keep SOPs updated while I work?

Business Tech & Tools

How do I create and keep SOPs updated while I work?

The short answer

Create the first version while you perform the job, then give the SOP a named owner, a visible “last updated” date, and a simple way to capture corrections. Do not wait for a quiet week to write perfect instructions from memory. That quiet week has a habit of never arriving.

The easiest system is a working draft beside the task itself. When a step changes, record the change while it is fresh. Review and approve higher-risk changes before they become the new standard.

Capture the real process, not the process you imagine

Open a blank document before you begin a repeatable task. As you work, record:

  • what started the process.
  • what information or access you needed.
  • each meaningful action in order.
  • choices you had to make.
  • checks that caught mistakes.
  • what proved the job was finished.
  • anything that delayed or confused you.

Screenshots can help with an unfamiliar screen, but they should support the words rather than replace them. Software menus change. The instruction “confirm the client name and reporting period before exporting” will usually outlast a picture of one blue button.

Asana describes process documentation as a living source of truth that includes steps, roles, and resources. Its guide also recommends testing and updating the document instead of treating it as finished forever. See Asana’s process-documentation guide.

Use a change queue so improvements do not disappear

Stopping in the middle of client work to rewrite a long document is rarely practical. Add a small “SOP change” note to the task instead:

Change note What to record
What happened “Invoice screen now asks for service date before amount”
Why it matters Missing the date delays submission
Proposed change Add service-date check before Step 4
Urgency Before next use, this week, or routine review
Evidence Help-page link, screenshot, error message, or approved decision

Put every note in one change queue. A note buried in email is not a maintenance system.

Decide which changes need approval

Not every correction needs a meeting. Fix spelling, broken links, and harmless clarification promptly. Review a change before publishing it when it affects:

  • customer promises or deliverables.
  • prices, refunds, or the movement of money.
  • passwords, permissions, privacy, or security.
  • a contract, license, safety rule, or regulated process.
  • the order of steps where mistakes are hard to reverse.
  • work owned by another person.

For a solo business, “approval” may simply mean that you pause, verify the source, test the new steps, and date the decision. If the subject involves legal, tax, employment, safety, or privacy requirements, confirm the current rule with the responsible agency or a qualified professional in your location and industry.

Keep a clean header on every SOP

At the top of the document, include:

  • SOP title.
  • process owner.
  • who should use it.
  • last updated date.
  • current version or revision number.
  • link to the recurring task or project template.
  • next planned review.

Then keep a short change log at the bottom. You do not need a dramatic versioning system. A line such as “September 9, 2026: added final-link test after two client links were restricted” is enough to explain why the instruction changed.

Test the document with the intended reader

Ask someone with the expected level of experience to follow the SOP without coaching. If no one else is available, leave it alone for several days and test it yourself from the first step.

Mark every place the reader must guess. Common gaps include which account to use, where a file lives, what “check” means, who can approve an exception, and how to know the work is complete. Asana’s SOP guidance recommends having the completed procedure reviewed by someone who performs the task. See its SOP template instructions.

Tie review timing to risk and change

Use calendar reviews as a safety net, not the only trigger.

Review trigger Example
After an error or near miss Wrong attachment almost went to a client
After a tool changes Booking software moved payment settings
After an exception repeats Three clients needed the same alternate approval path
Before handing off work A contractor will perform the process next month
Scheduled review Quarterly for high-consequence work, annually for stable low-risk work

Archive old versions so you can understand past work, but show only one clearly labeled current version to the person doing the task. If two “final” copies live in different folders, neither one is trustworthy.

Sources and further reading

A free next step

Not sure which business fits you yet?

The free Freedom Path Assessment can help you compare your strengths, schedule, income goals, and preferred way of working before you commit to a business direction.

Take the Freedom Path Assessment Free

Related Questions

← All questions