How to Organise a College Tech Fest: Complete Guide 2026

A college tech fest is not one event. It is eight to twelve events running in parallel, staffed by volunteers who have exams, on a budget that is not confirmed until three weeks out. This guide is organised by timeline, and it concentrates on the things that go wrong every year rather than the things that are obvious.

Twelve to eight weeks out: decide the shape

Structure the fest as a parent event with tracks

The single most consequential early decision is how you model the fest. The mistake is to create one event called "Techfest 2026" with a dropdown of workshops. The correct model is a parent event with each workshop, competition and talk as its own track.

Why it matters, concretely:

• Each track needs its own capacity. A lab holds 30 and the auditorium holds 300; one shared number for the fest is meaningless.
• Each track needs its own price. A hands-on CAD workshop is not priced like a keynote.
• Each track needs its own check-in, because they run at the same time in different rooms.
• Each track gets its own page to share, which is what your department heads and student coordinators will actually circulate.

Get this wrong and you spend the fest reconciling a spreadsheet. Get it right and each track lead can see their own numbers without asking you.

Set capacity from the room, not from ambition

Capacity should be the number of seats in the room, minus your organisers. Software will enforce whatever number you type, so the number needs to be true. Overselling a computing lab by three is not a rounding error — it is three people who paid and cannot be seated.

Eight to six weeks out: pricing and the budget

Work out your per-head cost before you set a ticket price. For a campus workshop the honest list is usually: materials, refreshments, printing, the speaker's travel, and a contingency you will need.

Item	Notes
Materials / kit	The one that scales strictly per head. Confirm the quantity from paid registrations, not from interest.
Refreshments	Order against expected attendance, not registrations — see the no-show note below.
Speaker / trainer	Fixed cost. Divide by your minimum viable attendance, not your target.
Certificates and printing	Near zero if certificates are digital and self-serve.
Payment processing	Gateway fee plus platform fee. Budget it explicitly rather than discovering it at payout.

On processing: free events on Vihaya carry no platform fee at all, and paid tickets are banded by the expected size of the event — smaller events pay the top of the range and larger fests the bottom. The full band table is published on the pricing page, so you can work out your number before you commit.

Decide who absorbs the fee

You have two options and both are legitimate: absorb the fee and receive slightly less than the ticket price, or pass it to the attendee so the amount you typed is the amount you keep. Decide deliberately, because it changes what you advertise. Most student committees prefer passing it on, since their budget is usually built from a round per-head figure.

Six to four weeks out: open registration

Ask for less than you think

Every additional field costs you completions. The defensible minimum for a campus fest is name, email, phone, college, and year or department. Everything else needs to justify itself:

• T-shirt size — only if you are actually ordering t-shirts, and only after they have paid.
• Food preference — only if you are serving food. Then it is essential, not optional.
• "How did you hear about us" — replace this with a referral code per coordinator; it gives you the same answer and it is accurate.

Validate the email address properly. On a campus fest the ticket email is the only channel you have to reach an attendee, and a one-character typo like gmail.con means somebody paid and received nothing. A good form should catch that before they submit rather than bouncing days later.

Use phased pricing to get early commitment

Set a super-early-bird and an early-bird window with both a deadline and a seat cap. The cap matters: a phase that ends only on a date will happily sell discounted tickets on the final day, when you no longer need the discount.

Give each coordinator a referral code

Departmental coordinators are your actual distribution channel. Give each one a code and you learn which departments and which people genuinely bring people, which is the information you need when you plan next year's committee.

Four to two weeks out: promotion that works on a campus

1. The class WhatsApp groups. Nothing else comes close. One message from a class representative outperforms a week of Instagram.
2. Department noticeboards with a QR code. Point it at the specific track's page, not the fest homepage — the extra click loses people.
3. Instagram for reach, WhatsApp for conversion. Instagram tells people the fest exists; the group message is what makes them register.
4. Nearby colleges. If you want outside participation you have to ask deliberately, through their coordinators, at least three weeks out.

Put the registration link everywhere, and make sure it works on a phone on college wifi. Most of your traffic is a student on mobile data between classes.

The final week

• Send joining instructions — venue with a map link, timings, what to bring, what is provided. This single email reduces day-of questions more than anything else.
• Export the roster per track and give each track lead their own list.
• Print attendance sheets as the offline fallback. College wifi fails at exactly the wrong moment; print the list that excludes unpaid registrations so the desk is not admitting people who never paid.
• Brief the door volunteers on the three refusals: wrong track, payment pending, already checked in. Volunteers freeze when they meet a case nobody warned them about.
• Confirm final numbers with catering against expected attendance.

On the day

Put one person on the door whose only job is check-in, and one floating person who handles exceptions so the queue never stops for a problem. Scanning a QR is fast; the queue is created by the one person whose name is spelled differently on their ticket.

Watch the live count against capacity per track. If a track is half empty at start time, walk people over from the one that is overfull — this is the sort of thing you can only do if the numbers are live and per-track.

After the fest

• Publish certificates within 48 hours, while people still care. Make them self-serve rather than emailing hundreds of PDFs by hand.
• Send one feedback form, five questions maximum.
• Write down the numbers for next year: registrations, actual attendance, no-show rate per track, revenue and cost per track. This is the single most valuable thing you can hand the next committee, and it is the thing that never gets done.

Planning a fest this semester? See how multi-track fest ticketing works on Vihaya Events, or browse ticketing by city.