Skip to content

Kamishibai board software: Digital kamishibai cards that stay red until the check is done

A kamishibai board is a rack of two-sided cards, one per recurring check, sorted by how often each is done. A card shows red until its check is done and green after, so an overdue audit is visible across the floor. Kamishibai board software keeps the cards, schedule and findings and turns every red into a tracked action.

Example kamishibai board for one line, Monday to Friday, with cards by cadence and layerFour rows of T-card slots across Monday to Friday. The team leader's daily 5S check is green Monday to Wednesday, red on Thursday and due on Friday. The operator's daily startup check is green every day so far and due on Friday. The supervisor's weekly standard work card is green on Monday and the weekly gauge check is amber on Wednesday, meaning it was done and raised a finding. The manager's monthly 5S audit is due on the 28th. Sample data.Kamishibai board, Line 2DoneNot doneMonTueWedThuFriDailyTeam leader5S check5S check5S check5S checkDueDailyOperatorStartupStartupStartupStartupDueWeeklySupervisorStd workGaugeMonthlyManager28thAmber: done, with a finding to fix. Sample data.
One line's board on a Thursday: daily cards for the team leader and operators, weekly for the supervisor, monthly for the manager. The red card is the check nobody has done yet. Sample data.

How a kamishibai board works

Four rules, and the board runs itself

The board sustains standards with many two-minute looks instead of one long audit a quarter. The rules are the same on a rack of cards and in software.

  1. Write one card per check

    Each card is one look at one thing: a torque wrench in its shadow slot, a guard closed, a gauge in calibration. The card says what to look at, where, what good looks like and who takes it. Two to five minutes, done at the workplace, never from a desk.

  2. Sort the cards by cadence and layer

    Daily cards go to operators and team leaders, weekly cards to supervisors, monthly cards to managers. That spread of layers is what makes the board a layered process audit: the same standard is checked by people with different distance from the work.

  3. Turn the card when the check is done

    Red side out until the audit is done, green side out after. Anyone passing the board sees which checks are late without opening anything. A check that fails stays green for having been done, and the finding is written on the back with an owner.

  4. Read the board at every huddle and reset it each period

    The team leader looks at the board in the tier 1 huddle and raises any card still red past its time. Daily cards reset each day, weekly cards on Monday, monthly cards on the first. Once a quarter, retire cards that have been green for a year and write new ones for the problems that appeared.

Who uses it

Who holds the cards, and what each layer is checking

A card is written for the person who will take it. The layers see different things because they stand at different distances from the work.
  1. Operator, every shift

    Confirm the station is ready and safe before the first part.

    Startup check: guards closed, gauges in date, the standard work sheet at the station matches the current revision.

  2. Team leader, daily

    Catch the small drift before it becomes a habit.

    A 5S spot check on one station, a safety walk, one standard work observation: the step order, the WIP limit, the tools in their shadows.

  3. Supervisor, weekly

    Verify that the daily cards are being done honestly and the standards still fit.

    A deeper standard work audit on one station and a gauge check, plus a look at this week's findings and whether their owners closed them.

  4. Plant manager or CI lead, monthly

    Audit the system, not the station.

    Did every layer take its cards? Which cards found nothing for a quarter and should be retired? Which finding keeps coming back and needs an A3?

The two sides of one kamishibai cardThe red side carries the check (torque wrench in its shadow slot with the calibration sticker in date), where (station 4 on line 2), the standard (sticker date within 12 months), who and when (team leader, every shift) and what to do if it is not met (raise a tag to Quality and write the finding). The green side is a sign-off table with date, initials and finding: three days signed, one with the finding expired and tag 1051 raised, and the next line blank. Sample data.Red side: the checkCHECKTorque wrench in its shadow slot,calibration sticker in dateWHEREStation 4, Line 2STANDARDSticker date within 12 monthsWHO, WHENTeam leader, every shiftIF NOT METRaise a tag to Quality andwrite the findingGreen side: the sign-offDateInitialsFinding12 JunRPNone13 JunRPNone14 JunLGExpired, tag 105115 JunBlank line: not done yet
One card, both sides. The red side tells the auditor exactly what good looks like, so two people doing the check get the same answer. The green side is the record, and the blank line is the open check. Sample data.

What a good board looks like

A board that sustains standards, next to one that decays

