NGO / Nonprofit13 min read•

NGO Website Development in India: Building a Scholarship Application Portal — Mobile Forms, Document Upload, Reviewer Scoring and Consent for Applicants Under 18

How a trust should take scholarship applications online: eligibility pages, OTP login and save-and-resume forms, secure documents, reviewer scoring, parental consent, fraud checks and costs.

#NGO website development India#scholarship application portal#online application form#DPDP Act children#education trust website

An NGO that gives scholarships should take applications through a proper portal on its own website: a public page that states who is eligible and by when, a mobile-friendly form that saves progress, secure document upload, a private dashboard where staff screen and score applications, and status updates to every applicant. That replaces the usual mix of a Google Form, a shared email inbox and WhatsApp photos of marksheets, which loses documents, exposes families' personal data and leaves the trust unable to show a donor how selections were made. In NGO website development in India this is one of the most useful things a mid-sized education trust can build, and one of the most sensitive, because almost every applicant is a child or a young adult from a low-income family handing over income certificates, caste certificates and bank details.

This guide is for trustees, programme managers and CSR partners of foundations that run scholarship, fellowship or education-support programmes. It covers the public pages, form design for applicants on low-end phones, document handling, the staff workflow, consent and data protection for minors, fraud checks, reporting for donors, and what such a portal costs.

Why a form and an inbox stop working

Small programmes begin with a Google Form or a PDF sent by email. The problems appear at around a hundred applications.

  • Documents scatter. Marksheets arrive as WhatsApp photos to a field worker's personal phone, as email attachments and as form uploads into one staff member's Google Drive.
  • Nobody knows the status. Applicants call to ask whether the form was received. Staff answer from memory.
  • Incomplete applications cannot be chased because there is no list of what is missing for whom.
  • Selection cannot be explained. When a donor or auditor asks why student A was chosen over student B, the answer is in someone's notebook.
  • Personal data is everywhere. Income certificates and Aadhaar copies sit on personal phones and in inboxes long after the cycle ends.
  • Renewals start from zero. A second-year scholar fills everything again.

A portal fixes these by giving each application a record, a status and an owner.

The public pages

Before the form, applicants and the teachers or social workers who guide them need plain information. Build one page per scholarship scheme with:

  • Who can apply: class or course, institutions or districts covered, family income limit, minimum marks, any priority groups. State the numbers ("family income below ₹3,00,000 a year"), not "economically weaker students".
  • What the scholarship covers: amount or range, what it can be used for (tuition, books, hostel), duration and renewal conditions. If supporters also offer books, uniforms or laptops for scholars, route those offers through a separate in-kind donations page with a needs list and pickup form so they do not arrive unannounced.
  • How many awards are expected this cycle, if known, so applicants understand the odds.
  • Dates: opening, closing, when results will be communicated.
  • Documents needed, as a checklist, with acceptable formats ("a clear phone photo is acceptable").
  • How selection works: the stages and criteria, and who decides.
  • Language choice: English plus the main languages of your applicants. For Maharashtra that usually means Marathi and Hindi.
  • Help: a phone or WhatsApp number and hours, and a named contact.
  • A fraud notice: "We never charge a fee to apply. We will never ask for an OTP or your bank PIN."

Keep the page available after the deadline with a "closed; next cycle opens in June" message. Pages for annual schemes build search visibility over the years, since students search for scholarships by class, course and state. Using the same URL each year, updated, is better than a new page per year.

Designing the form for the people who fill it

Most applicants will use a parent's or neighbour's Android phone on mobile data, possibly at a cyber café. Design for that.

Structure

  • An eligibility check first. Three or four questions (class, family income band, district, marks). If the answers do not meet the criteria, say so kindly and point to other resources, instead of letting someone spend forty minutes on a form that will be rejected.
  • Login by mobile OTP, not email and password. Many applicants have no working email. Allow one phone number to manage more than one applicant, since siblings often share a phone.
  • Short steps with a progress bar: applicant details, family and income, education, bank details, documents, declaration.
  • Save and resume. Save automatically after each step, and send an SMS or WhatsApp link to return. This single feature does more for completion than any other.
  • Assisted applications. Let a registered teacher, field worker or partner NGO fill forms on behalf of applicants, recorded under that person's own login, with the applicant's or parent's consent captured.

