Online Referral Form Checklist: Collect Only What Your Community Service Really Needs

Scope: who this online referral form checklist is for

This online referral form checklist is for small charities, community services, advice projects, local support groups, and volunteer-led teams that receive requests for help through a website form. It focuses on the intake form itself: the questions someone sees when they are about to submit a self-referral, partner referral, volunteer referral, enquiry, or request for help. It is not a full guide to writing a service page, privacy notice, safeguarding policy, or case management process. Use it to make careful choices about field selection, consent wording, safe contact, attachments, urgent-help signposting, confirmation messages, and the internal handover after submission. Treat the examples as operational drafting prompts, not legal, safeguarding, clinical, or data protection advice.

Before you build the form: define the service, route, limits, and reader

The safest referral form usually starts with operational decisions, not form fields. If the service route is unclear, the form may ask for information the team cannot use, cannot review promptly, or cannot store safely. Before choosing questions, agree what the form is for. Is it an enquiry route, a referral route, a triage route, or a waiting-list request? Can people refer themselves, or must referrals come from professionals or partner organisations? Who receives submissions, how often are they checked, and what happens if a submission suggests immediate risk? This step also protects users. A person should know, before submitting, whether the form is likely to reach the right team and whether another route is needed for urgent help.

The core online referral form checklist

Use this as the main pre-publication checklist for the form. It is written for the moment before someone submits a request: what they need to understand, what the team needs to receive, and what should not be collected too early. A small service does not need a long form by default. It needs enough information to understand the request, contact the person safely, route the submission, and avoid misleading the sender about what happens next.

Data minimisation and sensitive information rules

A referral form should separate first-contact information from later assessment information. The first form may need enough detail to triage a request, but it should not automatically collect full case histories, documents, or sensitive records just because they might be useful later. For every proposed question, ask whether the team needs it at the first response stage. If the answer is “maybe later”, delay it. If a question may expose someone to risk, collect only what is needed, explain why, and make sure the submission is routed to a suitable monitored place. Do not send credentials, private records, analytics exports, screenshots containing private information, or identifiable sensitive records through general forms, email threads, or informal review routes.

Field-by-field recommendations: ask, make optional, avoid, or delay

The right fields depend on your service scope, referral route, and safeguarding responsibilities. The table below gives practical starting points for common referral form questions. Use required fields sparingly. A required field should normally be necessary for eligibility, safe contact, routing, triage, or permission to follow up. If a field is helpful but not essential, make it optional or ask it later.

Safety, safeguarding, urgent-help signposting, and internal escalation

An online referral form can make it easier for people to ask for help, but it can also create risk if users assume it is monitored continuously. If the form is not an emergency or urgent-help route, say so before submission and again in the confirmation message. For internal handling, decide what happens when a submission mentions immediate harm, abuse, homelessness that cannot wait, lack of food or medication, suicidal thoughts, domestic abuse, safeguarding concerns, or another serious issue relevant to your service. The form should not be the only place this process exists; volunteers and staff need a clear escalation route, named responsibility, and a record of action taken. Avoid routing sensitive submissions to unmanaged personal inboxes. Keep access limited to people who need it, and make sure the first reviewer knows what to do when a referral is outside scope or urgent.

Plain-language template structure and example microcopy

A simple community referral form can often follow this structure: 1. What this form is for: name the service, who it helps, and what kind of request the form covers. 2. If you need urgent help: explain what to do instead of using the form if the situation cannot wait. 3. Who is completing the form: the person needing help, a family member, a professional, a volunteer, a partner, or someone else. 4. Details of the person needing help: collect only the information needed to identify the request and contact them safely. 5. Safe contact preferences: ask how and when the person can be contacted, and whether any method should be avoided. 6. What help is needed: use a short summary box, relevant tick boxes, and clear boundaries that discourage unnecessary sensitive detail. 7. Permission or consent wording where relevant: explain what the team will do with the referral and what contact or sharing is being requested. 8. What happens next: set realistic expectations without promising a response time, outcome, confidentiality arrangement, or support route the team cannot guarantee. Example wording you can adapt: “Please give a short summary of the help needed. You do not need to include full records, documents, or detailed personal history at this stage.” “Tell us the safest way to contact you. If there is a phone number, email address, time of day, or message wording we should avoid, please say so.” “This form is checked by our team during our normal working pattern. If the situation is urgent or someone is at immediate risk, use the urgent help route listed above instead of waiting for a reply from this form.” “After you submit the form, we will review the information and decide the next appropriate step. Submitting the form does not guarantee that the service can provide support.”

