Version six of the halo ring
The customer wants a halo engagement ring with a slightly thinner band and a hidden diamond on the side of the gallery. Your CAD designer sends the first render. You forward it by WhatsApp. The customer's partner is not supposed to see it, so the customer replies at odd hours with screenshots, arrows and questions.
By version four, the customer is comparing it with version two, which she preferred for the claws. By version six, you are fairly sure you know what she wants. You send the file to the caster. When the casting comes back, she says the band looks wider than she approved.
Maybe it is. You scroll back through three weeks of messages, trying to work out which image she actually said yes to.
Why render approvals get muddled
Renders move through at least three channels: designer to jeweller, jeweller to customer, customer back to jeweller. Each forward loses the file name and version number, so 'the one from Tuesday' is the closest thing to a reference.
Customers comment on images, not specifications. A render cannot show band width in millimetres unless someone puts it there, so the customer approves a picture and the jeweller casts a specification, and the two may not match.
And the approval itself is informal. 'Love it!' in a chat is enthusiasm, not sign-off. Nobody asked the customer to confirm the final details: metal, finger size, stone sizes and band width.
The cost of an unclear sign-off
| Problem | What it causes |
|---|---|
| Unnumbered renders | Casting from the wrong version |
| Comments on old versions | Designer changes that undo earlier decisions |
| No specification alongside the image | A casting that matches the picture but not the expectation |
| Informal approval | No clear record if the customer disputes the result |
| Chat threads on staff phones | Design history lost when someone leaves |
A recast means metal, casting fees and time, and it usually happens close to the date the customer needs the piece. Your own terms decide who pays when the result differs from what was agreed. That is only possible to work out if you know what was agreed.
Proposal commissions add a layer of their own. The buyer is often a partner working in secret, relaying the design to a friend or sister who knows the finger size and taste, and forwarding your renders on to them. By the time the approval comes back, it may have passed through three phones. If the only record is a screenshot of a screenshot, nobody can say with certainty which version the approval referred to, and the ring is being made for a moment that cannot be moved.
How we build a proper approval step
- Each commission gets a design record. When your CAD designer sends a render, it is uploaded there as a numbered version, with the key specification alongside: metal, finger size, band width, stone sizes and settings.
- The customer receives a private link, not an image, showing the latest version with its specification. Earlier versions stay visible but clearly marked as superseded.
- The customer can leave comments pinned to the version they are looking at, and your designer sees them in the same place.
- When the customer is happy, they press an approve button that confirms the version and specification. The approval is recorded with the date.
- Only the approved version is marked for casting, and the file sent to the caster is taken from that record.
- Discreet mode keeps notifications and the link subject line neutral, for proposals where a partner shares the device or inbox.
The design files themselves stay in your CAD software. We store the exports (renders, and optionally the specification sheet) and link them to the commission.
After the change
Customers still ask for changes, and that is part of the pleasure of bespoke work. But every change is against a numbered version, and when the ring comes back from casting you can open the approval and look at exactly what was signed off together.
- Every render numbered, dated and kept
- Customer comments attached to the version they refer to
- A formal sign-off with the specification spelled out
- Castings made from the approved version only
Signs your design approvals need this
- Renders go to customers as images in chat apps.
- You have cast from a version the customer later disputed.
- Customers sometimes comment on an old render.
- Band widths and stone sizes are not written next to the render.
- Design history lives on one person's phone.