Fields

  • Ask only for what you use to decide or to pay. Each extra field loses applicants and adds data you must protect.
  • Use the right input types: a number keypad for phone, PIN code and marks; date pickers that work without scrolling back twenty years; dropdowns for state, district and board.
  • Validate gently and in the applicant's language: "Mobile number must have 10 digits".
  • Explain why you ask sensitive questions. "We ask for category only where a scheme is reserved for specific groups."
  • For income, offer bands or an exact figure backed by a certificate. Do not ask for both.
  • Collect bank details only from shortlisted applicants, at a later stage, unless you truly need them at the start.

Low-bandwidth behaviour

  • Keep each page light; no large banners or sliders in the form.
  • Compress images in the browser before upload, so a 6 MB phone photo becomes a few hundred kilobytes.
  • Show upload progress and allow retry without losing the rest of the page.
  • Do not time out a session while someone is typing a long answer.

Our guides to websites for low-bandwidth mobile users and multilingual Hindi and Marathi sites cover the build techniques; the same principles apply to applicants as to donors.

Documents: upload, storage and Aadhaar

Typical documents are the latest marksheet, admission or bonafide letter, fee receipt or fee structure, income certificate, a photograph, a bank passbook front page and sometimes a caste or disability certificate.

Upload

  • Accept JPG, PNG and PDF; accept phone photos. Set a sensible size limit after compression (for example 5 MB a file).
  • Check the file type on the server, not only by its extension, and scan uploads for malware.
  • Show a thumbnail after upload so the applicant can see it is readable. Let them replace it until submission.
  • Mark each document as required or optional per scheme, and let staff request a re-upload of one document without reopening the whole form.

Storage

  • Store files in private storage that cannot be reached by a public URL. Staff view them through the portal after logging in, with short-lived links.
  • Do not email documents as attachments between staff. Share a link to the record.
  • Encrypt backups, and limit who can download in bulk.
  • Log who viewed or downloaded which document.

Aadhaar

Avoid collecting Aadhaar numbers or copies unless there is a clear legal basis and need. Where identity proof is required, accept alternatives, and if an applicant offers Aadhaar, ask for a masked copy showing only the last four digits (UIDAI provides a masked Aadhaar download). Never display or export full Aadhaar numbers. Take advice on what your trust may lawfully collect; this is an area where "everyone does it" is not a defence.

The staff side: from submission to payment

The private dashboard is where the portal earns its cost.

Stages

Give every application a status that moves through a defined path:

  1. Draft (started, not submitted)
  2. Submitted
  3. Incomplete (sent back for a document or correction)
  4. Eligible / Not eligible (after screening)
  5. Under review (scoring)
  6. Shortlisted (interview or home visit)
  7. Selected / Waitlisted / Not selected
  8. Award accepted
  9. Payment made (by instalment)
  10. Renewal due

What staff need at each stage

  • Screening: a checklist per application (income within limit, marks meet minimum, documents readable), with a reason code for rejection.
  • Scoring: a rubric with criteria and weights (for example, need 40, merit 30, circumstances 20, essay or interview 10). Two reviewers score independently; the system shows the average and flags large differences for discussion.
  • Conflict of interest: a reviewer can declare a conflict and is removed from that application.
  • Blind review, where practical: hide name, photo and religion or caste fields from scorers unless the scheme's criteria need them.
  • Interview and home-visit notes recorded against the application, with the visitor's name and date.
  • Committee decision: a final list with the decision, date and approver recorded. Changes after approval are logged.
  • Payment tracking: amount sanctioned, instalments, paid to (institution or student), date and reference. The portal records payments; the money itself moves through your bank as usual.
  • Renewals: existing scholars upload the new marksheet and fee receipt; their profile carries over.

Roles

Not everyone should see everything. Typical roles are administrator, programme manager, reviewer (sees assigned applications, perhaps anonymised), field worker (sees and assists their own applicants), finance (sees selected applicants and bank details) and donor or CSR partner (sees summary reports only). Bank details and income documents should be visible to the fewest people possible. Our article on CMS roles and staff access for NGO websites explains how to set this up, and the same discipline on two-factor login and backups described in donation website security applies here with more force.

Keeping applicants informed

