Regulatory Affairs Specialist Guide

Overview

This guide is written for prospective and early-career regulatory affairs specialists, and for professionals transitioning from quality assurance, clinical operations, or manufacturing. It offers more than a job description. It summarizes practical day-to-day expectations and early career decisions that matter.

The guide defines the role, the submissions you will draft, the tools you will use, the metrics you will be measured on, and the career choices you will face in your first one to three years. It draws on professional resources such as the RAPS Regulatory Affairs Career Guide for role context and career framing. It spans responsibilities across the product lifecycle and across product types (pharma, biotech, medical devices, and IVDs). Where regional differences affect practice, they are called out.

Where evidence does not support a specific claim, language is narrowed to reflect consensus guidance and public agency sources. This document is practical in orientation. It emphasizes the operational outputs you will own or influence, the cross-functional handoffs you must learn, and concrete artifacts you can build before accumulating deep submission experience. Links to primary sources and agency guidance are included inline to support verification and further reading.

---

What does a regulatory affairs specialist do?

A regulatory affairs specialist helps a company meet the laws, regulations, and agency expectations that govern product development, approval, marketing, and maintenance. Northeastern University's role overview describes this as working to ensure compliance with state, local, federal, international, and industrial regulations. The operative task is to interpret regulatory requirements and translate them into actionable plans that product, clinical, quality, and commercial teams can execute.

In practice the specialist is a liaison between the company and health authorities. They read agency guidance, identify implications for a specific product, and convert ambiguous regulatory text into checklists, decision trees, and templates that non-RA functions can follow. That translation work — making regulations operationally usable — is the core of the job rather than simply knowing regulation text. RAPS documents how the role evolves substantially with experience, from execution-weighted early years to strategy-focused senior practice.

Understanding the role requires recognizing the balance between strategy and execution. Early work is advisory and preventive, shaping studies and designing dossier-ready data collection. Later work is executional, drafting dossier sections, managing agency responses, and maintaining registrations. Developing judgment about which regulatory requirements matter at a given decision point is the foundational skill for early-career specialists.

Role boundaries with quality assurance and clinical

Understanding where regulatory affairs ends and quality assurance begins is one of the most practical distinctions an early-career specialist needs to internalize. Professional guidance and common organizational practice help define these boundaries.

The clearest way to draw the line is to ask what each function owns at a given moment in the product lifecycle. RA owns the strategy and content of interactions with regulators — what to submit, when, in what format, and with what justification. QA owns the system integrity that makes those submissions credible, including SOPs, audit programs, deviation records, and CAPA narratives. In short, RA writes and defends the story told to regulators; QA maintains the evidence base that makes that story believable.

Concrete contrasts make the distinction operationally useful. RA typically drafts a Clinical Overview (CTD Module 2.5) or a 510(k) summary while QA authors a CAPA report or an audit response. RA engages early to shape strategy; QA operates continuously to maintain compliance. RA assesses regulatory risk (will a gap trigger a deficiency), while QA assesses quality system risk (will a deviation compromise product integrity). Agency correspondence is often controlled through senior RA, and QA interacts with inspectors during audits.

Clinical operations is a third lane. Clinical executes studies — protocol adherence, site management, data integrity — while RA ensures the study design will generate data suitable for regulatory submission. Clear handoffs — who reviews protocols for regulatory sufficiency, who owns investigator queries, who signs off labeling language — prevent both overreach and missed contributions.

---

Core responsibilities across the product lifecycle

Describing the RA specialist's role across the product lifecycle helps prioritize early learning. The nature of RA work changes from front-loaded strategy to later execution and maintenance. Early phases emphasize regulatory strategy input — deciding what evidence will be required, the format it must take, and which gaps could pose later problems. Later phases emphasize dossier assembly, agency interactions, and post-approval lifecycle management.

The practical takeaway is that foundational skill is not rote memorization of guidelines. It is the judgment to identify which regulatory requirements matter at each decision point. As a product advances, the specialist's activities shift.

In preclinical and early clinical stages you will influence study design and documentation hygiene. In pre-submission you will coordinate multi-function inputs into a coherent dossier and manage controlled review workflows to avoid version drift. After approval you will coordinate change controls, variations, and periodic safety reporting to keep registrations current. Learning to ask "will this hold up in the dossier?" early in the process is a high-leverage habit that reduces late rework and agency queries.

Preclinical and clinical phases

