SystemQuality Operations & CAPA

CAPA Tracking & Escalation

A CAPA tracking system that draws each action's promised dates as a line, places overdue work on its tier by working days, and reads every extension request before a named person signs it.

See one second extension judged, tiered and signed ↓
Watch with transcript →
The problem

A second extension on sterile work, granted on a typed reason

Each week the coordinator exports the overdue report from the QMS, chases owners by email and carries the worst of it to the monthly quality review. An owner who cannot make the date files a request with a typed reason and a new date. Someone signs it, the record shows the new date, and the old one survives only in the history.

Nobody sees that the same action has now slipped twice, that the line keeps running without the fix, or that the client's quality agreement asked to be told. Late work climbs by habit: an email when it looks bad, a line in the council deck. At inspection the investigator asks for the CAPA log, counts the extensions, and the site rebuilds why each one was granted.

Built forQA CAPA coordinatorsCAPA action ownersDepartment headsSite QA heads

The Problem Today

A CAPA date moves on a typed reason, and a second slip can run with nothing in place to protect the product.

164
211.192 citations, FDA FY2025 drug inspections published
2
isolator glove tests per campaign at minimum, EU GMP Annex 1 published

Kept apart, joined by hand

  • QMS export
  • Requests
  • Campaigns
  • Supplier
  • Escalation by memoryLate work reaches a manager when someone thinks it looks bad
  • The client finds out lateA moved date can first surface at the client's own audit

The Solution

  1. Each promise drawn as a lineFlat while its date holds, a step at each signed extension
  2. Tiers placed by working daysOwner, department head, site council, head of quality
  3. Each request read and challengedRisk, history, schedule and letters; the agents' own count corrected
  4. Endorsed, then signed with protectionThe department head endorses; the site QA head signs with an interim control

Built-in controls

  • An amended request loses its signatures
  • No one decides their own extension
  • No message leaves the plant unread

What You Get

Each slip becomes a signed decision with the product protected meanwhile, and the client hears of it as its agreement asks.

  • Protection from the next campaignA second sterile extension carries a full glove test before each run
  • A CAPA log with its reasons keptEach step of each line carries its reason, evidence and signer
  • Each client sees its new dateWith the reason and the interim control, for its own products only
Features

CAPA tracking features, from the slip chart to the signed extension

One action, a glove test before every isolator campaign, asks for its second extension; the coordinator, the engineering manager and the QA head take it to a signed decision.

demoSample data: every person, action and record, and the isolator itself.

  1. 01Slip chart

    CAPA tracking on one chart: every promised date, week by week

    • A line for each action's promises. The line stays flat while the date holds and steps up only at a signed extension, so a second slip shows as a second step.
    • Overdue work placed on its tier. Working days past the date set the tier, from the owner to the top tier, and nobody counts them by hand.
    • The agents' reading next to the lines. What each agent read, how sure it is and whom it hands to show beside the chart, and the coordinator can steer the run in plain words.
  2. 02Extension read

    CAPA extension justification read against risk, history and the schedule

    • Second extensions on Grade A work flagged. The reader names the repeat, the grade and what is missing, here an interim control while campaigns keep running on the isolator.
    • Equipment history read with the request. An earlier glove failure and a settle plate count on the same isolator are cited, so the case for protection rests on records.
  3. 03Request packet

    CAPA due date extension request shown as the QMS record, with its letter

    • The request as its system holds it. Promise history, reason code, justification and attachments read as one document, the way an inspector will open it.
    • Read to the end before any signature. The packet counts as read only at its end after the set reading time, and each read is logged under the reader's name.
  4. 04Challenger

    Inspector's questions on repeated extensions, the agents' own draft included

    • Repeated extensions questioned first. The opening point asks what protects the product through the campaigns before the new date, when the shared tester could test every port meanwhile.
    • A miscount in the agents' draft caught. A campaign count of two is corrected to three from the schedule, and a drafted interim the rule already requires is rejected.
  5. 05Tier 2 message

    CAPA escalation process: the tier 2 request for endorsement, drafted

    • Drafted from the evidence, with citations. Each sentence carries its source, so the department head sees the dates, the supplier's letter and the procedure clause behind the ask.
    • Opened exactly as it will arrive. Sender, recipient, subject and body show before sending, and nothing leaves until the coordinator presses send.
  6. 06Endorsement

    Department head endorsement, signed under their own name and meaning

    • Endorsement after the packet is read. The engineering manager cannot endorse until the tier 2 message has reached them and the packet was read to its end.
    • Name, meaning, reason and time together. User ID and password, the printed meaning, the reason, the time and the session are recorded in the manner of 21 CFR Part 11 §11.50.
  7. 07QA decision

    Second extension approved only with an interim control in force

    • Interim controls that add protection. A daily visual check, which Annex 1 already asks for, or one glove change that leaves the other ports untested is blocked; a full test before each campaign passes.
    • Approve as asked only as a named override. Until the rule learned from earlier rulings is approved, skipping the interim means overriding the challenger's point by name in the signature.
    • Safer steps take effect at once. The interim task opens the moment the QA head signs, with its own owner, ahead of the next campaign.
  8. 08Second step

    The action's line takes its second step, with the interim task beside it

    • Only signatures move a line. The step appears after the QA head signs, so the chart never shows a date nobody approved.
    • Interim controls tracked as tasks. The interim test has its own line, owner and end, and only the QA head can end it.
    • An amended request reopens. If the owner changes the date after approval, the signatures clear, the evidence pack reads unsigned and the agents read the new version.
  9. 09Client notice

    Client notice of the new CAPA date, the reason and the interim control

    • Drafted where the quality agreement asks. The notice cites its clause and states the new date, the reason and what protects the product until then.
    • Read and sent by the coordinator. Send stays disabled until the coordinator has read the whole notice; the client's portal changes only after sending.
    • A client sees its own products. The client's reviewer reads dates for its products only, and can ask a structured question that a person answers.