After submission, review, maintenance, and related content links

The form is only one part of the intake process. After submission, the sender needs a confirmation message, the team needs a safe handover, and someone needs ownership of review and maintenance. Keep confirmation messages useful but limited. They should confirm that something was submitted, explain the next step if known, repeat urgent-help guidance where needed, and avoid exposing sensitive details in an email acknowledgement. Also review the live form when your service changes. If funding, eligibility, opening patterns, staffing, safeguarding routes, or partner referral processes change, the form may need to change too. Link the form clearly from the service page, and make sure it is consistent with your privacy information and any safeguarding or urgent-help information you publish. If those pages do not exist or are out of date, treat that as a content and governance task before promoting the form more widely. Capacity note: Chestnut Communities is not currently offering paid reviews, implementation, urgent support, support SLAs, or automatic AI replies. Use this checklist as a self-serve planning aid, and involve appropriate local leads or professional advisers where your form handles safeguarding, legal, clinical, or high-risk information.

Keep the form maintained

A referral form can become risky when nobody owns it after launch. Assign responsibility for checking fields, routing, wording, and internal notifications. Remove questions that are no longer used, and test the form as a real user would: on a phone, with plain-language expectations, and through the full back-office handover.

Field-by-field referral form recommendations

Data minimisation test for each proposed question

Submission and confirmation message requirements

Before-you-build referral form checklist

Core online referral form checklist

Ongoing review and maintenance checklist

Evidence boundary for this checklist

A referral form is not automatically an urgent-help route

Do not collect information just because it may be useful later

Frequently asked questions

What is the minimum an online referral form should ask?
At minimum, an online referral form usually needs to explain what service the request is for, who is completing the form, who needs help, how to contact them safely, what help is being requested, any essential eligibility or routing information, and what happens after submission. The exact minimum depends on your service scope, referral route, contact needs, triage process, and safeguarding responsibilities.

Should sensitive information be collected on the first referral form?
Collect sensitive information on the first form only when it is genuinely needed for eligibility, safe contact, triage, routing, or immediate safeguarding action. If detailed records, case histories, documents, health information, financial information, or legal details are not needed at first contact, delay them until a safer and more appropriate stage.

Should attachments be allowed on a community referral form?
Allow attachments only if they are essential at referral stage and your team has a safe way to receive, store, review, and delete them. Uploaded files can contain more personal or sensitive information than the team needs. If documents are not essential for the first response, ask for a short summary instead and request documents later through an appropriate route.

What should the form say about urgent help?
The form should say whether it is monitored for urgent requests. If it is not an urgent-help route, say that before submission and provide the correct alternative route for situations that cannot wait. Avoid implying that the form is checked 24/7 unless that is true and staffed.

What confirmation should someone receive after submitting a referral?
They should receive a clear confirmation that the form was submitted, a brief explanation of the next step if known, any safe contact reminder, and urgent-help guidance if relevant. Avoid repeating unnecessary sensitive details in email acknowledgements, and do not promise response times or outcomes the team cannot reliably meet.

Is this checklist a substitute for legal, safeguarding, or data protection advice?
No. This checklist is a practical planning aid for designing an intake form. It is not legal, safeguarding, clinical, or data protection advice. If your form handles high-risk, regulated, or sensitive information, involve the appropriate responsible people or professional advisers before publishing it.