NGO Event Registration Page: Walkathon Guide

NGO Website Development in India: Building an Event Registration Page for a Walkathon, Marathon or Charity Run

An event registration page for an NGO is a dedicated page, or a short set of linked pages, where people sign up for a walkathon, marathon, charity run or gala, and where your team gets back a clean list of who is coming. In NGO website development in India, the page itself is the easy part. What decides whether the event runs smoothly is everything behind it: a form that asks only what you need, a capacity count that stops overselling, a confirmation people actually receive, a QR code that speeds up check-in, and a follow-up plan for the days after. This guide walks through each piece in the order you would build it.

It is written for NGO fundraising managers, event coordinators and anyone briefing a developer. The worked example is hypothetical: no real NGO or event is described, and the numbers are illustrations, not benchmarks. This article deliberately leaves out payment fees and tax treatment; for receipts and 80G, see our guide to an 80G-compliant donation platform. Legal points are summarised from official texts as read in October 2026 and are not legal advice.

How this differs from other fundraising pages

A festival or year-end campaign page asks a visitor to give, and a peer-to-peer page lets a supporter ask their own network. An event page books a person into a place at a specific time. Giving may be attached, but the page must work even if nobody donates, because its first job is logistics and safety.

What NGO website development in India needs on the event page itself

Before any form, the page needs to answer a visitor's practical questions in the first screen. A useful order is:

What and why: event name, one sentence on the cause, and what registrations support. Keep the claim modest and specific.
When and where: date, reporting time, start time, venue with a map link, and the nearest public transport or parking note.
Categories: for example a 3 km family walk, a 5 km run, a 10 km run. State the age rules for each, and whether children must be accompanied.
Accessibility and safety: whether the route suits wheelchair users or prams, whether there is first aid and drinking water, and any medical declaration you will ask for.
Contact and cancellation: a real phone or WhatsApp number, and a plain statement about what happens on cancellation or bad weather.
A single clear button: "Register" that leads to the form.

Give the page a stable URL you can reuse next year, so it builds search authority over time. Our guide to SEO page planning for NGO donors covers that thinking.

The registration form: fields that earn their place

Every extra field costs you completed registrations and adds data you must protect. A good rule is to separate fields into three groups.

Essential for the booking

Full name (as it should appear on the bib or certificate)
Mobile number (needed for the WhatsApp confirmation and for on-the-day contact)
Email address
Category chosen (distance or ticket type)
Number of participants, if a family or group registers together

Needed only for some events, and only if you will use them

Date of birth or age band: needed where categories are age-restricted or where you must know whether a participant is a minor. An age band ("under 18", "18 to 59", "60 and above") is often enough and collects less than an exact date of birth.
Emergency contact name and number: reasonable for a run or long walk. Say on the form why you are asking.
T-shirt size: only if you are giving a t-shirt.
Medical declaration (a simple tick box that the participant is fit to take part), and any health condition they choose to share. Make the second one optional and explain who will see it.

Participant fundraising pages inside an event

Many NGO runs ask participants to raise money from friends. That is a peer-to-peer layer on top of registration. The detailed mechanics, including how every gift must reach the NGO's own account and how fundraiser pages should be moderated, are in our peer-to-peer fundraising guide, so this section covers only what is specific to events.

Make it optional at registration. A tick box such as "I would like a personal fundraising page" is enough. Forcing a target on everyone can lower sign-ups.
Create the page automatically from the registration record, pre-filled with the participant's name, event, category and a short suggested message that they can edit. This is quicker than asking them to start a second sign-up.
Give participants a shareable link and a ready WhatsApp message, which they can send in one tap. Do not send messages on their behalf to their contacts.
Offer a team page for offices, colleges and housing societies. A team lead registers a group, members join under it, and the team total sits above individual totals. This is often how CSR-linked or corporate-volunteer groups take part; our guide to CSR volunteer portals covers that audience.
Moderate before publishing. Review pages for inappropriate images, medical claims about beneficiaries and anything that implies a different cause from the one your event supports.

