Game day and sponsorship

A stadium has no signal and a sponsor has a Monday deadline.

A dozen people spread across a concourse, a suite and a pitch-side activation. Every one of them is taking photos, and none of the photos are in the same place by the time somebody has to hand them over.

The night

The deadline is external, which changes everything.

When the photos were only for your own channels, late was survivable. A sponsorship deliverable is somebody else's contract. The content has to be handed over, in a usable size, on a date you agreed months ago — and it is currently spread across a dozen phones belonging to people who worked the game and went home.

Where it goes wrong

  1. Stadiums defeat live uploads.

    Sixty thousand people are on the same masts. Anything that has to upload at the moment of capture fails quietly, and the staff member has no idea it did not work.

  2. Nobody owns the collection.

    Everyone assumes somebody else is gathering it. On Monday it turns out the answer was nobody, and the chase starts.

  3. The sponsor needs it large.

    A compressed chat photo cannot go on a hoarding, in a programme, or on a partner's own channels. Full resolution is not a nice-to-have when the deliverable is contractual.

How it runs

  1. 01

    Before the gates

    One album for the fixture. Hand the join code to everyone working it, including the agency staff who are only there for this game.

  2. 02

    Through the match

    They send as they go. With no signal the app holds the files on the phone and sends them on the walk out, in the car, or back at the hotel.

  3. 03

    Monday morning

    One album, full resolution, with who shot what and when. Approve the ones that clear, tag them by activation, and export the set.

There was no signal at the venue so nothing uploaded.

Hand the sponsor the whole night, on time.

Related

What teams like this look at next