Assurance and operations

Do not just write SOPs. Keep the evidence.

An assessor rarely asks whether you have a backup procedure. They ask to see the restore-test record from the date you say it ran. We build both halves: the controlled procedures, and the retained evidence that demonstrates them.

Standard operating procedures and controlled documents

Procedures and evidence are two different deliverables

Most laboratories preparing for their first serious audit discover the same gap. The procedures exist, often written carefully. What is missing is the trail showing they were followed: the access review that was done in March, the restore that was tested in June, the change record for the server migration.

We treat the SOP library and the evidence as separate deliverables, because an assessor does.

The library

Six families of controlled IT procedures

Governance

IT governance, information-security policy, computerized-systems policy, GxP system inventory and data-integrity policy.

User administration

Account creation, modification and disabling, periodic access review, privileged accounts and authentication management.

Operations

Backup, restore, system monitoring, scheduled jobs, server and network administration, time synchronisation.

Validation

CSV, GxP assessment, Part 11 assessment, supplier assessment, risk assessment, change control, periodic review and system retirement.

Security

Vulnerability and patch management, malware protection, removable media, incident response, remote access, portable devices and security monitoring.

Data

Data governance, archival, retention, electronic records, audit-trail review and data migration.

Records an assessor may expect to retrieve

  • Current user-access lists and the historical approvals behind them
  • Backup logs and, more importantly, restore-test records
  • Training records for staff touching regulated systems
  • Validation packages for systems in scope
  • Change controls, including infrastructure changes affecting validated systems
  • Incident records and resulting CAPAs
  • Audit-trail review records
  • Periodic system review records
  • The asset register, with GxP classification and validation status per system
  • Supplier assessments and vulnerability or patch assessments
The asset register

What each entry records

  1. Asset and owner

    The system identifier and the department or role accountable for it.

  2. GxP status

    Direct impact, supporting, or non-GxP.

  3. Validation status

    Validated, qualified, or not applicable, with the date.

  4. Backup

    Whether it is backed up and by what method — including configuration backup for network devices.

  5. Network

    Which zone it sits in, which tells you what it can reach.

Common questions

Can you write our SOPs for us?

We can draft the IT and infrastructure procedures and provide the technical content, and we maintain the records our services generate. Approval of SOPs sits with your quality system — a supplier-approved procedure is not a controlled procedure.

We already have SOPs. What would you actually add?

Usually the evidence layer. We check whether each procedure produces a retrievable record, and whether that record is actually being produced. The gap between a written procedure and a demonstrable one is where most findings originate.

How far back should evidence go?

That follows from your retention obligations and the regulatory context, which your QA defines. Our part is making sure the records are generated, protected and retrievable for whatever period you set.

Where our responsibility ends

Pracoda provides technical infrastructure implementation and documentation support. SOP approval, document control, regulatory interpretation, validation approval, data review and final quality release remain with the client's authorized QA, system owner or qualified regulatory and validation specialists. Compliance support does not constitute regulatory certification, legal advice or a guarantee of audit outcome.

Find your documentation gaps before an assessor does

Tell us when your next audit or assessment is and what IT documentation exists today. We will tell you what we would prioritise.

  • Reply within one working day
  • Evidence, not just procedures

We use your details only to reply to you. See our privacy policy.

Need a consultation?

Tell us what you are building.

Share the problem, the platform and the deadline. We will come back with an approach, a team and an estimate.