The data warning from that other guide applies here too: a fundraiser page publishes a person's name and photo. Make visibility a choice, and let participants use a first name or a team name instead.

Capacity limits and waitlists

Events have real limits: route permits, venue capacity, kits, volunteers and insurance. Your website should respect them.

Set capacity per category

Set a limit per category and, if relevant, per time slot. The count should decrease when someone completes registration, not when they open the form. If you collect a fee, decide what happens to a seat held during an incomplete payment: a short hold of a few minutes, released automatically, is the usual approach. Tell your developer to test the case where two people try to take the last seat at the same moment, because that is where overselling bugs appear.

Waitlist rules

When a category is full, switch the button to "Join waitlist". Decide in advance, and write on the page:

How the waitlist is ordered (first come, first served is easiest to explain).
How long a person has to confirm when a seat frees up (for example, 24 hours) before it moves to the next person.
What information you collect from waitlisted people. Collect only name, mobile and category at that stage, and ask for the rest once they are offered a seat.
What happens to waitlist data when the event closes. Delete it, or ask for explicit consent to keep it for the next event.

Confirmation by email and WhatsApp

A registration is only real to the participant once they receive confirmation. Send it immediately, and keep it useful.

What the confirmation should contain

Event name, date, reporting time, venue and map link
Category and, if relevant, the bib or registration number
A QR code or a registration reference, for check-in (see below)
Kit collection details if kits are given out before the day
A cancellation or transfer link, and your contact number
A short note on what personal data you collected and a link to your privacy notice

Email versus WhatsApp

Email is reliable, easy to archive, and suited to a PDF or an image with a QR code. WhatsApp is read more quickly by many Indian participants, but it has rules. Business-initiated messages sent outside an open customer conversation must use approved templates, and Meta's policy requires opt-in from the person receiving them. Our guides on WhatsApp opt-in compliance, template messages and the 24-hour messaging window explain these constraints; pricing and categories change, so confirm current terms with your provider rather than relying on an old article.

A practical pattern:

At the form, include an unticked opt-in box: "Send my confirmation and event updates on WhatsApp."
Always send the email confirmation as the record.
If the participant opted in, send a short WhatsApp confirmation using an approved template, with the key facts and a link to the full details.
Send reminders at two points: a few days before (kit collection, what to bring, weather note) and the evening before (reporting time, route, parking).
Use WhatsApp for operational updates only unless people have agreed to hear about other things. Do not turn event registrants into a general fundraising list without a separate, clear consent.

If you do not use the WhatsApp Business API, a manual broadcast to a long list is both a policy risk and a workload. A WhatsApp automation connected to the registration data is cleaner; see our WhatsApp flow service.

Volunteer sign-up for the event

Large events depend on volunteers: registration desk, route marshals, hydration points, first aid helpers, photographers, crowd management. Treat volunteers as a second registration type with its own short form rather than mixing them into the participant list.

Roles and shifts: let people choose a role and a time window, with a count of how many are needed per role. Show "3 of 10 filled" so people can see where help is needed.
Eligibility: if volunteers will work with children or vulnerable people, state any requirement for ID or a conduct agreement, and handle those documents offline or in a restricted system.
Contact for the day: a mobile number is essential. Use it for the shift reminder and nothing else without consent.

Consent and data minimisation under India's DPDP Act

An event registration collects personal data from many people at once, including, quite possibly, children and health-related information. The Digital Personal Data Protection Act, 2023 applies to digital personal data, and the DPDP Rules, 2025 were notified by the government in November 2025. Secondary commentary (not the gazette text) places the main notice, consent and rights provisions of the Rules in force from 13 May 2027, eighteen months after notification, with a consent-manager provision earlier in November 2026. TODO: confirm each commencement date against the gazette notification or with your adviser before relying on it. Building good habits into the form now is cheaper than retrofitting a database later. Our deeper guides are the DPDP website compliance guide and the donor data protection guide.

