Describe your venue and workflow. Makeform creates a tech rider form for each act's lineup, backline, inputs, stage layout, power, monitoring, access, and contacts.
Route details to Slack, Google Sheets, and Zapier.
Builder prompts
Choose a scenario, tailor the prompt, or send it to the Makeform builder. These are practical starting points, not live submissions.
Audience
Bands appearing at a small or midsize venue
Format
Sectioned advance form with conditional backline questions
Prompt size
269 chars
Example form structure
Sectioned advance form with conditional backline questions
Act, tour manager, and production contacts
Lineup, instruments, and backline
Numbered channel and monitor list
Upload your stage plot or existing rider
Arrival, load-in, and soundcheck times
Suggested routing tags
Awaiting review
Advance questions
Production ready
Request a numbered channel list with source, mic or DI, stand, phantom power, and monitor destination.
Step 1
Collect
lineup, contacts, schedule, and files
Step 2
Review
audio, stage, power, and backline
Step 3
Resolve
substitutions, conflicts, and missing details
Step 4
Confirm
final advance shared with show crew
Why use a structured rider
A structured form gathers current contacts, exact inputs, stage placement, and substitutions for this date.
Collect sources in channel order with mic, DI, stand, phantom power, and monitor notes for the patch plan.
Pair stage plots with performer positions, risers, power drops, and changeover notes.
Show venue inventory, flag substitutions, and resolve unanswered requirements before load-in.
Built for live production
Replace the sample inventory, deadlines, stage names, and crew contacts with your event details.
Collect requirements while showing the available PA, consoles, microphones, wedges, stands, and backline.
Capture stage, set, changeover, travel party, vehicles, passes, and artist contacts.
Coordinate bands with speeches, presentations, shared stages, catering, and cues.
Confirm local inventory, dimensions, access, crew, substitutions, parking, and curfew.
Production advance workflow
Separate required specifications from preferences and let both sides confirm what will be supplied.
State the stage, inventory, deadline, and who completes the rider.
Group schedule, audio, stage, backline, lighting, power, logistics, and hospitality. Require show-critical fields.
Reveal RF, house backline, and vehicle questions only when relevant.
Review uploads, record substitutions, and circulate the confirmed advance to show crew.
Form vs email vs static rider
Keep artist PDFs as references, then use the form for consistent date-specific answers and missing details.
Field guide
Use these six sections as a checklist, then remove anything your production does not need.
Identity and contacts
Separate the billing name from tour, FOH, and monitor contacts. Identify who approves substitutions.
Schedule and logistics
Confirm arrival through load-out. Vehicle size, stairs, lifts, and doors can change the plan.
Audio and monitoring
Request numbered sources with connector, mic or DI, stand, phantom power, playback path, and destination mix.
Stage and backline
Ask for performer positions, footprint, risers, backline, stands, and power. Label uploads by act and revision.
Lighting and effects
Gather console, show-file, key light, haze, strobe, video, effects, operator, and cueing needs.
Access and hospitality
Collect access needs, dressing rooms, water, meals, dietary requirements, and guest-list handoff.
Related tools
Keep booking, equipment, vendor, and feedback intake separate so the rider stays focused on production.
Collect availability, fees, lineup, repertoire, and booking contacts before advancing production.
Open toolGather the wider event brief, schedule, stakeholders, venue, audience, and delivery priorities.
Open toolConfirm date-specific logistics and responsibilities with clients and event partners.
Open toolTurn approved production requirements into an itemized request for internal inventory.
Open toolCollect vendor contacts, services, footprint, power, insurance documents, and arrival plans.
Open toolCapture artist, client, attendee, or crew feedback after the show ends.
Open toolFAQ
Answers for venues, producers, tour managers, and artists preparing an advance.
It collects an artist's production requirements for one booking: contacts, lineup, schedule, inputs, monitoring, stage, backline, lighting, power, access, and hospitality. The producer reviews anything the local package cannot provide.
Ask for contacts, lineup, schedule, inputs, monitors, stage plot, backline, power, lighting, load-in, vehicles, dressing rooms, meals, and access needs. Separate essentials from preferences and ask about substitutes.
Yes. Add uploads for riders, plots, channel lists, lighting files, or specifications. Keep date-specific details as fields so reviewers can spot changed lineups and exceptions.
Use one ordered entry per source with channel, instrument, connector, mic or DI, stand, phantom power, and monitor destination. Add playback, console files, splits, IEM, RF, and talkback when relevant.
Yes. Show frequency fields for wireless systems, backline details for house requests, trailer length for arriving trailers, or effects details only when planned.
Yes. Makeform offers unlimited free forms and responses, so you can generate, edit, publish, and reuse your tech rider form without a response cap. The paid tier removes the Makeform badge.
Send it before crew calls or equipment orders are locked. Set a deadline and request a labeled revision when the lineup, touring package, or design changes.
Follow production order, name stages and inventory consistently, record substitutions, and route a dated final advance to audio, lighting, stage, hospitality, and access leads.
Advance the show before load-in begins.
