Running an NGO takes time, money and people who care about the cause. But when someone hears about the organization and wants to know more, what will they find online?

A donor may want to see the projects before giving money. A volunteer may want to know what the organization does. A company may want to check its work before discussing a partnership. Someone looking for help may simply need a phone number or an address.

Without a proper website, finding those details can be difficult.

For an NGO that needs a simple website, a 72-hour project can be worth considering. Once the project is confirmed and the required information has been supplied, the site can work toward a 72-hour completion goal.

The first thing I would look at is the information people actually need.

The home page should tell visitors what the NGO does. The about page can explain how it started, its purpose and the people behind it. Other pages can cover its programmes, projects, events and ways to get involved.

A group working with children might show its education programmes and the communities it serves. An environmental organization could show its clean-up campaigns or conservation work. An NGO supporting families could explain the help it provides and who qualifies for it.

There is no need to fill the pages with big claims. Tell people what the organization does.

Pictures from real activities can make a big difference too. If the NGO has photographs from previous projects, they can be used to show the work instead of filling the site with unrelated images.

The number of pages will depend on the organization. Some may need only a few pages, while others may need more room for their programmes and projects.

This page about website pages available within a 72-hour project can help with planning. You can also see what is included in a 72-hour website package before deciding what the organization needs.

The design does not have to be flashy.

I would rather visit an NGO website that is easy to read than one filled with unnecessary effects. The name and logo should be easy to see. The menu should be simple. Important information should not be buried several clicks away.

There should also be a clear way to contact the organization.

That could be a phone number, email address, contact form or another method the NGO already uses. If the organization accepts donations or volunteers, those options should be easy to find.

For organizations thinking about how their site should be designed, this article looks at custom-designed 72-hour websites. There is also a comparison of custom and template websites.

One thing I would not leave out is the NGO's previous work.

People want to know whether an organization is actually doing what it says. A project page can show where a programme took place, what was done, when it happened and who benefited.

For example, instead of simply writing “we support local communities,” an NGO could describe a particular project and explain what was provided.

That gives visitors something they can understand.

The same applies to new work. When another project starts, the website can be updated. An event can be announced. A completed programme can be written about. A new volunteer opportunity can be posted.

The site does not need a new article every week. It just needs to reflect what is happening when there is something worth sharing.

An NGO starting its first website does not have to upload everything it has ever done. Start with the information people are most likely to look for. More can be added later.

The 72-hour timeframe also has limits.

A simple site containing information about the NGO, its projects and its contact details is one thing. A large system with donor accounts, private member sections, databases, payment functions and detailed reporting is another.

If the project needs that level of development, it should be treated as a larger project. A three-day target should not be used to pretend that complicated work is simple.

Getting the materials ready before development begins can save time.

The NGO should have its logo, photographs, written content, project information, contact details and other approved materials available. Someone should also be ready to check the pages and approve the final information.

The reason all of this matters is simple: people check organizations before supporting them.

A person may see a fundraising message on Facebook or another social platform and search for the NGO. A volunteer may want to know whether the organization is active. A company may want to see previous projects before making contact.

The website will not make that decision for them. It simply gives them somewhere to check the information.

Money is another issue, especially for smaller NGOs. There is no reason to pay for features the organization does not need. Start with what is useful and add more when there is a reason to do so.

The 72-hour website pricing information gives an idea of the available packages. You can also read about affordable website development within 72 hours.

Before publishing the site, check everything.

Make sure names are spelled correctly. Check telephone numbers and email addresses. Test forms. Open every important link. Check the project information and photographs. Then view the site on a phone.

These are small things, but mistakes on an organization's website can create unnecessary doubts.

An NGO does not need a huge website. It needs a place where people can find out what it does, see its work and know how to reach it.

For an organization with a defined project and its materials ready, working toward a 72-hour completion goal can get that first website online without turning the project into a long process.

After that, the site can be updated whenever the organization has something new to share.