Capturing Undocumented Know-How Before a Key Employee Departs

Consider a hypothetical catering kitchen whose opening lead has run the morning start-up for six years. She knows which compressor sounds wrong before the thermometer confirms it, which sanitizer dilution the inspector will ask about, and which supplier delivers late when the weather turns. None of this appears in a binder. It appears when she unlocks the back door at 5:40 a.m., and it stops appearing on the day she gives notice.

The resignation rarely arrives with a handover. It arrives with two weeks of notice, a request for a few hours of shadowing, and an assumption that the replacement will pick things up. The replacement picks up what was written down, which tends to be the parts about which nobody needed to ask. The steps that lived in one person’s habits, the order that matters, and the check performed only when a particular delivery arrives all leave with her. Small firms often discover this on the first morning after the last shift, when a cooler reading is missing and no one can say whether it was taken.

A procedure does not need to be elaborate to survive that morning. It needs to exist in a form a stranger can follow, with each step in the order it happens and each gate that holds the next step until the previous one is confirmed. EEZYSOP provides step-by-step procedures a team follows, with gated steps completed in order and completion tracked, for $19/month. The harder work is writing down what one person does without thinking, and that work is easiest to do before the notice arrives.

The Procedure That Leaves With the Person

Consider a restaurant whose opening manager closes every night from memory. She knows the walk-in cooler runs warm if its door stays open too long, that the second fryer needs its filter changed before the Friday rush, and that the alarm code changes on the first of the month. None of this appears on paper. Consider also a clinic whose billing coordinator knows which payer rejects which code, and how to word a resubmission so it clears on the first pass. In both cases, the knowledge belongs to one person.

What the reader is searching for is a method: how to move a process out of someone’s head and into a form a stranger can follow, before that person gives notice. The question underneath is narrower than it sounds. It asks what the procedure consists of, in what order, and where a judgment call hides inside a step that looks mechanical.

What goes missing is rarely the large steps. Everyone remembers those. What disappears is the small condition attached to a step: the door that must close before the compressor starts, the portal that logs out after a short idle period, the sequence that fails if the steps run in reverse. When no one records these conditions, the replacement guesses at step four or learns it by breaking something. The costs are plain. Errors rise in the first weeks. A senior employee loses hours to retraining, frequently while still doing the old job. Someone spends a Saturday rebuilding a checklist from a former colleague’s text messages.

Documentation tools exist for this. Trainual, Process Street, SweetProcess, Whale, Scribe, and a shared Google Doc or SharePoint binder each capture steps in different ways. The useful question is less which tool has the most features than whether the tool keeps the sequence intact. EEZYSOP writes procedures as step-by-step sequences that a team completes in order. Gated steps cannot be skipped, and completion is tracked, so a new hire cannot reach step six without finishing step five. Whichever tool a firm chooses, the underlying work is the same: watch the person who knows the process perform it while narrating each decision, then record the conditions they would never think to mention.

How Documentation Tools Solve the Problem, and Where They Stop

A written procedure does three things that memory cannot. It states the steps in order, it names an owner who answers for their accuracy, and it records who was trained on which version and when. Tools in this category, among them Trainual, Process Street, SweetProcess, Whale and Scribe, offer some combination of those functions. Google Docs and SharePoint binders can hold the text, but they seldom track training or enforce sequence, so the manager assembles that evidence by hand.

Version control matters as much as the text. The reviewer approves each revision, and the manager retires the old one so that no trainee works from a superseded page.

The limits are real. A document does not make anyone follow it. The manager must still observe the work and correct the drift. A procedure written by someone who skips steps is wrong in the same way the writer is wrong, and it stays wrong until a reviewer who did not write it walks through it. The knowledge also lives in the expert’s head, so the manager should schedule interviews with that expert, record them, and watch the expert perform the task while someone notes each action taken without thought. Those unstated actions are the ones that disappear on the last shift.

Reference document or gated checklist

A reference document is consulted when a reader needs it. Nothing prevents a reader from jumping to step six. A gated checklist works differently: each step opens only after the step before it is marked complete. The trainee cannot advance until the step is done, and the system records the completion. EEZYSOP works this way, with gated steps completed in order and completion tracked, at $19 per month. The manager decides which procedures warrant gating. A shutdown sequence for a walk-in freezer usually does. A template for a monthly newsletter usually does not.

What EEZYSOP Does With a Process You Have Captured

EEZYSOP holds standard operating procedures as step-by-step procedures and training that a team follows. Its most useful feature for a departing employee is the gate. A step can be set so that the next person must complete it before the following step unlocks, and completion is tracked, so a manager can see how far a new hire has progressed.

