What to Do When a Finished Job Comes Back

The job was delivered, the money was collected, the file was closed. Three days later the customer is at the door with the same job in hand: it did not work out. Everyone at the bench starts talking at once; whose measurement was wrong, what was said, will this be redone, what happens to the payment.

That conversation is usually run on memory. Yet a returned job neither teaches anything nor comes to an end unless it enters the workshop's own records; after a while the same scene can repeat with another customer.

The First Hour of a Returned Job

The promise made in the first hour can shape everything that follows. It is easy to say "we will look at it right away" while the customer is standing there; that sentence quietly reorders the other jobs on the bench. Looking at the job first and giving a time afterwards can be a steadier start.

What needs discussing here is not who was right, but where the job parted from the expectation. Earlier we looked at what happens when a customer asks for a change mid-job; a request arriving after delivery can come from the same place, from what was spoken but never written down.

Logging the Returned Job

A returned job may look like a continuation of the first one, but for tracking it is a separate job. When a new record is opened and tied to the number of the first job, how many times that job has come back can become visible on its own.

Three things in the record may be enough: why the job came back, who took it on and when it will be delivered. Without those three lines the job turns into a vague pile waiting at the edge of the bench under "someone should look at this". We used the same table in what gets missed when a job is left unfinished; it can hold for this waiting too.

Separating the Reason

A correction made without naming the reason can bring the same job back a second time. "Not happy with it" is not a reason, it is a result. Underneath it there may be size, material, an unclear request or use, and each one is settled somewhere else.

Once that separation is made, the list of returned jobs can turn into a workbook over time: which reason came up how many times, at which step things break.

Where the Cost Stays

Rework has a cost: material, labour hours and the other job that cannot be done in those hours. When these three are not added up, the correction can turn into an invisible expense filed under "we do it anyway".

Talking about the cost is one thing; recording it is the workshop's own knowledge. When the hours spent on rework are written down like the first job, the answer to why I quoted two different prices for the same job can also become clearer.

How Rework Enters the Queue

When a returned job goes on the bench, the order of the other jobs changes. Leaving that change unsaid can start a second delay.

The state of waiting jobs

If it can roughly be seen which job will be delayed by how many hours once the correction cuts in, the decision can be made with information. If it cannot, the queue can end up being set by whoever speaks loudest.

The date that was promised

The date given for a correction can be taken as seriously as the date given for the first job. Saying "ready by this evening" for a job that will not finish the same day can damage trust a second time.

Who will do it

Having the person who did the job take on the correction can help with learning; where the workload does not allow it, the record needs to be written down so that whoever corrects it can read the reason.

What Is Said to the Customer

The answer given to the customer may have three parts: what will be redone, when it will be ready and whether a cost arises. Said together, the conversation can be shorter.

Giving that answer from a single place matters as well. A customer who hears one date on the phone and another at the bench may think the job is not being tracked. We looked at this single-address question in before starting to track customer complaints too.

The Part Played by the Pre-Delivery Check

A short check before delivery can reduce the number of returned jobs. The check does not have to be a long list; a few lines suited to the type of job can be enough in most workshops.

The written form of those steps can sit in the same notebook as the preparation in getting ready to hand the job over to the customer.

If the Same Job Comes Back Twice

A job that comes back a second time may call for looking at the flow rather than the workmanship. Correcting the same job twice can suggest a gap in the way the order is taken or in the check before delivery.

In such cases stepping back may work better than carrying on with corrections: how was this job ordered, which question was not asked, who assumed what. The answers often sit not at the bench but in the first conversation.

Summary

A returned job can quietly wear down both the queue and the earnings for as long as it stays out of the records. Opening a new record, separating the reason as size, material, unclear request, use or workmanship, writing down the hours spent on the correction and giving the customer a single date can make this work visible. A few lines of checking before delivery can then reduce the chance of the same job turning back at the door.

Frequently Asked Questions