
Every factory owner asks the same questions each morning. How much did we make yesterday? Were there problems? What went out of the gate? Which orders are in trouble? Who owes us money? In most SMEs, the answers arrive in pieces: a call to the production manager, a WhatsApp photo of the production register, an Excel sheet from accounts on a good day, and a long conversation with the planner. By the time the picture is complete, it is lunchtime, and half of it is already out of date.
An automatic daily report replaces that routine with a single summary that arrives before the owner reaches the factory. This guide explains what to include, where each number comes from, how to design it so it gets read, and how to automate it step by step — one of the most visible early wins of manufacturing automation.
Why the manual report fails
- It is late. Someone has to collect registers, count, type and send. The report arrives hours after the day it describes.
- It is inconsistent. Different people compile it on different days, with different definitions.
- It hides problems. Totals look fine while one machine stopped for six hours or one customer's order slipped.
- It costs time. A supervisor or clerk spends an hour or more every day on it — time not spent on the floor.
- It can be massaged. When people compile reports about their own performance, bad news softens.
What to include
The report should fit on one phone screen at first glance, with detail one tap away. Seven sections cover what most owners need.
1. Output against plan
Yesterday's good production by line, section or product group, against the plan, in the units the factory thinks in — pieces, kilograms, tonnes, metres. Show the month to date against target as well, because one bad day matters less than a bad trend.
2. Rejections
Rejected quantity and percentage, overall and for the worst two or three parts or defects. Include customer rejections received yesterday, which matter more than internal ones.
3. Stoppages
Machines or lines that stopped for more than a threshold — say thirty minutes — with the reason and duration, and any machine still stopped this morning. Total downtime hours by reason give the context.
4. Dispatch
Value and quantity dispatched yesterday and month to date, by customer for the main customers. For many owners this is the number that matters most, because it becomes revenue.
5. Orders
Orders received yesterday, the value of the open order book, and — most useful — the orders whose planned completion is now later than the promised date. This list is the owner's early warning for customer calls.
6. Cash
Receivables due this week and overdue, with the largest overdue customers. Where the accounting system can provide them, collections received yesterday. Many owners say this is the section they read first.
7. Exceptions and notes
Anything unusual that the numbers don't capture: a safety incident, a customer visit, a major breakdown still being worked on. A short note from the production manager, added to the automatic report, keeps the human context.
Design for a busy reader
- Exceptions first. Lead with what is wrong — behind plan, stopped, late, overdue — not with what is normal.
- Comparison with every number. A number alone means little. Show plan, target, yesterday or the usual level beside it.
- Consistent definitions. Write down what each number means — for example, whether output counts parts before or after final inspection — and never change it silently.
- Short. If the summary takes more than a minute to read, it won't be read every day.
- Drill-down available. A link from each section to the detail — which machine, which order, which customer — for when the owner wants to know more.
Where each number comes from
| Section | Source |
|---|---|
| Output | Shop-floor booking on tablets, machine counts, or production entry at the end of each shift |
| Rejections | Inspection records and rejection booking; customer complaint log |
| Stoppages | Downtime booking with reasons, or machine run/stop signals |
| Dispatch | Delivery challans and invoices |
| Orders | Sales order register and production plan |
| Cash | Accounts — receivables and collections |
The report is only as good as these sources. If output is written on paper and typed in the next morning, the report can't arrive before that typing is done. Automating the report therefore usually goes hand in hand with moving the underlying entries to where the work happens.
Automating it step by step
- Agree the content and definitions with the owner, using the manual report as the starting point.
- Automate what is already digital. Dispatch and invoicing are usually already in software; orders and receivables often are too. Put these in the report first.
- Move output and stoppages to shop-floor booking — operator or supervisor entries on tablets, or machine signals where available. See our guide to Android tablets on the shop floor.
- Add rejections from inspection booking.
- Schedule the report to generate at a fixed time — early enough to be read before the morning meeting — and send it by email with a link to the dashboard.
- Retire the manual report once the automatic one has matched it for a few weeks.
Getting cash numbers from accounts
Many SMEs keep accounts in Tally or another accounting package while operations move to factory software. Receivables in the daily report then depend on getting data from accounts. Options range from a scheduled export that the factory software imports, to a direct connection where the accounting software supports one, to a manual upload by the accountant once a day. Which is practical depends on your accounting setup and should be confirmed before it is promised. Our guide to using Tally alongside factory software covers the options.
Beyond the daily email
Once the data flows automatically, other reports follow at almost no cost: a shift report for the production manager at the end of each shift, a weekly summary with trends for the management meeting, a monthly report for the bank or investors, and alerts in real time for events that can't wait until morning — a machine stopped for an hour, a customer rejection, a large order received. The rule for alerts is the same as for the report: few, important and sent to the person who can act.
What owners do differently
Owners who receive a reliable daily report typically change how they spend the morning. Instead of collecting information, they ask about exceptions: why did press 4 stop, what is the plan for the late order, when will the overdue customer pay. Meetings get shorter. Supervisors stop compiling and spend more time on the floor. And because the same report arrives every day, trends become visible — a slowly rising rejection rate, a customer whose payments are slipping, a section that consistently misses its plan on Mondays.
Different reports for different people
The owner's report is not the only one worth automating, and it should not try to serve everyone. The production manager needs the same output and stoppage data in more detail — by machine, operator and shift — and needs it at the end of each shift rather than the next morning. The quality head needs rejections by part, defect and machine, with open NCRs. The sales head needs order status and dispatch by customer. Each of these can be generated from the same data with its own content and timing. Keeping the owner's report short is easier when the detail exists somewhere else for those who need it.
Targets that mean something
A report that compares actual output with a target is only useful if the target is realistic. Many factories carry targets set years ago, or calculated from theoretical machine speeds, which are missed every day and therefore ignored. Better targets come from the plan — what was actually scheduled for that day — or from recent performance on the same products. Once shop-floor booking has run for a few months, the report can show both: performance against plan, and the plan against what the machines achieved on their best comparable days. The gap between the two is the improvement opportunity.
Keeping the report honest
An automatic report is harder to massage than a manual one, but it is not immune. If operators book output generously, or downtime reasons are always "other", the report reflects that. Two habits keep it honest: compare booked output with packed or dispatched quantities each week, and occasionally walk the floor with the report in hand to check that what it says matches what you see. When people know the numbers are checked, they record them more carefully.
A worked example
An injection moulding company with 24 machines across two shifts produced its daily report by hand: the night supervisor counted output from production slips, the quality inspector added rejections, and the office typed it into Excel. The owner received it at around 11 am, by which time he had already called three people.
The company started with what was already in software — dispatch and orders — and added operator booking on tablets at each pair of machines, with downtime reasons. Within six weeks, a report was emailed at 7 am with output by machine against plan, rejections by part, stoppages over thirty minutes, dispatch, late orders and overdue receivables from a daily accounts export. The manual report stopped. The supervisor's hour of counting moved to the floor, and the morning meeting began with the report's exceptions instead of a status round.
Common mistakes
- Too many numbers. A report with forty metrics is read once. Seven sections with exceptions first are read daily.
- Automating bad data. If output is entered late or inaccurately, automation spreads wrong numbers faster. Fix the source first.
- No owner for definitions. When someone changes how output is counted without telling anyone, trust in the report disappears.
- Report without action. The report should feed a short daily meeting where exceptions get owners and dates.
Measuring the benefit
The benefit of an automatic report is easy to underestimate because much of it is time that simply stops being wasted. Measure it before and after: hours per day spent compiling reports, the time the report arrives, the number of status calls the owner and planner make, and how quickly exceptions — a stopped machine, a late order — reach someone who can act. Most factories find that the report pays for the shop-floor booking needed to feed it within months, before counting any improvement in output or delivery.
A final point: start small. A report with three reliable numbers that arrives at 7 am every day is worth more than an ambitious design that waits months for every data source to be ready.
Working with Corposol
Corposol builds custom manufacturing software for Indian SMEs, including shop-floor booking, dashboards and automatic daily, shift and weekly reports built on the same data. Read how we built factory automation software for a plastics manufacturer. All custom code is transferred to you on final payment.
Frequently asked questions
What should be in a factory owner's daily report?
Yesterday's output against plan, rejections, major stoppages, dispatch value, orders received, orders at risk of being late, and a short cash view — receivables due and overdue. Each with a comparison to target or to the usual level, and exceptions highlighted.
Where does the data for an automatic report come from?
From the systems where work is recorded: shop-floor booking or machine signals for output and stoppages, quality records for rejections, dispatch and invoicing for shipments, the order book for orders, and accounts for receivables.
How is the report delivered?
Usually as an email with a short summary and a link to a dashboard, generated at a fixed time each morning. A phone-friendly dashboard lets the owner drill into any number.
What if some data is still on paper?
Start with the numbers that are already recorded digitally, and add the rest as each area moves off paper. A partial automatic report is still better than a complete manual one that arrives at noon.
