Reviewing a revised sapphire crystal sample well means treating it as a delta approval, not a fresh approval: you verify that the change you asked for was made, confirm nothing else moved, and document every deviation against the drawing before sign-off. The fastest way to do this without restarting your project is a four-gate review — geometry, edge condition, optical surface, and documented deviation — applied identically to every revision.
Why revised samples fail silently
The most expensive sample failure is not the one you reject. It is the one you approve because the visible problem was fixed, and a second problem — introduced by the correction itself — goes unnoticed until it appears in production quantities.
A disciplined reviewer therefore separates two questions:
- Was the requested change made correctly? This is the delta check.
- Is the revised sample still correct everywhere else? This is the regression check.
Skipping question two is what turns a one-week correction into a production problem. Skipping question one, meanwhile, wastes the supplier's correction cycle and signals to the factory that your feedback is unreliable — which quietly degrades the quality of every subsequent revision.
The Four-Gate Sample Review
Use four gates, in order. A sample that fails an early gate should be returned with documentation before you spend time on later gates — this respects both your inspection budget and the supplier's correction loop.
Gate 1 — Geometry. Compare the revised sample against the drawing and against the previous sample. Measure every dimension that appears in your change request, and at minimum spot-check the dimensions adjacent to it. If the correction required an edge profile change, confirm whether the stated tolerances on the drawing still apply to the new profile — and ask the supplier to confirm in writing which tolerance callouts were affected by the revision.
Gate 2 — Edge condition. Chipping, burrs and polish quality at the edge are the features most likely to change when a cutting or grinding method changes. Inspect the full circumference, not the representative arc. If the revision changed the edge treatment, request that the supplier identify in writing which edge zone was reworked.
Gate 3 — Optical surface. Coatings, if specified, and surface finish can be affected by handling during rework as much as by the correction itself. Review for coating uniformity across the full aperture and for handling marks introduced after the correction. If your drawing specifies coating requirements, confirm with the supplier that the coating process and its specification were unchanged between revisions — and treat any coating statement from the supplier as something to verify against your own spec, not assume.
Gate 4 — Documented deviation. Before approval or rejection, require a written response from the supplier that lists, for each point in your change request: what was changed, how it was verified, and any residual deviation from the drawing with its measured value. A sample approved without Gate 4 documentation is an approval you cannot defend internally when a later batch question arises.
Decision table: pass, reject, or request documentation
| Observation at review | Action | Rationale |
|---|---|---|
| Requested change verified; all other gates clean | Approve, with Gate 4 document filed | Delta and regression checks both closed |
| Requested change verified; new defect in an unrelated gate | Reject the revision, document the new defect separately from the original request | Prevents the correction history from becoming confused; the supplier needs to know a new issue exists, not just the old one |
| Requested change partially made; no new defects | Do not approve. Request written confirmation of what remains open and whether it can be closed in the same revision cycle | A partial fix approved under time pressure becomes a permanent drawing deviation |
| Requested change made; supplier reports a residual deviation within drawing tolerance | Approve only with the measured value and callout recorded in the file | You need the number on file before production, not after |
| Cannot verify a dimension in-house | Hold approval; request supplier measurement report for that dimension | Approval without measurement is opinion, not review |
Note that every row above assumes your drawing and tolerances are the arbiter. If a drawing callout is ambiguous — for instance a tolerance written in a way that can be read two ways — resolve the ambiguity in writing with the supplier before approving, not after.
Approval questions to put in writing
Send these with your next revision request. They cost nothing to ask and prevent the most common review disputes:
- "For each point in the change request, state what was changed and how it was measured."
- "List any drawing callouts affected by this revision, including tolerance values as measured on the revised sample."
- "Confirm whether the cutting, grinding or coating process changed between the previous revision and this one."
- "State any residual deviation from the drawing, with its measured value and the relevant callout."
- "Confirm the current sample, revision-fee, and shipping policy for this stage of the project, so both sides reference the same terms."
That last point matters. Sample policy — who covers what, and under what conditions a revision proceeds — is a commercial matter that varies by project and by supplier, and it can change. Do not carry assumptions from your first sample into the revision; confirm the current terms directly with JadeZone Sapphire for your specific project.
Pre-approval checklist
Run this before signing off any revised sapphire crystal sample:
- Change request document is versioned and dated; the revision references it by number.
- Every requested change measured against the drawing, results recorded.
- Adjacent and previously clean dimensions spot-checked (regression check).
- Full edge circumference inspected, not a representative arc.
- Optical surface and coating (if specified) checked across the full aperture.
- Supplier's written deviation report received and filed with the sample.
- Any residual deviation recorded with measured value and callout.
- Drawing ambiguities resolved in writing before approval.
- Current sample and revision terms confirmed directly with the supplier.
- Approval decision (approve / reject / hold) recorded with reviewer name and date.
A checklist that lives in one reviewer's head does not survive staff changes or a two-month gap between revisions. Put it in the project file.
Download the drawing checklist — a one-page version of the review script and pre-approval checklist, formatted for attachment to your revision correspondence.
FAQ
We approved revision two, and a problem appeared later. Can we still reference the original drawing? Yes — the drawing remains the arbiter regardless of what was approved, which is exactly why Gate 4 documentation matters. If the deviation report was filed, you can determine whether the issue was present at approval or introduced later. If it was not filed, the review record is weaker, and the practical next step is to request a supplier measurement report against the drawing for the affected callouts.
The revised sample looks right but we can't measure one tolerance in-house. Should we approve? Hold approval and request a supplier measurement report for that specific dimension. Approval without measurement is unverifiable later. If you approve on visual grounds alone, record that decision and its basis in the project file so the limitation is visible.
The correction introduced a new defect in a different area. Do we combine the two issues in one feedback document? Keep them separate. The original change request is one thread; the new defect is a second thread with its own documentation. Combining them makes it harder for the supplier's production side to see that a process change, not the original drawing, caused the new issue.
Do sample and revision terms carry over from the first sample? Treat them as open questions until confirmed. Sample fees, shipping responsibility and revision conditions are commercial terms set per project, and they can change between stages. Confirm the current policy directly with JadeZone Sapphire in writing before requesting the next revision.
How detailed should the deviation report be? Detailed enough that a reviewer who never saw the sample could understand what was measured, against which callout, and what value resulted. A report that says "corrected per request" without measurements does not close Gate 4.
When a revised sample arrives, the review you run in the first hours determines whether your project moves forward or quietly accrues risk. Structure beats instinct.
Download the drawing checklist and attach it to your next revision request — then confirm your project's current sample and revision terms directly with JadeZone Sapphire.