Silence is the main source of calls and distrust.

  • Acknowledge every submission immediately by SMS or WhatsApp and on screen, with an application number.
  • Show status in the applicant's login: received, under review, action needed, decision.
  • Send targeted reminders: to drafts a week and two days before the deadline; to "incomplete" applicants naming the missing document.
  • Tell everyone the result, including those not selected, with a respectful message and, where possible, pointers to other schemes.
  • Use plain language in the applicant's chosen language.

For WhatsApp, use the Business API with approved utility templates and collect opt-in on the form. SMS to Indian numbers needs DLT-registered templates. Keep personal details out of the message body: "Your application GS-2027-0412 needs one document. Log in to see details" rather than naming the income certificate.

Consent and data protection, especially for children

A scholarship portal processes personal data of children and their families, including financial and sometimes health or disability information. Three things to get right.

Notice and consent

At the start of the form, in the applicant's language, state what you collect, why, who will see it (staff, reviewers, the funding partner if any), how long you keep it and how to withdraw or correct it. Ask for consent with an unticked checkbox, and record when it was given and from which phone number.

Applicants under 18

India's Digital Personal Data Protection Act, 2023 defines a child as a person under 18 and requires a data fiduciary to obtain verifiable consent from a parent or lawful guardian before processing a child's personal data. It also restricts tracking, behavioural monitoring and targeted advertising directed at children. The DPDP Rules, 2025, notified in November 2025, describe how verifiable parental consent may be obtained and set out limited exemptions for certain classes of organisations and purposes; most of the rules take effect 18 months after notification. Whether any exemption applies to a charitable trust awarding scholarships is a question for your legal adviser. In practice, build the form so that for an applicant under 18:

  • a parent or guardian's name, relationship and mobile number are collected;
  • the parent or guardian confirms consent through an OTP on their own number;
  • the record shows who consented and when;
  • no advertising or remarketing tags load on any portal page.

That last point matters more widely: keep Meta Pixel, Google Ads remarketing and similar scripts off the application pages entirely. Measure form completion with privacy-respecting analytics events that carry no personal data.

Retention and deletion

Decide and publish how long you keep data: for example, unsuccessful applications deleted or anonymised a fixed number of months after the cycle closes, and scholars' records kept for the period your auditors and funders require. Build the deletion into the system as a scheduled job with a report, not as a task someone is supposed to remember.

Stories and photos

Selection for a scholarship is not consent to appear in your annual report. Ask separately, later, and make it easy to decline with no consequence for the award. See our guide to beneficiary stories, photos and consent.

Guarding against fraud and impersonation

Scholarship programmes attract two kinds of fraud.

Fake or duplicate applications. Build in:

  • one application per applicant per cycle, checked on a combination of name, date of birth and institution;
  • flags when the same bank account or phone number appears on several unrelated applications;
  • verification of enrolment with the institution for shortlisted applicants;
  • a small first payment to confirm bank details, or payment directly to the institution where possible.

Impersonation of your trust. Fraudsters copy scholarship pages and collect "processing fees" from families. Reduce the risk by:

  • hosting the portal on your own domain (a subdomain such as apply.yourtrust.org is fine) with HTTPS, and stating on every page that this is the only official address;
  • stating clearly that applying is free;
  • sending messages only from named, published sender IDs and numbers;
  • publishing a page for reporting fakes.

Reports for trustees, donors and CSR partners

A well-built portal answers funders' questions in minutes:

  • applications received, eligible, shortlisted and selected, by scheme, district, gender and course;
  • amount sanctioned and disbursed, by instalment and funder;
  • scholars' progress: continuing, completed, dropped out, with marks where collected;
  • processing time from submission to decision.

Give CSR partners aggregated reports, or an anonymised view, not access to individual files. If a funder wants named data, check that your consent notice covers sharing with that funder. Our article on programme pages and impact reporting for donors and CSR covers presenting these results publicly.

Build options and what they cost

Option 1: form builder plus spreadsheet. A paid form tool with file upload and save-and-resume, feeding a sheet. Suitable for one scheme with under about a hundred applications. Cost is low (often under ₹15,000 a year in subscriptions), but there is no real workflow, weak access control and documents end up in a shared drive.

