Ready for collection.
Still in your care.

Start with the property, not a selling price.

A customer leaving a ring for work creates a different responsibility from a shop buying that ring. The repair desk uses a separate customer-owned record. It does not add an available-stock item, create an asking price, place the piece in a buying estimate or include it in the available-at-start stock count.

Choose an existing customer at the current location explicitly. The picker shows names, with a bounded search; it does not assume the first customer is the right person. Describe one piece, record its observed condition and state the work requested. Keep unfamiliar marks unknown instead of guessing the alloy or brand from the request.

Accessories deserve their own answer. Unknown means you have not established what accompanied the piece. None means you recorded that nothing accompanied it. Listed means you state the box, pouch or other accessories received. Those are different records, especially when another employee handles collection.

A target date is optional and entered deliberately as a calendar date. An empty date stays unknown. Recording a requested date does not schedule a bench, send a reminder or guarantee that the work will be finished by then.

One ring, one requested resize, several useful questions.

Consider a hypothetical customer who leaves a yellow-metal ring to ask about resizing. The intake description notes a plain band with a single pale stone. The condition records visible scratches and a stone the customer says feels loose. The markings field remains unknown because the operator cannot read the stamp reliably.

The requested work is recorded in the customer's terms: assess a resize and check the setting. A small pouch is listed as an accessory. The operator does not turn the yellow color into a gold-purity finding, the pale stone into a diamond identification or the requested work into contractual authorization.

When work starts, a new event records the change and its note. When the shop records the piece ready, the job stays distinct from a completed return. An item can be waiting in a collection tray even after the bench work is done. A later manager records who received it and checks the handover explicitly.

Use this example in a walkthrough with the details that matter at your counter: a difficult hallmark, an accessory left behind, a target date that is unknown and a customer who chooses not to proceed. The useful test is whether the record preserves each distinction without promoting the customer's property into resale stock.

Four stages, with a separate unrepaired return.

Owners, administrators and managers can record the terminal handover. Staff can intake and record work or readiness; authorized readers can inspect the record. The return is not an independent approval: the same manager may have handled an earlier stage.

Returned unrepaired is available from received or in progress. It keeps the return visible instead of cancelling a row and making the custody obligation disappear. A ready job cannot silently jump backward, and this slice has no reopen or editable-history shortcut.

Keep an interruption from becoming a second job.

A failed connection does not tell the operator whether intake or a handover was recorded. The mounted repair page keeps the original request together and checks for its original receipt before offering an identical retry. Changing the selected job or typing the next note does not replace that unresolved request.

A confirmed receipt describes that accepted event. It is not a refreshed view of the job. Refresh the selected job explicitly before reviewing another stage. If another employee has already advanced it, the old reviewed head cannot silently overwrite the newer event; the operator keeps their note and reviews the current state.

After a known outcome, an explicit separate-request control allows another deliberate request, including another intake with similar details. Pending or uncertain requests cannot be discarded that way. This recovery is held by the open page; navigating away does not preserve an unsent working draft or its recovery controller.

Operational exceptions still need human handling. A disputed collection, changed work instructions or a piece sent to an outside bench is not resolved by inventing a transition. Offsite custody, corrections and extended repair scheduling remain later work.

Original events explain the current stage.

The desk shows the most recent twenty jobs for the location and an explicit limit when older jobs are outside that list. A direct authorized job link can reopen an older record. Each supported lifecycle has at most four events, so its full recorded stage history is shown without a hidden older-events page.

Read the original customer-name and property statements alongside each event's recorded operator and time. They are recorded facts and claims, not a verified ownership finding. A customer record edited later is not a reason to rewrite an earlier intake statement.

The first slice records text evidence only. It does not attach repair photographs or PDFs, generate a signed acceptance document, send a ready message, collect a deposit or create parts-and-labor charges. Existing inventory inspections and private photos remain separate; an inventory-photo record is not silently borrowed for a customer repair.

Evaluate the handover before calling it a complete repair system.

Bring a representative resize request and an unrepaired return. Have a staff member enter the piece, then ask a manager to record the recipient. Repeat a command after an interrupted response, let a second employee advance the job and confirm that the original note and unresolved request survive.

Check your requirements for authorization, liability, customer communication, bench scheduling, invoicing, tax, payments and retention separately. Those workflows are not supplied by this bounded custody desk. It records operational stages without claiming full repair-service or Bravo feature parity.

For a piece the shop owns, use the inspection and evidence record. For an intact resale decision, use the manual resale worksheet. For the exact current boundaries, read availability and roadmap.

Register a first-time customer without losing the repair draft.

A first-time resize customer may not yet appear in the repair picker. Open the customer directory in a separate tab, search by name and inspect any possible match before registering another person. The directory uses bounded fifty-row live pages and an explicit selected-record view; it does not load the entire customer book into every screen.

Registration preserves its original submitted facts and recovery request. If the response is interrupted, check that original request before trying to create another record. Matching names require a deliberate separate-person choice; the software does not silently merge customers or verify their identity.

After checking the selected current customer, an explicit repair link can carry that chosen customer into the repair desk. Otherwise return to the open repair draft and search the newly recorded name. Neither operation sends a customer message, changes an existing repair event or treats a registration receipt as a refreshed customer record. Keep ready and returned separate even when the person collecting differs from the customer who left the ring.