Map the requirement by region and site
Record quantities, variants, dimensions, installation windows and delivery constraints for each location. Regions can be useful planning groups, but a geographic label does not establish identical requirements or provider coverage. Include sites with unusual access or different formats as explicit rows. Keep actual deadlines and requested dates separate. The programme should show what needs to arrive where before proposing how production will be allocated.
Ask providers for scoped answers
Invite only providers deliberately selected by the buyer and give them the relevant current package. Ask about exact process, construction, capacity, lead time, legal delivering entity and responsibility for transport or subcontracting. A broad advertised service area is not acceptance of this campaign. Compare responses against the same scope and record exclusions. Private financial proposals belong to authorised records, not a public regional supplier ranking.
Coordinate common specifications
If several production locations are proposed, identify which artwork, material and appearance requirements remain common. Record site-specific substitutions and technical acceptance separately. Establish useful inspection and packing references so outputs can be reconciled at destination. A shared template supports coordination but does not guarantee identical equipment, results or availability. Ask providers to accept the actual handover sequence and keep variations attributable to the relevant sites.
Worked example — fictional
A fictional programme has northern and southern delivery groups. One selected provider can produce the shared poster formats, while another can supply a specialist fixture insert for a subset of sites. The buyer records the actual scope split and legal contractor for each group. A remote branch has restricted receiving hours, so the transport plan is reviewed separately. The programme does not assume that the geographically nearest provider is available or that distance alone establishes lower environmental impact. Accepted quantities and delivery responsibilities remain traceable by site.
Common pitfalls
Assigning work by postcode alone can overlook process limits or access constraints. A provider’s capacity statement can change and needs current confirmation. Different packing conventions can make identical-looking outputs hard to allocate. Avoid claiming guaranteed national fulfilment or carbon savings from a map. A programme’s completion percentage should come from actual delivery and acceptance records, not the planned regional allocation.
Export a controlled allocation plan
Use the transport and site tools to state proposed groups, quantities, provider scope and open conditions. Ask the buyer to accept the actual allocation, then issue each provider’s minimum necessary package. Reconcile dispatch, receipt and discrepancies by reference. Preserve observed constraints for the next campaign while requiring renewed capacity, technical and date confirmations instead of treating the previous regional plan as a permanent network guarantee.
Decision checkpoint
Ask who remains accountable for a site when production and transport use different organisations. Record the accepted responsibility instead of leaving the branch to resolve a missing kit between providers. Legal scope and operational contacts should remain understandable in the final handover.
Take this to the next job
- Map actual site requirements
- Request provider-specific capacity and scope
- Maintain common specification references
- Accept allocation and responsibilities
- Reconcile actual regional outcomes