Option 2: WordPress with an application plugin or a customised form-and-workflow set-up. A reasonable middle route for a few hundred applications: OTP login, multi-step form, private file storage, basic stages and exports. Roughly ₹60,000 to ₹1,80,000 to set up, depending on languages, schemes and notifications.

Option 3: a custom portal. For several schemes, thousands of applications, reviewer scoring, renewals, payment tracking, role-based access and funder reports. Roughly ₹2,50,000 to ₹8,00,000 or more, depending on scope, over two to four months.

Running costs include hosting sized for the deadline-week peak, SMS and WhatsApp charges, backups, security updates and support during the application window. Budget roughly ₹40,000 to ₹1,50,000 a year for options 2 and 3.

Plan the timeline backwards from the opening date. A portal that opens in June needs the criteria, form fields and scoring rubric agreed by March; most delays come from deciding the process, not from writing the code. Test with five real students and a field worker before opening, and watch where they get stuck.

A worked example

This is an illustration, not a client case.

A Pune trust awards about 150 scholarships a year to first-generation college students from Maharashtra and receives around 1,800 applications by email and paper. In a portal build:

  • The scheme page is published in English and Marathi with an eligibility check. In the first cycle, a share of visitors are told at the first step that they do not meet the income or course criteria, and staff time on ineligible forms falls.
  • Applicants log in by OTP, complete six steps and upload five documents from a phone. Drafts receive two reminders before the deadline.
  • Twelve volunteer reviewers score anonymised applications on a four-part rubric, two per application.
  • The committee approves a list; selected students confirm bank details; payments are recorded per instalment.
  • The trust's CSR partner receives a district-wise and gender-wise summary, with no names.
  • Six months after the cycle, unsuccessful applicants' documents are deleted by a scheduled job, and the trust keeps anonymised statistics.

The number of awards does not change. What changes is that every decision has a record, applicants know where they stand, and sensitive documents are in one controlled place.

How Govindani can help

Govindani Infotech has built more than 500 websites and donation platforms for non-profits in India, including application and case-management portals alongside NGO websites. For scholarship programmes we build multilingual application forms with OTP login and save-and-resume, private document storage, reviewer scoring, payment tracking and funder reports, hosted on the trust's own domain. See NGO website pricing, or contact us or call 092019 58274 to discuss your next application cycle.

Frequently asked questions

How can an NGO accept scholarship applications online?

Publish a scheme page with eligibility, dates and a document checklist, then take applications through a portal on the NGO's own domain with mobile OTP login, a multi-step form that saves progress, secure document upload and an acknowledgement with an application number. Staff screen, score and decide in a private dashboard, and every applicant is told the result.

Is a Google Form enough for scholarship applications?

For a small scheme with a few dozen applicants, it can be. Beyond about a hundred applications, it becomes hard to chase incomplete forms, control who sees income and identity documents, record how selections were made and delete data afterwards. A portal with stages, roles and private storage handles these.

What documents should a scholarship application form ask for?

Usually the latest marksheet, proof of admission or a bonafide certificate, the fee structure or receipt, an income certificate, a photograph and bank details for those shortlisted. Ask only for what you use to decide or pay, accept clear phone photos, and avoid collecting full Aadhaar numbers unless there is a legal basis.

Do NGOs need parental consent to collect data from students under 18?

Under India's Digital Personal Data Protection Act, 2023, processing a child's personal data requires verifiable consent from a parent or lawful guardian, subject to limited exemptions set out in the rules. Collect the parent's or guardian's details and confirm consent by OTP on their number, and ask your legal adviser whether any exemption applies to your trust.

How much does a scholarship application portal cost in India?

As an indicative range, a WordPress-based set-up with OTP login, multi-step forms and basic workflow costs about ₹60,000 to ₹1,80,000, and a custom portal with reviewer scoring, renewals, payment tracking and funder reports costs about ₹2,50,000 to ₹8,00,000 or more, plus annual hosting, messaging and support.

Sources

About the author: written by the Govindani Infotech non-profit team in Pune, who have built donation platforms, application portals and CRM systems for more than 500 NGOs and trusts in India.

Need Help With Your Digital Strategy?

Govindani Infotech helps Indian businesses and NGOs build websites, run ads, and grow online. Contact us for a free consultation.