A small NGO website should help someone get an answer. Can I use this service? Where does this organisation work? How do I volunteer? Who can I contact?
I would build around those questions before discussing sliders, animations or a large photo gallery. A clear, maintained website can be modest. Its job is to explain the work honestly and make the next step easy.
This is a practical planning guide for a small organisation, not a list of legal requirements or a claim that every NGO needs the same website.
Start with the person who needs help
A potential service user and a potential partner may arrive with very different questions. Write down the two or three most important audiences, then the task each person needs to complete.
For example, a fictional community training group might need visitors to find a course, check who can apply and ask about the next session. Those tasks should be easy to reach from the homepage. A long message from the director can sit elsewhere.
NCVO's website planning guidance makes a useful point: understand what people need before deciding that a new website is the answer. Ask a few people who actually use your services to try the current information first.
A useful five-page starting point
- Home: a plain explanation of the organisation, its work and the main next steps.
- Our work: current activities, where they happen and who they are intended for.
- Get support or get involved: eligibility, practical steps and a contact route.
- About: the people responsible, background and verifiable organisational details.
- Contact: current contact information, hours if relevant and what to expect after enquiring.
These are starting roles for pages, not a compulsory menu. An organisation with one activity might combine several of them. A group handling several services may need a separate page for each.
If you publish registration details, reports, partner names or achievements, check that they are accurate and that you have permission to use any partner logo. Do not leave placeholder statistics on a live page.
Turn an activity into information someone can use
“We empower communities through development initiatives” sounds important but tells a visitor very little. Try a structure like this instead:
We run [activity] for [intended participants] in [area]. Sessions take place [when and where]. To ask about joining, contact [team or role] through [channel]. We will explain [eligibility, availability and next steps]. Information last checked: [date].
Use actual details. If the next date is not confirmed, say that. If a programme has ended, mark it as completed rather than allowing an old announcement to look current.
For local audiences, consider a Bangla version of essential service information before translating every historical report. Give both versions someone responsible for keeping them accurate. An outdated translation can be more confusing than a smaller, well-maintained set of pages.
Make it readable on an ordinary phone
Put essential details in the page itself, rather than only inside a poster or a downloadable document. Use clear headings, readable text and links that explain where they lead. Describe meaningful images for people who cannot see them. These practices are also covered in the W3C's accessible writing guidance.
Test the page on a small screen. Can someone find the relevant activity, understand what to do and contact the right person without pinching and zooming? Keep large images under control so the page does not depend on a fast connection.
Keep trust practical
Photographs can help explain the work, but they should not expose someone or suggest a story that is not theirs. Use images you are entitled to publish and think carefully about consent and identifying details. The AI-generated cover here depicts an imagined office, not an NGO that TapuLab has worked with.
Keep a basic public enquiry form short. Do not ask people to submit sensitive case histories just to make initial contact. Work out a suitable process separately if the organisation needs to collect sensitive information.
Before launch, assign a named person to review the site and a backup person to receive enquiries. Check dates, contact details and forms on a routine you can actually maintain.
If the website is ready but replies keep getting missed, the next problem is the workflow. Read my Bangla guide to tracking customer enquiries, or talk to me about a practical NGO website.