Duplicate Jobs, Stopped Before They're Raised

Duplicate jobs almost never arrive looking like duplicates.

• The same work order lands once in the shared inbox and once forwarded by a site manager being helpful
• A client raises an order, hears nothing for a week, and chases. The chase is formatted exactly like a fresh instruction
• A portal fires an update that reads like a new job. Someone raises a job manually because a client rang, while the emailed version sits eleven emails down the inbox.

None of that is carelessness. It is what happens when work arrives through five channels into one inbox, and the person opening it has sixty other emails behind it. The check that would catch every one of these takes about fifteen seconds. Search the system for the client's reference before creating anything. It is exactly the kind of check that loses to volume, every time.

By the time anyone notices, the second job usually has a date on it. Often it has been attended. Costs sit on two records, the client is looking at two lines on an invoice they expected one of, and someone has to reconstruct the week and raise a credit.

Worth doing this arithmetic on your own numbers rather than taking anyone's word for it.

Take the fully loaded cost of putting an engineer in front of a customer. Wage, vehicle, fuel, and the slot in the diary that could not be sold to anyone else. For most trades that lands somewhere between £80 and £200 for a routine attendance. Then add the office time to spot the duplicate, work out which record is real, void one and raise the credit note. Rarely less than half an hour, and often more once two people have touched it.

Multiply by however many duplicates you think you get in a month. Most businesses guess low, because the ones you remember are the ones that reached an invoice. The ones caught quietly at scheduling never make it into anyone's mental tally.

Then there is the part that does not price neatly. A client who receives an invoice for two attendances when they raised one order starts checking your other invoices. That costs more than the visit did.

When an instruction arrives, Build Concierge:

Step 1:

Reads the client's own reference off it - The work order number, the purchase order, the ticket or job reference, wherever it sits in the email body or the attached document, in whatever format that client uses.

Step 2:

Searches your job management system for that reference before creating anything.

Step 3:

Creates the job as normal when there is no match. Nothing slows down.

Step 4:

Stops when there is a match. No second job is raised.

Step 5:

Tells the office instead, naming the reference and pointing at the job that already exists, so one person looks once and moves on.

• One job per work order, on every client, without anyone having to remember.
• Engineers never dispatched twice to the same address for the same fault.
• No invoice showing two attendances for work your client ordered once.
• An alert in seconds rather than a discovery a fortnight later at billing.
• A quiet by-product: a record of which clients duplicate most, which is a useful conversation to have with them.

Match on the client's reference

The default, and the right starting point. Works with work order numbers, PO numbers and portal ticket references, whatever your client puts on their instruction.

Match on more than one field

Where a client recycles references across sites, the check can match on reference plus site or postcode, so genuinely separate jobs still get created.

Tell the office, or tell the sender

A blocked duplicate can alert your team internally, or reply straight to whoever sent it confirming the job is already in hand. That stops the next chase before it happens.

Different rules per client

One client's references are immaculate. Another's are a free text field. The check can be tighter or looser per contract without you running five separate processes.

• A job management system Build Concierge can search.
• Instructions carrying a client reference somewhere consistent. It does not have to be in the same place for every client, but it does have to be there.
• A decision on who hears about a blocked duplicate.

We look at how work actually arrives

A short call, plus a handful of real instructions from your busiest clients, so we can see where the reference sits in each format.

We build the check

Usually one per client route. Read the reference, search, branch to an alert when it finds a match.

We run it alongside you first

For the first few days it reports what it would have blocked rather than blocking anything, so you can see what it catches before you rely on it.