How Do Written Procedures Keep Your Line Running When Something Breaks? (Part 2 of 3)

Part 2 of a 3-part series: the five one-page documents that cut downtime, how to capture what your veteran techs know, and a 30-day plan to get your first machine covered.

Ken deAlmeida

10/15/20265 min read

a man riding a skateboard down the side of a ramp
a man riding a skateboard down the side of a ramp

Part 2 of 3. Part 1 covers why every machine needs written operating, setup, and maintenance procedures. This one is about putting them to work. Part 3 covers what they mean when you're preparing to sell or go public.

Short answer: put the right page at the right machine before the failure, not after. In practice that comes down to five short documents: a fault response sheet, a startup and shutdown checklist, a setup sheet, a maintenance checklist, and a line-down quick reference. None of them needs to be longer than a page or two, and together they're the difference between a 20-minute stop and a two-hour one.

Why does downtime keep getting longer even when your people are good?

Because the people who know how to fix things are getting harder to find and harder to replace. The average time to fix an unplanned failure has climbed from 49 minutes to 81 minutes, largely because of skills gaps and parts delays, and the average manufacturing facility now sees around 25 unplanned downtime incidents a month, adding up to more than 300 hours of lost production a year (MaintainX, 2024).

The labor picture explains part of it. Roughly 415,000 manufacturing jobs sit unfilled nationwide, and 65% of manufacturers call attracting and retaining people with the right skills a top challenge (Manufacturing.net, citing BLS and NAM). The same article offers an illustration worth keeping in mind: an experienced technician might clear a conveyor issue in 20 minutes where a replacement needs two hours. That's an example, not a measured figure, but anyone who has run a plant knows the gap is real. Written procedures are how you shrink it.

What are the five documents that actually keep a line running?

Keep each one to a page or two, written as actions for the person standing at the machine. The standard is simple: state what the operator checks, adjusts, confirms, and records, and skip phrases like "ensure proper setup" (DocuWriter).

  1. Fault response sheet. List the five faults or stops that happen most on this machine. For each one: what it usually means, what to check first, what to do, and the point where the operator stops and calls maintenance. This is the single highest-value page in the set, because it's the one used at the worst moment.

  2. Startup and shutdown checklist. The same steps in the same order every time, including the pre-run checks that catch problems before they become stops.

  3. Setup and changeover sheet. Settings, positions, and sequence for each product or format, with annotated photos wherever position and orientation matter (Harmoni).

  4. Daily and weekly maintenance checklist. Inspection steps written down so they stop living only in an experienced technician's memory (OxMaint). If you're building the parts side too, our post on tool room setup and parts inventory covers what to stock for each machine.

  5. Line-down quick reference. Where the electrical drawings live, where the air, hydraulic, and electrical isolation points are, the lockout/tagout steps for the machine (lockout/tagout is OSHA-mandated, per Harmoni), where the critical spares are, and who to call, with phone numbers.

That fifth one gets skipped more than any other, and it's the one that matters most at 2 a.m. when whoever's on shift has never seen this failure before.

How do you capture what your most experienced tech already knows?

Don't wait for an exit interview. The more reliable approach is capturing knowledge as a byproduct of daily work, and starting well before retirements are close (OxMaint). The practices that source recommends are structured shift handovers, searchable work-order history with notes on what was done and which parts were used, standardized inspection steps, and pairing newer technicians with experienced ones on real jobs. Both that source and the Rockwell-authored Manufacturing.net article come from companies that sell software, so take their product pitches with a grain of salt. The practices themselves work fine with a clipboard and a phone.

Here's a low-tech version that works. Next time your best tech fixes something, have a newer person shadow the repair and write down each step as it happens. Take photos of the parts and positions. Then turn it into a one-page fault sheet that afternoon, while it's fresh, and have the veteran correct it. That's thirty minutes of work that captures twenty years of knowing where to look first.

Where should the paperwork actually live?

At the machine, not in the office. Procedures traditionally lived in binders in a manager's office (Fabrico), and that's the fastest way to make sure nobody reads them. Put the fault sheet and startup checklist in a sleeve or on a laminated card right at the machine, and keep one master copy somewhere controlled so everyone's working from the same version. If you go digital later, the rule stays the same: it has to be in front of the operator in a few seconds.

How do you keep procedures from going stale?

Any change to the machine is a change to the page. That's the whole rule. A setup changes, maintenance swaps a component, a guard gets modified, and suddenly the document disagrees with the machine. Once the plant changes faster than the paperwork, people stop trusting the paperwork and go back to tribal knowledge (DocuWriter).

Three habits keep it honest:

  • Name an owner for each machine's documents. Someone whose job it is to update them, not "whoever has time."

  • Update after every real repair. If a fix turned up something the fault sheet didn't cover, add it that day.

  • Review on a schedule. Quarterly is plenty for most machines. Have the newest operator walk through the sheet and flag anything that doesn't match what they see.

What's a realistic 30-day plan to get started?

Start with one machine and prove it works there, same as we recommend for automation projects.

  1. Week 1: Pick your bottleneck machine. Pull the last ten stops or breakdowns and sort them into the top five causes.

  2. Week 2: Write the fault response sheet and startup/shutdown checklist. Photos, not paragraphs, wherever position matters.

  3. Week 3: Hand the pages to your newest operator and watch them use them. Fix every spot where they hesitate.

  4. Week 4: Add the daily/weekly maintenance checklist and the line-down quick reference. Then pick the next machine.

By the end of the month you have one machine covered properly and a template for the rest.

How does AutoIC help with this?

This is where our troubleshooting and maintenance work meets our commissioning work. When we install a machine, operator training and handover documents are part of getting it running and keeping it running. When we're called in for an emergency, we see exactly which machines have a fault sheet on the wall and which ones depend on one person's memory, and the difference in how fast a line comes back is obvious. We can help you build these documents for existing equipment, starting with the machines that hurt most when they stop, and fold the same format into any new equipment we integrate.

What's AutoIC's take on this?

Most downtime isn't caused by exotic failures. It's caused by ordinary ones that take too long to diagnose because the knowledge isn't where the machine is. Five short pages per machine won't prevent every stop, but they'll make most of them shorter, and they make the plant a lot less dependent on any one person's phone being on at 2 a.m. Keep It Super Simple: if a page can't be used by someone half-awake at the machine, rewrite it.

Next up: Part 3 looks at what this documentation is worth when you're preparing to sell the business or go public.

If you want help getting your first machine covered, that's a good place to start a free consult. Check out our FAQ for more on how we support equipment after install, or get in touch and we'll come take a look.

Solutions

Expert automation for manufacturing process improvement.

Consulting

Support

ken@autoicllc.com

603-748-6216

© 2025. All rights reserved.