What a role map is not
A role map is orientation — not a job description, a competency framework, or a statement of what any employer expects of you.
You work out how to get a product approved — which country first, which route, what evidence regulators will want — and you keep that plan honest as the science develops.
You build the regulatory strategy across regions, use scientific advice and pre-submission meetings deliberately, structure dossiers to ICH M4 (CTD), plan lifecycle change under ICH Q12, and assess how a development decision today constrains a filing three years out.
Regulatory strategy is where commercial ambition meets what the evidence will actually support, and the value of the role lies in saying so early rather than defending an untenable position at a filing meeting.
YOUR NEIGHBOURHOOD, IN ONE CONNECTED SYSTEM
Between development and the regulators, translating in both directions before either has committed.
- Target product profile and development plan
- Data emerging from non-clinical and clinical programmes
- Submission assembly and filing
- Launch sequencing and market entry
- Clinical and non-clinical teams for what the evidence can support
- CMC and quality for what the manufacturing story will look like at filing
- Regulatory intelligence on precedent and current agency expectations
- Programme leadership planning timelines and investment
- Regulatory operations, which executes the strategy as submissions
- Commercial teams whose launch assumptions rest on the approval route
- The regulatory strategy and its regional sequencing
- The interpretation of agency feedback and what it commits the organisation to
- The advice that a proposed development shortcut will not survive review
- The approval decision, which is the regulator’s
- Clinical or manufacturing design choices
- Commercial launch decisions
- Programme leadership, where the evidence will not support the intended claim
- Senior management, where a regional strategy carries material timeline or cost consequences
- Regulatory strategy documents and their revisions against emerging data
- Meeting requests, briefing packages and records of agency feedback
- Gap assessments between the development plan and filing requirements
WHAT THIS ROLE CAN EVIDENCE · 0
No published competency maps to Regulatory Strategy Lead yet. 14 are published across the registry, and this role is not among the ones they name.
Read the standard and its stated coverage →A role map is Locate, moment 2 of 5: what surrounds your work, what you own, and what you escalate. It does not teach the practice or test it. Next is Learn — the Regulatory Affairs pathway. No scenario exercises this role yet, so Practise comes later for it, then what any of it evidences. Skip any of them — the order does not change.
The regulations and standards this pathway anchors on. SPEQ decodes and cites each one; the authoritative text lives at the official source.
- ICH Q12Technical and Regulatory Considerations for Pharmaceutical Product Lifecycle ManagementICH · last revised 2019-11-01
- 21 CFR 314.80Postmarketing Reporting of Adverse Drug ExperiencesFDA · last revised 2023-01-01
- ICH E2B(R3)Electronic Transmission of Individual Case Safety Reports (ICSRs)ICH · last revised 2013-01-01