All blueprints

See whether the change worked.

Connect the finding, corrective action and follow-up evidence. Ask neil to investigate recurrence and prepare the effectiveness review in Seal.

Illustration of a seal examining a circled change in a trace alongside run, sample and procedure records.

Example evidence

Failures fell. So did use.

Before · 150 runs12
After · 60 runs5

Recorded failures · shared scale 0–15

Native Seal chart of fictional CAPA-071: twelve failures before the change and five after, with the exposure counts retained.
Fictional records in the current Seal interface. Published means a saved version, not approval. Open native Seal view

Fewer failures is only half the comparison.

The count drops from 12 to 5. But the pumps also run less often: 150 runs before the change, only 60 after.

Inspect the six source periods
Same pump population and leakage classification; April intervention excluded.
PeriodWindowFailuresRuns
JanuaryBefore448
FebruaryBefore552
MarchBefore350
MayAfter220
JuneAfter122
JulyAfter218

Keep the action and its effect in the same investigation

A procedure was changed. The work order is complete. The people involved have been trained. Those are implementation records; the effectiveness review asks a different question: did the intended outcome improve under comparable conditions?

Seal connects the source deviation, investigation, action, controlled change and follow-up evidence. Open the CAPA to inspect the work performed; follow its source records to challenge the conclusion. The example above keeps both the failure count and the equipment-use population, so a quieter production period does not masquerade as a successful correction.

Define the comparison before reviewing the outcome

Record the failure classification, asset or product population, baseline, intervention date, follow-up window and measure of exposure. Retain the inclusion and exclusion rules. Decide how much observation is needed and what result would satisfy the review, with the rationale and required authority.

CAPA-071 compares January–March with May–July, excluding the April intervention. The saved charts use six linked period records. They show a descriptive comparison, not a statistical conclusion: event classification, population changes and uncertainty still need assessment. A missing run count is missing evidence—not zero exposure and not a zero failure rate.

Investigate competing explanations

The same symptom can follow a different mechanism. Keep observations separate from hypotheses, and connect each proposed explanation to supporting evidence, contrary evidence and the work that would distinguish it. Equipment configuration, replacement-part lots, service history, operating conditions and personnel scope may all matter.

neil can investigate the permitted record population, compare related events and prepare linked evidence requests. Ask it to expose the assumptions behind the comparison and propose the next measurements. An investigator reviews the explanation; a pattern alone is not a root-cause determination.

Turn the investigation into controlled work

Each action retains its owner, due date, dependency, required completion evidence and relationship to the finding. A procedure revision, equipment modification and training assignment can be different pieces of the same response. Configure reminders and escalation around the agreed workflow, retaining reasons and approvals for changed commitments.

Bring the source procedure to neil. It can author proposed changes to the plan, capture fields and review states, then prepare verification cases. That includes a missing exposure count, a recurrence after implementation and an attempted closure with outstanding evidence. Your team tests and publishes the change through its authorised process.

Review effectiveness without rewriting the history

Retain the implemented version, original baseline, actual follow-up population, analysis and reviewer conclusion. If the outcome is not demonstrated, record why and define the further work. A configured reassessment or reopening path should preserve the earlier decision, not erase it.

The review record should let a colleague reconstruct what changed, which records were compared, what remains uncertain and why the CAPA was closed or continued. It should not require rebuilding that history from separate action trackers and spreadsheets.

Explore deviations and investigations, change control and equipment.

Operating model

Configured in Seal, with shared records across the work.

Included in this blueprint

  • Linked to Source
  • Root Cause Tools
  • Action Tracking
  • Mandatory Effectiveness
  • Automatic Reopen
  • Trend Analysis
  • Escalation Workflows
  • Audit-Ready Records
  • AI Root Cause Suggestions
  • neil Effectiveness Analysis

Connected across Seal

Capabilities

Connected records

Entity hierarchy
What it records
Kind
CAPA
Connect the source, action, effectiveness criteria and review. Configure closure requirements for the intended workflow.
entity
Corrective Action
Fix a problem that has occurred. Verify it doesn't recur.
template
CAPA-071 / pump leakage
Twelve failures before the change, five after. Equipment use also falls from 150 to 60 runs. Effectiveness remains unproven.
record
Preventive Action
Fix a potential problem before it occurs. Proactive, from risk or trend analysis.
template
Systemic CAPA
Link related events and investigate shared contributing conditions before proposing a wider change.
template
Effectiveness Verification
Retain the population, exposure, criteria and follow-up evidence. Inconclusive or failed checks follow a configured reassessment path.
entity
Effectiveness follow-up
Six source periods retain failures and exposure. The observed rate changes from 8.0 to 8.3 failures per hundred runs; review remains open.
record
Root Cause Analysis
Compare candidate explanations with supporting and conflicting evidence. Record how they were tested before concluding a cause.
entity
5-Why Analysis
Why unclear? Procedure poorly written. Why? Never peer-reviewed. Why? No review process. Now you can fix it.
template
Fishbone Diagram
Equipment, Process, People, Materials, Environment, Measurement. Consider all categories before settling.
template
Is/Is-Not Analysis
Compare affected and unaffected populations. Patterns suggest hypotheses to test; they do not establish a cause.
template
Source Event
Deviation, audit finding, or complaint. Full context travels with the CAPA.
entity
Action Item
Owner, due date and evidence requirement, with configured escalation for overdue work.
entity
Escalation
Owner → Manager → QA Leadership. No CAPAs lost in the queue.
entity

Questions and answers

Configure closure to require the approved effectiveness review, not merely an attachment. Define the criteria, source population, exposure and observation window up front. Verify the workflow with missing, failed and inconclusive evidence before using it.
Use a configured path to reassess the action and its evidence. A failed check does not by itself prove the original cause was wrong: incomplete implementation, changed exposure or measurement differences may matter. Retain the original assessment and record the next authorised work.
Yes. When you identify that multiple deviations share a common root cause, you can link them all to a single CAPA. This is better than opening multiple CAPAs for what's really one systemic issue.
Dashboards show CAPA workload by owner and team. You can see who's overloaded and redistribute. Trend analysis helps you identify systemic issues that, once fixed, will prevent future CAPAs. Better to fix one root cause than manage ten symptoms.
Both are supported. Corrective actions address problems that have occurred. Preventive actions address potential problems identified through risk assessment, trend analysis, or proactive review. The workflow is similar, but the triggering event differs.
External CAPAs can be tracked in the system with appropriate visibility controls. You see status and evidence without exposing internal details. Link them to your supplier quality records and incoming inspection results.
Yes. Define your own phases, approval requirements, and escalation rules. Different CAPA types can have different workflows. A simple correction might need less rigor than a systemic corrective action.
Audit findings can trigger CAPAs directly. The finding links to the CAPA, and you can track audit response status across all findings. When auditors return, show them which findings are addressed and which CAPAs verified effective.
Compare related events, assets, parts and operating conditions across the permitted records. Shared categories are a starting point for investigation, not proof of a common cause. Link the evidence and testable explanations before extending an action to a wider population.
Closure rates, overdue percentages, time-to-close distributions, effectiveness verification pass rates, recurrence rates. Dashboards show whether your CAPA program is actually preventing problems or just documenting them.

Related blueprints

See your process in Seal.

Tell us about your workflow. We’ll show you how neil and Seal can help your team.

Book a demo