During preclinical and early clinical development, the key decision is what evidence and format will support the intended regulatory pathway. Guidance such as ICH M4 (CTD structure) and ICH E6(R2) (GCP) frames those expectations. The specialist's contribution at this stage is primarily strategic: advising on study designs, endpoints, and data formats so nonclinical and clinical results can be assembled into a future Module 4/5 or device CER/PER.

Practically, this means reviewing preclinical protocols for Module 4 compatibility. It also means confirming clinical endpoints align with the anticipated label and establishing documentation hygiene such as version control, audit trails, and traceability. These interventions are targeted and preventive rather than large drafting projects. The habit of front-end scrutiny is one of the most impactful behaviors an early specialist can develop.

Pre-submission and submissions

Pre-submission work covers the meetings, briefings, and dossier assembly activities that precede a formal filing with a health authority. For medicines this typically uses the ICH CTD format. For devices the relevant pre-submission programs and 510(k)/PMA pathways apply.

The specialist's role is to coordinate CMC, nonclinical, clinical, biostatistics, and publishing contributors into a dossier that meets structural, metadata, and substantive requirements. Structural defects — broken cross-references, missing sections, metadata errors in the eCTD package — create real submission risk. Controlled review workflows that maintain shared owners, traceable comments, and sequence state control are essential to prevent submission delays. In this phase RA visibility is high and the ability to manage review choreography is a core competency.

Post-approval and lifecycle management

Managing products after approval is a sustained RA responsibility because approvals generate continuous change and reporting obligations under statutes such as 21 CFR 314 and related device regulations. Post-approval tasks include submitting variations or supplements for formulation, site, or labeling changes. They also include managing periodic safety reports (PBRER/PSUR under ICH) and correctly classifying changes because classification determines the reporting pathway and timeline.

Change control is a critical cross-functional process. A safety-driven labeling update will typically involve pharmacovigilance, regulatory, QA, and commercial input. The specialist coordinates that input to produce a traceable submission. Sponsors can run dozens of supplements annually, so lifecycle coordination and accurate classification are essential operational skills.

---

Skills that compound impact in regulatory roles

Identifying the skills that accelerate impact helps early specialists prioritize development beyond baseline regulatory knowledge. RAPS and industry practice highlight a set of compounding competencies. Regulatory knowledge is necessary but not sufficient. Systems thinking, documented risk rationale, clear cross-functional communication, data fluency, and project leadership without formal authority are the capabilities that distinguish high performers.

Systems thinking enables a specialist to see how a change in Module 3 (quality) can affect a label claim in Module 1. This catches problems a narrow reviewer would miss. Closely related is risk documentation. Capturing regulatory rationale, evidence considered, and rejected alternatives creates an audit trail that protects both the company and the specialist during inspections. These skills turn individual decisions into defensible, repeatable outcomes.

Communication across functions and comfort with data are practical daily requirements that compound influence. Translating a deficiency letter for a CMC scientist, turning a clinical endpoints concern into clear instructions for a biostatistician, and briefing senior leadership on timing and risk are behaviors that increase impact. Data fluency — understanding how adverse event narratives and safety tables map to clinical datasets — is increasingly expected. Leading cross-functional timelines and escalating blockers without formal authority is equally essential.

---

Deliverables by product type and where specialists contribute

Recognizing typical deliverables by product type clarifies where you will draft, review, or coordinate content as a specialist. The required documents and governing frameworks differ substantially between drugs/biologics and devices/IVDs. For medicines, the ICH CTD and the specific CFR parts for IND, NDA/BLA, and BLA frame the content requirements. For devices, US 510(k)/PMA pathways and EU MDR/IVDR Technical Documentation (CER/PER) define expectations.

For drugs and biologics, specialists commonly draft Module 1 administrative documents (forms, cover letters, proposed labeling). They contribute to Module 2 summaries (Quality Overall Summary, supervised input to Clinical/Nonclinical Overviews) and support Module 3 quality/CMC sections. Subject-matter experts author Module 4 and Module 5 content. For an IND the specialist often helps assemble the Investigational Plan, Investigator's Brochure, and CMC information, gaining drafting experience under senior review.

For medical devices and IVDs, specialists typically assemble substantial equivalence arguments, device descriptions, performance testing summaries, and labeling for 510(k) submissions. They may coordinate the deeper clinical evidence packages required for PMA. In the EU, CERs and PERs are high-value documents that specialists often draft or coordinate, synthesizing literature, clinical investigation data, and post-market surveillance.

