A welcome, not an inventory
Your Nonprofit Has Several Ways to Help. Does a New Supporter Know Where to Start?
Giving, volunteering, and participating are different commitments. A generous Get Involved page helps a person recognize the right next step before asking them to make it.
Caring is not the same as knowing what to do
A person can believe in an organization’s work and still close its website without acting.
They may have arrived through a neighbor, a local story, a school, or a photograph that made the mission feel close. They are interested. Then they encounter a page full of possibilities: donate, become a partner, join the movement, volunteer, attend, sponsor, advocate, subscribe, give monthly, start a team.
Every option may be worthwhile. Together, they can feel like being handed the entire organization chart at the front door.
I have a great deal of respect for the people who keep nonprofits moving. Their work often depends on many forms of contribution, and they have good reasons for valuing each one. The website’s job is to translate that internal richness into a first choice a newcomer can understand.
The person should not need to know the names of programs, committees, or campaigns to begin helping.
The first page has a smaller job than the organization
A Get Involved page does not have to contain every instruction for every form of support. It needs to help the visitor choose a route and understand what the next page will ask of them.
That is a different task from writing a donation policy, recruiting for a specific volunteer role, explaining a grant transition, or documenting a sponsorship agreement. Those subjects need their own details. The first page should lead to them clearly.
I would begin by writing three ordinary sentences from the visitor’s point of view: I want to give money. I want to give time. I want to attend or take part.
Some organizations will need additional routes. Advocacy, professional partnerships, or participation in a service may require distinct treatment. The categories should follow the actual work and the people trying to use the site. Three is an example, not a mandatory navigation system.
The test is whether someone unfamiliar with the organization can explain the choices in their own words.
Separate the kind of help from the size of the commitment
Giving money, giving time, and attending an event are different actions. Within each action, the commitment can vary.
A person may be ready to make one gift but not to begin recurring support. A potential volunteer may have one Saturday available but be unable to commit weekly. Someone may want to attend an introduction before deciding whether to participate more deeply.
Mixing all these possibilities into one undifferentiated appeal asks the visitor to solve two problems at once: what kind of contribution fits, and how much they are ready to commit.
A better first route establishes the type of action. The next layer explains its available forms and conditions. For volunteering, that might mean occasional opportunities, regular roles, or a first conversation. For participation, it might mean a public event, a workshop, or a member activity.
Do not invent a low-commitment option because it would make the page more attractive. If every available role requires training and a regular schedule, say so. A clear boundary is more respectful than an easy invitation that turns into a surprise obligation.
A fictional food organization gives us a useful test
Imagine a fictional neighborhood food organization with three current needs: financial support for its work, volunteers for scheduled packing sessions, and attendees for a public introduction evening.
A weak first page might present three buttons labeled “Make an impact,” “Join our family,” and “Be the change.” The phrases convey enthusiasm, but they ask the visitor to guess what will happen after clicking.
A clearer version could use the following routes. These are sample labels and information requirements, not actual opportunities or promises.
On a narrow screen, scroll the table horizontally.
| Route | What the visitor needs to know before choosing | What the destination should provide |
|---|---|---|
| Give toward the work | The purpose of financial support and the available giving options | Clear gift choices, relevant terms, and a usable completion process |
| Help with a packing session | The task, typical commitment, location, and any preparation | Current opportunities, requirements, availability, and the next step |
| Come to an introduction evening | What the evening covers and who it is for | Date, access information, registration requirements, and a contact |
The page is not less inspiring because its links have become more precise. It is giving the inspiration somewhere to go.
Explain the commitment before the form
A form is a poor place to reveal that volunteering requires six months of weekly availability or that an event is intended for an audience different from the one the visitor imagined.
Put the consequential information before the person begins. For a role, that may include the task, time pattern, location, preparation, screening, supervision, and how the organization will respond. For an event, it may include the format, duration, access arrangements, cost if any, and whether registration is required.
The first page can summarize these matters and link to the complete explanation. It does not have to become a dense manual.
The same principle applies to giving. A person should be able to distinguish a one-time gift from recurring support and understand the relevant option before completing it. The specific financial, tax, and policy language should come from the organization’s approved information.
Good navigation makes the nature of the decision visible. It does not use ambiguity to move somebody farther into a process than they intended.
Make the question route part of the design
Some visitors will not fit neatly into the main paths. A local business may want to offer a service. A parent may need to ask whether a teenager can participate. Someone may want to attend but be uncertain about an access arrangement.
A useful page gives those questions a route without turning every uncertain visitor into a general inbox problem.
The contact choice should explain its purpose. “Questions about volunteering” is more helpful than a row of staff names that requires the visitor to know who manages what. If the organization uses one contact form, a small number of clear subjects can help route the message internally.
Only ask for information needed to handle that inquiry. A person asking whether a session is accessible should not have to complete a full volunteer application first.
The destination needs an owner. It also needs a realistic explanation of what happens next, based on the organization’s actual process. Do not promise a response time because it looks reassuring if no one has confirmed that the team can meet it.
Write links that survive outside the paragraph
People encounter links in different ways. Some scan visually. Some navigate with a keyboard. Some use assistive technology. Repeated “Learn more” labels can force extra work when the surrounding context is not readily available.
The W3C’s guidance on link purpose explains why the destination’s purpose should be understandable from the link and its available context. For this page, the practical writing habit is straightforward: describe the next step.
“See current volunteer opportunities,” “Read about monthly giving,” and “View the introduction evening details” make different promises. The destination should fulfill the one the link makes.
A button’s emotional tone cannot compensate for a mismatch. If “Volunteer now” opens an information request rather than an opportunity list or application, a more accurate label can prevent confusion.
Clarity is also kind to the staff. Better questions at the beginning can reduce the number of people who arrive at the wrong process and need to be redirected later.
The destination should remember why the person clicked
A visitor who chooses a packing session should arrive at a page that continues that thought. If the next page opens with the organization’s complete history and hides opportunities near the bottom, the first page has only moved the confusion.
The destination should establish the action quickly, explain the relevant conditions, and present the next usable step. It should also allow the person to return to other ways of helping without losing their place.
This is especially important when a third-party system handles registration or giving. The visual design may change. The organization can still explain the transition and make the purpose clear before sending the visitor away.
Test the whole route, including confirmation and any follow-up message. A good first page cannot repair a broken destination, a confusing account requirement, or a confirmation that fails to say what the person has actually completed.
The journey ends when the visitor understands the result and the next responsibility, not when a button has been clicked.
Forms should help people finish accurately
The W3C’s form-label guidance and instructions guidance offer useful foundations: controls need clear labels, and people need the information required to complete them.
For a nonprofit, that may mean explaining why a field is requested, distinguishing required information, and making errors understandable. A visitor should not have to guess which phone format the system wants or lose a completed response because one field needs correction.
Keep the first interaction proportionate. A full application may be appropriate for a role with substantial responsibilities. It may be unnecessary for someone requesting the date of an introductory meeting.
Accessibility also belongs in the ordinary design review. Check keyboard operation, visible focus, readable text, contrast, headings, mobile layout, and the behavior of error messages. A page that looks welcoming but cannot be completed by part of its audience is leaving important work unfinished.
The invitation should be usable by the people it addresses.
Capacity is information, not an embarrassment
Sometimes the organization has enough volunteers for a particular activity. Sometimes the next session is full. Sometimes a program is temporarily unable to take new participants.
The page should say so and offer an appropriate next step where one exists. That might be another current opportunity, a clearly explained interest list, or a date when information will be updated.
Avoid collecting applications into a process nobody is currently able to manage. Interest has value, but so does the visitor’s time.
An interest list should also be described accurately. Joining one is not the same as receiving a place. If the organization cannot predict when an opening will occur, it can say that plainly.
This connects to the broader issue in The Capacity Behind Nonprofit Impact. The first-choice page should reflect the work the organization can actually support, not an ideal version of capacity that exists only in the appeal.
Measure a next step that means something
Clicks can reveal which routes attract attention. They do not tell the whole story.
For the fictional food organization, the useful outcomes differ by path. A giving route might be examined through completed gifts and comprehension of the selected option. A volunteering route might be assessed through appropriate inquiries, completed onboarding, and attendance at the agreed session. An introduction evening might be evaluated through registrations, attendance, and the questions participants still have afterward.
Use measures appropriate to the actual systems and permissions. Do not assume that a tracking platform can identify every step across devices or third-party services.
The point is to connect the page’s promise to a meaningful result. A high click rate paired with repeated confusion may indicate that the labels attract attention without preparing people well.
Likewise, fewer applications can be a positive change if the page now explains the commitment and the people who proceed are better matched to the role. Volume should be interpreted beside fit, completion, and staff capacity.
Read the questions the page creates
The organization’s inbox can reveal information a dashboard misses.
Are people asking whether a one-time volunteer opportunity exists? Do they think an event is a service appointment? Are they unclear about where activities take place? Do they assume a registration is confirmed when it is still awaiting review?
Group recurring questions by the point in the journey where the answer should have appeared. Then improve that point. Do not respond to every confusion by adding another paragraph to the first page.
Some answers belong in a route summary. Others belong beside a form field, on an event detail page, or in the confirmation message. A coherent system distributes information according to the decision being made.
The staff should be able to recognize the visitor’s route too. If someone contacts the organization after clicking “Questions about volunteering,” that context should reach the person who replies where the system supports it.
A small test with people who are new to the work
Give a few people an ordinary task without explaining the site first. Ask one to find an occasional opportunity, another to learn how to make a gift, and another to decide whether the introduction evening suits them.
Watch where they hesitate. Ask them to explain what they expect the next page to do before clicking. Afterward, ask what they believe they have completed and what will happen next.
This is a practical usability exercise, not statistical proof that the entire audience will behave the same way. It can still expose a label that insiders understand and newcomers do not.
Test on a phone as well as a larger screen. Include the real destination systems and confirmation steps. If the task crosses into an email or third-party form, that handoff belongs in the review.
A route should remain understandable after it leaves the page you designed.
Keep the welcome current
Every route needs an owner who can confirm whether its opportunities, requirements, and destinations remain accurate. A beautiful page with an expired event and an unattended volunteer form gradually teaches visitors not to rely on it.
A simple maintenance record can name the route, responsible person, last review, and next known change. The review should follow the organization’s operating rhythm. An event schedule and a general giving explanation may need different frequencies.
Keep broader subject matter in its proper place. A grant ending requires a specific explanation of program continuity; that discussion already has its own article. In-kind giving needs the organization’s actual acceptance and handling process. The Get Involved page should route those needs without trying to become every policy at once.
The wider fundraising advisory page considers the relationship beyond the first choice.
Make room for a person to begin
A newcomer does not owe the organization an immediate maximum commitment. They may be offering an afternoon, a first gift, a question, or the willingness to come and listen.
A generous page recognizes that beginning. It explains the choices without ranking people by what they can currently provide. It makes the work understandable and lets the person find a contribution that fits.
The organization can still be ambitious. It can still explain the importance of sustained support. It simply starts by helping someone take one clear, appropriate step.
That is how a page becomes a welcome rather than an inventory.
Continue the thought
Questions worth
answering.
Should donate, volunteer, and attend have equal visual emphasis?
Not necessarily. The organization’s current priorities and audience needs should guide emphasis. Each available route should still be understandable, and the design should not disguise the nature of a commitment.
What if we have no occasional volunteer opportunities?
Say so. Explain the available roles and their requirements. An honest description helps people decide whether the opportunity fits and prevents avoidable disappointment.
Are more form submissions always better?
No. Examine whether the submissions are appropriate, understood, and manageable. A useful route connects interest to a meaningful next step the organization can support.