Consider a hypothetical restaurant whose dishwasher lead, Marcus, is leaving at the end of the month. He closes the wash line most nights, and nobody else has written down how. Before his last shift, a manager captures his closing routine as a procedure, one discrete action per step:

  • Step 1: Drain the sump and clean the strainer. The next lead completes this step before Step 2 unlocks.
  • Step 2: Test sanitizer concentration and record the reading on the chart. Step 3 stays locked until this is done.
  • Step 3: Run the final rack cycle and confirm the machine reaches temperature.
  • Step 4: Check that chemical jugs are sealed and labeled.
  • Step 5: Initial the closing log.

The new lead works through the steps in order. Completion of each one is recorded, so the manager does not have to ask whether the strainer was cleaned. The gate does not verify the work. It enforces sequence and leaves a record of what was done.

That limit matters. EEZYSOP cannot confirm that a sanitizer reading is accurate or that a jug is correctly labeled. Those judgments still belong to a trained person, and the procedure is only as precise as the person who wrote it. A shared document in Google Docs or SharePoint can hold the same text, but it does not hold a later step closed until an earlier one is finished. Trainual, Process Street, SweetProcess and Scribe each approach documentation and training differently, and a firm should compare them against the way its own team actually works.

Pricing for EEZYSOP is $19 per month. For current plan details, see the pricing page on the site.

What EEZYSOP Costs

EEZYSOP costs $19 per month. That is the price this article states, and it is the only figure a buyer should treat as settled.

Pricing details beyond the $19 monthly figure are on the EEZYSOP site. A buyer who needs current terms before budgeting should read them there.

Consider a hypothetical restaurant whose closing sequence exists only in the memory of its general manager. When that manager gives notice, the owner must reconstruct the sequence from fragments. The monthly fee is small beside the hours spent on that reconstruction. The real question is whether the tool captures the procedure in steps a new hire can follow in order, or merely stores a document that nobody opens.

Other options in this category include Trainual, Process Street, SweetProcess, Whale, Scribe, and shared folders in Google Docs or SharePoint. This article does not state their prices. A firm that compares them should take each vendor’s current pricing from that vendor’s own site on the day it decides.

Billing for EEZYSOP runs through the EEZYVERSE family account. A company that uses several EEZY products receives one central bill at eezycloud.com/account/.

The price matters less than the outcome. A firm can choose any of these options and still lose its only record of how the work gets done. The cost that counts is the one incurred on the last shift of the person who holds the procedure.

Getting Started and What the First Week Looks Like

Consider a hypothetical warehouse of twelve staff, whose receiving supervisor has given notice. No real firm stands behind this scenario. The first week begins on Monday, and the operations manager chooses one process to document: receiving and putaway, because an error there reaches every order that follows.

Tuesday. The manager sits with the supervisor for ninety minutes and records the work as it is performed, not as the handbook describes it. The supervisor explains why the second pallet of each shipment is checked against the purchase order before the first is shelved. The manager writes each step in the order the work happens, including the steps nobody has written down.

Wednesday. The manager enters the steps in EEZYSOP and marks each step whose skipping causes damage as gated. Shelving before the count is confirmed, for example, is gated. A gated step cannot be completed until the step before it is complete. Shared documents such as Google Docs or a SharePoint binder can hold the text, and tools such as Trainual, Process Street, or SweetProcess can hold the sequence and sign-offs. Each has its own setup, so the manager compares how each one enforces order rather than what each one costs.

Thursday. A second employee, who has never performed receiving, runs the procedure cold, without the supervisor present. The tester notes each ambiguous instruction, each step that assumes knowledge the page does not contain, and each point where the tester stops to ask a question.

Friday. The manager corrects each failure and runs the revised procedure again. The supervisor reviews the final version and approves it. The manager records completion for every step and stores the document where the next shift can find it. The supervisor’s last day arrives the following Thursday, and the receiving process no longer depends on one person’s memory.

The Honest Alternatives

Several products already document procedures, and a small firm should weigh them before it chooses. The descriptions below reflect each product’s general category. Features and pricing change, so each vendor’s site holds the current terms.

  • Trainual organizes company knowledge into training and process pages. It suits a team that expects to document many roles, and a firm with three employees may find its breadth more than it needs.
  • Process Street centers on checklists and recurring workflows. A team that runs the same routine every day will find it natural. A team whose procedures rarely repeat may find the structure heavier than the work.
  • SweetProcess focuses on written procedures and process mapping, which helps an owner who wants a clear inventory of how work moves.
  • Whale aims at documenting processes for small teams. Its appeal lies in simplicity. Confirm that its level of enforcement matches the steps you need.
  • Scribe records on-screen actions and converts them into step-by-step guides. It saves writing time for software tasks and offers little for work done by hand or in person.
  • Google Docs or SharePoint binders require no new login, and every employee can open them. They hold words well. They do not enforce order, and they do not record who completed which step.

