12 applied questions drawn from the Supervisor course, graded instantly against the same 75% bar as the real assessment. Free, unlimited attempts — the questions reshuffle every time.
Questions12
Pass mark75%
Time18:00
Your best—
Passing here is a readiness signal, not the credential — the KaizenFlow AI Certified Supervisor credential is earned in the proctored, applied assessment. When the timer runs out, the exam submits with whatever you've answered.
Review — every question, with the reasoning and the module it comes from
18:000/12 answered
Your queue shows six findings this morning: $4,200/wk changeover at Station 3, $3,100/wk micro-stops at Station 1, $2,600/wk misfeed at Station 4, then $600, $350, and $200 one-offs. Crew arrives in fifteen minutes.
The outgoing supervisor tells you at the door: 'We got to the Station 1 micro-stops last night.' The finding shows no closure note, and the queue still prices it at $3,100/wk.
You skipped the pre-shift queue read. In the huddle, eight of your ten minutes go to figuring out which findings even have owners, and the crew leaves with one assignment made.
The AI raises a $3,500/wk recurring scrap finding on Station 6. Walking it, you find the reason code traces to a worn die — a tooling defect the floor has no way to correct.
You handed Station 3 to an operator with 'go take a look at the changeover when you get a chance.' Two hours later they're still on routine work, and the overrun has cost another cycle.
A new $2,600/wk misfeed finding suggests your senior operator as next-best action. She's mid-changeover on Line 2 — stepping away stalls the whole line. Two other capable operators are free.
A newer operator has run Station 4 clean for three straight shifts — zero misfeeds since a fixture change she suggested. You mostly pull up the live view when something's red.
A supervisor on another shift reads out each operator's downtime minutes at the huddle, worst first. Within a month, that shift's 'Other' reason-code rate has tripled and logged micro-stops have dropped by half.
A well-meaning team lead arrives at the huddle with a printed spreadsheet of yesterday's output by hour, and suggests walking the crew through it before the board.
Two weeks ago you announced a scrap fix as 'recovered' before the ledger confirmed it. The verification came back short, and since then the crew audibly discounts the numbers you open with.
Station 4's misfeed code has returned every three or four shifts for a month, across three different owners who each worked and closed it competently. The anomaly alert now fires on an almost predictable cadence.
You told engineering at the morning meeting that 'Station 3 keeps breaking down.' A week later nothing has moved — your request sits behind a dozen others, with no dollar figure and no history attached.