How to get invited to a literature festival in India

Almost every writer I know believes the invitation works like this: you publish a book, the festival notices the book, the festival invites you to talk about the book.

That is not how it works. I have sat on the programming side of the table, and the sequence is close to the reverse.

How do literature festival sessions actually get built?

A programmer starts with the year, not with the authors.

You begin with a rough sense of what the festival is about this time — what is in the air, what an audience will queue for, what the festival wants to be seen caring about. From that you get themes. From themes you get sessions: a title, a shape, a reason for the audience to sit down. Only then does the casting begin — who can hold this particular room for fifty minutes, who will disagree productively with whom, who has thought about this before today.

The book comes in at the end of that chain, if at all. It is often the reason someone is eligible — it explains why they’re credible on the subject — but it is very rarely the reason they’re chosen.

This is why the most common pitch fails before it’s finished. “I have a book out, can I be part of the festival?” is not answerable. It doesn’t tell the programmer which session you belong in, because you haven’t looked at the sessions. It hands them a problem instead of solving one.

The pitch that works does the programmer’s job for them. It says: here is a conversation your festival is clearly interested in, here is why I am unusually good on it, here is what I would say that nobody else on that stage would.

Why isn’t “I have a book out” a pitch?

Because roughly every writer at that festival also has a book out. It is the entry requirement, not the argument.

Think about what the programmer is actually short of. Not authors — authors are abundant, and every publisher in the country is sending lists. What they’re short of is people who can make a session good. A session is a piece of live performance in front of an audience that paid nothing to be there and can leave at any moment. Most of them are mediocre. The programmer knows this and lives in fear of it.

So the scarce commodity is not a book. It is a person who will make the room feel like something happened.

What makes a writer bookable?

Two things, and only one of them is about your book.

Can you hold a room? This is a real skill and it is not correlated with the quality of your prose. Some of the finest writers in India are, on a stage, quiet and internal and slightly embarrassed to be there. That is not a moral failing. But a programmer who has watched you go flat in front of four hundred people will hesitate, and will keep hesitating, and will never tell you why.

The good news is that this is learnable and observable. Speak at bookshops. Speak on podcasts. Speak at a college. Do the small rooms badly until you do them well. And be findable doing it — a programmer casting a session will look for evidence you can talk, and video of you being interesting is the most persuasive thing you own.

Are you interesting on something beyond your own book? This is the one that actually separates people.

A writer who can only talk about their novel can be placed in exactly one session: the one about their novel. A writer who is genuinely, specifically knowledgeable about grief, or Partition archives, or the economics of the film industry, or liver disease, or fandom, can be placed in five. They become useful across the programme. They get invited back.

I saw a version of this play out with The Liver Doctor by Dr Cyriac Abby Philips at HarperCollins India. It is a book with a real literary voice. But what carried it — what actually gave people a reason to listen — were the health takeaways. Those were portable. They travelled into rooms that had nothing to do with publishing, which is precisely what a programmer is looking for: someone who brings an audience a reason to care that isn’t just “there is a new book.”

Should I go through my publisher or approach the festival directly?

Both, and they do different jobs.

Your publisher’s list is how you get considered. Publishers send names to festivals every year; festivals rely on those lists because they’re a filter. This is real leverage and you should use it — tell your publicist which festivals matter to you and why, early, and be specific rather than saying “any of them.”

But understand what that route can and cannot do. A publisher’s list gets your name into the pile. It does not tell the programmer which session you belong in, and it usually can’t, because the person compiling it is representing thirty authors and has to be even-handed about all of them.

The direct approach is how you get placed. It is not rude, if it’s done properly. A short, specific, well-aimed note to a programmer — one that shows you’ve read last year’s programme and understood what the festival is trying to be — is a gift, not an imposition. What is rude is the mass mail: the same paragraph, obviously sent to eleven festivals, with the name swapped.

The two work together. The list makes you legitimate. The note makes you placeable.

When should I be pitching?

Earlier than feels reasonable, and not only when you want something.

Programming is built months ahead of the festival, and the interesting slots are gone long before the schedule is public. By the time you see the lineup announced, the decision about you was made a long time ago. If your pitch arrives in the same month as the festival, you are asking to be squeezed into a structure that is already finished.

There is a second timing problem, subtler and more damaging. Most writers surface only in their publication month, when they want something, and then disappear. That pattern is legible from the other side of the table, and it makes you feel like an errand rather than a person.

The writers who get invited repeatedly are the ones who exist between books. They turn up at other people’s sessions. They say yes to the unglamorous panel. They are around. None of this is strategy in any cynical sense — it’s just that festivals are built by people, and people programme those they’ve seen being good in a room.

What should I take from all this?

Stop asking festivals to be interested in your book. Start being someone their programme is worse without.

That is a harder ask, and a slower one, and I’m aware it’s not the tactical answer anybody wants. But the tactical answers are mostly noise. The programmer’s question, every single time, is who will make this session good. Answer that question and the invitation is almost administrative.

Fail to answer it and no amount of pitching will help — because the pitch was never the thing being evaluated. You were.