How a Line-Up Actually Happens: Notes from a Chilterns Programme Meeting

It's a Tuesday evening in late October, and eight people are crammed around a table in a converted chapel off a Chilterns high street. There's a wall of sticky notes, a laptop open on a spreadsheet with more tabs than anyone wants, and a pot of tea that went cold forty minutes ago. On the agenda: the last thirty slots of a 2026 festival programme.

Nobody in the room is paid much, and at least two of them have come straight from work. But this is where the line-up actually gets made — not in a grand announcement, but in an argument about whether a nature writer from Wendover can hold a room at 11am on a Saturday.

The spreadsheet comes before the stars

Ask what surprises people most about programming and the answer is consistently unglamorous: the rooms decide.

'Everyone thinks we start with the famous names,' says Priya, who has programmed a two-day festival in Tring for six years. 'We start with the venues. Which hall seats 90 and has a working hearing loop? Which one has a piano we can't move? Which one floods if it rains?' Get that wrong and no amount of star power saves you.

So the first pass is a grid: times, rooms, capacities, ticket prices, walking times between venues. Only then do names go in. A big author with a 40-minute signing queue and a 20-minute walk to the next venue is a scheduling problem before they're an artistic one.

The maths of a headline name

Programmers use the word 'anchor' a lot. An anchor is a name that goes on the front of the brochure and shifts tickets to people who wouldn't otherwise come. That's the theory. The practice involves a calculator.

'We work out what a name has to sell to justify itself,' says one publicist who has pitched authors to Chilterns festivals for a decade. 'Fee, travel, a hotel if it's a late finish, a green room, sometimes a moderator. If the ticket price is twelve quid and the room holds 150, the arithmetic gets tight fast.'

Which is why so many programmes look lopsided in a way that makes sense once you're inside: one or two anchors, a lot of mid-list authors, and a scattering of local names who cost very little and bring their own audiences. The anchors pay for the experiment. The experiment is the point.

The local-voice question isn't box-ticking

There's a lazy assumption that local authors are there to make a programme look community-minded. Programmers describe it differently — as a test of whether someone has a constituency.

'It's not "are you local", it's "will anyone come",' says a programmer for a festival near Chesham. 'A historian who's been speaking to the local civic society for fifteen years will fill a hall. A novelist who lives four miles away but has never done an event might sell nine tickets. Both are fine, but they're different slots.'

The ones who do well tend to offer something extra: a walk, a workshop, a link to a museum or a library, a subject with a postcode in it. That's the kind of thing that turns a booking into a partnership.

What gets pitched, and what gets binned

Programmers are unanimous that most pitches fail on length, not quality. A typical inbox in pitching season runs to several hundred emails.

What works, according to the people reading them:

• One page. A short bio, three bullets on what the talk actually covers, and a line on who it's for.
• A link to a recording of you speaking. Not a book trailer. A recording of you, in a room, being interesting for twenty minutes.
• Availability, travel, and whether you can get there by train. Chilterns venues are not all near a station, and a lift from Tring to a village hall is a genuine logistical item.
• Two or three possible subjects, not one. Programmers are matching to themes and slots, not just to authors.

What gets binned: forwarded press releases with no date on them, 'as seen on television' with no indication of when, attachments over 10MB, and anything that opens with a demand.

The pitch that actually works

The stories programmers tell about good pitches are usually about people who made the job easier.

There's the nature writer who offered a morning walk and an afternoon talk, so the festival got two events and a walk out of one booking. There's the poet who said she'd run a workshop for teenagers if it helped, and then did. There's the debut novelist who emailed in January, mentioned she'd be in the area anyway, and followed up once — not five times.

'Enthusiasm is contagious, but only if it's specific,' one programmer says. 'Tell me what you'd do in the room. Don't tell me you're passionate about storytelling.'

Chemistry, and the moderator nobody budgets for

The best panels aren't three people taking turns to read. They're a conversation with a shape, which means someone has to shape it. Chairs are the most underrated line in any festival budget, and the least likely to be thanked.

Programmers pair authors on friction as well as overlap: a critic with a practitioner, a sceptic with an enthusiast, two people who disagree about the same book. They also try not to put two similar events against each other, and they try not to schedule the anchor at 9am on a Sunday, when the room is full of people who came out of loyalty and want to be home by lunch.

And then there's the pub. Nearly every programmer mentions it. The informal hour after the last event, where an author meets a bookseller, or two writers discover they're working on the same thing, is where next year's programme quietly starts.

What to do if you want a slot in 2026

Pitch between January and March. Be specific about the talk rather than the book. Offer more than one format. Say what you can do without being asked. And be decent to the person managing the inbox, who is probably doing this on a Tuesday evening with cold tea and a spreadsheet that has too many tabs.