GxP third-party risk

SaaS platforms, AI providers, cloud hosts, CROs, and GxP suppliers change faster than annual spreadsheets can track — especially when a validated vendor quietly ships new AI features. ProcessX runs risk-tiered qualification, AI and release impact checks, and ongoing re-assessment as governed ServiceNow records, standalone or alongside your existing security TPRM flow.

VENDOR QUALIFICATION · VND-00418IT QUALITY SIGN-OFF
Illustrative recordChoose a step or evidence row to inspect
STEP 03 · SignCurrent in example

Part 11 e-signature on qualification approval with conditions

Inspection only. The example record and its signature state stay unchanged.
Awaiting signature — IT QualityMeaning: Qualification approval with conditions · Re-authentication required · Hash-chained on signingAWAITING SIG
Illustrative record: an AI-enabled SaaS vendor assessed against your GxP intended use, where configured AI drafts the gap summary and IT Quality signs.
PX-REC-01 · WHAT SHIPS

What ships in GxP third-party risk

Risk-tiered vendor intake, AI vendor assessment, qualification and quality agreements, and SaaS release and re-assessment workflows.

  • Risk-tiered vendor intake

    Every SaaS platform, AI tool, cloud host, CRO, or GxP supplier enters one controlled ServiceNow front door. GxP applicability, data criticality, security posture, and AI involvement set the risk tier once — scaling due diligence so low-risk vendors stop waiting on full audits.

  • AI vendor and model assessment

    For third parties that embed or host AI: model provenance, customer-data training boundaries, sub-processor exposure, and change-notice commitments are evaluated against your intended use, recorded as approval conditions, and linked directly to governed AI use cases.

  • Qualification and quality agreements

    Questionnaires, SOC and ISO evidence, audit findings, remediation tasks, and quality agreements live on one ServiceNow vendor record — closing with a Part 11 qualification signature instead of scattered email threads and shared drives.

  • SaaS release impact and continuous re-assessment

    Vendor release notes, new AI features, sub-processor updates, and expiring attestations open scoped impact assessments on the record — determining whether targeted regression is needed before changes reach production users, alongside scheduled risk-tiered reviews.

PX-REC-02 · CONTROLS AND EVIDENCE

The controls that apply, and the evidence they leave

The controls live inside the ServiceNow records, not in separate documents, and everything the workflow does leaves evidence.

Controls enforced

  1. C1Qualification depth enforced by calculated risk tier; approval is blocked while required findings remain open
  2. C2Vendor AI capabilities cannot be approved for GxP use until intended-use assessment and conditions are signed
  3. C3Role segregation between business requester, technical/security reviewer, and Quality approver
  4. C4Part 11 electronic signatures and immutable audit trail on every tiering decision, condition, and status change

Evidence produced

  1. E1Inspection-ready vendor qualification file on ServiceNow: applicability, risk tier, audit outcomes, and quality agreement
  2. E2Signed release and AI-change impact decisions linked to the validated systems the vendor supports
  3. E3Remediation findings and approval conditions tracked to verified closure on the record
  4. E4Live approved-vendor and approved-AI status visible across IT, Procurement, Security, and Quality
PX-REC-03 · REGULATORY BASIS

What supplier, Annex 11, and SaaS validation rules expect of third parties

Outsourcing software, cloud hosting, AI models, or clinical and manufacturing services never transfers regulatory accountability. Regulators expect risk-scaled vendor evaluation, executed quality agreements, control over sub-processors and silent SaaS releases, and a Part 11 audit file that stays current beyond initial onboarding.

  • 21 CFR 211.84 / 820.50Purchasing and supplier controls scale qualification depth by GxP impact and block vendor approval while required remediation findings remain openRisk-tiered gate
  • EU ANNEX 11 §3Formal agreements, supplier audit evidence, SOC/ISO attestations, and Quality approvals stay bound to one inspectable ServiceNow vendor recordSigned vendor file
  • ICH Q9 / Q10Ongoing supplier monitoring, expiring attestations, and quarterly SaaS release notes trigger scoped impact assessments linked to the systems the vendor supportsContinuous watch
  • SAAS & AI SCOPEEmbedded vendor AI features, model provenance, customer-data training boundaries, and sub-processors require signed intended-use conditions before enablementConditions bound

Bring us your hardest GxP third-party risk workflow.

We'll walk through how it would run on your ServiceNow: governed, evidenced, and with AI only where you want it.

Use your company address. We can’t take personal email providers.

Digits are fine, with or without spaces or dashes.

or email processx@usdm.com