Know the route, who decides, what you can choose and where to ask for help.

Begin with understanding

A pathway should not ask for trust merely because it looks polished or carries an institutional name. It should explain what it is for, who it is intended to serve, what its current status is and which institution is responsible for each material decision.

The Programme may make information easier to follow and support an authorised handoff. It does not decide whether a person is eligible, selected, admitted, assessed, awarded, licensed or accepted unless a controlling instrument gives that exact decision to a named competent entity. The relevant pathway must identify the actual decision-maker and must state the limit of every other role.

Who a pathway may be designed for

An approved pathway may describe an intended participant group so that people can judge whether it is relevant to them. That description should use necessary, respectful criteria. It should not reduce a person to a label, imply that a characteristic guarantees suitability or use broad identity categories as a substitute for an actual pathway purpose.

The directory may help a reader compare visible criteria. Only the competent institution or other authorised decision-maker can determine individual eligibility under the approved rules. Reading a page, creating an account or providing information does not guarantee that a person will proceed.

The journey is a set of visible states—not a promise of progress

The public pathway should tell a person where the route currently stands and what can happen next. A person may be able to read, consider, ask a question, provide information, receive a decision from the responsible institution, view a record or request correction. Those actions are not a guaranteed chain.

At any point, the pathway may require clarification, become unavailable, pause for review or end. A safe interface states the current position, the responsible actor, what the person needs to do—if anything—and what route exists for help or review. It never turns silence, delay or a technical error into a negative decision.

Before you begin

Before an action is enabled, the pathway should answer all of the following:

• What is the pathway for, and what is outside its scope?
• Who coordinates the route, and who makes the specialist decision?
• Which criteria apply, and where is the current version recorded?
• What information or documents may be requested, and for what purpose?
• Who may receive that information, and which parts are optional?
• What accessible format, communication or assistance routes are available?
• What records may be created, who issues them and what do they mean?
• What can be corrected, questioned or reviewed, and by whom?
• What is the pathway’s current status and last review date?

If a material answer is missing, the action should remain unavailable.

Your information and your choices

Every request for information should be proportionate to a defined purpose. The interface should explain why a field is needed, who is responsible for it, who may see it, how long it is expected to be kept and what happens if the person chooses not to provide it. Where a choice can later be changed, the change route and its practical consequences should be clear.

The Programme should not collect broad personal histories simply because they might be useful later. Information should be gathered at the point it is needed, protected according to its sensitivity and disclosed only to an authorised recipient for the stated purpose. These principles reflect widely used data-protection ideas such as purpose limitation, data minimisation and protection by design; the exact legal requirements depend on the real operator, activity and applicable law.²

Accessible participation is part of the route

Accessibility is not an additional page offered after a barrier appears. Instructions, forms, status messages, documents and help routes should be designed for keyboard use, screen readers, reflow, zoom, clear language and appropriate alternatives. Where an individual adjustment or another format is available, the pathway should explain how to request it without requiring unnecessary disclosure.³

An accessibility target is not the same as proven conformance. A public conformance statement may be made only after complete pages, responsive variants, interactive states and relevant assistive-technology journeys have been tested and known limitations have been recorded.

Language should preserve meaning

English is the controlled source for this content. Persian and Arabic require deliberate human transcreation because dignity, agency, authority and limitation language can be distorted by literal translation. French and Russian require professional parity review. The selected language, writing direction and language of any change in context must be declared correctly in the interface.⁴

When a pathway is ready

An enabled action belongs inside an approved pathway detail page. It should say exactly what it does—for example, “Read the participation requirements” or “Begin the approved information step”—rather than using an urgent or vague command.

The action should remain reversible where the pathway allows it. A person should be able to save, leave, return, ask for an accessible alternative or understand why the action is not available. The interface should not create artificial pressure.

Empty and disabled states

No approved pathways are visible

Programme services are introduced in defined phases. Before any public action becomes available, its responsible entity, authority, information safeguards, security controls and support route are confirmed and presented alongside it.

Participant action disabled

Programme services are introduced in defined phases. Before any public action becomes available, its responsible entity, authority, information safeguards, security controls and support route are confirmed and presented alongside it.

Accessible assistance route not yet active

Programme services are introduced in defined phases. Before any public action becomes available, its responsible entity, authority, information safeguards, security controls and support route are confirmed and presented alongside it.

Closing actions

View approved pathways Read Records, Rights & Help