Host an event

Open Organize → Host event. You will see every approved club you coordinate; choose the one hosting and you go straight into the event form.

Titlerequired

What the event is called. This is the line people scan in the feed: name the thing, don't tease it.

Event typerequired

One of Hackathon, Workshop, Coding Contest, Cultural Fest, Music, Dance, Sports, Seminar, Networking, Social Event or Other. Students filter the feed by this, so pick the honest one.

Start and end date-timerequired

When it actually runs. Multi-day events simply span the days; you don't create one event per day.

Banner

An image up to 5MB. Events with a banner get noticeably more attention in the feed than events without one.

Description

The full pitch: what happens, who it's for, what to bring. You can have AI draft it from the title and details you've already entered, then edit it into your own words.

Co-host clubs

Other approved clubs running it with you. Co-hosts appear on the event page; the primary host club owns the dashboard and the money.

Location typerequired

Offline or Online. Offline takes an address, city and state, plus optional map coordinates and a flag for whether it is inside the institute. Online takes a meeting link.

Registration deadline

Separate from the start time. Registrations close automatically when it passes. Set it a day or two early if you need to print badges or finalise catering.

Team event

Turn on to collect team entries, then set a minimum and maximum team size. One person registers and brings their teammates in under the same entry.

Approval required

Nobody is confirmed until a coordinator accepts them. Use it for limited-seat or curated events; leave it off and registrations confirm themselves.

Required document

Ask each registrant to upload one of College ID, Resume, Registration Form or Payment Screenshot, or None. Use College ID when eligibility depends on being a student somewhere specific.

Every event has at least one ticket type. Each one carries its own seat count, so you can run, say, 100 free student seats alongside 20 paid external seats on the same event.

Ticket typerequired

Free, Paid or Early Bird. Free tickets confirm on registration; paid tickets confirm once payment succeeds.

Total seatsrequired

The cap for that ticket type. Registration closes for it when the seats run out.

Price

In rupees, for paid tickets. This is what your club is owed; the platform fee is added on top and paid by the buyer.

Early-bird deadline

Optional date after which that ticket type stops being offered.

Custom fields are added to the registration form for this event. Each one has a label, a type, and a required flag:

• Text: short free answers, e.g. a GitHub handle or a T-shirt size.
• Number: years of experience, team member count, anything numeric.
• Dropdown: a fixed set of choices you supply as a comma-separated list.
• Checkbox: a yes/no, such as agreeing to a code of conduct.
• URL: a portfolio, repository or submission link.

Answers arrive attached to each registration in the dashboard, so you never have to reconcile a separate spreadsheet against your attendee list.

Three optional blocks that render on the public event page. Speakers take a name and a role; prizes take a title and a reward; FAQs take a question and an answer. Filling in the FAQ block is the cheapest way to stop the same three questions arriving in your DMs all week.

Publishing puts the event in the campus feed immediately, with its own public page you can share anywhere. Everything except the hosting club stays editable afterwards from the event dashboard: fix a venue, extend a deadline, add seats, correct a typo in the description.

To close registrations early, move the registration deadline to the past rather than deleting the event; the page stays up and the registrations you already have are unaffected.

Once entries start arriving, everything happens in the organizer dashboard: Manage your event.