Jewelry inventory for a family office
Travel pieces and vault pieces were on one vague schedule. This is an anonymized scenario, not a named client and not a return.
The gap in the file
Everyday pieces were worn and insured on a household rider. A vaulted suite had a specialist schedule. The family office had neither list in a form it could reconcile.
A request to move two pieces between households made the split visible. Serials were in a jeweler's email. The office file still described a complete set.
What we coordinated
Worn versus vaulted
Split the inventory into pieces that leave the house and pieces that do not, with locations that match.
Identifiers
Collected serials, prior appraisals, and photographs into one object list the office could keep.
One office file
Put the schedule, the vault log, and the worn list in the same packet so a later request does not start from three inboxes.
File status after the work
This table is a documentation checklist, not performance. No IRRs, no multiples, no fabricated results.
Why the file held
Two lists, one packet
Worn pieces and vaulted pieces are described separately. The office no longer treats a split suite as a single line.
Serials live with the object
Identifiers left the jeweler's inbox and sit next to the appraisals in the office file.
No custody
Jewelry stayed with the household and the vault. We coordinated the lists.
What this scenario is not
It is not a testimonial, a named client, or a claim about investment return. It is an example of jewelry lists that a family office could not reconcile.
.svg)
.svg)
