Checked before it is saved
Submissions, approvals, events, settings changes, alerts and deviations all pass the ruleset first.
ProductsPillarsThree pillars.
• The platform
Three pillars.
One record.
Every Factro product runs on three pillars. Compliance native: a Compliance Engine checks every action against your ruleset. Process driven: Task Manager moves the work across departments. AI first: Prism explains what your records are telling you.
Inside ERP, MES and QMS. Nothing to bolt on.
Pillar 01 · Compliance Native
Every action is checked.
Before it is saved.
An isolated service holds the ruleset for your framework and industry, and checks every action against it.
Held, not lost
An action that fails a rule waits for the right signature, with the reason attached.
Every decision is signed
Approve, approve with conditions or reject. The signature and its meaning go to the append-only, hash-chained audit trail.
Rulesets
The ruleset changes when
the regulation does.
One ruleset per framework and industry. It changes only when the regulation does, after internal and external review.
Pharmaceuticals
Frameworks
- US21 CFR Part 11
- EUEU Annex 11
- INRevised Schedule M
- GlobalPIC/S GMP
- GlobalICH Q10 / GAMP 5
RS-PHAv2026.4
CTL-DIData integrityCTL-DOCDocumentationCTL-PRDProductionCTL-QCQuality controlCTL-RELReleaseCTL-TRNTraining
Validated internally and externally
- 01
A governing body issues a change
New or revised regulation is published.
- 02
Impact assessed
We map the change to each affected rule and control.
- 03
Internal validation
Our quality and engineering teams test every affected rule.
- 04
External validation
Independent reviewers check conformance before release.
- 05
Versioned release
A new ruleset version ships with release notes. Earlier versions stay on record.
Pillar 02 · Process Driven
Work finds its owner.
Nobody has to chase it.
Task Manager drives the work within and across departments, as you configure it. Every handover arrives as a ticket with an owner, a clock and the record attached.
My work
Workflow and ad-hoc tickets assigned to you, across every module.
Open work105 open, 4 in progress, 1 blocked
Overdue2Oldest is 1 day over
Due in the next 24 hours3Next sign-off in 7h
Completed, last 7 days15Plus 1 done, waiting for verification
On time, last 7 days90%Up 4 points on the 7 days before
Time to verify, last 7 days1d 6hMedian, raised to completed
Open5
TKT-0142Overdue 1d
Plan sales order SO-22
Order to make, step 3 of 5TKT-0139Overdue 4h
Raise invoice for GDR-10231
Make to release, step 6 of 6In progress4
TKT-014018h left
Effectiveness check, DEV-0447
CAPA actionTKT-013820h left
Order O-5510 accepted from production
HandoverBlocked1
TKT-0136Blocked 2d
GRN-4471 handover to QC
HandoverDone15
TKT-0121Done 3d late
Invoice raised for GDR-10190
Make to release, step 6 of 6Every ticket has an owner
Workflow tickets land in Task Manager by role. Ad-hoc tickets sit beside them.
The clock is on the card
Overdue, due today and time left show on every ticket, so a delay is visible early.
Handovers are acknowledged
A blocked handover names who it is waiting on until they accept it.
Task performance
Every task counts.
So does the person behind it.
Each task is measured from assignment to close. Good work gets noticed, overdue work gets escalated, and management sees the whole plant without asking for a report.
Measured
Every task, timed from assignment to close.
0%On time
0Closed this month
0.0 hMedian time to close
Celebrated
Good work gets noticed.
50 batch reviews,
all on timePriya R. · QA
all on timePriya R. · QA
Line 2 closed every IPQC check on time this month.
Accountable
Overdue work never goes quiet.
- ASOwner · Arjun S.Review EBR B-2279 · due 14:00
- JBShift lead · Joy B.Notified at 16:00
- MKQA head · Meera K.At 18:00 if still open
Visible to management
The whole plant at a glance.
| On time by week | W1 | W2 | W3 | W4 | W5 | W6 | W7 | W8 |
|---|---|---|---|---|---|---|---|---|
| Stores | 92 | 94 | 90 | 95 | 96 | 93 | 97 | 96 |
| Quality control | 85 | 88 | 82 | 86 | 90 | 91 | 89 | 93 |
| Production | 90 | 92 | 94 | 91 | 93 | 95 | 94 | 96 |
| Quality assurance | 88 | 84 | 87 | 90 | 92 | 89 | 93 | 94 |
| Engineering | 78 | 80 | 76 | 83 | 85 | 82 | 86 | 88 |
| Dispatch | 95 | 96 | 94 | 97 | 96 | 98 | 97 | 98 |
Pillar 03 · AI First
One interface. Five agents.
Meet Prism.
Five specialist agents in one window, open from any page. Each reads the records for its job, shows its sources, and hands the decision back to a person.
01PlannerKnow what is at risk before you promise.02Stores AnalystSpot the lot that will cause trouble.03Compliance CheckerCatch a gap while the batch is still open.04Deviation AnalystInvestigate with the history already read.05Release ReviewerRelease on facts. A person still signs.
NextMore to comeNew agents join the same window.
Privacy
Private by design.
Scoped to your plant.
Prism AI runs on private models in Factro’s private cloud, and sees only what your role allows.
Role-based access
An agent reads only what your role can open, with the same permissions as the rest of Factro.
Stays in your tenant
Questions, records and answers stay inside your tenant. Nothing is sent to an outside AI service.
Fine-tuned local models
The models run in Factro’s private cloud, next to your data, not on a public AI platform.
Scoped to your organisation
Agents answer about your plant, your records and your work. Lunch recipes are politely declined.
Decisions stay with people
Agents do not sign, release or close anything. Every regulated step still needs a person.
Sources with every answer
Each finding links to the records it came from, so it can be checked before anyone acts.
What the agents are built onCompliance score with gap guidanceDeviation history and trendsStructured, AI-ready records
Before you start
Questions
plants ask us.
Straight answers on rulesets, tasks and what the agents do and do not do.
Talk to our teamWhat does the Compliance Engine check?
Every submission, approval, event, settings change, alert and deviation, before it is saved. An action that passes is saved; one that breaks a rule is held, with the reason attached, until the right person signs for it. Either way, the check is written to the append-only, hash-chained audit trail with the rule that decided it.
Who can change a ruleset?
Only Factro, and only when a governing body changes the regulation. Each change is mapped to the rules and controls it affects, validated by our quality and engineering teams and by independent reviewers, and released as a new version with release notes. Earlier versions stay on record, so you can show which rules applied to any past batch.
What can our plant configure?
Everything that is yours to decide: workflows, approval conditions, release queues, roles, SLAs and the handovers between departments, set around your SOPs. The ruleset carries the regulation; your configuration carries your procedures. Every configuration change is recorded in the audit trail with who made it, when and why.
Can a task be closed without meeting a control?
No. Task Manager moves the work, and the Compliance Engine decides whether the action is allowed. A ticket whose action fails a rule stays open with the reason on it, until the condition is met or an authorised person signs an exception.
How do the three pillars work together?
On one record. A failed IPQC check is held by the Compliance Engine before the batch can move on, opens as a deviation ticket with an owner and a clock in Task Manager, and reaches the Deviation Analyst in Prism AI with the history for that line, product and stage already attached. Nothing is copied between the three, so nothing can drift apart.
Does our data leave our tenant?
No. Prism AI runs on Factro’s proprietary model in Factro’s private cloud, scoped to your tenant and to the role of the person asking. Nothing is sent to an outside AI service, and nothing is used to train a model.
Regulatory frameworks shown here are control-mapping references, not product certifications. Applicability depends on your processes, configuration, validation and operating procedures.
AI-generated findings need review against source records and your quality procedures.
Make it your workflow
Bring your process.
See all three at work.
Walk through one batch with our team, from the rule that checks it to the task that moves it and the agent that explains it.