How RPF handles jurisdictions
RPF content can be jurisdiction-agnostic or scoped to a specific market. The jurisdiction switcher in the header lets you pick the market you want to see.
Roles, profiles, information uses, materials and flows can each be marked as global (applies everywhere) or specific to a market. The jurisdiction switcher decides which slice of the catalogue you see.
Professional bodies see whether their market is covered; project leaders see roles relevant to where they operate; practitioners see the pathway that applies to them.
What the switcher changes
When you pick a jurisdiction, the public Roles, Profiles, Information Uses and Flows lists narrow to content that is either global or scoped to that market. Content scoped to other markets is hidden.
Picking 'Global' (or clearing the choice) shows the entire catalogue across every market. The switcher narrows; it never hides global canonical content.
How your jurisdiction is chosen
On every request RPF resolves your active jurisdiction in this priority order:
- 1An explicit ?j= market in the URL — used for sharing a market-specific link. It applies for that visit.
- 2Your saved choice — your account preference if you are signed in, otherwise the choice remembered in this browser.
- 3Otherwise, Global — the full catalogue with no market filter.
Switching markets
Use the jurisdiction control in the top-right of the header, next to the language toggle. Click the round pill — it shows your current market — to open the market menu, then choose one. Your choice takes effect immediately.
Market recommendation
If you have not chosen a market and RPF can tell which country you are browsing from, a banner appears suggesting your local market. It is only a suggestion — RPF never switches your jurisdiction automatically. Switch from the banner, or dismiss it and stay on Global; once dismissed, it does not return.
