🏅 SOP 22 — Batch Quality Score

SOP Name:         Batch Quality Score
Process Code:     BATCH_SCORE_V1
Version:          V1
Owner:            Factory Supervisor
Applies To:       Factory Supervisor, QC
Frequency:        Once per completed batch
Last Updated:     2026-06-25
Review Frequency: Monthly

1. Purpose

Give every batch a simple, comparable quality score so trends and problem batches are visible at a glance.

2. Who Is Responsible

Factory Supervisor / QC — scores the batch and records it.

3. When To Use This SOP

After a batch is complete and Visual QC (VISUAL_QC_REJECT_V1) is done, before the daily report.

4. Visual Process Flow

flowchart TD
A[Batch complete] --> B[Collect QC + reject data]
B --> C[Score each factor]
C --> D[Total = Batch Quality Score]
D --> E{Score band?}
E -- Green --> F[Record + continue]
E -- Yellow --> G[Note cause, watch next batch]
E -- Red --> H[Inform Ram/Srinivasan]

5. Scoring Factors (20 points each, total 100)

Factor	What good looks like	Score /20
Rejection rate	Low reject % vs batch size
Shape & edges	Sharp edges, correct size
Surface finish	No cracks/powdering
Interlock fit	Fits correctly
Process discipline	First-20 + hourly checks done, batch card kept
Total		/100

Score Bands

🟢 Green  85–100  Good batch — continue
🟡 Yellow 60–84   Acceptable — note cause, watch next batch
🔴 Red    < 60    Problem batch — inform management

6. Do / Don't

✅ Do	❌ Don't
Score from actual QC/reject data	Score from memory or feeling
Record the main cause for low scores	Leave a red batch unexplained
Compare against recent batches	Treat each batch in isolation

7. Checklist

[ ] QC + reject data collected
[ ] All 5 factors scored
[ ] Total calculated
[ ] Band assigned (Green/Yellow/Red)
[ ] Cause noted if Yellow/Red
[ ] Score recorded

8. Records To Update

🔵 Batch record (score + band)
🔵 Daily Production Report
🔵 Telegram alert if Red

9. Escalation Rule

Inform Ram/Srinivasan for any Red batch, or two consecutive Yellow batches with the same cause.

10. Common Mistakes

Scoring without the actual reject numbers.
Not recording the cause of a low score.
Ignoring a downward trend across batches.

11. Improvement Suggestion

If you find a better way to do this process, add a comment below or submit an improvement request in the SOP Improvement Register.

Automation Readiness

Telegram command: /score
n8n workflow:     wf_batch_score_v1
Odoo object:      quality.check (custom score field)
Approval role:    Factory Supervisor + QC
Supabase table:   batch_quality_scores
Status:           Future automation