Every outdoor event is really two events. There is the one the public sees, a field full of stages, stalls and bunting on a warm afternoon. Then there is the one that makes it possible, a three week operation of deliveries, cable runs, fencing, toilets and radio checks that starts long before the first ticket is scanned.
The second event lives on a map. Or it should.
Most production teams still run their site on a PDF site plan exported once in April and a group chat that scrolls faster than anyone can follow. The plan goes out of date the moment a supplier moves a generator. The chat holds the answer to where the medical tent went, buried under 200 messages about parking. By the time the crew arrives on site, half the team is working from a version that no longer matches the ground.
This guide is for the people who hold that second event together. Production managers and event producers. Site and operations managers. Health and safety leads, volunteer coordinators and the crew chiefs who walk the site at six in the morning checking that what was drawn in the office survived contact with reality.
The good news is that a shared, live map fixes most of the friction without adding a new system to learn. If your team already coordinates trips or routes on a map, this is the same habit pointed at a field. If you are moving off spreadsheets and static plans for the first time, the jump is smaller than you expect.
The producer who owns the site
You signed the licence. You hold the safety plan, the supplier list and the timeline that ties them together. What you need from a map is a single view that everyone defers to, so the answer to 'where does that go' is never in doubt. Drop a pin for every fixed point, the main stage, the welfare field, the contractor compound, the box office. Colour them by zone. Now the plan is not a drawing you email out, it is a place your whole team stands in together. When a supplier asks for their pitch location, you send them a precise pin rather than a paragraph of directions that ages badly.
The operations lead running build and breakdown
Your week is a sequence. Fencing before power, power before staging, staging before traders, traders before the public. A static plan cannot show that sequence. A live map can, because you can update it as the site changes hour by hour. Mark the heavy goods route and the crane lift zones. Flag the gates that open for deliveries and the ones that stay shut. When the ground crew can see the same map you do, you stop repeating yourself on the radio. The map carries the brief so you do not have to. Build runs to plan more often when the plan is somewhere everyone can reach, not folded in a hi-vis pocket.
The crew and volunteers working the day
On the day, nobody reads a 40 page operations manual. They glance at a phone between jobs. A volunteer pointed to the wrong gate wastes 20 minutes and arrives flustered. Share one map with the whole crew on their own phones and the questions drop away. Where is the water point, the nearest welfare tent, the lost property cabin. Tap, see, go. Because the map updates centrally, a change made in the production office at noon is on every volunteer's screen by the time they next look. No reprints. No 'which version is this'. Just the site as it actually stands, in the hand of the person who needs it.
Build the site plan in layers
A good event map is not one drawing. It is a stack of layers you can switch on and off, each answering a different question. Built this way, the same map serves the producer planning in March, the build crew in the rain three days out and the steward looking for a water point at the height of the show. It works whether you are running a 200 capacity village fete or a field the size of a small town. Start at the bottom and work up.
Start with the boundary and the zones
Draw the perimeter first. The fence line defines everything else, from where the public can go to where your licence applies. Inside it, block out the zones in broad strokes before any detail goes in. Arena, traders, camping, back of house, contractor compound, car parks. Give each zone a colour and a clear edge. Most disputes on site are really boundary disputes, a trader who has crept into a fire lane or a camper who has pitched in a vehicle route. When the zones are mapped and shared, the boundary argues for you.
Add the infrastructure everything depends on
Next come the fixed services. Power distribution and cable runs. Water points and waste. Generators, fuel stores, lighting towers. Welfare and medical. Toilets, because the walk from the far camping field to the nearest block decides how happy 3,000 people are at two in the morning. Pin each one precisely. A generator marked 'somewhere near the bar' is not marked at all. This layer is the one your safety officer and your suppliers will lean on hardest, so it pays to get the positions exact rather than approximate.
Draw the routes, not just the points
This is the layer most static plans miss. An event is movement before it is anything else. Map the heavy goods route from the main road to the build area. Mark the emergency vehicle access that must stay clear at all times. Show the public flow from the car parks to the gates to the arena, then where it doubles back at the end of the night. Trace the litter pick route and the cash collection route. A point tells someone where a thing is. A route tells them how to move through the site without crossing a path they should not. On a busy site that distinction prevents real harm.
Mark the public-facing points last
Once the operational spine is in place, add what the audience needs. Information points, bars, food courts, cash machines, charging lockers, accessible viewing platforms, the lost property cabin. These are the pins you might later share in a public version of the map, the same way a festival-goer reads a map to find their way around. Keep them in their own layer so you can show the crew everything and show the public only what helps them. One base, two audiences.
Map the three phases of an event, not just the show
The single biggest shift from a static plan to a live map is time. A drawing shows one moment. A site runs through three. Each needs its own view.
Build
Build week is the most dangerous and the least photographed part of any event. Plant moving on soft ground, part-built structures, trip hazards everywhere, a crew who may never have worked this site before. Your map during build should show the order of works and the live position of each contractor. As fencing goes up, mark it done. As power is tested, flag it live. The build map is a checklist you can see from above. It tells a latecomer exactly where the job has got to without a five minute phone call.
Show
When the gates open, the map changes job. It stops being a build tracker and becomes an operations view. Stewards report a blocked exit, you mark it and reroute the flow. A bar runs dry, you pin the resupply. The show-day map is about response time, which is the difference between a near miss and an incident. The faster the right person sees the right pin, the smaller the problem stays.
Breakdown
Breakdown is build in reverse, with a tired crew and a deadline to hand the site back. The map earns its keep here too. What has been struck, what is still standing, which contractor is collecting what and when. A clear breakdown map is also the start of next year's plan, because the notes you make while it is fresh are the ones you will thank yourself for in 12 months. Save the map, duplicate it for next year, then you have a head start on the next edition.
The things crews forget to map
Experience shows up as the small pins nobody thought to add the first time. A short list worth stealing.
- Comms blackspots. The corners of the site where radios and phones fail. Mark them, because that is where a runner still beats a radio.
- The mud plan. British summers being what they are, know in advance which routes turn to soup after rain and where the trackway or wood chip goes first.
- Accessibility. Step-free routes, the accessible viewing platform, the blue badge parking, the nearest accessible toilet to each zone. Map it as carefully as the power.
- The quiet hours. Where the night crew shelter, where the 24 hour welfare point sits, where a lone worker can be found if they stop answering.
- Contractor parking. The unglamorous pin that stops a 40 tonne truck blocking your only emergency route at the worst possible moment.
Where Pin Drop fits
Pin Drop has been a home for collaborative maps since 2011. The same shared map a family uses to plan a trip is the one a production team uses to run a field. The product is built around three ideas that matter on an event site.
Zero training to get started. Nobody on a build crew has time to learn software in the car park. Dropping a pin and sharing a map works the way you would expect on the first try, which matters when half your team are seasonal crew or volunteers.
Your map follows you across devices. Plan on a laptop in the office, check it on a phone in a muddy field, hand it to a steward on their own handset. The same map, current everywhere, with no reprint and no version confusion.
Private by default. An event site plan is sensitive. It shows your medical points, your cash routes, your security positions. Pin Drop maps stay private unless you choose to share them, so the operational version stays with the crew while a cut-down version can go to the public. If you want to understand how that boundary works, our guide to private maps walks through it.
This is not only a festival concern. If your work is weddings and private events rather than public festivals, the same layered map keeps a marquee build, a supplier convoy and a guest arrival from colliding on one farm track. The canvas is smaller. The logic is identical.
A three week countdown
If you are starting from a blank map, this is a sensible order of work.
- Three weeks out. Draw the boundary and the zones. Share the map with your core team so the plan is collaborative from day one.
- Two weeks out. Add infrastructure and routes. Send each supplier their exact pitch as a pin rather than a description.
- One week out. Layer in the public-facing points and the accessibility detail. Walk the map against the real site if you can.
- Build week. Switch the map into tracking mode. Mark each element done as it lands.
- Show days. Run operations from the map. Every steward on the same version.
- Breakdown. Track the strike, then save and duplicate the map for next year.
Summer is short and the events calendar is unforgiving. The teams who run a calm site are rarely the ones with the biggest budget. They are the ones whose left hand knows what the right hand is doing, usually because both are looking at the same map. If you are planning holiday cover for your wider field team across the season, the same shared-map habit carries straight over.
You can start a map for your next event in a couple of minutes at pindrop.it. Build it once, share it with the crew, then let the site run a little more smoothly than last year.
Further reading. For the attendee's side of the same field, see our festival season mapping guide. For the wider shift from static documents to live maps in field operations, read from spreadsheets to maps.
