Key takeaways
- The quality system records deviations and CAPAs well; the work that closes them happens in other teams' inboxes.
- GeniOS links each record to the emails, meetings, orders and documents that show whether it is really moving.
- The QA manager hears about a CAPA at risk days before its due date, with one owner and one next step.
- Closure needs proof, such as the approved report or the completed action, never a status changed by hand.
The problem
A tablet plant raises a deviation on a Monday night shift: a seal on a granulator was found worn after a batch. The batch is held. Quality opens a deviation record with an investigation due in 30 days. The investigation points to a gasket that wears faster than the maintenance schedule assumed, and three corrective actions are agreed: replace the gasket with a better grade, change the maintenance interval, and update the cleaning procedure.
Each action belongs to a different team. Engineering has to source the new gasket. Maintenance planning has to change the schedule. The production manager has to revise the procedure and retrain operators. The QA manager owns the record, but not the work. Engineering replies that the part has a four-week lead time. The procedure draft sits in a reviewer's inbox. Nobody updates the CAPA, because each person thinks their piece is in hand.
Three weeks later the QA manager opens the weekly overdue list and sees the CAPA due in six days with nothing closed. A partner audit is booked for the 24th, and the CAPA log is in scope. Now she is writing an extension request instead of closing the action, and the auditor will ask why.
Why it slips today
Quality systems are good at holding records, due dates and approvals. They know a CAPA is open. They do not know that the part it depends on was never ordered, or that the reviewer who must sign the procedure is on leave.
| Where it lives | Who sees it | How it slips |
|---|---|---|
| Your quality system | QA | Shows the due date, not the blocker |
| Engineering and supplier email | Engineering | A long lead time is known but not raised |
| Document review queue | Reviewers | A procedure draft waits for a signature for weeks |
| Weekly quality review | Plant leadership | Overdue items are found once they are already overdue |
An overdue report is accurate, but it is late by design. What a QA manager needs is the CAPA that will miss its date, while there is still time to order the part or move the review.
The solution
GeniOS reads email, calendar, chat, documents and the quality and planning tools the plant already uses, read-only to start. It forms the quality team's goals from its own plans and meetings, such as zero overdue CAPAs before an audit, and checks every open deviation and action against them.
- Investigations near their due date. Deviation investigations with no draft report or root cause as the deadline gets close.
- Actions blocked outside quality. CAPA steps waiting on a part, a purchase order, a reviewer or another team's schedule.
- Effectiveness checks due. Checks that a fix really worked, scheduled months after closure and easy to forget.
- Repeat deviations. The same equipment, step or supplier causing deviations again, which suggests the first CAPA did not reach the cause.
For the wider picture of audits and evidence, see Audit Readiness and Risk and Compliance Monitoring.
See it on the whiteboard
Here is one CAPA moving from a quiet email about a lead time to a rush order placed in time.
CAPA-118 will be overdue before the audit
How: approve a rush order for the gasket today and file a justified extension for one step.
- Your tools. Engineering mentions a four-week lead time, the quality system shows the CAPA due in six days, and the calendar shows an audit on the 24th.
- GeniOS thinks. It sees a CAPA that cannot close on time, the second this quarter blocked on spare parts, with an audit coming.
- Intelligence. Ravi, the QA manager, gets one note: approve a rush order today and file a justified extension for the one step that cannot finish.
- Delegated. He hands the rush order note to a Reply Drafter agent for purchasing and approves it.
- Goal moves. The purchase order appears, GeniOS closes the item and the audit goal moves forward.
How GeniOS thinks and plans
For each open deviation and CAPA GeniOS connects four things. What happened: the record, the agreed actions and what each owner has said or done since. The pattern: actions that keep waiting on the same kind of blocker, such as parts, reviewers or a busy production schedule, and deviations that repeat on the same equipment. The impact: a held batch, a due date, an audit or inspection in the calendar, or a customer complaint linked to the deviation. The owner: the person who can move the blocked step, which is often outside quality.
It checks each item against the quality team's goals, such as no overdue CAPAs before an audit or investigations closed within 30 days. A CAPA due before an audit with a missing part rises; an effectiveness check due in three months stays quiet until it matters. Then it picks one next step, one owner and one date.
GeniOS does not decide root causes or approve quality records. People do that in the quality system, under the plant's own procedures. GeniOS makes sure the work around those decisions is moving.
How it delegates and gets it done
The owner answers with Delegate, Done, Later or Not relevant. Delegate hands the work to a person, such as the engineer sourcing a part or the reviewer who must sign a procedure, or to an AI agent, such as a Reply Drafter for a purchase request or a Scheduler for a training session. Nothing is sent until a person approves it.
An item closes only on proof: the approved investigation report, the purchase order, the signed procedure, the training record, the completed effectiveness check. A status changed by hand is not enough. When proof arrives, the goal moves, and GeniOS learns which blockers recur so it can raise them earlier. When a quote or rush order is needed, the purchase side works like Procurement Quote Management.
How it reaches you
Intelligence arrives on its own in the GeniOS Mac app, from the menu bar, and in the web dashboard. The QA manager sees the few deviations and CAPAs that need him today, each with a reason and a date.
What he no longer does: export an overdue list every week, chase engineering for lead times, walk the document queue to find stuck reviews, or decide which of sixty open records to look at first. Plant leadership sees the items at risk before the weekly review, not during it.
A worked example
The company, names, dates and numbers in this example are made up to explain the idea. A 400-person generics plant makes tablets and capsules for several markets. Ravi is the QA manager. In February a worn granulator seal leads to a held batch worth about $210,000 and a deviation with three corrective actions.
The engineer finds that the better-grade gasket has a four-week lead time, says so in an email to his manager, and waits for approval. The procedure update is drafted but sits with a reviewer. The CAPA is due on 18 March. A partner audit is set for 24 March.
On 12 March Ravi gets one note: CAPA-118 will miss its date, the gasket was never ordered, and this is the second CAPA this quarter blocked on spare parts. It suggests approving a rush order today, filing a justified extension for the gasket step only, and asking the reviewer to sign the procedure this week.
Ravi delegates the rush order note to a Reply Drafter for purchasing and the procedure review to the production manager. He approves the note at 10:30, and the purchase order appears the same morning. The procedure is signed on 14 March. GeniOS closes each step as its proof arrives. At the audit, CAPA-118 shows two actions closed and one extension with a clear reason and a part on order. GeniOS also raises a separate item: keep critical spares for this equipment in stock.
How to measure it
- CAPAs closed by the original due date. The share closed on time without an extension.
- Days of warning before a due date. How early a CAPA at risk is raised to its owner.
- Investigations closed within 30 days. Or whatever window the plant's procedure sets.
- Repeat deviations. Deviations on the same equipment or step within six months of a closed CAPA.
Where it applies
It fits regulated plants where quality owns the record but other teams own the work, including drug, device and ingredient manufacturing.
- Domains: Quality, Operations, Legal & Compliance
- Industries: Pharmaceuticals & Life Sciences, Manufacturing
- Roles: Executives, Managers
Questions about deviation and CAPA follow-through
Does GeniOS change records in our quality system?
No. It starts read-only and people keep making every quality decision in your own system. GeniOS watches the work around each record and raises what is slipping.
Will it decide the root cause?
No. Root cause and approval stay with your quality team under your procedures. GeniOS can point out that the same equipment or step keeps appearing.
What counts as proof that an action is done?
A record that shows the work happened, such as a purchase order, a signed procedure or a training record. A status changed by hand does not close the item.
How early does it warn us?
As soon as a blocker appears that makes the due date unlikely, such as a long lead time or a stuck review. That is often weeks before the overdue list would show it.
Status
Exploring This is an application area we are exploring with early customers. If CAPAs and deviations are where your audits get hard, book a call and we will show how it would work on your own inboxes and records, starting read-only.