Nonprofit Service Page Checklist: Make Each Service Clear Before People Ask for Help

Why service page clarity matters

When someone lands on a service page, they are usually trying to make a practical access decision: Is this service for me, can I use it, how do I start, and what happens next? That visitor may be a potential participant, family member, carer, community partner, professional referrer, volunteer, or member. They may already be unsure whether they qualify, whether the session is running, whether there is a cost, or whether calling is the right first step. This nonprofit service page checklist focuses on individual pages for services, groups, sessions, advice routes, activities, and member benefits. It is not a homepage audit, a full website review, or a replacement for your safeguarding, consent, referral, privacy, or professional judgement processes. The aim is simpler: make each offer clear enough that a visitor can decide their next step without having to guess.

Quick answer: the core nonprofit service page checklist

If you only have time to review one page today, use this list. A clear service page does not need to be long, but it should answer the access questions that decide whether someone can use the service.

Before writing: define the page’s job

Before drafting, write one sentence for the page’s job: This page helps [type of visitor] decide whether [service or offer] is right for them and take [next step]. That sentence keeps the page focused. If the page is trying to explain everything about a programme, persuade funders, brief partners, and collect referrals at the same time, the visitor’s access decision can get buried. A separate service page is usually useful when the offer has its own eligibility, location, format, cost, booking route, referral criteria, privacy considerations, waiting list, or next-step process. A shared listing may be enough when several offers are genuinely similar and a visitor can decide from a short description, date, and single access route. For example, a weekly drop-in café, a phone advice line, and a referred counselling service probably need different page patterns because people access them in different ways. Three craft sessions with the same audience, venue, cost, and booking route might sit comfortably in one activities listing. If you are unsure, ask: Would a first-time visitor need more than a sentence or two to decide whether this is for them and how to start? If yes, give the offer enough space.

Checklist items 1 to 3: describe the service, who it fits, and how people access it

The top of the page should answer the first three questions quickly: What is this, is it for me, and how do I start? 1. Say what the service is in one plain-language sentence. Avoid leading with internal project names, funding labels, or organisational shorthand. A visitor should not have to know your programme structure to understand the offer. For example: “A weekly in-person support group for unpaid carers in Northfield” is clearer than “Carers Wellbeing Pathway”. 2. State who the service is for. Include the practical fit details that affect access, such as age, area, membership status, referral need, lived experience, family role, or professional relationship. Use positive wording first: “This group is for…” Then add limits only where they are needed for a visitor to self-select. 3. Explain exactly how to start. Name the route and make it visible near the top of the page. If people can self-refer, say so. If a professional referral is required, say who can refer and what the person can do if they are not already connected to that professional. If the route is drop-in, explain whether people need to book first or can simply arrive. Try not to present several equal calls to action unless each one has a clear purpose. If email is for questions, a form is for referrals, and phone is for access needs, label them that way.

Checklist items 4 to 6: make availability, place, format, and cost clear

Once someone thinks the service might fit, they need to know whether they can realistically use it. 4. Show availability. Include days, times, frequency, term dates, appointment windows, seasonal pauses, or waiting list status where relevant. If the pattern changes, explain how the page is kept current rather than leaving people to wonder. For example: “Sessions usually run on Tuesdays during term time. This page was reviewed on 12 March 2026.” 5. Make place and format clear. Say whether the service is in person, online, by phone, by outreach, or blended. For in-person services, include the address or area, plus practical access details where useful: entrance notes, public transport, parking, accessible toilets, step-free access, or what to do if someone has access needs. For online or phone services, explain when the link or call details are shared. 6. State the cost. If it is free, say that plainly. If there are charges, suggested donations, concessions, membership fees, deposits, or materials costs, explain how they work. If the cost varies, give the visitor a safe way to check before committing. Avoid making people contact you just to discover whether they can afford to take part, unless there is no practical alternative.

Checklist items 7 to 8: explain what happens next and set contact boundaries

