Nobody is going to hand you a 90-day plan just because you need one. If your onboarding consists of a laptop, a login, and a stack of SOPs, the fastest way through it is to stop waiting for someone else to structure your first month and start building the map yourself.

Start with the primary source, not the summary

Every company’s SOPs are someone’s interpretation of a regulation, written at a point in time, by someone who may not still work there. That interpretation is worth learning, but it isn’t the same as understanding the regulation it’s built from. If you’re at a device company, read 21 CFR Part 820 itself — now the Quality Management System Regulation, restructured in February 2026 to incorporate ISO 13485:2016 by reference — alongside the SOP, not instead of it. The gap between the two is often where the real judgment calls live: an SOP might tell you to complete a section, but the regulation tells you why that section exists and what it’s actually trying to prevent. What changed under the QMSR is a reasonable first stop if your onboarding materials haven’t caught up to it yet, but the regulation itself is the primary source your own reading list should be built around, not a secondary one.

Build your own map of who actually knows what

A formal onboarding plan, when one exists, usually assigns you a single point of contact and a short list of introductory meetings. That’s a starting roster, not a map. The people who actually hold the institutional knowledge you need — who remembers why a predicate was rejected two years ago, who has the unofficial rationale for a labeling decision that never made it into any file — are identified by asking around, not by title. Keep your own running list as you go: who wrote the CAPA that closed cleanly, who reviewed the last submission before it went out the door, who’s the person colleagues quietly route questions to regardless of what the org chart says. If your company already has a formal process for pairing new hires with a guide, the manager’s side of that process is worth reading too — it tells you what a good version of your onboarding was supposed to look like, even if yours didn’t get one.

Where this goes wrong

Waiting for a plan that isn’t coming

If nobody has handed you a structured first month by the end of week one, they probably aren’t going to. Waiting costs you weeks a self-directed reading list wouldn’t have.

Reading only the internal summary and never opening the source

An SOP is a paraphrase, and paraphrases lose precision. If you can only cite the internal document, you can’t yet defend the position it’s based on.

Treating the org chart as the map of who to ask

Titles describe reporting lines, not institutional memory. The person who actually knows why a decision was made is often two levels away from the person whose title suggests they would.

None of this is unique to a first job in regulatory affairs — it’s the same self-directed habit that a good first 90 days runs on at any stage of a career, whether or not someone else structured it for you. What makes onboarding different is that it’s the one stretch where building this habit is also the entire job description.

Sources & further reading

  1. 21 CFR Part 820 — Quality Management System Regulation ecfr.gov
  2. Regulatory Academy — What the QMSR Actually Changes regulatoryacademy.com
  3. Regulatory Academy — How to Onboard a New Regulatory Affairs Hire regulatoryacademy.com
  4. Regulatory Academy — Your First 90 Days in Regulatory Affairs regulatoryacademy.com

This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.