A daily production report (DPR) is a one-page record of what each machine or line made in a shift. It shows planned quantity, actual quantity, good and rejected pieces, downtime with reasons, and material used. The supervisor fills it at the end of each shift, and the production head checks it the next morning against the plan. Our free Excel format has these columns with the formulas built in, plus a filled example from a plastic moulding unit.
What is a daily production report?
In a factory, DPR means daily production report, not the film-shoot report that also shows up in search. It records what was made, what was lost and why. The owner usually sees a weekly roll-up.
What each column in the DPR format means
The sheet has 6 header fields filled once per shift, then 12 columns filled once per machine.
| Field | What to write | Formula / rule |
|---|---|---|
| Date | Date of the shift | One sheet per shift |
| Shift | Shift name and timing | e.g. A, 06:00–14:00 |
| Plant / unit | Plant, shop or bay | Same name every day |
| Shift length (min) | Total minutes in the shift | 8 hours = 480 |
| Planned break (min) | Lunch and tea breaks | Planned run time = shift length − break |
| Filled by / checked by | Supervisor and production head | Both sign |
| 1. Machine / work order | Machine ID and its work order | From the day's plan |
| 2. Item | Item code and short name | Same code as stores and the BOM; add the unit if not pieces |
| 3. Planned qty | Quantity planned for this shift | From the work order |
| 4. Produced qty | Everything that came off the machine | Actual count, not the target |
| 5. Rejected qty | Pieces scrapped | Cannot be reworked |
| 6. Rework qty | Pieces held for rework | Not good until they pass |
| 7. Good qty | Pieces fit to move ahead | Produced − Rejected − Rework |
| 8. Rejection % | Share of output scrapped | Rejected ÷ Produced × 100 |
| 9. Achievement % | Share of plan met with good pieces | Good ÷ Planned × 100 |
| 10. Downtime (min) | Minutes stopped in planned run time | Sum of all stops |
| 11. Downtime reason | Reason code plus one short note | From the code list, e.g. BD: heater band failed |
| 12. Material issued / returned (kg) | Received from stores, then sent back unused | Consumed = issued − returned |
The starter reason codes are BD (breakdown), MC (mould or die change), MW (material wait), PC (power cut), QH (quality hold) and NO (no operator). Edit them to suit your plant, but keep the list fixed once set.
Utilisation is worked out in the shift summary, not on each machine row. Run time = planned run time − downtime. Utilisation % = run time ÷ planned run time × 100.
How to fill the DPR, step by step
- Before the shift: copy planned qty for each machine from the day's work orders.
- During the shift: log each stop as it happens, with minutes and a reason code.
- At shift end: count produced pieces, then separate rejected and rework pieces.
- Material: write raw material issued, then weigh and return what is left to stores.
- Formulas: the sheet works out good qty, rejection % and achievement %. The shift summary works out utilisation %.
- Sign off: the supervisor signs, and the production head checks it next morning against the plan.
Update the DPR every shift, not once a day. Minutes of downtime are forgotten by evening. Material issued should follow the quantities in your bill of materials format.
[[IMAGE {"type":"compare","title":"Shift data: Excel sheet vs TranZact","columns":["Excel DPR","TranZact"],"rows":[["Work order","Copied by hand","Work orders in one system"],["Stock","Retyped for stores","Stock in, issue, multi-store"],["Costing","Worked out in another sheet","Production costing"],["Reports","Built by hand","65+ reports and dashboards"]]}]]
Worked example: a plastic moulding unit, one shift, three machines
All numbers below are illustrative. Shift A runs 06:00–14:00, which is 480 minutes. With a 30-minute break, each machine has 450 minutes of planned run time.
Table 1 (Example): DPR for Shift A
| Field | IMM-01 | IMM-02 | IMM-03 |
|---|---|---|---|
| Work order / item | WO-1121, 1 L container | WO-1122, 1 L lid | WO-1123, 28 mm cap |
| Planned qty (pcs) | 1,500 | 2,400 | 6,000 |
| Produced qty | 1,400 | 1,950 | 5,800 |
| Rejected / rework | 28 / 0 | 15 / 15 | 58 / 0 |
| Good qty | 1,372 | 1,920 | 5,742 |
| Rejection % | 2.0% | 0.8% | 1.0% |
| Achievement % | 91.5% | 80.0% | 95.7% |
| Downtime (min) / reason | 30 / MC | 90 / BD | 15 / MW |
| Material issued / returned (kg) | 175 / 30 | 75 / 24 | 45 / 20 |
Check one row yourself. IMM-02 produced 1,950 lids, with 15 rejected and 15 on rework. Good qty is 1,950 − 15 − 15 = 1,920, and 1,920 ÷ 2,400 = 80.0%.
Table 2 (Example): shift summary
| Measure | Shift A total | How it is worked out |
|---|---|---|
| Planned run time | 1,350 min | 3 machines × 450 |
| Downtime | 135 min | BD 90 + MC 30 + MW 15 |
| Run time | 1,215 min | 1,350 − 135 |
| Utilisation | 90.0% | 1,215 ÷ 1,350 × 100 |
| Material issued | 295 kg | 175 + 75 + 45 |
| Material returned | 74 kg | 30 + 24 + 20 |
| Material consumed | 221 kg | 295 − 74 |
What the production head reads from this report
IMM-02 lost 90 minutes to a heater band failure and reached 80.0% of plan. The gap of 480 lids goes into tomorrow's plan.
IMM-01's 2.0% rejection points at the mould change. And 74 kg of unused material goes back to stores, or stock will be wrong.
Shift-wise, machine-wise or plan-vs-actual: which DPR layout fits?
| Layout | One row is | Fits |
|---|---|---|
| Machine-wise (this template) | One machine, one shift | Moulding, machine shops, press shops |
| Line-wise | One line, one shift | Assembly or packing lines making one product |
| Plan-vs-actual roll-up | One work order or item, one week | The owner's weekly review |
If one item passes through several machines, the process routing decides which machine reports which step.
A production schedule is made before the shift and says what to make, on which machine, and when. The report is filled after the shift and records what actually happened. Compare the two every day.
Common DPR mistakes
- Adding pieces of different items into one total. Fix: track achievement % per item, or convert output to value in ₹.
- Counting rework as good on the same day. Fix: keep rework in its own column until it passes.
- Blank or "misc" downtime reasons. Fix: use the fixed reason codes, with minutes against each.
- Mixing units for the same item. Fix: use the one unit stores uses for that item.
- Filling the sheet next day from memory, or writing targets instead of counts. Fix: fill it before the shift ends, from actual counts.
- The DPR never reaching stores. Fix: send material returns and output to stores the same day.
Many shop floors still write the DPR in a paper register first. TranZact's AI reads a photo of a paper entry and turns it into a system entry, with no typing.
Where the DPR breaks in Excel, and where TranZact fills it for you
Excel works for one shift on a few machines. It breaks when the same numbers have to be typed again into stock, purchase and costing. Each retyping is a chance for the sheet and the stores count to drift apart.
TranZact is manufacturing AI software used by 10,000+ manufacturers. The work order, routing, stock and costing sit in one system. Its reports and dashboards replace the sheet built by hand.
TranZact production facts (as of 18 Nov 2026)
- Production: multi-level BOM, work orders, process routing, sub-contracting and production costing. See production management.
- Inventory: stock in, issue, multi-store, reorder and AI stock alerts.
- Reports: 65+ reports, plus AI tasks and dashboards.
- Dominate plan only: real-time MIS, machine planning, and quality control for raw material and finished goods.
- Accounts: stay in Tally, Busy or Zoho Books. One-way sync, no double entry.
- Plans: billed yearly, from Grow at ₹8,333/month for 4 users. There is no free plan. See pricing.
- Go-live: live in 2–3 weeks.
TranZact does not have a screen called "Daily Production Report". In a demo, bring your current DPR and see how your work orders, stock and reports would look.
Start with the free Excel format today. Don't be the bottleneck. Become the AI-Run Factory.