The training record that was a quality record: HR for pharmaceuticals and life sciences

During an inspection, a pharmaceutical manufacturer was asked for the training history of an operator on a batch produced two years earlier. The operator had left eighteen months before. HR had archived his training records with his personnel file, on the schedule HR used for leavers, and part of the file had been disposed of. The quality function, which had assumed the records were held under its own retention rules, discovered otherwise in front of the inspector. Nothing had been done in bad faith. Two functions had each assumed the other owned a record that, in a regulated plant, belonged to the quality system and had been treated as an HR document.

HR in a regulated manufacturer has a feature no other sector shares: a subset of what looks like the employee file — training, qualification, authorisation, signature registers — is part of the quality system, with its own owner, its own change control and its own retention. Treating those records as HR documents is the most common structural error in the sector, and the opening is how it is discovered.

HR RECORDS              QUALITY RECORDS
  contract and terms      training records, per procedure
  leave and attendance    qualification and authorisation status
  payroll                 signature and initials register
  performance, conduct    area and clean-room authorisations
  personal details        job description as a controlled document

  owner: HR               owner: quality
  retention: HR policy    retention: the quality system's
  change: ordinary        change: controlled, with audit trail

Decide which column every record is in, once,
and configure the system to enforce it.

The decision is made once, per record category, and written down: which records are quality records, who owns them, how they change, how long they are kept, and how they are retrieved for inspection. Configured into the system that holds them — with controlled change and an audit trail for the quality column — the two functions stop assuming. This is employee information management with a regulatory dimension, and the ownership map is the deliverable that would have kept the operator's training history where the inspector expected to find it.

In a regulated plant, induction is training with documentary consequence: what the person was trained on, by whom, when, and whether they were assessed as qualified becomes part of the quality record. Onboarding therefore ends not when induction is complete but when the individual is qualified and authorised for their role — and the gap between the two is where risk sits. The sequence is fixed: quality-system and GMP induction before area access, role-specific procedure training recorded per document, qualification assessed before independent working, signature and initials register entry created, clean-room and area authorisation issued, data-integrity and documentation practice trained. Probation is aligned to qualification milestones, so that a person who is confirmed is a person who is qualified.

1. 1

   GMP and quality induction before any area access

   Recorded per person, with the version of the procedure trained on.

2. 2

   Procedure training recorded per document, per version

   Because a procedure revision changes who is trained on the current version — see below.

3. 3

   Qualification assessed, not assumed

   Observed, signed off, recorded. Attendance is not qualification.

4. 4

   Authorisation issued and expiry-tracked

   Area, clean-room, named responsibilities. The roster and the batch record reference this.

The control that manual systems cannot keep is retraining triggered by procedure revision. When a procedure changes, everyone trained on the superseded version needs training on the new one before performing it, and the record has to show that they were. A spreadsheet that holds 'trained on SOP-042' cannot show which version, and the manual remedy — someone remembering who was trained on what — is where the gaps that inspections find come from. A system that holds training per procedure per version, and flags every person whose training is now against a superseded version, turns the revision into a task list rather than a memory exercise. This is the single highest-value capability the learning and development function in a regulated plant can have.

Regulated environments require adherence, and the risk is that adherence becomes the whole culture — people stop raising anything that is not a formal deviation, and the quality system loses the near-miss information it depends on. The relations question underneath is whether an error is, by default, a disciplinary matter. Where it is, error reporting stops. The distinction between an error, which is information for the quality system, and misconduct, which is a process, is a supervisor skill, and getting it wrong in either direction is costly: one way the quality system goes blind, the other conduct goes unaddressed. Error and deviation reporting has to be separated from the disciplinary process explicitly, data-integrity concerns routed independently and protected, and production pressure never accepted as a reason for a procedural shortcut. A plant where nobody reports a near miss has a relations problem presenting as a compliance success.

• Separate routes: deviation reporting, grievance and disciplinary are three doors, and staff must know which is which.
• Train supervisors on error versus misconduct. It is the judgement the whole culture rests on.
• Recognise catching problems, not only clean records. A clean record produced by silence is the worst outcome available.
• Watch the shift pressure. Documentation time squeezed by production targets is where shortcuts start, and the grievance and disciplinary process will see the consequence before the quality system does.

Progression in a regulated environment is tied to qualification and training records, which makes the ladder auditable and makes gaps visible well in advance — if anyone maintains it. Succession for roles that carry named responsibilities in the quality system deserves separate treatment, because those cannot be filled at short notice and the qualification path is long; the recruitment pool for them is small and competitors know exactly who holds which qualification. Naming successors and starting their qualification path before the vacancy exists is the difference between a planned handover and a gap that stops release.

Regulated plants run with contractor and temporary staff — maintenance, cleaning, validation, seasonal operators — and every one of them who enters a controlled area is subject to the same training and authorisation requirements as an employee. The record of that training belongs to the plant, not to the contractor, because it is the plant's quality system the inspector is examining. The failure mode is the contractor who says training was done and the plant that has no record of it; the fix is a separate contractor register with training per person per procedure, held on the same system and the same retention as employees' records. The HR policies and governance work here is a single page stating that nobody enters a controlled area without a training record held by the plant, and that the page is applied under schedule pressure as much as on a quiet day.

• Contractor training recorded by the plant, per person, per procedure, per version.
• No area access without the record, including for the validation engineer who is only here for a week.
• Retained on the quality system's rules, because the batch record will reference them.

Draw the two-column table for your own records: which are HR, which are quality, who owns each, how long each is kept. Then check where the quality records actually live and whether they are retained on the quality system's rules or HR's. That exercise — an afternoon with the quality head — is where HR for pharmaceuticals and life sciences work begins, because it is the confusion that put the manufacturer in the opening in front of an inspector without a record. Then per-version training and retraining on revision. Then the error-versus-misconduct distinction, with the supervisors. Pharma HR work is unusual in that its first deliverable is a map of who owns what; everything else follows from getting that right.