This is a ready-to-use 30-60-90 day plan for a new GxP quality hire (document control specialist, QA associate, or a comparable entry role) and the manager onboarding them. It turns the first three months into a deliberate ramp: learn the system, do the core task precisely, connect the dots, and build toward the next role. Replace every <<FILL: ...>> placeholder with your own specifics. A filled specimen follows. This is general guidance to adapt, not legal, regulatory, or HR advice. It pairs with the article Breaking Into GxP Quality.
Header
| Field | Entry |
|---|---|
| New hire | <<FILL>> |
| Role | <<FILL>> |
| Manager / mentor | <<FILL>> |
| Start date | <<FILL>> |
| Target track | <<FILL: CSV/validation, data integrity, or QA/quality systems>> |
1. The through-line
Do the visible task precisely, then spend your discretionary attention understanding why the task exists and what it connects to. That combination is what moves people out of entry-level roles quickly.
2. Days 1 to 30, learn the system
| Area | Actions | What good looks like |
|---|---|---|
| QMS layout | Learn where SOPs live, the document hierarchy, and the change control flow | You can find any controlled document and explain the document hierarchy |
| Good documentation practice | Learn the site’s good documentation practices and how records are corrected | Your entries follow GDP without reminders |
| Your core task | Shadow, then perform the core task under review | You complete the task with supervision and few corrections |
| Training | Complete assigned GxP and role training | Training record current; you can state what each SOP is for |
| People | Meet QA, QC, validation, and the system owners you interface with | You can name who you hand work to and who you get it from |
30-day self-check: <<FILL: can you find any controlled document and explain the change control flow?>>
3. Days 31 to 60, do the core task well
| Area | Actions | What good looks like |
|---|---|---|
| Core task quality | Own the core task: review records for completeness, route changes, log deviations accurately | Your work passes QA review with few or no corrections |
| Precision | Practice exact, unambiguous entries and problem statements | A stranger could understand your records without you present |
| First connection | Sit in on a deviation or a CAPA discussion | You can explain how a deviation becomes a CAPA |
| Ask why | For each recurring task, ask what requirement it satisfies | You can tie your daily work to a regulation or a risk |
60-day self-check: <<FILL: do your records pass QA review cleanly, and can you explain the why behind two of your recurring tasks?>>
4. Days 61 to 90, connect and build toward the next role
| Area | Actions | What good looks like |
|---|---|---|
| Read an investigation | Read a closed deviation or CAPA end to end | You can say whether the root cause was real and the CAPA addressed it |
| Shadow | Shadow an audit, an inspection prep, or a validation execution | You have seen the field as a system, not a set of tasks |
| Systems thinking | For one change, trace what depends on it | You can answer “what depends on this?” for a real example |
| Portfolio and track | Produce one portfolio item; decide which track to pursue | You have a portfolio item and a clear view of your track |
90-day self-check: <<FILL: do you have a portfolio item and a specific next-role target with a reason?>>
5. Portfolio outcome (by day 90)
| Deliverable | Done? |
|---|---|
| One clean, precise GxP document you authored or executed | <<FILL>> |
| A written summary of one closed investigation and whether the root cause held | <<FILL>> |
| A named target track and next role, with your reasoning | <<FILL>> |
6. Manager checkpoints
| Checkpoint | Date | Outcome |
|---|---|---|
| 30-day review | <<FILL>> | <<FILL>> |
| 60-day review | <<FILL>> | <<FILL>> |
| 90-day review | <<FILL>> | <<FILL>> |
7. References
The onboarding shape draws on the article Breaking Into GxP Quality. Underlying expectations map to ICH Q10 (pharmaceutical quality system), good documentation practice, and your site’s own SOPs. Follow your site’s controlled procedures over any general guidance here.
Filled specimen
One new document control specialist, 60 days in, targeting a CSV track.
- Days 1 to 30: learned the QMS layout, can find any controlled document and explain the change control flow; GxP training complete; met the QA reviewers and two system owners. 30-day self-check passed.
- Days 31 to 60: owns record-completeness review; last ten record packages passed QA review with one minor correction; sat in on a deviation triage and can explain how it became a CAPA; asked why the batch-record review checklist exists and traced it to 21 CFR 211.194. 60-day self-check passed.
- Days 61 to 90 (planned): read a closed CAPA end to end, shadow a CSV execution, produce a mock IQ/OQ script as the portfolio item, confirm the CSV track.
The plan works because the hire did the visible task precisely first (clean QA reviews) and then spent discretionary attention on why it exists (tracing the checklist to the regulation), which is the exact combination the article says gets people promoted.
How to adapt this plan
- Set the role, manager, and start date, and the new hire’s target track.
- Point the QMS-layout and GDP items to your site’s real procedures.
- Keep the “what good looks like” column concrete and observable for each phase.
- Schedule the three manager checkpoints on real dates before day 1.
- Treat the portfolio outcome as the visible proof the ramp worked.