Stage Plot and Tech Rider for Indian Bands: Free Template Guide (2026)

Every sound engineer in India has a story about the band that turned up at soundcheck with no information. Nobody knew the drummer needed four toms miked, the keyboard player wanted a stereo DI, or the vocalist couldn't hear herself without a wedge pointed straight at her. The fix costs nothing: a one-page stage plot and a short technical rider, sent to the venue days before the gig. This guide explains what both documents are, what goes in them, how Indian venues and festivals actually use them, and how to build your own template you can reuse for every show.

Stage plot vs tech rider: what's the difference?

People use the words loosely, so let's be precise.

• Stage plot. A simple top-down drawing of your stage. It shows where each musician stands, where amps, drum riser, keyboards and monitors go, and where power is needed. Think of it as a map.
• Input list. A numbered list of every channel you need on the mixing desk: kick, snare, hi-hat, toms, overheads, bass DI, guitar mics, keys, vocals, playback. Engineers patch from this list.
• Technical rider. The written document that bundles the stage plot and input list with your backline needs, monitor mixes, power, and any special requirements.
• Hospitality rider. Separate from the tech rider. Food, water, green room, travel and accommodation. Keep it apart so the production team only gets what they need.

For most independent acts in India, the tech rider is two pages: page one is the stage plot, page two is the input list plus notes. That's enough for a club gig in Bengaluru or a college fest in Pune.

Why Indian indie acts need one even for small gigs

You might think a rider is for headliners. It isn't. It's a courtesy that makes you easier to book again.

• Shared backline is the norm. Many Indian clubs and cafés provide a house drum kit and amps. Your rider tells them exactly what you'll use and what you're bringing.
• Soundchecks are short. On multi-band bills, openers often get 15 minutes or a quick line check. A clear input list means the engineer has patched before you arrive.
• Festivals ask for it. Showcase applications and festival production teams routinely request a tech rider and stage plot. Our guide to music festival and showcase applications explains where these fit in the application.
• It protects you in the contract. A good gig contract references your tech rider as an attachment, so the promoter has agreed in writing to what's provided.

What goes on a stage plot

Keep it to one page, landscape, readable when printed in black and white. Include:

• Stage orientation. Mark "Audience / Front of house" at the bottom so nobody reads it upside down.
• Each performer's position with name and instrument: "Riya — lead vocal, acoustic guitar".
• Drum kit and riser, with the kit drawn roughly to scale if you can.
• Amps and cabs, labelled: "Bass amp (house OK)", "Guitar combo (own)".
• Monitors (wedges) numbered to match your monitor mixes. Mark in-ear users clearly.
• DI boxes and where they're needed.
• Power drops. Mark every spot that needs a socket, with how many outlets. In India, flag if you need 5A or 15A sockets, or a stabilised supply for sensitive gear.
• Mic stands, noting boom vs straight.
• Band contact at the top: one name and phone number for production questions.

You don't need special software. A drawing tool, a slide app or a free stage plot builder works fine. Dedicated tools such as Stage Plot Pro exist if you want standard symbols. What matters is that it's clear.

What goes in an input list

Number every channel in the order engineers usually patch: drums first, then bass, guitars, keys, playback, vocals. For each line give:

• Channel number
• Source (kick in, snare top, bass DI, acoustic DI, lead vocal)
• Mic or DI preference ("SM57 or similar", "active DI")
• Stand type (short boom, tall boom, clip)
• Phantom power if needed
• Notes ("stereo pair", "own mic", "wireless")

Write it as a numbered list, not a grid. Many venues will forward your rider on WhatsApp, where a list reads cleanly on a phone. Something like:

• Ch 1: Kick in — Beta 91 or similar — no stand
• Ch 2: Kick out — Beta 52 or similar — short boom
• Ch 3: Snare top — SM57 — clip or short boom
• Ch 4: Hi-hat — small condenser — short boom — 48V
• Ch 9: Bass — active DI — own
• Ch 14: Lead vocal — SM58 or own — tall boom

