CONTINUITY
The operation survives absence, turnover and holidays, because running it does not require the person who designed it.
REMOTE OPERATIONS / SOP + DOCUMENTATION
The work repeats. The knowledge does not.
Aevrion captures recurring operational work as procedures a competent person can follow—with owners, exceptions, handoffs and decision paths written down, and kept current as the operation changes.
The unit of this service is a documented recurring workflow. It is not administrative assistance, and documenting a process is not a commitment to automate it.
01 / WHAT MEMORY COSTS
An operation nobody has written down.
The work still gets done. It gets done because particular people remember how—and almost everything the business wants to do next runs into that fact.
- 01
ONE PERSON IS THE PROCESS
The operation holds together because someone keeps it in their head. Their absence is not an inconvenience—it is an outage.
- 02
DELEGATION STALLS
New people are trained by shadowing, so the operation can only grow at the speed of the person explaining it.
- 03
THE SAME DECISION, DIFFERENT ANSWERS
Recurring judgment calls get made differently depending on who is making them, because the criteria were never written down.
- 04
HANDOFFS RUN ON GOODWILL
Work crosses between people on recollection rather than a defined transfer, so nobody can say who is holding it right now.
- 05
NOTHING CAN BE CHECKED
Without a stated procedure there is no standard to check against, so quality becomes a matter of opinion after the fact.
- 06
IMPROVEMENT HAS NOTHING TO EDIT
You cannot change a process you cannot see. Every improvement starts by reconstructing what the current one actually is.
None of these are failures of the people doing the work. They are what happens when the work was never written down.
02 / WHAT A PROCEDURE CONTAINS
Six things a written procedure has to answer.
A document that lists steps is not yet a procedure. These are what make it something a person who was not there can actually run.
- 01
THE STEPS
What is done, in order, in enough detail that a competent person who has not done it before can follow it without asking.
- 02
THE OWNER
Who runs the procedure, who reviews it, and who decides when it changes.
- 03
THE TRIGGER + RHYTHM
What starts the work and how often it runs, so it is scheduled rather than remembered.
- 04
THE EXCEPTIONS
The cases that do not fit the steps, where they go, and who judges them.
- 05
THE HANDOFFS
Where work crosses between people or systems: what moves, to whom, and what confirms it arrived.
- 06
THE DECISION PATHS
The recurring judgment calls, their criteria and their decision-maker—so the same situation gets the same answer.
Only the first is about the steps. The rest decide whether the procedure survives contact with a real week.
03 / HOW IT GETS WRITTEN
Watch the work before describing it.
Documentation written from how a process is supposed to run describes a process nobody follows. The sequence starts with the operation as it actually happens.
- 01
OBSERVE
Follow the work as it is actually done, including the steps that were never in anyone's description of it.
OUTPUT / DECISIONThe real process, not the intended one. - 02
DECISIONS
Find the points where a person decides something, and what they are deciding it on.
OUTPUT / DECISIONThe judgment inside the routine, made visible. - 03
OWNERSHIP
Establish who runs it, who reviews it and who is allowed to change it.
OUTPUT / DECISIONNames against the work. - 04
PROCEDURE
Write the steps so someone competent but unfamiliar could run them without a translator.
OUTPUT / DECISIONA procedure a new person could run. - 05
EXCEPTIONS
Define what does not fit, where it goes and who judges it.
OUTPUT / DECISIONA defined route for the cases the steps miss. - 06
HANDOFF
Put the procedure where the operation uses it, with an owner and a review point.
OUTPUT / DECISIONOperating knowledge in the business, not in a folder.
04 / THE USABILITY STANDARD
Notes describe the work.
A procedure carries it.
Most operations already have something written down: a shared document, an onboarding page, the recording of a call. It usually describes the work at the level of someone who already understands it—which is exactly the level at which it stops being useful to anyone else.
The test is not length or format. It is whether a competent person who has never done this work can complete it correctly from the document alone, and know what to do when something does not fit.
If it still needs the original person on hand to be usable, the knowledge has not actually moved.05 / EXCEPTIONS + JUDGMENT
The cases the procedure does not cover.
A recurring operation will meet situations its steps do not describe. Documentation that pretends otherwise fails in its first unusual week.
- 01
EXCEPTIONS ARE EXPECTED
The procedure states that some cases will not fit, instead of implying that every case will.
- 02
A DEFINED ROUTE
Each kind of exception has somewhere to go and someone to judge it, so it is escalated rather than improvised.
- 03
CRITERIA, NOT INSTINCT
Recurring decisions carry the criteria they are made on, so consistency does not depend on who is available.
- 04
THE LIMIT OF THE DOCUMENT
Where judgment is genuinely required, the procedure says so and names who holds it—rather than writing a rule that will be ignored.
- 05
EXCEPTIONS FEED THE RECORD
Cases that keep recurring are a signal that the procedure is incomplete, and they are what the next revision is written from.
06 / STAYING TRUE
A record that stops changing stops being true.
Documentation drifts from reality quietly, and the first sign is usually someone deciding not to trust it. These are the conditions that keep an operating record worth reading.
- CURRENCY
- The procedure describes how the work is done today, not how it was done at handover.
- CURRENT
- TRIGGERED REVIEW
- A change to the work is what starts a change to the record, not a calendar reminder.
- LINKED
- NAMED REVIEWER
- Someone is responsible for whether the document still matches the operation.
- ASSIGNED
- VERSION CLARITY
- It is obvious which version is in force, so two people are not running different instructions.
- SINGLE
- EXCEPTION FEEDBACK
- Recurring exceptions are collected and used to revise the procedure.
- FED BACK
- ACCESSIBILITY
- The people doing the work can reach the document where and when they do the work.
- REACHABLE
07 / CONTINUITY + DELEGATION
Operating knowledge the business keeps.
The point of writing an operation down is not the document. It is what the document makes possible for the business that owns it.
DELEGATION
Work can be handed to a new person, a new team or an external partner against a stated standard rather than a training period.
INDEPENDENCE
The documentation belongs to the business. If an engagement ends, the operating knowledge stays where it was written.
That includes independence from Aevrion. A documented operation is one the business could take anywhere—which is what makes it an asset rather than a dependency.
08 / HONEST LIMITS
What documentation does not do on its own.
Writing an operation down changes what the business can do with it. It does not, by itself, change the operation.
WHAT IT CHANGES
The work becomes inspectable, delegable and improvable. Handoffs get a standard. Recurring decisions get criteria. A new person has something to follow instead of someone to follow around.
WHAT IT DOES NOT CHANGE
A documented process is not automatically a good one, a faster one or an automated one. Documentation makes those decisions possible—it does not make them for you.
Aevrion does not claim that every documented process should be automated, or that documentation removes the need for someone to run the work. It turns both of those into decisions the business can actually take.
09 / AFTER IT IS WRITTEN
A documented operation is a decision you can finally make.
Once the work exists on paper, the question of who should run it stops being a matter of who happens to know how. These are the options a written operation opens.
KEEP RUNNING IT
The operation stays internal—but now against a stated standard a new person can pick up without shadowing anyone.
HAND IT OVER
The workflow can be operated by someone else, internally or as a managed engagement, because a standard now exists to hold it to.
AUTOMATE PART OF IT
The steps that turn out to be genuinely repeatable become candidates for controlled automation. The rest stay with people, on purpose.
Which of these is right is a business decision, not a default. Documentation exists so that it can be made on evidence rather than impression.
10 / DECISION SUPPORT
Questions to resolve before documenting an operation.
01What is an SOP at Aevrion?
A written procedure for a recurring workflow that carries its steps, its owner, its rhythm, its exceptions, its handoffs and its decision paths—written so a competent person who has not done the work before can run it correctly. A document that only lists steps is notes, not a procedure.
02Does documenting an operation mean Aevrion has to run it?
No. Documentation can be the entire engagement. Where an operation is undocumented, writing it down is often the honest first step before any decision about who should run it—including keeping it entirely internal.
03Where does the content come from?
From the operation as it is actually performed: following the work, the people who do it and the cases that come up—rather than from how the process was originally intended to run. A description written from intent documents a process nobody follows.
04Does a documented process have to be automated?
No. Documenting or operating a workflow reveals which steps are repeatable enough to be worth automating, but that is a separate decision with its own scope. Plenty of documented steps should stay with people, and Aevrion does not treat documentation as an automation pipeline.
05Who owns the documentation?
The business does. It is a deliverable you keep, in a form you can edit, and it is deliberately independent of Aevrion—if the engagement ends, the operating knowledge does not leave with it.
06How do procedures stay current?
By being maintained as part of the work rather than revisited on a schedule: a change to the operation is what triggers a change to the record, a named reviewer is responsible for the match, and recurring exceptions feed the next revision.
07What about work that is pure judgment?
Work that is genuinely ad hoc judgment does not compress into steps, and pretending otherwise produces a document people ignore. What can be documented in those cases is the decision criteria, the boundaries and who holds the call—which is usually the part that was actually missing.
08Can Aevrion document an operation it did not build or run?
Usually yes, subject to access to the work and to the people who do it. The constraint is rarely the systems involved; it is whether the operation can be observed closely enough to describe honestly.
09What affects scope and cost?
The number of workflows, how many people and systems each one crosses, how much of the work is judgment rather than steps, how much of the current process is already written down, and how much exception and decision detail the operation carries. A named workflow is the starting point for an accurate proposal.
11 / START WITH THE WORKFLOW
Get the operation out of people's heads.
Describe the recurring work that depends on too few people—what it is, how often it runs, and who is currently the only one who knows how. Aevrion will help define what documenting it would cover and what the business would be able to do afterwards.
Start a project