ILUO, explained: how Toyota grades operator skill (and how to run it in a small shop)

September 2026 · 5 minute read

Ask most small shops who can run the lathe and you get a list of names. Ask who can run it alone, for a full shift, when the regular guy is out, and the list gets a lot shorter. Ask who could train a new hire on it and sometimes the list is one name, and that name took vacation last July and the lathe sat.

Trained or not trained is a checkbox, and checkboxes lie. Someone who watched a setup twice and someone who has run the machine for nine years both get the same checkmark. ILUO exists because that difference is the whole game.

The four letters

ILUO comes out of the Toyota production system and it has become the standard way lean plants grade operator skill, all the way up to the automotive supply chains that live under IATF audits. The trick that makes it stick in people's heads: each letter has more strokes than the last, so the letter itself shows the level.

IIn training. One stroke. Needs someone telling them what to do and checking the work. Don't leave them alone with it.

LLearning. Two strokes. Knows the steps, runs it with supervision close by. Getting there.

UUnassisted. Three strokes. Runs the station alone, full shift, normal and abnormal conditions, no babysitting. This is the level that counts for coverage.

OOwner. Closed loop. Runs it alone and can train the next person to a U. Every station needs at least one, or your training plan is a rumor.

The important line is between L and U. An L looks productive on a good day. The difference shows up on the bad day: the weird noise, the out-of-spec part, the material that isn't quite right. A U handles it. An L comes and finds you, and if you're not there, the station stops or the bad part ships.

Why it beats what you're probably doing

Most small shops carry this information in one place: the boss's head. That works right up until the boss is on vacation, or the shop grows past the point where one head can hold it, or the one guy who was quietly the only U on inspection puts in his two weeks.

Writing it down as a grid changes three things. First, coverage risk becomes visible before it becomes downtime. Count the U's and O's under each station. Any station with fewer than two is one absence away from stopping. That count is your cross-training list, already in priority order. Second, training gets a definition. "Get Casey trained up on the lathe" is a wish. "Get Casey from L to U on the lathe by November" is a plan, and both of you know what U means because it's written on the wall. Third, the grading is behavioral. You're not certifying hours attended in a classroom. You're recording what you have watched someone actually do.

How to run it in a small shop

Make the grid. Team down the side, stations across the top. Not job titles, stations: the actual machines and tasks that have to be covered for the shop to run. If it can idle the shop when nobody can do it, it gets a column. Include the unglamorous ones. Inspection and shipping stop shops as surely as mills do.

Grade honestly, and grade what you'd bet a shift on. The system dies from inflation. If you give someone a U because they'd be insulted by an L, the grid stops being a coverage tool and becomes a feelings chart. The test for U is simple: would you schedule them on that station alone tomorrow without a backup plan? If you hesitate, that's an L. Tell the team the definitions up front and most people grade themselves harder than you would.

Count, then act. Two numbers fall out of the grid immediately. Per station: how many people are U or better, with anything under two flagged. Per person: how many stations they can carry, which shows you who your flexible people are and who is stuck on one machine. The stations flagged under two are the training priorities. The people with one station are the training candidates. Match them.

Review it on a cadence, not on a crisis. Monthly is plenty for a small shop. Someone moves from L to U when you've watched them handle the bad day, not when the calendar says they've been there long enough. And O is earned by training someone, not by seniority.

The honest caveats

ILUO measures skill at a station. It doesn't measure whether someone shows up, works safe, or gets along with the team. Those matter and they belong in your coaching conversations, not in the grid. Keep the grid about one question: who can run what, alone.

And a grading system doesn't train anyone. The grid tells you where the gaps are. Closing them is still shoulder-to-shoulder time on the floor, and that only happens if you schedule it like it's real work, because it is.

Straight disclosure: we sell a cross-training matrix template that does the ILUO grid, the coverage counts, and the under-two flag automatically, as part of a pack with a coverage planner, a huddle sheet, and a coaching log. You can also build the grid yourself in an afternoon with a blank spreadsheet, and if that's your speed, this article is everything you need. Either way, write it down. The version in your head has a single point of failure, and it's you.

The board has a coverage screen. It shows who can run what, and who is out today. See the board