In one sentence
QFormance is built around a small set of shared systems — scope, access, approvals, controls, the action register — and the value comes from the connections between modules, not just the features within them.
Three things to remember
- The same action register, approval workflow, controls component, scope picker, and access-control engine are used by every module that needs them. Learn it once, recognize it everywhere.
- Imported risks are forks, not links. A copy goes to the receiving module so it can adapt without polluting the source.
- The compliance map is the multiplier. Section-level mapping powers audits, gap analysis, and AI clause suggestions automatically.
Documents ↔ Audits
- Compliance mapping on document headings feeds clause context to audit questions automatically.
- Audit questions link to specific document sections for reference during audits.
- Topics in the audit Question Bank are linked to controlled documents.
Documents ↔ Gap Analysis
- The compliance map on document headings is the evidence the gap analysis reads automatically.
- Auto-populate evidence links scans the map to connect document sections to clauses in seconds.
- AI gap analysis then assesses each clause against the linked evidence.
Documents ↔ Training
- Documents with Requires Acknowledgement appear in users' Training Hub → Pending.
- Quizzes authored on documents are tied to the exact approved version at acknowledgement time.
- Completions feed Training Reporting.
Risk Register ↔ JHA, MOC, FMEA, Exemptions, NCRs
- Risks from the register can be imported into JHAs, MOCs, FMEAs, and Exemptions.
- Imported risks are forks — edits in the receiving module don't affect the original.
- Risk scoring uses the same configurable matrix across all modules.
- NCR root cause analysis can push a risk to the register via Capture Residual Risk on the Root Cause tab — the resulting register risk can then be imported by any other module.
Audits ↔ Non-Conformances
- Audit findings can generate NCRs directly from the Perform / Findings view.
- Linked items connect audits to existing NCRs.
- NCR actions can be tracked and reviewed within audits.
NCR ↔ Actions & Meetings
- NCR actions can be linked to meetings for review.
- Meeting minutes can reference NCR discussions.
- Actions created in meetings appear in the NCR's action list.
Meetings ↔ AI & Actions
- AI Meeting Minutes generates a structured summary from pasted notes or an uploaded transcript (.vtt, .srt, .txt).
- Approved controlled documents can be included as context — the AI grounds the minutes in their content; only documents you have access to are available.
- The review step surfaces agreed action items and optional AI recommendations (unresolved risks, compliance exposures, process improvements).
- Saving with actions creates real Action records linked to the meeting — they appear in each assignee's Actions view.
MOC ↔ Documents
- MOCs are raised against a specific document — the document determines the approval chain.
- Document changes can trigger MOC creation.
- Approved MOCs can auto-create document revisions.
The shared building blocks
QFormance feels like one system because the same five components show up everywhere they're useful.
Shared action system
| What it is | Modules that use it |
|---|---|
| One action register, one set of statuses, one closure flow | NCR, Audit, MOC, JHA, FMEA, Meeting, Gap Analysis |
Every action appears in the centralized Actions page. Status changes, closure notes, and verification work identically everywhere.
Shared approval workflow
| What it is | Modules that use it |
|---|---|
| Up to 3-step approval chain, delegation, configurable routing | MOC, Exemptions, JHA, FMEA, Documents |
See Approvals for the chain mechanics.
Shared controls
| What it is | Modules that use it |
|---|---|
| Same controls component with document linking and per-dimension scoring | Risk Register, JHA, FMEA |
Shared scope and access
| What it is | Where you see it |
|---|---|
| The facility + department picker | Every record's create form and detail page — see Facility & Department Scope |
| The org-wide vs restricted access model with access groups | Every record module — see Access Control |
Learning how scope and access work is one-and-done across the whole product.
Entity links
Most modules support linking to other items:
- Link NCRs to audits, meetings, risks, and documents.
- Link risks to NCRs, audits, and MOCs.
- Links are bidirectional — they appear on both sides.