Labeling and UDI compliance — including FDA GUDID entries and 21 CFR Part 830 requirements — are common RA responsibilities. These tasks require coordination with manufacturing, marketing, and quality to ensure consistency across label content and registry entries.

---

Tool stack for modern RA work (and how each maps to tasks)

Knowing the categories of tools used in RA work — and what regulatory standards they support — demonstrates operational readiness even before hands-on experience. Key categories include eCTD publishing/validation, RIM, QMS/document control, regulatory intelligence, and labeling/UDI tools. Each category maps to different parts of the submission and lifecycle workflow and is commonly referenced in job interviews and SOPs.

eCTD publishing and validation tools support assembly, structural validation, and lifecycle management of electronic submissions. For many submissions eCTD format is mandatory. Structural defects in the XML backbone or lifecycle operations can block filing. These tools validate packages against the ICH eCTD specification and FDA technical guidance. For quick pre-publication checks without moving confidential dossier content outside the local environment, browser-based validators that run structural, lifecycle, and metadata checks locally are a practical option. Assyro's free eCTD validator, for example, runs 358 CFR, ICH, and FDA TRC structural checks across Modules 1–5 — including lifecycle XML and checksum manifests — entirely in the browser, and exports a redacted structural summary for QA review.

RIM systems track submission histories, registrations, dossier versions, and regulatory milestones across markets and products. They provide an auditable record that becomes essential for managing variations and renewals at scale. QMS and document control systems manage SOPs, work instructions, and controlled documents that underpin GxP compliance. RA interacts with QMS platforms when initiating or reviewing change controls and routing labeling for approval.

Regulatory intelligence platforms monitor guidance, agency announcements, and enforcement actions across agencies (FDA, EMA, Health Canada, etc.). They reduce the manual time required to track changes that impact products. Solutions that embed change monitoring directly into submission workflows — rather than requiring a separate research step — are particularly valuable for lean teams. For tracking FDA approval timelines against your own program calendar, a PDUFA date tracker that carries source-linked deadlines and daily updates is a practical free utility. Teams working in biologics or biosimilars can also use Assyro's FDA Purple Book tool to inspect licensed biologics, exclusivity dates, and patent-list records directly from official FDA data.

Labeling and UDI tools support the creation, review, and lifecycle management of labels and GUDID entries for devices, as well as SPL/structured product information for medicines. For an early specialist, fluency in these tool categories — describing the regulatory standard each supports and how it connects to a daily task — signals operational readiness even without deep platform experience.

---

KPIs that matter for RA specialists

Selecting KPIs that link specialist behavior to upstream actions is more actionable than tracking only on-time submission, which is a lagging indicator. A practical RA scorecard focuses on dossier quality, inspection findings, cycle times, pre-publication defect rates, classification accuracy, and labeling consistency. These metrics are measurable and tied to behaviors the specialist can influence.

A starter scorecard includes:

• Post-submission questions per dossier (fewer queries indicate better pre-submission QC)
• RA-related inspection findings (reflect documentation and classification quality)
• Module-level cycle time from draft to lock (reveals review bottlenecks)
• Hyperlink and metadata defect rate pre-publish (measures pre-publication QC rigor)
• Change control classification accuracy (reduces remediation and compliance exposure)
• Labeling consistency rate across markets (measures proactive lifecycle management)

A practical way to use these metrics early is to keep a personal log of each submission, change control, or response you contribute to. Record outcomes (agency queries, inspection findings, cycle times) to build a learning record and portfolio evidence.

---

Career paths and practical ways to enter the field

Choosing an entry path into RA matters less than demonstrating transferable regulatory judgment. RAPS documents multiple routes into the profession including direct entry from life sciences degrees and lateral transitions from QA, clinical, manufacturing, medical writing, or regulatory consulting. Employers commonly expect a bachelor's in life sciences, pharmacy, or engineering for entry roles, with advanced degrees more common at senior levels. Demonstrated submission history or portfolio artifacts often outweigh credentials for early hires, as outlined in Indeed's guidance on becoming a regulatory affairs specialist.

If you are transitioning from an adjacent function, a focused 90–180 day plan accelerates the learning curve and helps establish credibility. A condensed plan divided into four focused blocks is practical:

