Short answer
The template — one row per machine per shift
| Column | What goes in | Why it's there |
|---|---|---|
| Machine | Machine code (TC-01, VMC-03) | The asset that lost or made the time |
| Shift / Operator | A / B / C and the operator's name | Fair comparison across shifts and people |
| Job card / Part | Job number and part name | Ties output and losses to the order and the quote |
| Target | Pieces planned for the shift on this job | Ahead or behind, at a glance |
| Good pieces | Counted at the machine | The number the customer pays for |
| Rejects + reason | Count, and the reason per reject (dimension, tool mark, burr…) | A number without a reason cannot be fixed |
| Setup min | Changeover and first-piece approval time | The loss job shops can do most about |
| Run min | Time actually cutting | Feeds availability and performance |
| Downtime min + reason | Every stop with its reason | The top reason is next week's project |
| OEE | Availability × performance × quality for the row | One number that compares machines honestly |
| Remarks | Breakdown root cause, tool changes, notes | The context a number can't carry |
A filled-in example
| Machine · Shift | Job / Part | Target | Good | Rejects | Setup | Run | Downtime | OEE |
|---|---|---|---|---|---|---|---|---|
| TC-01 · A (Suresh) | JC-0231 · Shaft pin 25 mm | 450 | 401 | 9 (dimension 7, burr 2) | 35 | 388 | 62 (setup 35, tool brk 15, material 12) | 71% |
| TC-01 · B (Ramesh) | JC-0231 · Shaft pin 25 mm | 450 | 434 | 4 (tool mark) | 0 | 421 | 29 (power 18, inspection 11) | 77% |
| VMC-03 · A (Priya) | JC-0228 · Flange 80 mm | 150 | 112 | 3 (dimension) | 48 | 302 | 148 (setup 48, no operator 60, tooling 40) | 50% |
Read it like an owner: TC-01's night shift beat the day shift with the same part because it had no setup and fewer stops — so the setup, not the operator, is the story. VMC-03 lost an hour with no operator and 40 minutes to tooling; that is a scheduling and a tool-crib problem, both fixable this week.
The shift summary — what the owner actually reads
- Output vs plan for the shift, in pieces and as a percentage.
- Top three downtime reasons by minutes, across all machines.
- Breakdowns: machine, reason, duration, who cleared it.
- Rejects by reason, across all machines.
- Machines idle with no job assigned, and for how long.
- One line per operator: pieces, rejects, productive time.
Five rules that keep the report honest
Rules
- Log at the machine
- Entries at the moment they happen, by the operator — not reconstructed by a supervisor later
- Every reject has a reason
- A short list the operator picks from; free text only in remarks
- Every stop has a reason
- Setup, breakdown, tooling, material, quality, utilities, operator
- Setup is not run time
- Book it separately or availability lies
- Same basis for every shift
- Same ideal cycle, same reason list, same clock — or comparisons are noise
Excel today, automatic tomorrow
Copy the columns above into a sheet with one tab per day and you have a working daily production report. It will be filled at the end of the shift from memory, and it will miss the short stops — but it is far better than a diary. When the report is worth more than the hour it takes to write, put a tablet at each machine and let the report write itself: the same columns, from the same taps, ready before the next shift starts. See production tracking in OpeEye.
Get this report every shift — without anyone writing it.
A 20-minute demo, on-site in Rajkot and across Gujarat or over a call anywhere in India. Free 15-day trial, no hardware to buy from us.
Questions shop owners ask
What should a daily production report for a CNC shop contain?
+
Per machine and per shift: operator, job card, part, target, good pieces, rejects with reasons, setup time, run time, downtime with reasons, and OEE. Plus a shift summary (total output vs plan, top three downtime reasons, breakdowns) and the day's totals. Anything more is rarely read; anything less hides the losses.
Who should fill the daily production report?
+
Nobody, ideally. The operator logs pieces, rejects and stops at the machine as they happen; the report is a summary of those entries. When a supervisor writes it from memory at 9 pm, the short stops disappear and rejects arrive without reasons.
Should the report be per machine or per operator?
+
Both, from the same data. Owners read it per machine (which asset lost time); supervisors read it per operator (who needs help or credit). If each entry records machine, operator and job together, the same report can be viewed either way.
How is a shift report different from a daily production report?
+
A shift report covers one shift and is ready when it ends, so the next shift starts with the facts. The daily production report combines the day's shifts with totals against plan. Both should come from the same logged events, not be typed twice.
Can I generate this report automatically?
+
Yes. With a tablet at each machine logging pieces, rejects and stops as they happen, shift reports and the daily production report are generated automatically — that is what OpeEye does. The Excel version below is for shops that are not there yet.
Related
- Production trackingPieces vs target per machine, operator, shift and job — without registers.
- Downtime reason codes27 reasons in 8 groups, worded for one-tap logging at the machine.
- How to calculate OEEThe formula, a worked example on a turning centre, and a calculator.
- OEE softwareAvailability × performance × quality, computed from real floor events.