In one sentence
QFormance is one connected quality system, not a stack of separate apps — once you understand how facility scope, access control, and the approval workflow work, every module reads the same way.
Three things every module shares
- Facility & department scope — every record knows where it applies. See Facility & Department Scope.
- Access control — every record knows who can see it. See Access Control.
- Approvals — the same approval engine powers Documents, MOC, Exemptions, JHA, and FMEA.
First sign-in
- Open your organization's QFormance URL.
- Sign in with email and password (or SSO / passkey if your org has those configured — see Auth & Sign-in Policy).
- You land on the Dashboard, which surfaces what needs your attention today: pending approvals, overdue actions, training due, audits in progress.
What's on the sidebar
The left sidebar is the map. Click anything to jump in.
| Module | What lives here |
|---|---|
| Documents | Controlled document library — authoring, versions, approvals, compliance mapping |
| Ask the Library | Natural-language Q&A across your controlled documents (AI-powered) |
| Training | Pending acknowledgements, assigned courses, completion history |
| Gap Analysis | Score your QMS against a regulatory standard, with AI assistance |
| Audits | Plan, conduct, and close internal and supplier audits |
| Audit Planner | Annual program — when each audit happens, at which facility |
| Meetings | Minutes, attendees, action capture, AI-drafted summaries |
| Risk Register | Identify, score, and manage organizational risks |
| FMEA | Process risk assessment with severity / occurrence / detection |
| JHA | Task-level safety assessment |
| MOC | Management of Change — controlled changes to processes, equipment, documents |
| Exemptions | Concessions, waivers, deviations with scope and expiry |
| Non-conformances | Issues, complaints, root cause, corrective actions |
| Suppliers | Supplier directory with cross-module activity and linked records |
| Clients | Client directory with cross-module activity and linked records |
| Products | Product / part catalog with a bill of materials and linked records |
| Trace Map | Follow the links, products, and actions from any record across modules |
| Actions | Every action assigned to you, across every module |
| Approvals | Items waiting for your sign-off |
Admins can turn individual modules on or off at Admin → Organization → Modules, so your sidebar may show a subset of the above.
How modules connect
QFormance is built so the interesting work happens between modules, not just inside them. A few connective threads run through the whole system.
One place for cross-cutting work
- Actions are pulled from every module — NCR corrective actions, audit findings, meeting action items, MOC and FMEA tasks — into a single Actions queue per person, each linked back to the record it came from.
- Approvals run on one shared engine and one queue. Documents, MOC, Exemptions, JHA, and FMEA route through the same approval chains, routing rules, and delegations, so signing off feels identical everywhere.
Shared reference data
- Suppliers, Clients, and Products are shared records you link to from NCRs, MOCs, audits, documents, meetings, risks, and more — so any record can point at the parts and partners it involves.
- Products carry a bill of materials, and picking a product narrows the supplier list (and vice-versa) on the forms that touch them.
- Documents are referenced everywhere — a MOC cites its source SOPs, an audit builds questions from a controlled document, a training obligation attaches to a document version, and gap analysis reads the documents mapped to each clause.
Shared scoring and standards
- Risk scoring uses one configurable matrix across the Risk Register, JHA, and FMEA — score it once, and it reads the same everywhere.
- Compliance mapping ties your documents to regulatory standards. That single map then powers audit-question context, gap analysis, and AI compliance-mapping suggestions automatically.
Records that feed each other
- An audit finding surfaces related NCRs and prior findings, so recurring problems are easy to spot.
- An NCR can generate a residual-risk entry for the Risk Register from its root cause and corrective actions.
- A meeting turns its minutes into real action items; a document revision turns into a training obligation for the people who need to re-acknowledge it.
Find any thread
- Cross-module similarity (AI) surfaces related records as you work — similar NCRs, related audit findings, comparable risks, exemptions, and meetings.
- Trace Map walks the links for you: start from any record and follow its connections, products, and actions across every module in one view.
- Every change, in every module, lands in the same Part 11 audit trail — a per-record History tab plus the activity timeline.
Notifications
The bell icon in the top header surfaces what needs you:
- Items waiting for your approval
- Actions assigned to you
- Approval status changes (approved, rejected)
- Training items that need acknowledgement
Click any notification to jump straight to the record.
Your profile
Your name at the bottom of the sidebar opens your profile — change name, email, password, language, notification preferences, and (where enabled) enroll passkeys.
What to read next
- Facility & Department Scope — the foundation every record sits on
- Access Control — who sees what
- Roles & permissions — what people can do
- Onboarding Checklist — for org admins setting up