• Weeks 1–4: Build regulatory literacy; read ICH M4 (CTD structure) and ICH E6(R2) (GCP), annotate requirements relevant to your product area, review applicable FDA device or IND guidance, and access historical submission records in your RIM.
• Weeks 5–8: Gain cross-functional exposure and draft initial documents; shadow a pre-submission meeting, draft a Module 1 cover letter or labeling comparison and get structured feedback, review QA change logs and map changes to reporting obligations, and complete a mock 510(k) summary exercise.
• Weeks 9–12: Deepen process and systems knowledge; map the eCTD lifecycle for one product, build a labeling logic matrix mapping claims to evidence, and complete a labeling mapping mini-project using a public label.
• Weeks 13–26: Move to strategic and portfolio work; develop a geo-route map for one product (registrations, renewals, divergence risks), draft a CTD Module 2 quality overview using public examples, participate in a health authority response drafting exercise, and begin a personal KPI log of outcomes for learning and performance narratives.

These milestones give structure to early contributions and create tangible artifacts to demonstrate regulatory judgment.

---

Certification chooser: RAC vs TOPRA and when to pursue them

Selecting a certification depends on your geographic focus and experience level. The Regulatory Affairs Certification (RAC) from RAPS and the TOPRA Diploma in Regulatory Affairs serve different audiences and career positioning goals. RAC offers variant exams (Drugs, Devices, Global) that are well recognized in the US and internationally. TOPRA's Diploma is a structured, longer-form credential with strong recognition in the European market.

RAC is suitable for US-focused professionals with 2+ years' RA experience who want a recognized, exam-based credential to signal baseline competency. TOPRA's Diploma is better suited to professionals committed to European regulatory careers and often involves a structured curriculum spanning a year or more. Early-career specialists with under two years of direct RA experience should prioritize building submission history and practical artifacts before investing in certification. Experience makes study time more meaningful and meets eligibility thresholds.

A practical 12-week RAC preparation outline:

• Weeks 1–2: Review the RAPS blueprint for your chosen variant and catalog knowledge gaps.
• Weeks 3–5: Study the regulatory framework domains (relevant CFR parts, ICH guidelines, FDA/EMA guidance) using primary sources.
• Weeks 6–8: Focus on submission process and lifecycle domains (IND/NDA/BLA or 510(k)/PMA).
• Weeks 9–10: Cover compliance, inspection, and post-market domains; review public Warning Letters and FDA inspection databases.
• Weeks 11–12: Complete two to three full practice exams and review incorrect answers against primary sources.

---

Employer types compared: sponsor vs CRO vs consultancy vs notified body

Choosing the employer type for your first RA role shapes your exposure to submissions, mentorship quality, tooling, and the pace of independent work. Each employer type carries distinct tradeoffs. Sponsors (pharma/device companies) typically offer deeper product ownership and lifecycle exposure with stronger tooling in larger organizations. CROs provide breadth across client programs and faster ramp-up on procedural tasks. Consultancies give diverse project exposure and faster movement to independent work for experienced specialists. Notified bodies or agencies provide a reviewer's perspective and strong regulatory framework understanding but usually slower career progression and lower compensation compared with industry.

Pros and cons summarized:

• Sponsor — Pros: product ownership, full lifecycle exposure, stronger tooling in large firms; Cons: narrower therapeutic exposure early.
• CRO — Pros: high submission volume and breadth; Cons: less strategic depth per product and client pressure on timelines.
• Consultancy — Pros: diverse projects and faster independence for experienced staff; Cons: variable process maturity and limited depth per engagement.
• Notified Body/Agency — Pros: deep reviewer insight and high credibility; Cons: lower pay than industry and slower commercial context experience.

The decision matrix below scores each employer type across six factors on a 1–3 scale (1 = low, 3 = high), reflecting common organizational patterns. Weight each factor by your personal priority and sum the rows to identify the best fit for your current career goals.

• Factor: Breadth of therapeutic/product exposure; Sponsor: 1; CRO: 3; Consultancy: 2; Notified Body: 2
• Factor: Structured mentorship; Sponsor: 3; CRO: 1; Consultancy: 1; Notified Body: 2
• Factor: Tool and process maturity; Sponsor: 3; CRO: 2; Consultancy: 1; Notified Body: 2
• Factor: Strategic depth per product; Sponsor: 3; CRO: 1; Consultancy: 2; Notified Body: 1
• Factor: Speed to independent work; Sponsor: 1; CRO: 2; Consultancy: 3; Notified Body: 1
• Factor: Regulatory framework depth; Sponsor: 2; CRO: 2; Consultancy: 2; Notified Body: 3

To use the matrix: assign a weight from 1–3 to each factor based on what matters most to you right now, multiply each cell score by your weight, and sum the row. The highest total indicates the employer type best aligned to your current priorities. If mentorship and tooling are your top priorities, a sponsor is likely to score highest. If breadth and speed to independence matter more, a CRO or consultancy may be preferable.

