An SQDP board gives a production team a fast answer to four questions that determine daily operational performance:
- Did we work safely?
- Did we produce according to quality requirements?
- Did we complete the plan and deliver on time?
- Did we achieve the expected level of production performance?
In a well-organised daily management system, these answers are not hidden across multiple Excel files, emails and weekly reports. They are visible immediately on one board that is updated every day.
An SQDP board is not simply a colourful calendar. It is the starting point for daily operational meetings, identifying deviations, assigning actions and checking whether those actions actually solved the problem.
This guide explains the complete system: what SQDP means, how to select KPIs, how to structure the board, how to define green, amber and red statuses, how to run the daily meeting and how to implement either a physical or digital SQDP board in a manufacturing environment.
Table of contents
- What is an SQDP board?
- What does SQDP stand for?
- Why do companies use SQDP boards?
- What does an SQDP board look like?
- How to choose KPIs for S, Q, D and P
- How to define green, amber and red thresholds
- How to run a daily SQDP meeting
- How to manage corrective actions
- SQDP, SQDC, SQCDP and other variants
- Physical board, Excel or digital application?
- How to implement an SQDP board step by step
- Common implementation mistakes
- Practical implementation example
- How to measure whether SQDP is working
- Frequently asked questions
What is an SQDP board?
An SQDP board is a visual daily management tool used to monitor safety, quality, delivery and production performance.
It usually presents the current month as a calendar or a structured set of KPI fields. Each day receives a status, most often:
- green — the target was achieved,
- amber — there was a deviation or risk requiring attention,
- red — the target was missed or immediate action is required.
The main purpose of the board is not reporting for its own sake. The board should support a repeatable management cycle:
- detect a deviation,
- describe the problem,
- assign an owner,
- define a due date,
- verify whether the action was effective.
For that reason, the SQDP board is often a central element of a Daily Management System. It connects performance data with the daily behaviour of the team.
A good board allows an operator, team leader, manager or visitor to understand the condition of the process within seconds. A poor board contains large amounts of data but does not make the current situation clear.
For a shorter introduction, see SQDP Board — What It Is, How It Looks and How to Implement It.
What does SQDP stand for?
The acronym SQDP usually represents four operational areas:
S — Safety
Safety comes first because no production target should be achieved at the cost of employee health or safe working conditions.
Typical Safety indicators include:
- accidents,
- near misses,
- unsafe conditions,
- unsafe behaviours,
- days without an accident,
- completed safety audits,
- overdue safety actions,
- use of personal protective equipment,
- reported hazards.
A mature Safety section should include both lagging indicators, such as accidents, and leading indicators, such as hazard reporting and audit completion.
Q — Quality
Quality shows whether the process delivered a product that meets customer and internal requirements.
Typical Quality indicators include:
- defect rate,
- scrap rate,
- rework,
- First Pass Yield,
- PPM,
- customer complaints,
- internal non-conformities,
- blocked batches,
- first-piece inspection results,
- cost of poor quality.
The Quality section should allow the team to identify not only that a problem occurred, but also what product, process or defect type caused it.
D — Delivery
Delivery shows whether the team completed the required work in the required quantity and at the required time.
Typical Delivery indicators include:
- production plan attainment,
- On Time Delivery,
- OTIF,
- delayed orders,
- missed shipments,
- backlog,
- material shortages,
- lead time,
- schedule adherence,
- internal delivery performance.
Delivery often combines several functions: production, planning, logistics, purchasing and maintenance. For this reason, a delivery problem can reveal issues outside the production line itself.
P — Production or People
The final letter is interpreted differently across organisations.
When P means Production, typical indicators include:
- output,
- productivity,
- OEE,
- downtime,
- line efficiency,
- cycle time,
- utilisation,
- changeover performance,
- labour hours per unit.
When P means People, typical indicators include:
- absenteeism,
- staffing level,
- training completion,
- skill matrix coverage,
- employee suggestions,
- Kaizen participation,
- rotation,
- multiskilling progress.
Both interpretations are valid. The important requirement is consistency: the organisation must define clearly what P means and which KPIs belong to that area.
A more detailed explanation of performance indicators is available in Manufacturing KPIs — How to Measure Safety, Quality, Delivery and People.
Why do companies use SQDP boards?
The main value of SQDP is that it creates one shared operational picture.
Without a visual daily management system, information is often spread across:
- Excel workbooks,
- ERP reports,
- emails,
- paper notes,
- whiteboards,
- production terminals,
- separate departmental databases.
Each source may contain correct information, but the team still lacks one place that answers the most important question:
What requires our attention today?
An SQDP board helps solve several recurring management problems.
Faster detection of deviations
A red or amber status makes the deviation visible immediately. The team does not need to wait for a weekly report.
Shorter and more focused meetings
The board gives the daily meeting a fixed structure. The team discusses abnormalities instead of reading every number.
Clear priorities
The sequence Safety, Quality, Delivery and Production prevents the meeting from focusing only on output.
Better accountability
Every corrective action should have one owner and one due date.
Improved escalation
Problems that cannot be solved at team level can be escalated to the next management tier with the relevant facts already prepared.
Greater transparency
Everyone sees the same information. This reduces arguments based on different spreadsheets or different versions of the data.
Stronger problem-solving discipline
Repeated red statuses reveal chronic issues that require root cause analysis instead of temporary countermeasures.
What does an SQDP board look like?
There is no single mandatory layout, but an effective SQDP board normally contains five elements.
1. Clearly separated SQDP areas
Each section should be easy to identify. The user should immediately see where Safety ends and Quality begins.
2. Current period
Many boards display one month as a calendar. Each day is marked with a status. Other boards show today, yesterday and a rolling trend.
3. KPI, target and actual result
A status colour without the actual number is often insufficient. The board should show at least:
- KPI name,
- target,
- actual result,
- status,
- optional short comment.
4. Corrective action area
The board should include a visible action register or link to it. A useful action record contains:
- problem description,
- immediate containment,
- action owner,
- due date,
- current status,
- effectiveness verification.
5. Trend view
The current day is important, but the team also needs to see whether performance is improving or deteriorating.
A practical board can include:
- daily status calendar,
- seven-day trend,
- monthly summary,
- repeated problem counter,
- open action count.
Example of a simple SQDP structure
The board should be readable from the location where the meeting is held. If participants must zoom in, open several tabs or search through a workbook, the board is too complicated.
How to choose KPIs for S, Q, D and P
A frequent implementation mistake is to place every available metric on the board.
The purpose of an SQDP board is not to replace all management reporting. It should contain the small number of indicators required for daily decisions.
A good daily KPI should be:
- understandable to the team,
- available every day,
- connected to an operational target,
- influenced by the people attending the meeting,
- quick to update,
- easy to compare with a threshold,
- useful for triggering an action.
Recommended starting set
Start with one primary KPI per area. Add another KPI only when it supports a real daily decision.
Avoid duplicated indicators
Delivery and Production often become duplicates.
A useful distinction is:
- Delivery — did we produce the correct quantity according to the schedule?
- Production — how efficiently did we use resources to achieve the result?
For example, a line may complete the production plan while OEE remains low because the team used overtime. Delivery would be green, but Production might be red or amber.
Use both lagging and leading indicators
A lagging KPI describes an outcome that has already occurred.
Examples:
- accident,
- customer complaint,
- missed shipment.
A leading KPI measures activities that reduce the probability of a future problem.
Examples:
- completed safety audits,
- preventive maintenance completion,
- first-piece inspection,
- overdue action count.
A strong SQDP system combines both types.
How to define green, amber and red thresholds
Colours only create value when their definitions are objective.
Each KPI should have documented rules explaining when the result is:
- green,
- amber,
- red.
Example: production plan attainment
- Green: 98% or more,
- Amber: 95% to 97.9%,
- Red: below 95%.
Example: defect rate
- Green: up to 1.0%,
- Amber: 1.01% to 1.5%,
- Red: above 1.5% or any critical defect.
Example: Safety
- Green: no accident and no unresolved critical hazard,
- Amber: near miss or reported hazard requiring action,
- Red: accident, serious unsafe act or critical risk.
Use thresholds based on process reality
Thresholds should be connected to:
- customer requirements,
- internal standards,
- legal requirements,
- historical process capability,
- improvement targets,
- business risk.
They should not be adjusted every time the team receives a red result.
A board that is permanently green despite missed customer deliveries is not a successful board. It is a reporting system with weak definitions.
Decide how to treat missing data
Missing data should not automatically become green.
A practical rule is:
- no data before the agreed update time — grey,
- data unavailable because the process failed — amber or red,
- KPI not applicable that day — clearly marked N/A.
How to run a daily SQDP meeting
A typical SQDP meeting should be short, structured and action-oriented.
For a production team, a useful duration is usually 10 to 15 minutes.
Recommended agenda
- Confirm attendance and required roles.
- Review Safety.
- Review Quality.
- Review Delivery.
- Review Production or People.
- Discuss only amber and red items.
- Review overdue actions.
- Assign new actions.
- Escalate unresolved issues.
- Confirm priorities for the shift or day.
Review Safety first
Starting with Safety reinforces the real hierarchy of priorities. The meeting should not begin with production output.
Focus on deviations
Green indicators should normally be acknowledged quickly. Meeting time should be used for:
- red status,
- amber risk,
- recurring deviation,
- overdue action,
- cross-functional support.
Do not solve every problem during the meeting
The daily meeting is for identifying, assigning and escalating issues.
Detailed root cause analysis should be moved to a separate problem-solving session with the relevant people.
Use a fixed meeting time
A predictable routine improves attendance and data availability. The board should be updated before the meeting, not during a long discussion.
Define roles
Typical roles include:
- meeting leader,
- KPI owner,
- action owner,
- escalation contact,
- person responsible for updating the board.
In small teams, one person may perform several roles.
How to manage corrective actions
A red status without an action is only information.
A useful action management process should contain six elements:
- issue,
- immediate containment,
- responsible person,
- due date,
- action status,
- effectiveness check.
Example action record
One owner per action
An action assigned to “Production and Logistics” usually has no clear owner.
Assign one named owner, even if several people support the work.
Separate action from root cause
“Talk to the operator” is not a complete corrective action.
The team should distinguish:
- containment,
- suspected cause,
- root cause,
- permanent corrective action,
- effectiveness verification.
Escalate overdue or blocked actions
The board should make overdue items visible. If an action requires authority, budget or support beyond the team, it should move to the next management level.
Close actions only after verification
Completing a task does not prove that the problem has been solved.
The team should verify whether the KPI improved and whether the issue returned.
SQDP, SQDC, SQCDP and other variants
Different organisations use different versions of the acronym.
There is no universal rule requiring one specific version.
The correct structure depends on:
- management level,
- type of process,
- customer requirements,
- business priorities,
- existing KPI system.
SQDP versus SQDC
SQDC replaces Production or People with Cost.
SQDC may be more suitable when managers need daily visibility of:
- scrap cost,
- overtime cost,
- premium freight,
- labour cost,
- consumption variance.
SQDP is often more intuitive at line or team level, where output, people and direct process performance are easier to influence daily.
Do not copy the acronym without defining it
Two companies may both use SQDP but measure completely different things.
The value comes from the operational definition, not the letters themselves.
Physical board, Excel or digital application?
An SQDP system can be implemented in several ways.
Physical board
Advantages:
- visible on the shop floor,
- simple to understand,
- low initial cost,
- supports face-to-face meetings,
- does not require a computer.
Limitations:
- history is difficult to analyse,
- remote access is impossible,
- action tracking may be weak,
- data can be lost when the board is erased,
- copying information between departments takes time.
Excel workbook
Advantages:
- familiar to most organisations,
- flexible,
- inexpensive,
- easy to calculate basic KPIs.
Limitations:
- version control problems,
- manual consolidation,
- files stored on individual computers,
- accidental formula changes,
- limited action workflow,
- weak mobile and shop-floor usability,
- difficult multi-site scaling.
Digital SQDP application
Advantages:
- real-time access,
- shared data source,
- automatic history,
- structured actions,
- easier trend analysis,
- remote access,
- multi-department and multi-site use,
- fewer problems with file versions.
Limitations:
- requires implementation,
- requires user training,
- may require subscription or internal IT support,
- poor configuration can reproduce the same problems digitally.
The right option depends on the scale of the organisation and the maturity of the process.
A detailed comparison is available in Lean Boards vs Excel — Which One Is Right for Your Plant?.
How to implement an SQDP board step by step
A successful implementation should begin with the management process, not with the appearance of the board.
Step 1: Select the pilot area
Choose one production line, team, warehouse zone or department.
The best pilot area has:
- a measurable daily process,
- a team leader willing to participate,
- recurring operational problems,
- access to basic data,
- visible value from faster reaction.
Avoid starting with the most complex area in the organisation.
Step 2: Define the purpose
Write down what the board should improve.
Examples:
- reduce delayed orders,
- improve response to quality deviations,
- make safety risks visible,
- reduce time spent preparing daily reports,
- improve action ownership.
Without a clear purpose, the board can become an additional reporting obligation.
Step 3: Define each SQDP area
Specify exactly what S, Q, D and P mean in the pilot area.
For example:
- Safety — accidents, near misses and open hazards,
- Quality — defect rate and customer complaints,
- Delivery — daily schedule attainment,
- Production — OEE and downtime.
Step 4: Select one primary KPI per area
Each KPI should have:
- formula,
- data source,
- owner,
- update frequency,
- target,
- colour thresholds.
Document the definition so that different people calculate the result in the same way.
Step 5: Design the board
The board should contain:
- current date or month,
- KPI names,
- targets,
- actual results,
- statuses,
- comments,
- action area,
- trend or summary.
Keep the first version simple.
Step 6: Define the daily meeting
Decide:
- meeting time,
- meeting location,
- duration,
- participants,
- leader,
- escalation route,
- expected preparation.
Step 7: Define the action process
Agree what happens after an amber or red result.
The process should specify:
- when an action is required,
- who creates it,
- who owns it,
- how due dates are set,
- how escalation works,
- how effectiveness is confirmed.
Step 8: Train the team
Training should explain:
- why the system is being introduced,
- what each KPI means,
- how colours are assigned,
- what happens after a red result,
- how the meeting should run,
- what is expected from each participant.
Step 9: Run a four-week pilot
During the pilot, observe:
- whether data is available on time,
- whether thresholds are clear,
- whether meetings remain short,
- whether actions are completed,
- whether the board helps decisions.
Do not redesign the board every day. Collect feedback and make controlled improvements.
Step 10: Standardise and scale
After the pilot, create a simple standard containing:
- board layout,
- KPI definitions,
- meeting standard,
- action workflow,
- escalation rules,
- review frequency.
Only then expand the system to other teams.
Common implementation mistakes
Too many indicators
The board becomes a dashboard for analysts instead of a daily management tool for the team.
No clear KPI definitions
Different shifts calculate the same indicator differently.
No action after red status
The board records failure but does not change behaviour.
Meetings that are too long
The team tries to perform root cause analysis during the daily review.
Data updated after the meeting
Participants discuss yesterday's status without reliable information.
Permanent red indicators
If a KPI stays red for weeks without escalation or corrective work, the colour loses meaning.
Permanent green indicators
If every day is green, verify whether thresholds are too easy or the KPI is irrelevant.
Copying another company's board
A template may help, but KPIs and thresholds must match the local process.
Using the board to blame people
The board should make process problems visible, not become a tool for public criticism.
Implementing software before defining the process
A digital platform cannot compensate for unclear ownership, undefined KPIs or weak meeting discipline.
Practical implementation example
Consider a production line with the following recurring issues:
- small safety hazards were reported informally,
- defect information was available only at the end of the shift,
- the plan was often missed because of material shortages,
- downtime actions were not consistently assigned.
The team introduced four primary indicators:
The daily meeting was scheduled for 08:10 and limited to 12 minutes.
On the third day, Delivery became red because production plan attainment reached 91%.
The board showed:
- missing material for order A214,
- 75 minutes of lost time,
- one delayed internal delivery,
- logistics team leader as action owner,
- due date on the same day.
The immediate action was to re-sequence production. The permanent action was to change the material call-off point.
For the next five days, the team checked whether the same shortage returned.
This example illustrates the complete SQDP cycle:
- deviation became visible,
- problem was described,
- owner was assigned,
- immediate action protected the plan,
- permanent action addressed the cause,
- effectiveness was verified.
How to measure whether SQDP is working
The number of green cells is not enough to prove success.
An effective SQDP system should improve both operational results and management behaviour.
Process indicators
Monitor whether:
- meetings start on time,
- data is updated before the meeting,
- meeting duration stays within the standard,
- every red status has an owner,
- overdue actions are escalated,
- actions include effectiveness checks.
Result indicators
Monitor trends in:
- accidents and hazards,
- defect rate,
- plan attainment,
- delivery performance,
- downtime,
- OEE,
- overdue action count,
- average action closure time,
- recurring problems.
Behavioural signs of a mature system
A mature SQDP process is visible when:
- operators understand the KPIs,
- team leaders use data to prioritise work,
- problems are raised without fear,
- chronic deviations trigger root cause analysis,
- managers support escalation,
- the board is used every day,
- the meeting can continue when one person is absent.
Review the board periodically
A monthly or quarterly review should ask:
- Are all KPIs still relevant?
- Are targets still appropriate?
- Is any indicator duplicated?
- Does the team use the information?
- Are actions solving problems?
- Should any manual data be automated?
The board should be stable enough to build routine, but flexible enough to remain useful.
Frequently asked questions
What does SQDP mean?
SQDP normally means Safety, Quality, Delivery and Production or People. The four areas are used to structure daily operational performance reviews.
What is the main purpose of an SQDP board?
Its main purpose is to make deviations visible, support short daily meetings and connect KPI results with corrective actions.
How many KPIs should an SQDP board contain?
A practical starting point is one primary KPI for each area. Additional KPIs should be added only when they support a daily decision.
How long should an SQDP meeting take?
For a team-level board, 10 to 15 minutes is usually sufficient. Complex problem solving should take place outside the daily meeting.
Should an SQDP board use two or three colours?
Both approaches are possible. Three colours provide an early warning through amber status, but only when the thresholds are clearly defined.
What is the difference between SQDP and SQDC?
SQDP normally includes Production or People, while SQDC includes Cost. The best version depends on the process and management level.
Can an SQDP board be managed in Excel?
Yes. Excel can work for a small pilot, but version control, manual consolidation and action management become more difficult as the system grows.
Is a digital SQDP board better than a physical board?
A digital board provides history, remote access and structured actions. A physical board may be sufficient for one team. The better option depends on scale, data availability and management needs.
Should every red status create an action?
A red status should at least trigger a decision. Some issues require immediate containment, others require a formal corrective action or escalation.
Can SQDP be used outside manufacturing?
Yes. The same structure can be adapted for warehouses, maintenance teams, offices, logistics processes and service operations.
SQDP implementation checklist
Before launching the board, confirm that:
- the pilot area has been selected,
- the purpose of the board is defined,
- S, Q, D and P have clear meanings,
- every KPI has one documented formula,
- every KPI has a data source and owner,
- green, amber and red rules are defined,
- the meeting has a fixed time and leader,
- actions have owners and due dates,
- escalation rules are understood,
- the team has been trained,
- the pilot review date has been scheduled.
Summary
An SQDP board is effective when it does more than display operational results.
It should create a daily management cycle:
- monitor Safety, Quality, Delivery and Production or People,
- detect abnormalities early,
- focus the daily meeting on deviations,
- assign actions and owners,
- escalate unresolved issues,
- verify whether corrective actions worked.
The board can be physical, based on Excel or implemented in a digital application. The tool matters, but the management process matters more.
Begin with clear definitions, a small number of useful KPIs and a disciplined daily meeting. Once the pilot works, standardise the process and scale it to other teams.
Related articles
Ready to deploy Lean boards?
14 days free. No credit card. Setup in 30 minutes.