Collect only what the event needs

Section 6(1) of the Act says consent must be limited to the personal data necessary for the specified purpose. For an event, that is a direct argument for the field audit above. If you cannot say what you will do with a field, remove it.

Use a clear notice and separate choices

Show a plain-language notice at the point of collection stating what data you collect, why, who sees it (for example, the t-shirt vendor sees only name and size), how long you keep it, and how to ask for correction or deletion.
Give the notice in the languages your participants read. Our multilingual NGO website guide covers that.
Use separate, unticked boxes for separate purposes: event logistics (necessary), WhatsApp updates (optional), future NGO newsletters (optional), photo and video use (optional, see below).
Record when and how each person agreed, so you can show it later.

Minors

Events attract families and school groups. Section 9(1) requires a data fiduciary to obtain verifiable consent of a parent or lawful guardian before processing a child's personal data, and section 9(3) prohibits tracking or behavioural monitoring of children and targeted advertising directed at children. The Act defines a child as someone under 18. In practice, for a family walk, this means:

Ask an adult to register children, and collect the minimum about the child (a first name and age band can be enough).
Capture the guardian's confirmation on the form.
Do not add children's data to marketing audiences or ad retargeting pools.
Be cautious about publishing children's names or photos. Our guide on beneficiary stories and photos with consent is relevant to event photography too.

TODO: confirm with a legal adviser the exact method of verifiable parental consent that the Rules prescribe once in force, and any exemptions that apply to your type of organisation.

Retention and deletion

Decide at design time how long each data set lives. A sensible starting point, to be confirmed with your adviser: delete waitlist data and emergency details soon after the event, and keep other records only as long as reporting needs them. Where a record is also needed for accounts or tax, keep that financial record separately and do not use it for marketing.

On-the-day check-in with QR codes

Check-in is where a good registration system proves itself.

How QR check-in works

At registration, the system generates a unique code for each participant. The code should carry a random reference, not the person's name or phone number, so a screenshot shared by mistake does not expose personal data.
The confirmation email and WhatsApp message include the QR image, and also the reference in text in case the image does not load.
At the venue, volunteers scan the code with a phone camera or a simple web page on their phones. The page looks up the reference and shows name, category and whether the person is already checked in.
The system marks the participant as checked in with a time stamp and shows a green or red result. A second scan of the same code shows "already checked in" so one code cannot be used twice.
If a code will not scan, the volunteer searches by name or mobile number as a fallback.

Plan for weak connectivity

Crowded venues and open fields often have poor mobile signal. Ask your developer how the check-in page behaves offline. Options include downloading the participant list to the volunteers' devices before the event and syncing afterwards, or providing a portable Wi-Fi hotspot. Test it at the venue before the day. Keep a printed list as the last backup, held by the desk lead and shredded after the event.

Post-event follow-up

The days after the event are when most NGOs lose momentum. Plan this before launch.

Within 24 hours

A thank-you message by email and, to opted-in participants, a WhatsApp template, with one or two photos if you have consent, and a link to a short feedback form.

Within a week

Publish a results page: number of participants, categories, what the event raised toward its goal, and what the money will fund. Only publish figures you have reconciled. If something is not yet confirmed, say so. Our guide to transparency and impact reporting covers how to present such numbers honestly.

Plugin or custom build

You can build event registration in several ways. The right choice depends on volume, complexity and how long you will run events.

Option 1: a WordPress plugin or a hosted event platform

Plugins can handle forms, ticket types, capacity and email confirmation quickly and cheaply, but QR check-in, waitlists, team pages and WhatsApp may need paid add-ons that must work together and be kept updated. A hosted platform launches faster still, at the cost of control: read its data terms, check where data is stored, and confirm you can export and delete your own participant records.

Option 3: a custom build on your NGO site

A custom module connects registration, capacity, fundraising pages, WhatsApp, QR check-in and your CRM in one system under your own rules. It costs more at the start and needs maintenance, and is justified when you run several events a year, need group or corporate registration, or want one view of each supporter across donations, events and volunteering. Our custom NGO website versus WordPress comparison explains the wider trade-off.