---

Global pathways at a glance: US vs EU vs UK vs Canada vs China

Choosing a primary market early creates compounding career value because jurisdictional fluency transfers to adjacent markets. The common starting choices are the US or EU, with UK, Canada, and China added progressively. Understanding the defining statutes, submission formats, and practical nuances of each jurisdiction helps prioritize learning.

• United States (FDA): The FDA ecosystem is characterized by a large guidance document corpus that effectively shapes agency expectations. Medicines follow the IND → NDA/BLA pathways under 21 CFR Parts 312, 314, and 601 using CTD/eCTD formats. Devices use 510(k) and PMA pathways under 21 CFR Parts 807 and 814. The FDA guidance search portal is the primary research tool.
• European Union (EMA/EU MDR/IVDR): For medicines, centralized, mutual recognition, and decentralized procedures coexist (dossier expectations follow CTD/eCTD and EudraLex Volume 2B). For devices, EU MDR 2017/745 and IVDR 2017/746 require Technical Documentation including CERs/PERs assessed by Notified Bodies. The MDR/IVDR transition increased clinical evidence and post-market surveillance obligations substantially.
• United Kingdom (MHRA): Post-Brexit, the MHRA manages national authorizations and the UKCA mark governs GB device conformity. The MHRA accepts CTD submissions for medicines but has unique guidance and transition arrangements that require direct verification on the MHRA website.
• Canada (Health Canada): Health Canada uses CTD format for drugs under its Food and Drug Regulations and a licensing framework for devices. It is often treated as an ICH-aligned reference market alongside FDA and EMA.
• China (NMPA): The NMPA has modernized its framework and joined ICH, adopting eCTD in many cases. Local clinical data expectations, translation requirements, and in-country testing obligations make China a specialist market. It is typically learned after US/EU fluency.

For most early specialists, deep competency in either the US or EU framework first, with the other as a comparative reference, is the most practical route. UK and Canada are natural extensions. China is usually a later addition.

---

Compensation and job outlook: what to expect and how to evaluate offers

Compensation varies by seniority, industry, employer type, and geography. The RAPS Compensation Survey provides the most comprehensive, current benchmarks specific to RA roles and should be consulted when evaluating offers. Structural drivers of pay include seniority level (associate to director/VP), industry (pharma/biotech typically higher than devices; CROs often lower than sponsors), geography (US salaries generally higher in absolute terms), and credential status (RAC can be associated with modest uplift in some settings).

When you evaluate an offer, weigh total development value rather than salary alone. Consider submission exposure (will you own modules or coordinate logistics), tooling maturity (modern RIM and eCTD environments increase transferable skills), mentorship structure (accessible senior reviewers accelerate learning), product pipeline and lifecycle stage (active INDs provide more hands-on drafting experience), and on-site vs remote models (early-career proximity to senior colleagues accelerates informal learning). These factors often have a larger long-term effect on market value than a modest initial salary premium.

---

Day-in-the-life snapshots by seniority

Understanding the typical daily balance of tasks at different seniority levels helps set realistic expectations and learning goals. The role evolves from execution and learning to ownership and strategic leadership as experience accrues.

• Regulatory Affairs Associate (0–2 years): Days are execution-weighted — drafting assigned dossier sections, populating submission checklists, managing version logs, formatting labeling, and attending project meetings as a contributor. Agency interactions are limited and supervised; the key habit is asking "why?" about decisions to build judgment.
• Regulatory Affairs Specialist (2–5 years): The role shifts to primary ownership of specific modules or filings, coordinating cross-functional inputs, managing review cycles, and preparing pre-submission briefing materials. Specialists draft deficiency responses and manage portfolios of two to four products, increasingly advising junior staff.
• Senior Regulatory Affairs Specialist (5+ years): Work focuses on strategy, cross-functional leadership, and higher-level agency interactions. Tasks include setting regulatory strategy, advising on go/no-go decision points, drafting executive summaries, and participating directly in agency meetings. Mentoring and team leadership become expected responsibilities.

---

Portfolio artifacts to build early and how to present them

Building demonstrable artifacts before you have a deep submission history is a high-leverage way to show regulatory thinking. Hiring managers value evidence of judgment and structured reasoning over credentials alone. Practical, public-source artifacts demonstrate both literacy and applied reasoning.

