The arrow points the other way
On a tour, the artist's team chases the venue for answers. At a festival, you are the venue, thirty times over. The festival advance team sends each act a packet, sets the deadlines, and collects what comes back. The craft is the same as advancing a single show. The difference is direction and scale: one production office holding the full picture while every act only cares about its own forty minutes.
The core problem
A festival advance fails differently than a tour advance. A tour misses one detail at one venue. A festival misses the same detail thirty times, and finds out on the same day. Consistency across acts matters more than perfection on any single one.
The artist advance packet
Every act gets the same packet, and the packet answers the questions before they get asked. The standard contents:
- Set time, set length, and stage assignment. The one thing every artist opens the email for. Include changeover length and whether the schedule has any slack.
- Stage and production specs. PA, consoles, monitor world, lighting rig, video, riser inventory, and power available at each stage.
- The shared backline list. What the festival provides per stage, and the rules for using it. This list prevents more day-of arguments than any other document you send.
- Load-in logistics. Site map, vehicle passes, dock or ramp locations, push distances, parking for buses and trailers, and shuttle plans where parking is remote.
- Credential and guest list procedure. How many passes each act gets, what each type grants, how names get submitted, and the hard cutoff.
- Hospitality options. What catering exists, meal times, buyout policy, and what the dressing room or trailer situation actually is.
- Settlement requirements. W-9 or local equivalent, wire details, insurance certificates if required, and who to see, where, and when to get paid.
- Your deadlines. One date for tech materials, one for guest lists, one for arrival details. Put them in the first email and repeat them in every follow-up.
What to collect from every act
The return side of the packet. For each act, you need the same set, which is exactly why a consistent structure beats a pile of reply-all threads:
- Tech rider, stage plot, and input list, current for this show, not the arena version of a band playing your side stage.
- Backline elections. What they will use from the house list, what they carry, what they refuse to share.
- Arrival details. Vehicle count and types, arrival time, driver contacts, and who is advancing day-of for the act.
- Personnel and credentials. Names for working passes, plus the guest list against their allotment.
- Hospitality needs, reconciled against what you offered, with dietary restrictions confirmed in writing.
- Payment paperwork, complete before the gates open. Chasing a W-9 at settlement is a self-inflicted wound.
The timeline
Scale changes the math: everything needs to start earlier and close earlier, because the last week belongs to the stragglers.
Changeovers and shared backline
The changeover is where festival advancing earns its keep. Fifteen to thirty minutes to strike one act and set the next, on repeat, all day, per stage. Three rules keep it survivable:
- Advance the changeover, not just the set. Every act should know what is striking behind them and setting in front of them. Share the stage's running order with every act on that stage.
- Default to shared, negotiate the exceptions. Publish the house kit per stage and make sharing the default position. Acts that refuse get flagged in the advance, and the changeover plan absorbs it deliberately.
- Rolling risers are the cheat code. Anything that can be preset on wheels off stage buys minutes you cannot buy any other way. Advance which acts get riser space, because everyone will want it.
Keeping forty advances straight
The hardest part of festival advancing is not any single advance. It is state: which acts have responded, which are missing tech, which have guest lists in, which have conflicts still open. An inbox cannot answer those questions; a status board can. Whatever system you use, it needs three properties: every act's advance has the same structure, every advance shows its status at a glance, and the artist's side can contribute without emailing attachments into the void.
This is the exact shape Advance with Me was built for. Your packet becomes a reusable template, every act on the bill gets its own structured advance from it, artist reps fill in their sections through scoped invite links, and AI intake maps the riders and tech packs they send into the structure for your review. Guest allotments, cutoffs, and approvals run per act, requests carry the name of whoever asked, and your stage crews see their day on the web or in the AWM Go iPhone app, which keeps working when the site's network does not. Our festivals page covers the full picture.
If you are the artist being advanced
Reading this from the other side of the table? Your job in a festival advance is to be the act the production office does not have to chase:
- Respond by the deadlines, even if the answer is partial. "Rider attached, arrival details to follow by Friday" beats silence.
- Send festival-real documents. A festival plot for a 40-minute set on shared backline, not your headline production dreams.
- Flag your non-negotiables early. The advance team can solve almost anything at six weeks and almost nothing at six hours.
- Get your guest list in before the cutoff. Festival cutoffs are real: the list feeds credential printing and gate systems, not a clipboard at will call.
Frequently asked questions
Who advances a festival, the festival or the artist?
The festival drives: its advance team sends the packet, sets the deadlines, and collects each act's materials. The artist's tour manager responds. On a tour those roles reverse, which is why TMs who work both sides make the best festival advance staff.
How far out should artist advancing start?
Eight to ten weeks for the bill, earlier for headliners and heavy production. Deadlines around four weeks out for materials, locked schedule and backline by two weeks, final week reserved for the chase.
How do you handle acts that never respond?
Escalate through channels: the advance contact, then the tour manager, then the agent who booked them, who has the strongest leverage. In parallel, advance defensively: assume house backline, standard inputs, and no special requirements, and write that assumption into the record so day-of surprises are their problem to argue, not yours.
What about backline sharing conflicts?
Publish the house list, make sharing the default, and surface refusals during the advance. Two acts refusing to share a kit across a 15-minute changeover is solvable at four weeks (a second kit, a riser plan) and a crisis at four minutes.
