Skip to main content

Your CSA plan, function by function.

Describe what your software does. Each function gets FDA’s risk call, the assurance it needs and a record to fill in, ready for Word.

The software

Regulated as

What it does

  1. Does a person review each decision before it takes effect?
  2. Is the trend relied on to catch safety problems?

Assurance plan for LIMS 4.2

FunctionProcess riskWhyAssurance
Passes or fails each resultHighIt judges acceptability with no human review: FDA’s example of high process risk (V.A.2).Scripted or hybrid testing, as rigorous as the harm a failure could cause (V.A.4).
Sends stability pull alertsNot highManaging data, automating an existing calculation and sending exception alerts are FDA’s examples of not-high process risk (V.A.2).Unscripted testing (scenario, error-guessing or exploratory) against objectives with pass or fail criteria (V.A.4). Test any calculation you configured.
Trends out-of-spec resultsNot highSafety is not decided from this trend, and FDA’s high example is for trending data essential to safety and quality (V.A.2).Unscripted testing (scenario, error-guessing or exploratory) against objectives with pass or fail criteria (V.A.4).
Monitors the system’s uptimeNot highSupporting software, such as test tools and general record-keeping, is not high process risk (V.A.1, V.A.2).Assess the vendor and check the installation. For some lower-risk functions the vendor’s work may be enough (V.A.5).
Signs users inIn scopeAt a drug site 21 CFR 211.68(b) requires controls so that only authorised people change records.Test that each role can change only what it should.

Where each call comes from.

From the examples in FDA’s final guidance, Computer Software Assurance for Production and Quality Management System Software (3 February 2026), with its section beside each call. A drug site rests the same method on 21 CFR 211.68(b), and an EU or PIC/S inspection adds the scripts the draft Annex 11 expects. CSV and CSA compared quotes each source.

Keep the record as the work runs.

In Seal each test, result and signature keeps its audit trail as the work runs: the evidence FDA prefers to screenshots.