Turning a 200-page operations manual into training

Almost every multi-site operator has one: a manual, a handbook or a procedure binder of somewhere between 120 and 300 pages that answers nearly every operational question. It is usually accurate and maintained by someone competent. And it is read, in full, by almost nobody who works a shift. Next to it sit a shared drive with sixty slide decks, laminated one-pagers by the machine and a handbook PDF emailed to every starter.

The instinct is to blame the manual and rewrite it, which produces a slightly shorter manual with the same problem. The manual is not the failure. The failure is the assumption sitting on top of it: that handing someone a document and recording that they received it counts as instructing them.

Reading is not instruction, and the law says so

This is not a teaching opinion. Codex art. I.2-21 requires training aimed at the worker's own workpost or function, not at the organisation or the policy set, and names the moments it is owed: hiring, a change of function, new equipment or technology. In the Netherlands the Arbowet asks for instruction that is effective and adapted to each worker's distinct tasks, and for supervision that it is followed (see the instruction law guide).

A 200-page manual is by construction adapted to the organisation, not to anyone's task. Every role reads the same document, most of which does not apply to them, and the parts that do are separated by forty pages that do not. Distributing it is good documentation and poor instruction, and an inspector reading either law is asking about the second.

Being precise here also stops you over-claiming. Neither law forbids a manual, requires a course or prescribes a format. They ask for a result: this person, in this job, received instruction adapted to what they actually do. The manual proves the content exists. It does not prove it arrived.

Sort two hundred pages into three piles

Before converting anything, split the document. Almost every operations manual is three documents wearing one cover, with different audiences, lifespans and destinations.

The test for the middle pile fits on a sticky note: does someone have to act on this without looking it up, in the moment, while something else is happening? If yes, it is instruction. If they can look it up, it is reference.

The most common way the project goes wrong is sweeping reference into courses because it is in the manual. That produces the modules everyone skips, fourteen screens of product codes with a quiz at the end, and it hides the information: a person who needs to know whether an item contains celery wants an answer, not a module. You are not deleting the manual. You are demoting it to what it was always good at, and lifting out the twenty or thirty percent that has to be taught.

Cut by role before you cut by chapter

Chapters reflect how the manual was written, not how the work is done. Cut by role first. Front of house and back of house draw from the same library and need different sequences of it; a shift supervisor needs a superset with different emphasis; someone who covers two stations needs both paths, not a merged one.

Then order each path the way the work unfolds: what the person touches on their first shift, then the safety or hygiene rule attached to that task, then the next task. A rule delivered before the task it protects has no anchor, and it is the first thing to go when the site gets busy. Assign all twenty-five modules to every new hire and completion collapses, not because people are unwilling but because the volume is visibly unreasonable. Assign eight that are obviously about their job and they finish them.

Convert in waves, ranked by change

The biggest cause of failure is scope. An operator decides to have a complete library by the end of the quarter, freezes all content updates while the migration runs, and finds in week six that the operation kept changing anyway. The people converting are the people who maintain the material, so either the freeze breaks or the migration stops, and meanwhile the sites work from a binder everyone has been told is obsolete.

Start with an inventory, not an upload. For every active piece of material, record what it is, which roles it serves, when it last changed and how often it is assigned or re-presented. Ranking by change frequency produces a much shorter list than ranking by importance, because nobody nominates their own material as unimportant. Expect two surprises: material assigned to nobody that has been maintained for years out of habit, and material two departments maintain separately in slightly different versions.

VCA question 4.1 names changes to rules and procedures as toolbox content, and the Codex requires training to be repeated and adapted as risks evolve: material tied to those triggers belongs in the first wave even if it is static today.

Retire the old copy the same day

For each item, the switch happens in one day, not over a month. Publish the module and assign it to the audience the old version had. Move the source file to an archive folder with the replacement date in the folder name, so anyone who finds it later sees it is superseded. And remove the old copy from wherever people actually reach for it: the induction folder, the link in the welcome email, the plastic sleeve on the wall.

That third step is the one that gets skipped, and skipping it is how a site runs last year's procedure with complete confidence. Name the date per item on which the answer to "what is the current procedure" moves from the binder to the platform, and tell the sites which side of that line they are on, because the alternative is each site deciding for itself.

What conversion does not fix

Converting an inaccurate procedure produces an accurate-looking course that teaches the wrong thing, so the conversion is a good moment for the procedure owner to read it, for many manuals the first full read in years. Conversion does not discharge supervision: a completion record answers the instruction question, not whether compliance is being watched. And conversion does not stop the source from ageing. The courses are exactly as current as the document behind them.

Running the conversion in Aristotl

Bring the first wave, not the whole folder. The documents go in as they are, from your own files or through a one-time import from Google Drive or SharePoint, and Aristotl drafts courses from them. The task procedures are the parts that turn into modules; reference and policy stay where people look them up.

Generate the task procedures first, then review. Each procedure becomes a short course with knowledge checks rather than a chapter with a quiz bolted on. A long document does not become a long course, because what a frontliner acts on is a fraction of what it contains. The procedure owner reads the draft once, edits what needs editing, and nothing goes out until you publish it.

Order each path and send it. Modules run three to five minutes on the worker's own phone, translated per worker, with no laptop. Assign each path to the sites or teams that had the old version.

Then retire the binder. From that point, "has read the manual" means completed, dated, per person, with a knowledge check result behind it, viewable per site and version in the platform.

Pick the procedure involved in your most recent incident, complaint or audit finding, and bring it to a demo. We convert that one chapter and show you the record it produces, which is a faster argument than a discussion about the other 190 pages.