The work your company repeats every day, handled by Velros AI instead of people Get a free assessment →
Managing work manuals
What Velros AI runs

It gathers how work is really done and the exception rules, and organizes them into manual drafts and proposed updates.

Managing work manuals

Repeat procedures, exception rules, how people do it differently, and the update history come together, and everyone finally works from the same page.

New-hire ramp time
Procedure variance and rework rate
Manual currency rate
Get an assessment

A work manual (an SOP) is harder to keep alive than to create. It usually gets written once, dropped in a folder, and left alone while the real way of working shifts, so the manual and the floor drift apart. New employees learn from a stale document and then ask a colleague anyway, the same task gets handled differently by different people, and quality wobbles by who did it. In the end the manual might as well not exist, and the know-how goes back to living in one person's memory.

A procedure like this, organized like this.

We gather the work as it actually arrives, and record what each step is judged against.

  1. Collect the real way it is handled

    Gather the actual order, judgments, and exceptions of how the work is really done from support and handling records, not the steps written in the document.

    Judgment When the documented steps and the floor steps differ, draft from the floor. A manual has to hold the real way, not the ideal, to be followed.
  2. Draft the standard procedure

    Structure the repeating way it is handled into steps, owners, judgment criteria, and exceptions as a manual draft.

    Judgment Among the variance between people, propose which is the better standard, but leave confirming the standard to a person.
  3. Diff and update the changes

    Compare against the existing manual, pull only the steps that changed into an update, and attach the reason for each change.

    Judgment Do not rewrite the whole thing, only touch what changed. Keep a change history so it can be reverted.
  4. Human review and confirmation

    Send the update to the person handling it and the person responsible to confirm it matches the company standard, and lock it as the distributed version.

    Judgment Only a person confirms the manual and writes it to long-term company memory. A wrong standard causes everyone's mistake.
  5. Distribute and keep the current version

    Distribute the confirmed manual, split off the old version, and when the next change signal comes, put it back in the update queue.

    Judgment Always keep a single current approved version, to stop people working from an old document.

When the document and the floor differ, a person sets the standard

We settle the exceptions that actually come up before they do. When a rule doesn't fit, we don't force it through. It goes to a person, with the evidence.

Exception The document and the real work differ

Do not erase either side on your own. Raise the difference together and let a person set the company standard.

Exception A procedure with frequent exceptions that is hard to standardize

Do not force it into one path. Lay it out as conditional branches (in this case, do this) so the exceptions are explicit.

Exception A procedure tied to a rule or law

Do not change it on your own. Raise it with the underlying rule for a person to confirm compliance.

Confirming and distributing are a person's responsibility

Anything touching money, contracts, personal data, or the brand is drafted and no further. It sends only after a person approves.

  • Confirming and distributing the manual

    A confirmed manual becomes everyone's working standard, so a person reviews it last.

  • Writing the standard to long-term company memory (the wiki)

    A standard written to long-term memory is hard to reverse, so a person must approve it.

  • An update that changes an existing procedure

    A change that voids the prior way needs a person to check the basis.

  • A change to a step tied to a law or rule

    A compliance judgment is a person's job, not code.

  • Announcing a procedure change internally

    Telling people when and what changes is a person's responsibility.

How you know it worked

We measure it by how much less asking and diverging there is

New-hire ramp time

Formal training averages 2.5 months, but reaching real proficiency can take up to 6 months (Panopto, 2018)

The more you have a current manual with the real way of working, the shorter the self-taught ramp.

Procedure variance and rework rate

Measured by how much the rework from people handling the same task differently drops (worth measuring in-house).

Manual currency rate

Measured by the share of items where the real procedure and the document have drifted apart (worth measuring in-house).

Rule

A work manual is core operational know-how and can qualify as a trade secret, so keep it under access control with limits on export. Procedures that carry a legal requirement, such as handling personal information, refunds, or contracts, are not made compliant by editing a document alone, so have a person confirm the underlying legal requirements alongside any change.

There is less that a person has to hold on to.

Once the scattered checks and repeat replies are drafted and sorted, your staff can spend the day on review and exceptions, and you look only at the decisions that matter.

Get an assessment
Today

Checks pile up on a person.

A manual gets written once and then left alone, so how you actually work and what the document says drift apart.

With Velros running it

The work arrives ready to go.

It pulls manual drafts from how work is really done and keeps them current, and a person approves what gets finalized and shared.

Time for a new hire to get up to speed Procedure drift and rework rate Share of manuals kept current

What people ask before they hand this over

The things people actually check first about Managing work manuals.

Can you revive a stale manual nobody reads anymore?

We compare it against the real way of working, build an update for only what changed, and attach what changed and why. Once a person confirms it, it is kept as the current approved version from then on.

Do you use the AI-drafted procedure as the standard as-is?

No. AI builds the draft, the update, and the reasoning, and committing it as the company standard for distribution is approved by a person.

What to sort out next

We start with the work that keeps a person tied up.

Book a call