A first extension is the coordinator's call; a second needs two signatures

Owners ask, coordinators decide first extensions, department heads endorse second ones and site QA heads decide them.

QA CAPA coordinators

Own the daily review and tier messages, and decide first extensions

  • Overdue work tiered before the meeting
  • Messages drafted with their sources
  • Client notices that wait for their read
CAPA action owners

Deliver the action, ask for extensions and attach the evidence

  • The name of whoever holds the request
  • The evidence still owed, item by item
  • Attachments accepted only from the real record
Department heads

Endorse or decline second extensions in their department

  • The full packet before any endorsement
  • A request that names its procedure clause
  • An endorsement that proves it was read
Site QA heads

Decide second extensions and set the interim control the product needs

  • Challenger points answered before signing
  • Interim controls drawn on the chart
  • Past rulings offered as proposed rules
More screens

A valve arrived, and its fitting waits on a loop shutdown nobody has booked

Around the slip chart: the action list, what each owner still owes, the council's agenda, rules learned from rulings, and what the client sees.

One action's audit trailEvery agent step and signature on the glove test action, each with reason, meaning and session; a CSV download and the request's evidence pack, which reads signed or unsigned.
Open actions with their tierThe plant's open actions by date with owner, client, extensions and tier; bulk reminders go out only after a sample of the drafts is opened.
What each owner still owesOwners grouped with the evidence each of their actions still needs, and a reminder drafted per person for the coordinator to send.
The site quality council's agendaActions that reached the council's tier or the top one, with what is owed and the owner's update; the council's decision is signed, with its reason code.
Rulings that turn into rulesThe QA head's past rulings on extensions beside the rule proposed from them; it guides the extension reader only after the company's head of quality has approved it.
The client's view of its CAPA datesThe client's reviewer sees its own actions with the last date notified and the new notice to acknowledge or question; internal notes stay out.

demoSample data, from the working solution.

No one may loosen an escalation setting they proposed themselves

A signature is accepted only from the person it names, and only after the record behind it was opened.

QA CAPA coordinator
Sees
The packet to its end, each tier message as it will arrive, and the client notice
Signs
First extensions within their authority, and sends each message and notice
Department head
Sees
The endorsement request and the packet with the supplier's letter
Signs
The endorsement of a second extension, or a decline with a reason
Site QA head
Sees
The packet, the challenger's open points and whether the dates hold
Signs
The decision on a second extension, the interim control and its end
Site quality council chair
Sees
Actions late past the council's tier, with what each still owes
Signs
The council's decision on each, with a reason code
Head of quality
Sees
Rules proposed from past rulings and any setting that loosens escalation
Signs
Learned rules, and loosened settings that someone else proposed

An interim control that adds nothing is rejected, even the agents' own

Whether a date may moveThe coordinator decides a first extension within authority; a second needs the department head's endorsement and the site QA head's signature.
What protects the product meanwhileThe site QA head sets the interim control; the agents draft one, and the challenger rejects any that adds nothing.
What leaves the plantAgents draft tier messages and client notices; the coordinator reads each one and sends it.
Whether evidence has arrivedThe chaser lists what each owner owes; an attachment counts only once its document exists in its own system.
Which past rulings guide the readerNo proposed rule shapes a reading before the head of quality has signed for it.

The production schedule counts the campaigns that run before the new date

Sources are manufacturing and quality systems alone; free text from an owner or the client never changes a date or a count.

QMSCAPA actions with owners and due dates, extension requests and their history, deviations
ERPThe production schedule and its campaigns, purchase orders for equipment on order
Environmental monitoringThe isolator glove test log and settle plate results
Document managementProcedures, IQ/OQ plans and supplier letters attached to requests
Learning managementTraining records the action's evidence depends on
Quality agreementsEach client's clause on when a moved CAPA date must be notified

CAPA tracking questions from coordinators and site QA heads

What is CAPA tracking?

CAPA tracking follows each corrective and preventive action from approval to closure against the date its owner promised. Here each open action is a line of its promised dates, overdue work is placed on its tier by working days, and each extension request is read before a named person signs it.

How is a CAPA extension justification judged?

Against the action's risk, its history, the production schedule and the attachments. The extension reader says what is missing, such as an interim control while product keeps running, and the challenger asks what an inspector would.

How does the CAPA escalation process work?

Overdue work rises by working days past its date: the owner first, then the department head, then the site quality council, and at the top the company's head of quality. The thresholds are settings: tightening takes effect immediately, while loosening waits for a second person's signature.

What is an interim control on a CAPA?

The protection in place until the corrective action is live. On a second extension of Grade A work, the site QA head approves only with an interim control that goes beyond what the rule already requires, and it is tracked as a task of its own.

Does the client hear about a moved CAPA date?

Where its quality agreement asks. The client notice writer drafts the new date, the reason and the interim control for that client's products only, and the coordinator reads it to the end before sending it to the client's portal.

Do the agents approve extensions or send messages?

No. They read, count, draft and challenge. The coordinator sends each message, the department head endorses, the site QA head decides, and nobody decides their own request.

How is CAPA timeliness measured?

In working days past the date the owner promised, with every earlier promise kept in view. An action's line steps up only at a signed extension, so a second slip shows as a second step, and the working days past the current date set its escalation tier.

Bring an action that
slipped twice.

Send one CAPA with its extension history and the schedule behind it, and we will show where its line stepped and what should have protected the product.