Most kamishibai boards fail quietly: the cards stay green, the findings stay on the card backs, and the standard drifts anyway. The difference is in six places.
Six elements of a kamishibai board, as they look on a board that works and on one that decays
CardsOne check each, two to five minutes, with the standard written on the card.A whole 5S audit on one card that takes forty minutes and gets skipped.
LayersOperators and team leaders hold daily cards, supervisors weekly, managers monthly, names on the board.Only the supervisor holds cards, so the board is one person's to-do list.
Red and greenRed means not done yet. A failed check is still turned green, with the finding written down.Red means failed, so a finding is hidden until the auditor is sure.
FindingsEach finding has an owner and a date and sits next to its card until it is fixed.Findings are written on the card back and read once a month, if at all.
RhythmRead in the tier 1 huddle every day; cards reset each period; the card set is reviewed quarterly.A board full of green from last month that nobody has reset.
RecordA time-stamped log of who did each check, when, and what they found, so trends show.No history beyond the current card side, so the same deviation recurs unnoticed.

Software earns its place on the last three rows. A rack of cards is good at red and green; it is poor at reminders, findings with owners and a record that shows a pattern. Read the Lean Studio kamishibai board page for a worked week and how to run the first board.

How it works in LeanSuite

What to ask of any kamishibai board software, and what LeanSuite does

Six questions for every vendor, including us. The LeanSuite answers restate the Audit Management, Daily Standard Work and Lean Studio pages, nothing more.
  1. One checklist per card, written by the people who do the check

    A card that says what good looks like gets the same answer from two auditors. A card that says "check 5S" does not.

    Ask the vendor: Can a line lead build or change a card's checklist without IT, and can we start from the paper cards we already have?

    LeanSuite: Build the checklist in Lean Creator, or upload the existing Excel or PDF checklist and the AI converts it into a digital form. Each question can be required, flagged, given a follow-up, a photo or points towards a pass mark.

  2. Cards scheduled by cadence to a person, a role or a machine

    The board works because the daily card is due every day whether anyone remembers it. The schedule, not willpower, is the method.

    Ask the vendor: Can one checklist be scheduled daily for team leaders, weekly for supervisors and monthly for managers, against a specific machine?

    LeanSuite: Schedule the audit in Daily Standard Work to a person, a role or an asset with a repeat rule. For a layered process audit, schedule the same checklist once per layer. Assignees get an email reminder before it is due. See Audit Management.

  3. Red until done, visible to everyone

    The rack's whole value is that a late check is seen from across the floor. Software that hides it in a report has lost the board.

    Ask the vendor: Where does a missed audit show, and who sees it without opening a report?

    LeanSuite: Auditors see their checks on a calendar or a Kanban board, and a missed audit shows in red on both. A live dashboard shows completion across the plant, and audit results can be shown on the tier board next to the KPIs.

  4. Done on the floor, with evidence

    A card turned green from the office is the board's commonest failure. The check has to happen at the station.

    Ask the vendor: Can the auditor complete the card on a phone at the station, with a photo where the standard asks for one?

    LeanSuite: Auditors complete checks on a phone or tablet. A question can require a photo, and a flagged answer carries the photo and comment with it. Every audit, finding and action is time-stamped.

  5. Every finding becomes an action with an owner

    The card shows the check was done; something else has to show the problem is being fixed. Without it, the board records failure and does nothing about it.

    Ask the vendor: When a check fails, what happens next, and who closes the loop?

    LeanSuite: From a not-met finding, raise a tag, an idea or a Kaizen in one click. A tag in Daily Issue Management gets an owner, a due date set by its priority, reminders, and waits for verification before it closes. A finding that keeps coming back becomes a Kaizen with the link kept.

  6. A board the team can still see as a board

    Some teams want the rack at the line and the record in the software; others want the rack on a screen. Both should be possible.

    Ask the vendor: Can we show the cards by cadence, as a board, on a screen at the line?

    LeanSuite: The Kamishibai Audit Board template in Lean Studio lays out daily, weekly and monthly card slots with findings as stickies, each with an owner, and Daily Standard Work results can sit on the same tier board as the line's KPIs.

Two things to know before a demo. There is no offline mode: the phone needs a connection to submit a check. And the AI drafts of a checklist are private until you publish them, so nothing is scheduled before a person has read it.

