
In many Indian factories, a part's journey includes at least one trip outside the gate. Shafts go out for induction hardening, brackets for zinc plating, housings for powder coating, gears for hobbing or grinding, castings for fettling or machining. These outside processes — job work — are essential, and they are also where production plans most often fall apart.
The internal operations are scheduled machine by machine; the vendor step is a line in the plan that says "plating — 3 days". In reality it is a week, or ten days, or the parts come back short with a few rejected, and the dispatch date is missed. This guide explains how to plan job-work steps properly: realistic lead times, batching, vendor capacity, follow-up and quality at receipt. It complements our guide to job-work challans and balances, which covers the paperwork side.
Why the vendor step is the weak link
- Lead times are guesses. The plan uses a standard number of days that someone set years ago.
- Batching is invisible. Parts wait in your despatch area until there are enough for a vendor trip, and wait again at the vendor until there is a full furnace or tank load.
- Vendor capacity is unknown. The vendor serves many customers. When everyone sends work at month-end, everyone waits.
- Follow-up is by phone. Someone calls the vendor when a customer complains, rather than when the parts are due.
- Returns are short or rejected. Parts come back with process rejects or quantity differences that are discovered at the next operation, or at dispatch.
Make the vendor step a real operation in the routing
The first change is structural. In the part's routing, the outside process should be an operation like any other — with the vendor (or a list of approved vendors), the process, the planned lead time, any minimum batch or load size, and the documents that must travel with the parts (drawing, specification, inspection requirements). The plan then shows the job leaving the factory, spending its lead time at the vendor and returning before the next internal operation can start.
This simple change makes the vendor step visible on the plan and on the order's progress. A job at a vendor is no longer "missing"; it is at a known place, due back on a known date.
Set lead times from history
If job-work challans are recorded in the system with dispatch and receipt dates, the actual lead time for every vendor and process is already available. From a few months of history you can see:
- The typical (median) lead time — the right number for planning.
- The spread — how often it takes much longer, which tells you how much buffer to allow.
- Seasonal effects — month-end, festival periods and monsoon transport delays.
- Differences between vendors for the same process, which matter when choosing where to send urgent work.
Planning with real lead times often produces an uncomfortable discovery: many promised dates were never achievable. That discovery is the first step to promising dates you can keep.
Batching: balance load size against due dates
Heat treatment, plating, painting and many other processes run in loads, and vendors charge by load, weight or minimum lot. It makes sense to batch parts for a vendor trip. But each part in the batch waits for the others. The plan should show, for each pending vendor batch:
- The parts and orders waiting, with their due dates.
- The total weight or quantity against the vendor's load or minimum.
- The latest date the batch can leave and still meet the earliest due date in it.
The planner can then decide to send a part load for an urgent order, combine work across orders, or pull an operation forward to complete a batch — with the trade-off visible rather than guessed.
Know your vendors' capacity
You cannot see inside a vendor's plant, but you can see your own load on it. A view of the quantity or weight you have sent to each vendor per week, together with what is planned to go in the coming weeks, shows when you are about to send more than the vendor usually turns around. Planned peaks can be discussed with the vendor in advance, spread across alternative vendors, or smoothed by changing the sequence of internal work. Our guide to supplier rating and vendor scorecards covers how to measure vendor performance over time.
Follow up before the due date, not after
A daily list of job-work batches due back in the next two or three days, and those already overdue, turns follow-up from firefighting into routine. The purchase or production control person calls or messages vendors with the list, confirms expected dates and updates them in the system. When a vendor confirms a delay, the plan shows which customer orders are affected, so sales can be told early.
Some vendors are willing to use a simple screen to confirm receipt, expected completion and dispatch. Where they are, follow-up becomes even lighter. Where they aren't, the internal update after a call is enough.
Receiving: count, inspect and reconcile
When parts come back, three checks should happen before they move to the next operation:
- Quantity against the challan, including any parts the vendor has rejected or scrapped.
- Weight where material is processed by weight, with process loss within the agreed allowance.
- Quality — hardness, coating thickness, appearance or dimensions as specified — with the vendor's test certificate where applicable.
Short receipts and rejects should be recorded against the challan and the vendor immediately. They affect the order (which may now be short), the vendor's balance and the vendor's quality rating.
What the planner should see
For a factory where most orders include outside processes, the planning screen should answer, at a glance:
- Which jobs are at which vendor, since when, and when they are due back.
- Which jobs are waiting to go out, and in which batch.
- Which orders are at risk because a vendor step is late or a batch has not left.
- The load planned for each vendor over the next few weeks.
With this view, the daily planning meeting spends its time on decisions — which batch to send, which vendor to chase, which customer to warn — rather than on finding out where things are.
Choosing which vendor gets which job
Many factories have two or three vendors for the same process. Deciding where to send each batch is usually left to whoever arranges transport. A better decision uses the information you already have: each vendor's current load from you, their recent lead time, their rejection rate and their rate for the process. For urgent work, the vendor with the shortest and most consistent turnaround is worth paying a little more. For routine work, the cheapest vendor with acceptable quality may be right. Recording the decision with the reason — and reviewing results monthly — builds a fair basis for allocating work and for vendor conversations about rates and performance.
Transport and paperwork
Parts often wait not for the vendor but for transport. A tempo goes to the plating vendor twice a week; parts that miss it wait for the next trip. Including transport days in the planned lead time, and showing the next scheduled trip on the planning screen, makes this waiting visible. Delivery challans for job work, with the GST details that go with them, should be generated from the system when the batch is prepared, so the paperwork is ready when the vehicle arrives rather than holding it up. Our guide to job-work challans and balances covers the documents.
Material at the vendor
Parts and material at a job-work vendor remain your stock and your responsibility. The planner and stores should see, at any time, what is at each vendor — by part, quantity and weight — and how long it has been there. Material that has been at a vendor far longer than the usual lead time is either forgotten, held up by a problem, or has been used in someone else's job. A monthly review of old balances with each vendor catches these early. Process loss — the weight lost in pickling, plating or machining — should be compared with the agreed allowance, because unexplained losses at a vendor are a real cost.
Customers' view of outside processes
Some customers, especially OEMs, approve specific vendors for special processes such as heat treatment and plating, and require their certificates with each lot. The routing should record the approved vendors for each part, so work is not sent to an unapproved vendor in a rush, and the receipt step should check that the certificate is present before the parts are released to the next operation. Keeping certificates against the lot also supports traceability when a customer raises a quality concern months later.
Measuring improvement
Three simple measures show whether job-work planning is improving: the share of vendor batches returned by their planned date, the average days parts wait internally before a batch leaves, and the number of customer orders delayed by an outside process. Review them monthly with the planner and purchase. The first measures vendor reliability and the realism of planned lead times; the second measures your own batching and transport discipline; the third connects both to what customers feel.
Bringing a process in-house
Good job-work records also inform a bigger decision: whether to bring a process in-house. When you know the volume sent to vendors each month, the cost including transport and losses, the lead time it adds to every order and the rejections it causes, you can compare these with the cost of equipment, space, people and approvals needed to do it yourself. Many SMEs make this decision on instinct; a few months of records make it a calculation.
A worked example
A manufacturer of hydraulic fittings sends most parts for zinc plating and some for case hardening, through four vendors. Its plan used a three-day lead time for plating and five for hardening. On-time delivery was poor, and the planner spent much of each day on the phone.
Recording challans with dates for a few months showed the actual median plating lead time was nearer six days, rising to ten at month-end, and that parts often waited three or four days internally before a plating batch was sent. The factory changed three things: planned lead times were set from the history, a daily "due back" list replaced ad-hoc calls, and the planner reviewed pending plating batches each morning against due dates. Delivery promises became longer but reliable, and the number of late orders fell. The vendor with the most consistent turnaround received a larger share of urgent work.
Getting started
- Record every job-work challan with dispatch and receipt dates, quantities and weights.
- Add outside processes as operations in part routings.
- After a few months, set planning lead times from actual history.
- Introduce a daily due-back list and a view of pending vendor batches.
- Add receipt inspection and vendor rating.
Working with Corposol
Corposol builds custom production planning and job-work management software for Indian manufacturers, as part of our manufacturing software work. All custom code is transferred to you on final payment.
Frequently asked questions
Why do job-work vendors cause so many delays?
Because the time parts spend outside is usually not in the plan. Planners schedule internal operations carefully, then treat the vendor step as a fixed few days, when in reality vendor lead time varies with batch size, their workload and transport.
How should vendor lead times be set?
From history: the actual time between dispatch and receipt for each vendor and process, recorded on job-work challans. The median gives a realistic planning lead time, and the spread shows how much buffer is needed.
Should we batch parts for outside processes?
Often yes, because many processes such as heat treatment and plating run in loads. But batching adds waiting time, so the plan should balance load size against the delivery dates of the orders in the batch.
Can vendors update status directly?
Vendors can be given a simple screen to confirm receipt, expected completion and dispatch, where they are willing to use one. Many SMEs start with their own staff updating status after a call.