Always write "or similar" after mic models. Indian venues vary hugely in their mic lockers, and demanding a specific microphone a small club doesn't own just creates friction.

Monitor mixes

Tell the engineer how many separate monitor mixes you need and roughly what goes in each.

• Mix 1 (lead vocal wedge): lots of vocal, a little keys and acoustic.
• Mix 2 (guitar): vocal, own guitar, some kick.
• Mix 3 (drums): kick, bass, click if used, vocal.

Be realistic. Many Indian clubs have two to four monitor sends. If you need more, say what you can share. If you run in-ear monitors with your own rack, say so and explain how you'll take a split.

Backline: what you bring vs what you need

List backline in two groups.

• Bringing: your own guitars, pedalboards, snare, cymbals, keyboard, laptop.
• Need from venue: drum kit shell sizes, bass amp, guitar amp, keyboard stand, chairs, tables for laptops.

If you're flying to a gig, this section matters more. Airlines limit luggage, so you'll rely on rented or house backline. Our tour planning guide covers travel logistics, and the rider is where you tell each venue what to rent locally.

Playback, click and laptops

Many indie acts in India now run tracks, samples or visuals. Be explicit:

• How many outputs from the laptop or interface, and whether you send stereo or multiple stems.
• Whether you need the click sent to the drummer only.
• Whether you need an HDMI or projector feed for visuals, and at what resolution.
• A backup plan if the laptop crashes. Engineers love seeing this written down.

Power, safety and Indian venue realities

Indian venues range from purpose-built clubs to rooftops and college grounds powered by a diesel generator. Your rider should protect your gear:

• Ask for stable, earthed power and, for outdoor shows, a separate line for sound and for lights.
• Mention voltage-sensitive gear (tube amps, synths) and ask about stabilisers or a UPS.
• For outdoor monsoon-season gigs, ask about stage cover and keeping electrics off wet floors.
• If you use any flame, fog or haze, say so. Many venues need permissions, which ties back to the event's permits (see our guide to live gigs, venues and permits).

Writing the rider politely

A rider is a request, not a demand letter. Open with a line like: "Below is our ideal setup. We're flexible — please tell us what's available and we'll adapt." Then:

• Mark essentials vs nice to have.
• Give one production contact who answers calls on show day.
• Put the date and version on the document so you know which one a venue has.
• Keep a short version for small venues: one page with stage plot and a ten-line input list.

A reusable template

Build it once, then update per show.

• Header: band name, contact, version date, line-up for this show.
• Page 1: stage plot drawing.
• Page 2: input list, monitor mixes, backline (bringing / need), power.
• Page 3 (optional): playback, visuals, special effects, changeover time needed.
• Footer: "Hospitality rider sent separately."

Export as PDF, name it clearly (for example "BandName-TechRider-v3-2026.pdf"), and add it to your electronic press kit so promoters and agents can grab it without asking. If you work with a booking agent, give them the latest version so they can send it with every confirmation.

Sending it and following up

• Send the rider when the gig is confirmed, not on the day.
• Ask the venue to reply with what they can't provide. Silence often means nobody read it.
• Two or three days before the show, confirm on WhatsApp with the house engineer directly.
• Carry printed copies. Tape one to the monitor desk and one near front of house.

Common mistakes

• Copying a big-band rider from the internet and asking a café for 32 channels.
• No contact number.
• Listing the line-up from two years ago.
• Forgetting the other acts: if you share a bill, ask what stays on stage between sets to speed up changeovers.
• Using a grid layout that breaks when forwarded. Lists travel better.

The takeaway

A clear stage plot and tech rider make you look professional, cut soundcheck stress and get you rebooked. Start with one page, keep it honest about what you truly need, and update it every time your line-up or setup changes. If you're still building up to bigger stages, our open mic guide is a good place to practise playing to a room — and even there, a quick note to the host about your inputs goes a long way.