Skip to content

Resource · approval

Keep a clear record of the proof decision.

Identify the version, capture the requested changes and record what has actually been approved before production release.

Spectra guide · Source review: 3 November 2026

Use the working documents

Start blank, or inspect the clearly labelled fictional example.

Download editable CSVOpen printable A4 sheetOpen fictional completed exampleDownload fictional example CSV

At a glance

The operational control is simple: identify the current version, who made the decision, what they approved and whether production is actually released. Treat any material change as a new review event.

01 / Issue

Give every proof a stable identity.

Show job reference, version, issue date, included items and any dimensions, materials or finishes the reader is being asked to review. Keep open technical or commercial questions visible.

02 / Decide

Capture more than an ‘approved’ email.

Record approve, approve with condition, revise, reject or hold; name the decision-maker; retain their comments; and state the scope. Approval of visual content should not be misread as structural, electrical, planning or brand-rights approval.

On the blank approval record, a new issued version supersedes the previous one even when the comment looks small. If the decision is conditional, write the condition in decision_scope and leave production_release_condition open until that condition is met.

03 / Release

Link the decision to production deliberately.

Only the current approved reference should reach the workshop. Record who released it and which other conditions—commercial, technical, material or access—still control the start of work.

Bring the job. Explore the next step.

Discuss your workflow