Consider assembling these achievable artifacts: a mock 510(k) summary using predicate device public records to demonstrate device regulatory literacy and substantial equivalence argumentation; a labeling logic matrix mapping each label claim to the supporting evidence module to show understanding of label-to-evidence traceability; a CTD Module 2 quality overview (QOS) draft using ICH M4Q guidance and public EPAR examples to demonstrate CMC and CTD structure knowledge; a geo-route map showing registration status, label version, and renewal obligations across key markets to demonstrate lifecycle thinking; and a CAPA narrative for a hypothetical documentation deviation to bridge QA and RA competencies.

When presenting artifacts in interviews, lead with the regulatory question you were answering, the framework you applied, and the decision you supported. Artifacts with a clear reasoning narrative are more persuasive than formatting exercises.

---

Ethics, escalation, and communicating risk under pressure

Regulatory specialists regularly face situations where they must communicate unwelcome regulatory realities to commercial teams and executives. The way you document and escalate those risks determines your credibility. The most important tactical habit is written documentation of risk-based decisions. Capture the regulatory rationale, referenced guidance, alternative positions, and the data considered at the time of the decision so the rationale is auditable during inspections or internal reviews. This documentation need not be long but must exist.

When business partners push back, acknowledge the commercial concern and reframe the discussion around concrete regulatory risk and precedent rather than preference. Grounding conversations in specific agency actions, Warning Letters, or analogous deficiency letters makes arguments factual and less adversarial. All substantive contacts with regulators — written or verbal — should be recorded in a meeting record or contact memo and stored in the product's submission history. FDA guidance on formal meeting management provides useful templates for structuring these records. Maintaining a working reference file of relevant public inspection outcomes and agency decisions in your product area helps you support recommendations without appearing obstructive.

---

Glossary of core regulatory terms and acronyms

A compact glossary reduces the cognitive load of reading guidance and templates and gives a shared vocabulary for cross-functional conversations. The following terms reflect standard usage and are widely referenced in regulatory guidance and submission practice:

• CTD (Common Technical Document): The ICH-defined format for organizing pharmaceutical regulatory submissions into Modules 1–5 (regional administrative, summaries, quality, nonclinical, clinical).
• eCTD (electronic Common Technical Document): The electronic implementation of the CTD using an XML backbone to define structure, lifecycle, and sequence of documents; mandatory for many FDA and EMA submissions.
• IND (Investigational New Drug Application): FDA filing under 21 CFR Part 312 that authorizes clinical trials of an unapproved drug in the US.
• NDA (New Drug Application): FDA filing under 21 CFR Part 314 requesting approval to market a new drug in the US.
• BLA (Biologics License Application): The biologics equivalent of an NDA, governed by 21 CFR Part 601.
• 510(k): FDA Premarket Notification under 21 CFR Part 807 Subpart E demonstrating substantial equivalence to a predicate device.
• PMA (Premarket Approval Application): FDA pathway under 21 CFR Part 814 for Class III devices requiring valid scientific evidence of safety and effectiveness.
• CER (Clinical Evaluation Report): EU MDR 2017/745 required document that evaluates clinical data supporting a device's safety and performance.
• PER (Performance Evaluation Report): The IVDR equivalent of a CER for IVDs.
• UDI (Unique Device Identification): System for identifying devices through distribution and use; governed in the US under 21 CFR Part 830 and by EU MDR/IVDR.
• RIM (Regulatory Information Management): Software systems that track submission histories, registrations, and regulatory milestones.
• PDUFA (Prescription Drug User Fee Act): US legislation setting FDA review performance goals and user fee timelines for NDAs/BLAs.
• PSUR / PBRER (Periodic Safety Update Report / Periodic Benefit-Risk Evaluation Report): Scheduled post-approval safety reports summarizing benefit-risk based on accumulated post-market data.

---

Choosing where to invest your early years in regulatory affairs is a compounding decision. The frameworks in this guide — the employer decision matrix, the 90–180 day plan, the KPI scorecard, and the portfolio artifact list — are designed to be reused as concrete inputs to that decision, not read once and set aside. A practical next step is to pick the section most relevant to your current stage: if you are evaluating your first role, apply the decision matrix; if you have just started, begin your personal KPI log and work through the 90-day milestones; if you are preparing for RAC, use the 12-week study outline. For the submission tooling side of the role, Assyro's free regulatory utilities — including the browser-based eCTD validator, PDUFA calendar, and ROI calculator — are worth bookmarking as working references regardless of what platform your employer uses.