A hypothetical worked example

Imagine an NGO working on children's education in a mid-sized Indian city. It plans a Sunday morning walkathon with a 3 km family walk and a 5 km run. This is an illustration only; no real organisation or figures are described.

Planning and form: The team caps the walk at 600 and the run at 300, based on the permit and the marshals it can field. The form asks name, mobile, email, category and age band; the run adds an emergency contact and a fitness tick box. T-shirt size appears only because a sponsor is providing shirts. No ID numbers or addresses are collected, and a guardian registers each child and confirms consent.

Consent and fundraising: Three unticked boxes cover WhatsApp updates, newsletters and photographs. Participants may tick "create my fundraising page", a volunteer reviews each page before it goes live, and two local companies use team pages.

Confirmation, waitlist and volunteers: Participants receive an email with a QR code, and a WhatsApp template message if they opted in, with reminders five days and one evening before. The run fills in week three, so a waitlist opens with a 24-hour window to accept released seats. A separate volunteer form lists five roles with required numbers, and marshal slots are filled first.

Check-in and follow-up: Four volunteers scan codes on their phones, with the list downloaded the evening before because venue signal is uncertain, and a printed backup with the desk lead. A thank-you goes out that evening, a results page follows once the numbers are reconciled, and emergency data is deleted on the date promised in the notice.

The lesson of the example is not the numbers; it is that every step was decided before the form went live.

Working with Govindani Infotech on NGO events

Govindani Infotech, a Pune-based web development company, builds NGO sites, donation flows, WhatsApp automations and CRM integrations. For event registration, the usual work is the NGO website itself, a website creation project for the event module, WhatsApp flows for confirmations and reminders, and a CRM so that participants, volunteers and donors sit in one record with their consent status. If you are planning an event and want a scoped quotation, message us on WhatsApp at https://wa.me/919201958278 or use the contact page.

Frequently Asked Questions

What should an NGO event registration form ask for?

Ask for what you need to run the event: name, mobile number, email, category and, where relevant, an age band and an emergency contact. Add fields such as t-shirt size only if you provide the item. Avoid ID numbers, home addresses and anything you cannot link to a specific use, because Section 6(1) of the DPDP Act limits consent to the personal data necessary for the stated purpose.

How do we stop a walkathon or run from being oversold?

Set a capacity per category, reduce the count when a registration is completed, and hold seats briefly during any payment step. Open a waitlist when a category is full, with written rules for ordering and for how long a person has to confirm an offered seat. Ask your developer to test two people booking the last seat simultaneously.

Can we send event confirmations and reminders on WhatsApp?

Yes, if the participant has opted in and you use approved message templates through the WhatsApp Business API or a provider. Always send an email confirmation as the main record. Keep WhatsApp for event operations unless people have separately agreed to hear about other things, and check current template rules with your provider.

How do we handle children at a charity run or walkathon?

The DPDP Act defines a child as under 18 and, in section 9, requires verifiable parental or guardian consent before processing a child's data and bars tracking and targeted advertising aimed at children. In practice, have an adult register children, collect minimal data, keep children out of marketing audiences, and confirm the method the Rules prescribe with your legal adviser.

Is a plugin enough for NGO event registration, or do we need a custom build?

A plugin or hosted platform is often enough for one small event. A custom build makes sense when you run recurring events, need team registration, QR check-in, WhatsApp and CRM links in one place, and want control of your participant data. Compare data handling and export options before choosing either.

Sources: Digital Personal Data Protection Act, 2023 - Section 6 (DPDPA.com), Digital Personal Data Protection Act, 2023 - Section 9 (DPDPA.com), PIB - Digital Personal Data Protection Rules, 2025, notified, Vinsys - DPDP Act compliance deadline 2026, Meta - WhatsApp Business Messaging Policy, Meta for Developers - WhatsApp Business Platform message templates