Transform My Role, explained
How a practitioner turns any job posting into a personal transformation plan against the canonical future-ready counterpart in their jurisdiction — what the journey looks like, what the system reads, what it never stores, and how saving and sponsorship work.
Transform My Role is RPF's practitioner-facing journey: paste a job posting URL (or, with an explicit rights tickbox, the text or a file), and within one screen see a structured competence profile, a side-by-side gap against the canonical future-ready counterpart in your jurisdiction, a curated agent panel that answers questions about your plan, and an exportable personal transformation plan.
Three audiences read this surface differently. Practitioners lead — Transform My Role is RPF's practitioner-primary journey. Careers counsellors and educators read it as a roadmap-shaped artefact they can walk a learner through. Professional bodies read it as the consumer-facing reason to sponsor the canonical future-ready Role for their discipline in their jurisdiction.
What is Transform My Role?
Transform My Role is a public, anonymous-friendly route at /[lang]/transform-my-role that takes a job posting in three ways — paste a URL, paste text, or upload a PDF/text/Markdown file — and emits a personal transformation plan structured as: extracted Items + Information Uses + Role candidates, mapping confidence against the canonical RPF taxonomy, a synthesised gap against the future-ready counterpart in your jurisdiction, and a list of suggested next-step learning items.
It is computed, not authored. The plan is a live derivation over the inputs you provide and the canonical published Role + Profile in your jurisdiction. Nothing is persisted by default; the job description, URL, and any uploaded bytes are read in memory and discarded. Only a non-content audit row records that a session happened, in what mode, in what jurisdiction, with what outcome.
Three audience views
Transform My Role is practitioners-primary — the practitioner card leads. Counsellors and bodies are the secondary audiences this surface enables, not the primary readers.
What does this role become in five years in my market, and what's my journey? Paste the URL of the job you're looking at, or the role you're in today, and Transform My Role drafts a plan: where the future-ready bar sits for this discipline in your jurisdiction, what items you're already covering, what items you'd need to add, what IRI/ICI depth gaps you'd need to close. Open the conversational panel to dig into any row. Export the plan as HTML, PDF, or an Assessor.io template handoff. Save it if you want change notices when the future-ready counterpart evolves.
Walk a learner through a transformation. Paste the posting they're targeting; the plan becomes the structured artefact for the coaching conversation. The agent panel's curated questions ("What does IRI mean?", "Why is this missing?", "Show me materials") are designed to be opened together with a learner — the citations make every answer auditable.
Your members run Transform My Role against the canonical future-ready Role you sponsor for your jurisdiction. The diff between today's posting and tomorrow's canonical is what your members read. Sponsor the canonical and your jurisdiction's transformation arc lights up against every job-posting they paste in.
The canonical journey
- 1Open /[lang]/transform-my-role. No signup required to see the plan. Pick how you want to share the role: paste a URL (default), paste the description text, or upload a PDF / plain-text / Markdown file. URL fetch needs nothing more; paste-text and upload require an explicit rights-acknowledgement tickbox.
- 2We extract a structured competence profile — candidate Roles, candidate Items, candidate Information Uses — by running the parsed text through the action-statement extraction agent. The raw job description never leaves the request; only the parsed Markdown crosses into the agent surface.
- 3We resolve those candidates against the canonical RPF taxonomy: existing Roles by slug + IRI-shape match, with a future-ready counterpart picked from the role_archetype chain in your jurisdiction. Each match carries a confidence tier (Matched / Suggested / Low confidence).
- 4We synthesise a transient "current-state" Profile from the matched candidates and run it against the resolved canonical future-ready Profile using the same gap math as the org-level Profile Gap surface (computeProfileGap). The Profile Gap output is the same shape — ΔIRI, ΔICI, missing/extra items, IU coverage changes, material substitutions.
- 5We assemble the personal transformation plan: header + match summary + gap section + suggested next steps. The plan is rendered on the page and exportable as HTML, PDF, or an Assessor.io template handoff (the export endpoints land in a follow-up; the plan is fully generated today).
- 6Open the curated agent panel below the plan to ask: How was the role mapped? What does future-ready mean? Why does jurisdiction matter? What is the gap? How do I close it? Why is nothing saved? Each curated answer cites the candidate(s) it references and the Profile / Role IDs in the mapping resolution. Register and save the plan to get change notices when the canonical future-ready counterpart for your jurisdiction is updated.
What the system reads (and never stores)
The job description text, the URL, and any uploaded bytes are read in memory and discarded once the extraction agent has produced the structured candidates. Nothing is persisted to disk beyond a short-TTL quarantine path for upload bytes (hard-capped at 60 minutes). The audit row records only operational shape — mode, jurisdiction, locale, timings, outcome, whether you opted in to save. No URL, no host, no headers, no IP, no User-Agent. The agent panel's curated context is built from the structured candidates only — it never carries the raw job description.
Saving, subscribing, and registered-only features
Saving a plan is registered-only. The save action persists the structured features (extracted candidates, mapping, gap) and the assembled plan package — never the job description, the URL, or upload bytes. A defensive zod refinement rejects any payload carrying job-description-shaped keys at write time.
Saved plans live under /[lang]/me/transform-plans. Each plan can opt in to change notices: we email you when the canonical future-ready Role for your jurisdiction is updated (new IUs added, new citations, jurisdiction overlays added). The email never includes the job description — only the canonical-change summary plus a link back to your saved plan.
Known limitations
- Transform My Role works one posting at a time. "Transform my team" (paste five postings, roll up) is on the v2 roadmap, not in scope today.
- The URL fetcher does not crawl LinkedIn, Indeed, Glassdoor, or ZipRecruiter — those hosts are on the conservative no-crawl list. Paste the text instead.
- The agent panel is curated — pre-baked questions with cited answers. A free-form chat backend lands when the generic agent surface does (Phase 19 metro-map slice).
- Mapping confidence below 0.4 surfaces as Low confidence; below 0.4 with no runner-up surfaces the no-match empty state with a sponsorship CTA pointing at the body one-pager.
- Anonymous users cannot save plans. The plan is generated and viewable in the session, but persistence and change-notice subscription require sign-in. The job description is not persisted in either case.
Next steps
Anonymous-friendly. Paste a URL or text, or upload a file.
Sponsor the canonical future-ready Role for your jurisdiction
Your jurisdiction has no canonical future-ready counterpart for this discipline yet — sponsor one and every Transform-My-Role session in your market lights up against it.
