Campaign handover

What this worksheet records

A campaign handover brings together already agreed records without pretending that their decisions are interchangeable. Identify the exact brief, specification and artwork versions, then name the legal provider responsible for the external work. Include the site allocation and any unresolved exception that affects production or delivery. An absent approval reference is an open gate, not a field to conceal. The recipient should be able to trace every instruction back to the record that established it.

Complete and review it

Build the handover only after checking that its referenced versions agree with the source records. A revised file or changed quantity should trigger a reviewed update rather than an overwrite of the old package. Separate production, installation and return responsibilities so one contractor is not silently made responsible for another's work. Ask the actual receiving party to confirm what package it received and any exclusions it still needs to resolve. Preserve both the manifest and that attributable response.

Field definitions

• handover_id: A stable identifier for this handover, 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.
• brief_revision: The exact brief revision used for this row; retain earlier versions and revisit affected decisions after a change.
• specification_revision: The exact specification revision used for this row; retain earlier versions and revisit affected decisions after a change.
• 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.
• chosen_provider_legal_entity: The actual party for chosen provider legal entity, with its responsibility or rights source identified; do not substitute the platform brand.
• quantity: The actual number required for this row’s site and variant; do not substitute a programme total.
• required_date: The actual required date, with date format or period meaning explicit; distinguish requested, planned, confirmed and observed values.
• approval_reference: The actual attributable source for approval reference; a reference is not evidence that a decision was authenticated or its content verified.
• packing_reference: The actual attributable source for packing reference; a reference is not evidence that a decision was authenticated or its content verified.
• installation_owner: The named person or agreed role responsible for installation owner; confirm its real scope rather than assuming authority from a typed name.
• return_owner: The named person or agreed role responsible for return owner; confirm its real scope rather than assuming authority from a typed name.
• open_exception: The specific unanswered open exception that needs an owned response before the relevant next gate can close.

Prepare a deliberate export

A full handover may contain private financial or review fields. Use a package limited to the chosen recipient's scope and retain the complete internal version separately. The blank manifest does not upload files, release production or accept a contract.

Take it to the next job

• Match every version in the handover to its source record.
• Name the responsible legal entity for each external package.
• Keep open exceptions and separate fulfilment gates visible.