Pitfalls

Where kamishibai boards go wrong, on a rack or in software

Each of these has an easy fix if it is caught in the first month.
  • Cards that take half an hour

    One card carrying a full 5S audit becomes the card nobody has time for, so it is skipped and then faked.

    Instead: Split it. A card is one look at one thing, two to five minutes, done where the thing is.

  • Red means failed

    If red means the check failed, auditors turn cards green to avoid the conversation, and findings disappear.

    Instead: Red means not done yet. A failed check is turned green for being done, and the finding is written with an owner.

  • Only one layer holds cards

    A board that only the supervisor fills is a to-do list, and it stops when the supervisor is on holiday.

    Instead: Operators and team leaders take the daily cards, supervisors weekly, managers monthly, with names on the board.

  • Findings without owners

    The board proves the check was done and nothing else. The same deviation is found every week.

    Instead: Every finding gets an owner and a date the day it is found, and the team leader reads open findings in the huddle.

  • Never resetting, never retiring

    A board full of last month's green says nothing about this week, and a card that has found nothing for a year is wasting a look.

    Instead: Reset by cadence. Review the card set quarterly and replace retired cards with checks for the problems that appeared.

  • Auditing the outcome instead of the process

    "Is the area tidy?" passes on a good day. "Is the shadow board complete and the daily clean signed?" tells you whether the standard is being kept.

    Instead: Write cards about the process condition that produces the outcome, with the standard on the card.

See it on your problem

What you see in a 45-minute LeanSuite demo

Bring two or three of your audit cards, paper or spreadsheet. We build one as a checklist, schedule it to a layer and show what a red looks like on the floor and on the tier board.
  1. A card built end to end

    Your paper card as a Lean Creator checklist, with a required photo, a pass mark and a flagged answer that raises a tag.

  2. The schedule

    The same checklist scheduled daily to a team leader, weekly to a supervisor and monthly to a manager, against one machine.

  3. The red

    What a missed audit looks like on the calendar and the Kanban board, and what a failed check looks like as a tag with an owner and a due date.

  4. The board

    The Kamishibai Audit Board in Lean Studio, and audit results next to the line's KPIs on the tier 1 board.

FAQs

Kamishibai board software: buyer questions

  1. Software that does the work of a kamishibai board: it holds one checklist per audit card, schedules each one to a person, a role or a machine on a daily, weekly or monthly cadence, shows which checks are late, and records every finding with an owner and a due date. In LeanSuite that is Audit Management with the checks scheduled in Daily Standard Work.

  2. Kamishibai is a Japanese street theatre that told stories with picture cards. Toyota borrowed the name for boards of audit cards: each card tells the auditor what to look at, and the rack of red and green cards tells everyone whether the checks were done.

  3. A layered process audit (LPA) is the audit system: short, frequent checks of the same process steps by several layers of the organization, each on its own schedule. The kamishibai board is the visual scheduler many plants use to run it. In LeanSuite you build one LPA checklist and schedule it separately for each layer.

  4. Many plants keep the rack at the line because a red card is a signal that can be seen from thirty feet away, and run the checklist, the schedule, the reminders and the findings in the software. That works; what fails is a rack whose findings never become actions.

  5. Two to five minutes. A card is one question or a handful of checks on one station, done on the floor. If a card takes half an hour, split it, or it will be the card that gets skipped.

  6. If the check was not done, the assignee gets an email reminder before it is due and the missed audit shows in red on the calendar and the Kanban board. If the check was done and failed, the auditor flags the answer with a photo and raises a tag, idea or Kaizen from the finding in one click; the tag gets an owner and a due date set by its priority, and it waits for verification before it closes.

  7. Yes. Upload the existing Excel or PDF checklist and the AI converts it into a digital form, or build the checklist in Lean Creator and let the AI draft the questions. Publish it and schedule it in Daily Standard Work to a person, a role or an asset with a repeat rule.

  8. Yes. The printable kamishibai audit cards give you six fold-over T-cards per sheet, a sample week, a blank weekly schedule and a findings log. The Lean Studio board page shows the same board as a sample with how to run it.

See your audit cards as a schedule, not a rack

Bring your paper cards. We build one as a checklist, schedule it to a layer and show you a red on the floor, in 45 minutes.