EEZYSOP, the product this site sells, writes procedures as step-by-step instructions, requires gated steps to be completed in order, and tracks completion. It costs $19/month.

Three questions narrow the choice. First, how many people will follow the procedure? A shared document may serve two people who sit together. A larger or distributed team needs a record of who did what. Second, how often do the steps change? Frequent revision favors a tool that makes edits and republishing simple, and rare revision favors a document that a manager can maintain in an afternoon. Third, does skipping a step cause harm? If a missed step spoils a batch, exposes a patient, or damages equipment, order and sign-off matter more than polish. If a missed step costs only a few minutes, a lighter tool will do.

Fitting the Procedure Into the Rest of the Stack

A procedure tool does not replace payroll, scheduling or the accounting ledger. Each holds a different kind of record. Payroll answers who was paid and how much. Scheduling answers who works when. The procedure answers what the person does once on shift. A firm that tries to force all three into one system often finds that none of them works well.

A procedure tool earns its place where a schedule assigns someone to a task they have never performed. A new closer on a warehouse dock, a second cook on a line or a technician covering an unfamiliar route needs the steps, in order, before working alone. EEZYSOP holds those steps and tracks completion, with gated steps that must finish in sequence. Trainual, Process Street, SweetProcess, Whale and Scribe cover overlapping ground, as do Google Docs and SharePoint binders. The better test is whether the people who follow the procedures will open the tool on a Tuesday morning.

EEZY products belong to the EEZYVERSE family. A company that uses more than one of them signs in once across all of them. Each product also sells on its own site, so a firm that needs only the procedure tool can buy it alone. Every EEZY product a company uses bills through one central account at eezycloud.com/account/. Support is published at eezycloud.com/support, with hours of Monday through Friday, 9 AM to 8 PM, and Saturday and Sunday, 9 AM to 12 PM Eastern.

Before adoption, ask the vendor in writing which connections the tool makes and which it does not. Do not assume that a procedure tool reads from payroll or feeds scheduling unless the vendor documents that link. Where no link exists, the handoff is a manual step, and the procedure should state it.

Once the documents exist, ownership matters more than software. A procedure nobody maintains becomes the single-person problem again, now stored in a shared folder. Assign each procedure to one named manager who owns its accuracy and approves changes. The person who performs the work drafts the revision, and the owner signs it off. Name a backup owner as well, so that the manager’s departure does not orphan the documents. Review each procedure on a fixed schedule, and change the document in the same week that the floor changes the step.

Frequently Asked Questions

How do I document a process before the only person who knows it leaves?

Start with the person who performs it. Have them walk through each task in order while a second person records every step, decision and required check. Then turn those notes into numbered steps. EEZYSOP lets you publish those steps as a procedure a new hire follows in sequence.

What should a process document include before the expert leaves?

Each step should name the action, the person or tool involved, the condition that triggers the next step, and the check that confirms the step is complete. Record exceptions as their own steps, since departing staff carry the knowledge of what goes wrong. EEZYSOP gated steps require completion in order, with completion tracked.

How long does it take to write SOPs for a small team?

No general figure exists, and any number offered without knowing the process would be guesswork. The time depends on the number of steps, how many decisions branch, and how many people must review the draft. A practical method is to time one walkthrough, then multiply by the number of procedures the departing person handles.

How much does EEZYSOP cost for a small team?

EEZYSOP costs $19 per month. Any pricing beyond that is on eezysop.com. Most of the cost of this project lies in staff hours spent recording the work, not in the subscription. Schedule those hours while the person who knows the work is still on payroll.

Who should review a documented procedure before it is used?

The person who performs the work should walk through the document with a manager who did not write it. A new hire who follows the steps exactly is the strongest test, because any gap shows up as a question or a stall. Revise each gap the test exposes, then record the revision date.

Review how EEZYSOP turns a process into step-by-step procedures that new hires complete in order, with completion tracked, before the one person who knows the work leaves. EEZYSOP costs $19 per month.

Get started with EEZYSOP

EEZYSOP is part of the EEZYVERSE family: one login, one bill, every EEZY product.

    Comments are closed