Where manual work hides in a manufacturing business

Manual work is a process problem before it is a software one.

Manufacturers often ask for an ERP when what they actually have is three teams keeping the same information in different places and reconciling it by hand at the end of every week. No system fixes that on its own — it just gives the duplication a nicer interface. Map an ordinary week first, and count the time spent re-entering data that already exists somewhere else, before choosing any software.

Find the reconciliation, then remove it.

Most manual hours in a factory trace back to two records that disagree. Production counts units, accounts count invoices and dispatch counts cartons. Making one of them the source of truth, and having the other two read from it, takes away the reconciliation itself rather than speeding it up, which no automation layered on top of the disagreement can do.

Automate the hand-off, not the job.

Leave the skilled work alone. The places worth automating are the moments work passes between people: the shift report that becomes a planning input, the dispatch note that becomes an invoice line. Those moments are where errors and delays cluster, and they are the least contentious things to change.

Fix capture before you build reports.

Dashboards built too early are a common mistake. While the way data is captured is still changing, people look at numbers they do not yet trust, and the dashboard spends its credibility before the data is ready. Fix capture first, report second.

Map one order from enquiry to payment

The quickest way to see where manual work hides is to follow a single, ordinary order through the business and write down every record it touches. Pick one from last week, not a showcase order, and trace it from the enquiry to the payment landing in the bank. Sit with each person who handles it and note what they look at, what they type and where they type it.

Most factories find the same facts written down several times on the way. Quantities, item codes and customer names travel from the quotation to the sales order, the job card, the shift report, the packing list, the e-way bill and the invoice, and each hop is often a person reading one document and typing into another. The records to list usually include these:

• Enquiry and quotation, often in email, WhatsApp or a spreadsheet
• The customer’s purchase order and your sales order
• Production plan and job cards for the floor
• Material issue slips and the stores register
• Shift production reports, frequently on paper
• Quality checks, rejections and rework notes
• Packing list, dispatch note and e-way bill
• Invoice and receipt in Tally or another accounting system

Three counts that should agree

Production, dispatch and accounts each count the same goods in their own unit. The floor counts pieces made, dispatch counts cartons or bundles shipped, and accounts count what was invoiced. When the three are kept separately, someone has to reconcile them, usually at the end of the week or the month, and that reconciliation is manual work that adds nothing.

Write down the conversions between the units (pieces per carton, cartons per pallet, kilograms per piece) once, in one place. Then put a week of the three counts side by side. Every gap is a question worth asking:

• Goods made but not dispatched: are they stock, rejects or simply not recorded?
• Goods dispatched but not invoiced: is billing waiting on paperwork from the floor?
• Goods invoiced in a different unit from the one dispatched: who converts, and by hand?
• Rejections noted on the floor but never taken out of stock: does the stock figure still include them?

One source of truth for each fact

Removing a reconciliation means deciding which record owns each fact, and making every other record read from it rather than keep its own copy. The owner should be the record closest to the moment the fact comes into being, entered by the person who sees it happen. A sensible starting split for a small factory looks like this:

• What was ordered: the sales order, entered once when the order is confirmed
• What was made: the production entry, made at the line or at the end of the shift
• What is in stock: the stores record, moved only by receipts, issues and dispatches
• What was shipped: the dispatch note, which then drafts the invoice
• What was billed and paid: the accounting system, posted from the dispatch rather than retyped

A worked example, with illustrative numbers

Suppose, purely as an illustration, a two-shift fabrication unit with about 40 people. The supervisor writes each shift’s output on paper. Next morning the planner types it into a spreadsheet to plan the day, and at dispatch the same quantities are typed into the packing list and then again into Tally for the invoice. The numbers are written once and typed three more times, by three different people.

If each of those three typing steps takes 20 minutes a shift, the unit spends two hours a day, or 12 hours across a six-day week, re-entering numbers it already has, before anyone spends time chasing the mismatches. Capturing output once at the end of the shift, on a tablet or a simple form, and letting planning, dispatch and invoicing read from it removes the retyping altogether. These figures show the method; they are not a measurement from any business, and your own week will give you your own.

Hand-offs worth automating first

Once each fact has an owner, the hand-offs between people become the obvious candidates for automation. They follow rules, they happen many times a week, and nobody’s skill is being replaced. Start with the one that causes the most chasing, and leave shop-floor judgement where it is. Typical first candidates:

• The shift report feeding the production plan, instead of being retyped each morning
• The dispatch note drafting the invoice line and the e-way bill
• Stock falling below its reorder level, raising an alert to the purchase person on WhatsApp
• A quality rejection opening a rework job card and taking the piece out of stock
• Supplier invoices read and posted to Tally once a person has checked them

Where our packages fit

Most of this starts with a map, not software. A Tech Strategy Consultation from ₹3,000 is two sessions that end with a current-state audit and a build-versus-buy recommendation, which is often enough to decide whether you need an ERP at all. For what an ERP project costs and why, see the ERP development cost guide.

When the map points to one system, Manufacturing ERP from ₹2,18,000 covers bills of materials, work orders, job cards, quality checks and costing per batch, with Tally sync; ERP & Inventory Rollout from ₹1,75,000 suits stock and purchase across several locations. If a full ERP is more than you need for now, Tally Integration & Automation from ₹12,000 stops invoices being retyped into Tally, and Document & Data-Entry Automation from ₹16,000 reads supplier documents into your system. The full set is on the ERP packages and prices page.