A Referral Should Give Someone a Next Step They Can Actually Complete

Oct 6

Help community teams find the gaps between sharing a contact, making a connection, and receiving useful support.

By Arbab Naseebullah Kasi, Chief Executive Officer - CEO, Feel Worldwide Foundation Inc.

Someone leaves a community desk with a phone number written on a card. The volunteer has been kind, the organization is real, and the information is current. Yet the person may still have no workable route forward. What should they say when they call? Who is expected to respond? What happens if nobody answers? A referral can be accurate and still leave the hardest part of the process unexplained.

For a small nonprofit or volunteer team, the useful decision is where to add a little support without promising unlimited case management. Start by examining one handover between services. The aim is to make the next action, its owner, and the fallback clear enough that the person can choose how to proceed.

Look beyond the moment the information leaves your desk

A directory tells people where help might exist. A referral connects a particular request to a possible next service. Neither establishes that contact occurred, an appointment was arranged, or support was received. Keep those events separate. Otherwise, a team can report many referrals while knowing very little about whether anyone reached the next door.

The UK Government Digital Service recommends examining both the organizations delivering a journey and the steps people actually experience. Its guidance identifies dead ends, confusing content, and poorly connected online and offline steps as problems a shared map can reveal. Although written for government services, that distinction is useful for community teams: your internal process and a resident's actual experience are not necessarily the same. Read the UK government guidance on mapping a person's whole problem.

Choose a narrow boundary. Instead of mapping every service in town, examine what happens between a person asking about adult learning and speaking with the receiving program's intake team. Put each action on a separate card: hear about an option, decide whether to pursue it, make contact, receive a reply, clarify requirements, and agree on the next step. Include waiting. A silence between two actions can be the very place the connection breaks.

A fictional handover that looks complete too soon

Consider Daniel, a fictional adult learner who asks a neighborhood volunteer about an evening computer course. The volunteer gives him the training center's general number and records “referred.” Daniel calls during his lunch break. The recorded message directs him to an online form, but he cannot tell whether submitting it reserves a place. He waits for a reply and does not know whom to ask. The volunteer assumes the center has taken over; the center has not yet received a completed request.

No one in this teaching example has deliberately withheld help. The gap is between two organizations' assumptions. Daniel understands the next step differently from the volunteer, and neither has confirmed the center's intake process. An extra reminder to “call again” would repeat the instruction without resolving the uncertainty.

A better design begins with the receiving center. The volunteer lead confirms the current intake route, what a first inquiry requires, the response window the center can actually support, and whom the volunteer team should contact if that route fails. They also ask whether an assisted introduction is welcome. A small organization cannot accept a new handover responsibility merely because another organization has assigned it one.

Daniel can then choose whether to contact the center himself, receive help preparing his question, or join an agreed introduction. The volunteer explains that an inquiry is not enrollment and that the center decides availability and any entry requirements. Daniel's choice remains central. Declining help with the call does not mean declining the course.

Write one handover note both sides can understand

An original teaching tool for this situation is a short next-step note. It should explain the purpose, the action each person has accepted, the expected response, and the route back if the connection fails. Keep the participant's copy readable on paper as well as on a phone. It is a practical agreement about the next contact, not a guarantee of service.

In the fictional example, the note might read: “You want to ask about an evening beginner computer class. You chose to call the intake desk on Tuesday. Ask whether a place is available and whether the interest form must be completed before speaking with someone. If you have no reply by the response date the center confirmed, you may contact our volunteer desk during its stated hours. With your permission, we can help clarify the next step. We cannot reserve a place.” These details would need verification before use in a real referral.

Ask the person whether the note matches what they understood and whether the proposed route works for them. A phone call may be unsuitable for someone who needs another communication format. A web form may be difficult on a shared device. Ask about the task, not for a personal explanation they do not want to give. The U.S. Web Design System's continuity principle asks teams to make the next action clear and consider the full experience across services and devices. Its direct context is public digital services; the practical question also helps here. Read the USWDS design principles.

Learn from real journeys without collecting people's lives

A staff discussion produces a useful first sketch, but it cannot establish how people experience the process. Invite a small, varied group of adults who used the referral route to describe where they went next, what they understood, and where they had to stop. Include people who did not complete it when they are willing to participate. Do not label a missed connection as a lack of motivation.

UK government's experience-mapping guidance recommends capturing several people's experiences before combining them. It also advises separate maps when groups follow substantially different steps. A person who contacts a service independently may have a different journey from someone using an interpreter or assisted contact. Combining every experience into one neat line can conceal the obstacle you most need to understand. Read the experience-mapping guidance.

Explain the purpose of the conversation, what notes you will keep, who will see them, and that participation is voluntary. Permission to receive a referral is not permission to publish a story or share someone's information with another organization. The UK government research-consent guidance emphasizes understandable information about the research, data use, and the right to stop. Apply those ethical principles alongside your organization's applicable privacy and safeguarding procedures. Read the guidance on informed consent for research.

For a team planning sheet, “the form did not explain what happens next” is usually more useful than a detailed account of an individual's circumstances. Keep any necessary personal follow-up in the organization's approved system with appropriate access. Do not put names, contact details, or private explanations on a shared workshop wall. An improvement exercise should reduce the burden on people, not create another request to retell their lives.

Decide what your team can genuinely own

An assisted introduction takes time. Following every referral indefinitely may exceed a volunteer team's capacity, and transferring information can create risks. Agree on a limited offer: which kinds of routine referrals the team supports, who handles a stalled connection, when that person is available, and when further contact ends. Urgent or specialist needs belong in the relevant established response pathway, not an improvised volunteer experiment.

Use outcome labels that preserve uncertainty. “Information provided,” “contact attempted,” “connected to intake,” and “service received” describe different events. “Person declined follow-up” and “outcome unknown” are also valid records. The labels are a proposed local tool, not a universal reporting standard. Record only what is necessary and what you have permission to know; no reply should automatically become either a success or a failure.

For one routine referral route, review a small set of recent, appropriately recorded connections. Where do people most often become unsure, and which gap can the two organizations jointly change? Perhaps the answer is a clearer confirmation message or a named contact for failed introductions. Test that adjustment on a limited basis. Look for fewer unclear next steps and better-confirmed connections, while also checking the extra staff time. If the receiving service has no capacity, improve the explanation and explore verified alternatives rather than promising that a smoother process creates places.

This attention to coordination and practical local problem-solving connects with FWF's Community Engagement, Volunteerism & Local Action pathway. Choose one referral your team makes regularly. Ask the receiving organization what actually happens after the first contact, then write a next-step note you can both stand behind. Community organizations can connect with FWF to discuss learning and collaboration needs without sending private participant records.

Sources reviewed October 6, 2026. Daniel and the sample note are fictional teaching examples. This article offers general service-design education, not a statement of available FWF referral services.