A service page should not stop at the first action. People also need to understand what happens after they click, call, email, book, or arrive. 7. Explain what happens next. If someone fills in a form, will they receive confirmation? Will a team member call? Will there be an assessment, welcome conversation, waiting list, appointment offer, membership step, or referral review? If they attend a drop-in, should they bring anything? If you cannot commit to a specific response time, do not invent one. Use wording your team can responsibly maintain. 8. Set contact boundaries. Say when the route is monitored, what it is for, and what it is not for. If the service is not an urgent or crisis route, say so clearly and signpost an appropriate urgent alternative for your context. If the page covers sensitive needs, safeguarding concerns, advice, or support, make escalation routes and human responsibility visible. Do not imply that an inbox, form, or voicemail is monitored continuously unless it is. Clear boundaries are not unfriendly. They help visitors choose the right route and help staff avoid receiving requests that the service cannot safely handle.

Checklist items 9 to 12: collect information safely and keep pages consistent

The final items are about safety, maintenance, and repeatability. 9. Only ask for information needed at this stage. A first-contact form might need a name, contact method, location, age range, or brief fit question. It may not need detailed personal history, documents, or sensitive records. Explain why you ask for information, link to privacy information, and think carefully before asking for uploads or detailed disclosures. 10. Make the page accessible and respectful. Use plain language, clear headings, descriptive links, and a tone that does not shame or discourage people. If people can request access adjustments, language support, communication support, or a different contact route, say how. If a professional referrer is the main reader, still write in a way that the person using the service could understand. 11. Assign a page owner and review point. Service details change: staff, locations, waiting lists, dates, costs, eligibility, and referral routes. Add a review date or internal update process so accuracy is not left to chance. 12. Use the same service-page pattern across similar offers. If one page puts cost at the top, another hides it in an FAQ, and another leaves it out, visitors and staff have to relearn every page. A consistent pattern also makes it easier for a team member or volunteer to spot missing details before publication.

Copyable charity service page template and final pre-publish test

Use the template below as a working page draft. Copy it into a document or your website editor, fill in each row, and remove any fields that genuinely do not apply. If a row is difficult to complete, treat that as a useful prompt: the service detail may need a decision before the page goes live. Before publishing, ask someone who did not write the page to read it as a first-time visitor. This could be a colleague, trustee, volunteer, or service team member. Give them a simple fictional scenario and ask them to answer the access questions without extra explanation from you. This article is intended as a self-serve checklist. Chestnut Communities is not currently offering paid reviews, implementation, urgent support, or automatic AI replies.

Copyable charity service page template

Quick answer: nonprofit service page checklist

Final pre-publish access test

Collect only what you need at this stage

If a detail changes often, show how it is maintained

Self-serve support note

Frequently asked questions

What should a nonprofit service page include?
A nonprofit service page should include a plain-language description, who the service is for, key eligibility or location criteria, how to start, availability, place and format, cost, what happens next, contact boundaries, privacy signposting, and a review process. For services with sensitive or urgent needs, it should also make escalation routes and response limits clear.

Does every service, group, session, or member benefit need its own page?
No. A separate page is most useful when visitors need distinct details to decide whether and how they can use the offer, such as different eligibility, referral routes, times, locations, costs, privacy considerations, or next steps. A shared listing can work when offers have the same audience, access route, and practical details, and a short entry gives enough information.

How much eligibility detail should a charity service page include?
Include enough eligibility detail for a visitor to self-select without guessing. Start with who the service is for, then add practical criteria such as area, age, membership, referral route, or circumstances where relevant. If there are exclusions or limits, explain them carefully and signpost alternatives where you can. Avoid asking people to prove eligibility before that information is needed.

Should we publish costs, availability, and waiting list information if they change?
Yes, if those details affect whether someone can use the service. If a detail changes often, publish the most useful stable information and show how it is maintained, such as a review date, named update owner, or instruction to check before travelling. Avoid hiding important access details simply because they require upkeep.

What should happen after someone fills in a form, emails, or calls?
The page should explain the next step the team can realistically provide. That might be an acknowledgement, a call back, a referral review, a waiting list update, a booking confirmation, or advice to attend a drop-in. If the route is not monitored continuously or is not suitable for urgent help, say so and provide an appropriate alternative for urgent situations.