The journey belongs in the service plan

What we found in the news

The World Health Organization’s Global age-friendly cities guide (opens in a new tab), published in 2007, states in its overview a useful view of older people:

“Older people are a resource for their families, communities and economies”

— World Health Organization, October 5, 2007

The overview goes on to place that contribution within supportive living environments. This is longstanding guidance, rather than a new study. We return to its starting point because it treats people as participants in community life.

Our operational reflection concerns one part of making participation possible: the journey to and from a service.

Why this matters to us

Imagine a community program offers an activity that someone would like to join. The room is welcoming, the information is clear, and the time initially seems suitable.

Then the person checks the journey. The bus arrives well before the building opens. The return service leaves shortly before the activity finishes. A different route requires an unfamiliar change.

From the program’s side, the place is available. From the person’s side, the offer still needs work.

At genus, we think the journey belongs in the service conversation. It can reveal practical choices that an attendance list alone cannot explain.

Ask people to describe the trip

Invite participants to explain how they would get there and home. Ask what they need to know before setting off and where the journey becomes uncertain.

Some people will have an arrangement that works well. Others may want help finding information, checking an entrance, or understanding where to wait. Avoid assuming that everyone has a family member available to drive.

Include people who have declined an offer or stopped attending, where they are willing to speak. Their experience may reveal a barrier the regular group has already found a way around.

Keep the conversation open. A person may choose not to make a particular journey for reasons that do not require fixing.

Connect the timetable with arrival and departure

Look at the service schedule alongside the travel arrangements people actually use. When can someone enter the building? Is the appropriate colleague present? What happens if an arrival is delayed?

Work through departure with the same care. A participant should know where to wait and whom to ask if the expected arrangement changes. Staff need to understand the boundaries of their responsibility and the organization’s approved response.

Where another provider is involved, confirm the relevant details with them rather than relying on an old leaflet or a colleague’s memory. Describe what is confirmed and what the person will need to arrange independently.

Do not imply that transport is part of the offer unless it has been agreed.

Try a practical adjustment and listen again

The useful response may be modest. Clearer arrival information, a different start time, or an agreed place to wait could be worth exploring. Each option needs checking against staffing, venue access, and the preferences of the people using the service.

Discuss the trade-offs openly. Moving a session to suit one bus route might make it harder for someone else to attend. Ask who would be affected before presenting the change as an improvement for everyone.

After trying an adjustment, invite feedback about the whole journey. Did the explanation match what happened? Was the return trip workable? What remains uncertain?

Keep the result in the operational review so that the same question does not disappear between transport, reception, and program planning.

What this means for the people you serve

People bring their own experience of travelling, timing, and asking for assistance. Let that knowledge shape the arrangements. Offer clear choices without assuming dependence or insisting on independence. The person should be able to explain what support, if any, makes the trip workable for them.

The genus connection

Today, configured genus experiences can provide program information, resources, and staff workflows suited to the organization’s services.

Those tools can help make agreed information available. They do not establish transport availability, guarantee an accessible journey, or coordinate an external provider automatically. The organization still needs to verify the practical arrangements and keep the explanation current.

One question for your next team meeting

If we followed someone’s whole journey to our service and home again, what would we notice that our timetable does not show?