Portal
Employee — enter data
SAMPLE DATA

Shift production report

Opens from a WhatsApp link — no app to install, no password. The supervisor selects from approved lists, so there is no free text for AI to misread.

▤
Shift Production Report
saves to the live database via n8n
🔒 In the real system, machine/shift/date come pre-filled from the supervisor's private link. For the demo you can pick them.
from approved SKU master
✓ coded from a list — no free text to interpret
Plan achievement—
Rejection rate—
Total downtime— min
values calculated live · validated by n8n before saving

How this satisfies the brief

✓
Mandatory data

Fields marked * block submission until complete. Nothing reaches the database half-filled.

✓
No guessing

Machine, SKU and reason code come from approved dropdowns, so there is no free text for AI to misread.

✓
Validation before save

Rejects good + reject > target, impossible downtime, and a duplicate report for the same shift.

◉
Audit trail

Stores user, timestamp, shift, machine and lot. Any later correction keeps the previous value.

◉
Manual fallback

If the link will not open, the supervisor sends plain WhatsApp text — a human confirms it before it saves.

Breakdown / downtime event

Raised the moment a machine stops. Creates a maintenance ticket, starts a clock, and escalates on its own if it stays open.

⚠
Breakdown Report
opens a ticket on submit
approved downtime code list
Downtime clockstarts at stop time
Alert toMaintenance + Owner
Auto-escalate if open> 4 hours
clock runs from stop time, not submit time

Ticket lifecycle

1
Raised

Supervisor submits. The clock starts at the recorded stop time, not the submission time.

2
Alerted

Maintenance receives the ticket on WhatsApp within two minutes.

3
Escalated

Still open past the agreed threshold, it goes to management automatically — nobody has to remember to chase it.

✓
Closed

Maintenance records the fix and the restart time, which closes the downtime minutes for that shift.

Rejection / quality incident

Links every defect to a machine, operation, SKU and heat number for traceability. The system notifies and holds — it never releases material by itself.

◆
Rejection Report
material goes on HOLD
approved rejection code list
ActionHold + notify Quality
Corrective action duewithin 48 hours
Material releaseneeds named Quality approval
material release needs a named Quality approval — never automatic

Quality boundary

✓
What the system does

Records the defect, raises a hold notification, opens a follow-up task, and alerts when corrective action runs overdue.

✕
What it never does

Release material, grant a concession, or make any quality decision without a named human approving it.

◉
Traceability

Defect links to machine, operation, SKU, heat/lot and person — a customer complaint can be traced back to its batch.

◉
Trend

Codes accumulate into the weekly ranking, turning scattered incidents into a ranked list worth acting on.