Home · Guides · How to run a conference in India

How to run a conference in India — a 12-week playbook

Written from actually running 200-2,000 person conferences in Bengaluru, Mumbai, Delhi and Hyderabad. No fluff. If you've been asked to organise your first serious conference, this is the timeline, the budget bands, and the mistakes to avoid.

On this page

Week 12-10: Theme, size, date, venue

Lock the theme early. A conference without a clear theme is a networking event with a projector. Write it in one sentence: "An X for Y people about Z outcome."

Pick your size band. 100-300 (intimate), 300-800 (mid), 800-2000 (large). Everything downstream — venue, budget, staff — scales off this.

Date. Avoid Mondays, avoid Fridays, avoid religious festival weeks. Tuesday-Thursday in Oct-Nov or Feb-Mar are the sweet spots in India.

Venue scouting. Visit 3-4. Ask: total footprint, breakout rooms, parking, network bandwidth, kitchen capacity, AV rider, F&B minimums, cancellation clause. Don't sign the first one because it "felt right."

Venue tip: ask what other event is happening the same day in the adjacent hall. Nothing kills the vibe like your fintech summit sharing a floor with a jewellery expo's dhol procession.

Week 10-8: Sponsors + registration open

Sponsor deck first. Even if you don't need sponsor money, having a clear deck lets you confidently say "we're not selling those tiers" when someone asks.

Registration site live by end of week 10. Sooner if you're charging for tickets. A conference site that goes live 4 weeks before the event will lose 40-60% of possible attendees compared to one live at 10 weeks.

What to put on the site:

Payments. UPI + card. If you're in India, UPI first — GPay/PhonePe intent flow converts 20-30% higher than card. GST invoices should auto-generate on payment; don't make attendees ask.

Week 8-4: Speakers + agenda

Confirm speakers 8 weeks out. Any later and you'll be chasing bios and headshots the week of the event. A speaker portal (where each speaker gets a private link to fill in bio, upload photo, drop slides) saves the coordinator's sanity.

Publish the agenda. Tracks, session names, times, room. Enable session RSVP with capacity so you know which sessions will be full and can plan overflow.

Session capacity math: your biggest track will overflow, your smallest will be empty. Plan for it. Livestream the biggest track into an overflow room.

Week 4-1: Reminders + rehearsal

Weekly reminders starting 4 weeks out, then 2 weeks, then 3 days, then day-of morning. Skip this and your no-show rate doubles.

Kiosk + badge print rehearsal. One week out, actually plug in the printer at your office and print 20 test badges. Discover the paper-size mismatch now, not on the morning of the event.

Staff briefing. 2 days out, run everyone through the kiosk flow, the scanner flow, the session check-in flow, and the "what if X" scenarios (attendee lost their pass, card declined at the desk, VIP not on the list).

Day-of: Check-in, sessions, engagement

Kiosk at the door. Two tablets minimum. One dedicated to walk-ins. Print badges on-demand.

Session-level check-in. Each session's QR at the room entrance. Real attendance data (not just "registered") is what sponsors and speakers actually want.

Engagement in-session. Live polls, moderated Q&A with upvotes, word clouds. Attendees vote and ask from their own phone, no separate app.

Runbook for the ops team. A shared doc with everyone's role, session start times, break slots, emergency contacts. Print 5 copies. WiFi will fail at exactly the wrong moment.

Post-event: Recap, NPS, next year

Recap same day. Session transcripts + AI-generated summary emailed to every checked-in attendee within hours. Highest email open rates of the entire conference cycle.

NPS survey. One-page form, three questions max. Sent 24-48 hours post-event.

Certificates. Auto-issued to every checked-in attendee. Signed PDF, public verification page. Attendees post these on LinkedIn — free reach for next year.

Post-event report. One page: attendance vs registration, top sessions by check-in, NPS score, top attendee quotes, sponsor lead counts. Sponsor teams will renew based on this document.

Budget bands (indicative, INR)

For a 500-person, one-day, mid-market conference in Bengaluru/Mumbai/Delhi:

Six mistakes to avoid

  1. Opening registration too late. 4 weeks is too little. 10-12 is the target.
  2. No session-level check-in. "Registered attendees" is a vanity number. Sponsors want "checked-in attendees per session."
  3. No reminder cadence. Sending one reminder is worse than sending none, because people mentally file "I've been reminded" but don't act.
  4. Ignoring the payment invoice workflow. Corporate attendees can't submit expenses without a GST invoice. If yours don't auto-generate, expect a flood of angry Slack messages the following week.
  5. Buying the wrong badge printer. Test print a full run 7 days before the event. Ink, paper size, lanyard hole punch position — all need testing.
  6. No post-event report. Sponsors renew based on numbers, not vibes. Send a one-page report within 5 business days.
Running your next conference on SignupDesk covers registration, kiosk, session RSVP, live polls, GST invoicing, AI recap emails and NPS survey — the whole stack from week 10 through the post-event report. See the conferences page →

Want this playbook applied to your event?

A 20-minute walkthrough will map every step above to the platform.

Book a demo →