The SQDIP Board: A 5-Minute Tier Meeting Run-Script for Small Plants
Skip the generic SQDIP definitions. Here is the actual daily run-script I use on the floor: what each letter tracks, the red/green rule, who speaks and in what order, and when to escalate.
Most of what gets written about the SQDIP board is useless to you. It tells you the letters stand for Safety, Quality, Delivery, Inventory, and People, draws a tidy five-column grid, and then walks away. That is a glossary entry, not a meeting. It does not tell you who talks, in what order, for how long, or what you actually do when a square turns red. So the board goes up on the wall, looks great for two weeks, and quietly dies because nobody knows how to run the thing.
I have watched this happen in more plants than I want to admit. A supervisor gets back from a lean workshop fired up, tapes up a beautiful SQDIP board, and three months later it is a graveyard of faded sticky notes nobody updates. The board was never the problem. The missing piece was the script: the repeatable five-minute routine that turns a wall of squares into a decision-making engine.
This post is that script. If you read my piece on the daily huddle, think of it this way: the huddle is the meeting, and SQDIP is the board the huddle runs against. The huddle is the verb. The board is the noun. You need both, and this is how they fit together.
What Each Letter Actually Tracks (in a small plant)
The generic advice keeps SQDIP abstract. On a real floor with 60 people, each letter is one number and one color. That is it. Do not let anyone turn a letter into a dashboard with nine sub-metrics. One letter, one lead measure, one red-or-green call.
Here is how I scope each one for a plant in the 25 to 500 range:
- S (Safety). Days since the last recordable incident, plus any near-miss reported in the last 24 hours. A near-miss reported is a good thing, not a bad thing. If someone speaks up, that square can still be green.
- Q (Quality). Scrap, rework, or a customer reject from yesterday against your internal limit. One number: did we cross the line or not.
- D (Delivery). Did we ship what we promised yesterday. On-time to the customer commit, not to some theoretical line rate. Late is late.
- I (Inventory or Cost). Pick the one that actually bites you. For most small shops it is either raw material you are about to run out of, or WIP piling up between two cells. If cost is your pain, use overtime hours from yesterday instead.
- P (People). Attendance and open positions for today. Who is out, who is covering, are you short on a critical skill on any shift.
Notice that every one of these looks backward at yesterday and forward at today. That is deliberate. The board is not a history museum. It exists to catch a problem while you can still do something about it.
The Red/Green Rule (the part everybody skips)
This is where most boards fall apart, so read this part twice. A square is green if the number is inside the standard. A square is red if it is outside the standard. There is no yellow. There is no “kind of.” There is no “well, we were close.”
I kill yellow on every board I touch. The moment you allow a yellow, every borderline call becomes a yellow, and yellow means nobody has to do anything. Red forces a response. Green means leave it alone. The discomfort of having to call something red out loud, in front of the team, is the entire point. That discomfort is what drives the fix.
The rule that makes it work: a red square is not a punishment, it is a request for help. The second your team believes that a red gets them yelled at, they will start gaming the numbers, and your board becomes fiction. Say it out loud in your first few meetings. “Red is how you ask me for help. I would rather see ten honest reds than one fake green.”
And if one square goes red, the whole board does not. You do not need a green board. You need an honest board. A board that is green every single day for a month is not a healthy plant, it is a board nobody is telling the truth on.
Who Speaks, in What Order, for How Long
Five minutes. Standing up. At the board, not in a conference room. Here is the running order I use, and the order matters because it goes from non-negotiable to negotiable:
- Supervisor opens Safety (30 seconds). You start. Safety is always first because it signals what you actually rank first. Read the S square, ask if anyone saw a near-miss yesterday, mark it.
- Quality lead calls Q (45 seconds). Whoever owns quality on that line reads the number. If it is red, one sentence on what happened. Not the fix yet, just the what.
- Whoever owns the schedule calls D (45 seconds). Did we ship. If we missed, what did we miss and is it caught up or still open.
- Materials or lead hand calls I (30 seconds). Are we about to run short, or is WIP stacking up somewhere.
- Supervisor closes People (30 seconds). Who is here, who is covering, are we short anywhere critical today.
- Reds get a name and a date (90 seconds total). This is the only part where you slow down. Every red square gets an owner and a “by-when.” Not a discussion. Not a root-cause session. Just: who owns it, when do they report back.
That is roughly four and a half minutes. The discipline is in what you refuse to do: you do not solve problems at the board. The board surfaces the problem and assigns it. The fix happens after, with the two people who actually need to be in the room, not the whole team standing around growing cold.
The Escalation Trigger
Here is the rule that separates a tier meeting from a status meeting. When a square goes red and the team at the board cannot commit to a fix by end of shift, it escalates to the next tier up. That is the trigger. Not “it is bad.” Not “the boss is mad.” The trigger is purely: can we fix it at this level by when we said, yes or no.
If yes, it stays at your board and you follow up tomorrow. If no, it goes up: to the plant manager’s board, the value-stream meeting, whatever your next layer is. In a small plant you might only have two tiers, the line and the plant. That is fine. Two honest tiers beat five theatrical ones.
The escalation has to carry information, not panic. When you push a red up, it travels with three things: what the number is, what you already tried, and what you need from the next level. A red that arrives upstairs as “Q is red, help” wastes everyone’s time. A red that arrives as “scrap is double standard on line 3, we think it is the new lot of material, we need quality engineering to test it today” actually moves.
Draw This on a Whiteboard Tomorrow
You do not need software. You do not need a vendor. Here is the layout. Grab a whiteboard, a ruler, and two markers (one red, one green), and draw this before first shift:
+----------------------------------------------------------+
| LINE 3 TIER BOARD DATE: ______ SHIFT: ___ |
+--------+--------+--------+--------+--------+--------------+
| S | Q | D | I | P | OWNER / |
| Safety |Quality |Deliver |Inv/Cost| People | BY-WHEN |
+--------+--------+--------+--------+--------+--------------+
| | | | | | |
| [O/X] | [O/X] | [O/X] | [O/X] | [O/X] | (reds only) |
| | | | | | |
| days | scrap | ship | short? | who's | |
| since | vs std | vs | / WIP | out / | |
| inc. | | commit | | cover | |
+--------+--------+--------+--------+--------+--------------+The logic you write on the side, in plain words so a new hire gets it day one:
- Green circle (O) = inside standard. Say the number, move on.
- Red X = outside standard. Say what happened in one sentence, then it gets an owner and a by-when in the right column.
- No yellow. If you are arguing about whether it is yellow, it is red.
- Every red leaves the board with a name and a date. No orphan reds.
Keep the board where the work is, at eye level, in the light. A board in the hallway by the break room is a poster. A board at the line is a tool.
Start Tomorrow, Fix It Friday
Do not spend two weeks designing the perfect board. Draw the rough version above tomorrow morning, run the five-minute script, and let it be clumsy for a week. You will find your standards are wrong, your timing is off, and one of the letters does not fit your plant. Good. Adjust it Friday. A board you are running and correcting beats a board you are still perfecting on a slide deck.
The thing that makes SQDIP work is not the acronym. It is the daily reps: same time, same order, honest colors, every red owned. Do that for thirty days and the board starts running you instead of the other way around.
If you want a clean version to print instead of redraw every morning, I put a one-page SQDIP board template together as part of my Manager’s Playbook series, along with the huddle script that pairs with it. But honestly, the whiteboard works. Start there, get the reps in, and upgrade the paper later. The reps are the asset, not the template.
Related notes
Liked this? Get the free SOP Writing Cheat Sheet.
The 6-step SOP format on one page. Free.