Custom Coin Proof Approval Checklist: What to Review Before Production

Use the proof to settle the brief

Keep the latest brief, reference art, and wording list beside the proof. Compare the central motif, supporting elements, names, dates, symbols, inscriptions, and intended front and back roles one item at a time. The question is whether the design matches the agreed direction, not whether the rendering still feels exciting.

Formal coin programs use structured review. The U.S. Mint describes reviewing candidate designs for coinability, accuracy, and appropriateness, while The Royal Mint places design approval before production. A private project has its own scope, but the practical lesson is the same: do more than take a quick visual impression (U.S. Mint; The Royal Mint).

• Confirm the version, date, and file name.
• Compare with the agreed brief or supplied artwork, not recollection.
• Identify the front and back roles.
• Mark every question on one copy.

Check text, symbols, and layout before judging style

Read every character as a final inscription

Copy errors hide inside illustrations. Read the text aloud, then compare it with a source list. Check capitalisation, punctuation, accents, numerals, spacing, and whether each name or date belongs on the intended side. Compare an exact emblem with its approved reference rather than accepting a close-looking version.

Follow the design around the boundary

Check clearance between lettering and a rim or border, the relationship between art and text, and the balance of open space. If the proof depicts an edge or orientation detail, confirm it is shown where expected. Ask about an unstated feature instead of filling in the blank yourself.

If terminology is causing confusion, the minting guides offer context on coin anatomy and relief. Use them to ask better questions, not to infer an unstated specification.

• Compare names, dates, numbers, symbols, and punctuation with the source list.
• Inspect both sides at normal size and close zoom.
• Check that motifs do not crowd lettering or borders.
• Confirm shown directional or edge detail.

Look past the artwork thumbnail

A polished screen image can hide legibility issues. Review the largest motif first, then the smallest. Fine lines, texture, narrow negative space, and small lettering should all have a clear job. The primary subject should read first without secondary details becoming noise.

Review relief and contrast as instructions

When a proof uses shading, highlights, color, or simulated texture, identify what communicates intended depth. The U.S. Mint distinguishes an initial line drawing from a later three-dimensional model, showing why a flat rendering and physical relief are not the same thing (U.S. Mint, Artistic Sculpting Process). Ask how foreground and background areas should relate, and flag thin or crowded details. Do not treat a screen effect as a promise of a physical result.

Reduce the proof on screen or print it smaller. If the message, focal point, or text disappears, note it while the design remains open to discussion.

• Identify the focal point before secondary detail.
• Flag extremely fine lines, tight gaps, or decorative shading.
• Ask which visual cues represent relief and which are rendering aids.
• View the art at a smaller size to test hierarchy and text legibility.

Confirm what approval means and record the decision

Before you reply “approved,” identify the proof version, attached notes, and aspects being approved. For changes, put every correction in one place and request a revised proof instead of relying on a mixed email thread. One annotated file and a short decision prevent an old image or stray comment becoming the working reference.

Resolve nonvisual questions too: what remains open, whether the proof is illustrative or specification-based, and what approval authorizes under the written terms. For rights, ownership, or reuse questions, a design checklist is not legal advice. Review the project FAQ and seek appropriate guidance if permissions are unclear.

A concise note can read: “Approved: Proof [version/date], subject to the marked correction to [item]. All other shown wording and layout are approved.” If something remains uncertain, do not give an unqualified approval.

• Name the exact version being approved.
• Keep changes in one marked-up file or list.
• Ask what remains subject to confirmation.
• Save the proof, source wording, feedback, and response together.

Run a final two-minute pass

On the final pass, set the proof aside for a minute, then return with the source wording and brief. Review the version identifier, text, side assignment, focal design, and small details. Ask: “Could someone outside the original discussion understand exactly what I approved?”

The proof need not answer every future question, but it should leave no ambiguity about the visible design you intend to authorize.

• Version identified
• Text and symbols checked
• Both sides and layout reviewed
• Open questions resolved or clearly held back
• Decision recorded in writing