Artwork approval record

What this worksheet records

An artwork approval record should answer who decided what about which exact version. Include the campaign and site when local variants differ. State the approval class and scope rather than using a broad tick that could be read as technical, financial and commercial approval at once. Record any conditions alongside the decision. The reviewer name is not sufficient proof of authority: retain the applicable delegation or authenticated decision reference from the agreed process.

Complete and review it

Keep approval, rejection and requested changes as distinct outcomes. A new file version should receive the reviews affected by its changes rather than inheriting every historical decision. Preserve the previous decision even when it no longer releases the current work. Where several reviewers disagree, use the defined scope and decision owner to resolve the conflict. This editable record can organise manual evidence, but an actual production release must use the commissioned engine or another agreed process that establishes identity and authority.

Field definitions

• decision_id: A stable identifier for this decision, used to connect related rows without merging unrelated records.
• campaign_id: A stable identifier for this campaign, used to connect related rows without merging unrelated records.
• site_id: A stable identifier for this site, used to connect related rows without merging unrelated records.
• artwork_version: The exact artwork version used for this row; retain earlier versions and revisit affected decisions after a change.
• sha256: The byte fingerprint of the exact file when available; it identifies bytes and performs no production approval.
• approval_class: The specific decision class, such as content, visual, technical, financial or provider acceptance.
• reviewer: The named person or agreed role responsible for reviewer; confirm its real scope rather than assuming authority from a typed name.
• authority_reference: The attributable grant or delegation supporting the stated decision authority; the worksheet does not authenticate it.
• decision: The actual decision relevant to this row’s declared purpose. Record the source or unresolved question where it is not confirmed.
• decision_date: The actual decision date, with date format or period meaning explicit; distinguish requested, planned, confirmed and observed values.
• scope: The actual boundary of scope for this row; name inclusions and exclusions instead of implying unlimited applicability or access.
• conditions: The actual conditions relevant to this row’s declared purpose. Record the source or unresolved question where it is not confirmed.
• comment: The actual comment relevant to this row’s declared purpose. Record the source or unresolved question where it is not confirmed.
• authenticated_record_reference: A reference to the actual agreed system or process establishing the decision; this CSV creates no authentication.

Prepare a deliberate export

Decision records may contain personal details and protected artwork references. Share only the relevant authorised review scope. Editing a CSV row does not authenticate a reviewer, grant access, place an order or release production.

Take it to the next job

• Record one approval class for one exact version and site.
• Preserve conditions, rejected decisions and historical approvals.
• Verify authority through the agreed attributable process.