Short answer: a repair promise date should be calculated backwards from your real queue, your bench capacity and any outside vendor's schedule, with a buffer added, and then stated as a specific date rather than a vague duration. "About a week" is the worst possible answer — it cannot be met, cannot be missed, and guarantees the customer will ring you to find out.
Why the vague date is expensive
Every "is it ready yet?" call costs a few minutes of somebody walking to a bench. Across a busy week that is a meaningful share of skilled labour spent answering a question a date would have answered.
But the bigger cost is trust, and it runs in the direction most jewelers do not expect. JCK's reporting on efficient repair departments makes the practical recommendation directly: quote specific delivery dates, not "one week." A specific date is a commitment the customer can plan around. A duration is a hedge, and customers read hedges correctly.
This matters more in repair than almost anywhere else, because repair is where people hand over something irreplaceable. The trade's consistent framing — from both JCK and David Geller — is that repairs are trust-sensitive rather than price-sensitive. The date is part of the trust.
There is a commercial argument too. JCK reports that nine or ten out of ten customers buy when quoted a repair price, against three or four out of ten on a sales pitch. A repair conversation is the highest-converting thing at your counter. Ending it with a hedge is a poor return on that.
Build the date backwards
Most shops plan forward: we'll start it when we can, and it'll be done when it's done. Backward planning gives you a date and, more usefully, an early-warning signal.
Work back from the delivery date and every stage acquires its own internal deadline. This has to reach the setter by the 12th to hit the 20th. The moment the 12th passes with the piece still on the bench, you know — before the customer's date is at risk, while there is still something to do about it.
Four inputs decide the date:
Your current queue. Not your capacity in the abstract, but what is already on the board ahead of this job.
Productive bench hours, not clock hours. Geller's assumption is that in a typical eight-hour day, jewelers work on products for five and a half hours. Schedule against that or every date slips by a third.
Outside vendor schedules. If casting runs Tuesdays, work that needs casting must be ready Monday. Missing a run by an hour costs days, and nothing about the bench being busy or idle changes that.
Long-lead inputs. A stone that needs ordering has a lead time that sits in front of all your own work. Order it at approval, not when the piece reaches the stage that needs it.
Then add the buffer. Geller's rule is to add 25 percent to all estimated repair times. The buffer is not padding — it is the ordinary variance of a working shop, priced into the promise rather than absorbed by the customer.
Set gentle internal deadlines ahead of the promised date, so the buffer belongs to you rather than being consumed silently.
The outside bench is where dates die
A large share of missed repair dates happen after the piece leaves your building — at the caster, the setter, the engraver, the plating house. Out of sight, out of mind, and rediscovered when the customer asks.
Three habits close most of that gap:
Log what left, where it went, and when it is due back. A send-out is a tracked stage with its own promised return date, not an absence.
Confirm receipt. So nothing goes quietly missing in transit, and so the vendor's clock is agreed rather than assumed.
Attach the full spec to every send-out. So the vendor never has to call back with a question. Each question is a lost day, and usually more than one because of when it gets answered.
Flag anything past its promised return automatically, so it surfaces before the customer's date is at risk rather than after. The principle is that a job at somebody else's bench should still be on your board — the same discipline covered in more depth in reducing production delays.
Batching: useful, but decide it
Batching by step is genuinely efficient. JCK's reporting describes assembly-line batching — grouping work by operation rather than by job — as eliminating wasted time and maximising productivity without sacrificing quality. Setup is often the real cost of an operation; Sara Grinnell's observation about retipping is that the main cost you incur is setup, which is exactly the cost batching amortises.
The trade-off is that batching adds waiting time for any individual piece. A ring that could have been done Tuesday waits until Thursday's laser session.
So batch deliberately, around two things: setup-heavy operations where the amortisation is real, and vendor schedules where the batch is imposed on you anyway. Do not batch indiscriminately, and do not let a batch become a queue nobody is watching.
A daily pass, not a weekly panic
Turnaround is a habit before it is a system. A five-minute morning scan of every open job — what moved yesterday, what is stuck, what is due out to a vendor, what is due back — catches problems while they are still cheap.
Three questions per job are enough:
- What stage is it in?
- Who owns the next action?
- What is it waiting on, if anything?
An order goes silent when it is between stages, waiting on something, or parked with no owner. The daily pass exists to make silence impossible.
Tell the customer before they ask
The best status update is one the customer did not request. "Your ring's at the setter, still on track for the 20th" costs nothing, requires no investigation if the information is already on the record, and does more for the relationship than a fast turnaround nobody knew about.
It also eliminates the call. Most status calls are not impatience; they are the absence of information.
Where Jewelia fits
Promise dates hold when the board reflects reality without anyone maintaining it. Production & Repairs gives every repair a stage, an owner and a due date, with stages you define rather than someone else's list, and a barcoded tag printed at intake so the physical piece and the digital job stay connected. Any stage can go to an outside plater, setter or engraver and stays on your board with its own due date instead of disappearing — which is the failure mode this whole piece is organised around.
Clients are notified automatically when a job changes to the stages you choose, so the proactive update happens without anyone remembering it, and the status call it would have prevented never arrives. The Planner turns the daily pass into a list of what is due out and due back today rather than a discipline you have to sustain. And analytics reports turnaround and throughput by job type, which is how you find out whether your standard promise dates are honest — and which procedures are quietly setting you up to miss.
There is a page for this: Jewelia for repair and service businesses, from $179 a month.
Bottom line
Give a date, not a duration. Calculate it backwards from the queue, from five and a half productive hours, and from your vendors' schedules, then add 25 percent. Log every send-out with a promised return and flag the overdue ones. Batch around setup and vendor runs, not by default. Run a five-minute pass every morning. And tell the customer where their piece is before they have to ask you.
Frequently asked questions
- How long should a jewelry repair take?
- There is no published industry standard, and chasing one is the wrong exercise. What matters is that the date you give is derived from your actual queue, your bench capacity and any outside vendor's schedule — and that you hit it. A longer honest date beats a shorter optimistic one every time.
- Why is 'about a week' worse than a specific date?
- Because it cannot be missed and it cannot be met, so it generates status calls instead of confidence. JCK's reporting on efficient repair departments is explicit on this: quote specific delivery dates, not 'one week.' A specific date also gives your own board something to schedule against.
- How much buffer should I add?
- David Geller's rule is to add 25 percent to all estimated repair times. Estimates run optimistic consistently, and the buffer absorbs the ordinary variance — a stone that needs ordering, a rework, a vendor running a day late — without touching the customer's date.
- What is the biggest cause of a missed repair date?
- Work sent outside. A piece at a plater, setter or engraver leaves your building and usually leaves your attention with it, so a slip is discovered days later when it is already on the critical path. Logging a promised return date for every send-out, and flagging overdue ones, is the single highest-return habit.
- Does batching repairs help or hurt turnaround?
- Both, which is why it needs deciding rather than drifting. JCK reports assembly-line batching by step eliminating wasted time and maximising productivity without sacrificing quality. But batching adds waiting time for any individual piece, so batch around setup-heavy operations and vendor schedules, not indiscriminately.
- Do customers need to be told when a job changes stage?
- Not at every stage, but proactive updates convert. The trade's consistent finding is that repairs are trust-sensitive rather than price-sensitive, and an unprompted 'it's at the setter, still on track for the 20th' does more for the relationship than a same-day turnaround nobody was told about.
Stop reading, start clicking.
Open a live Jewelia company with real inventory, memo, jobs and reports already in it. One work email, no card, no sales call, nothing to install.




