A document library
that maintains itself.
Get your full documentation set in place fast — then let QFormance keep it current. Live definitions, reusable components, automatic headers, and QMS connections that trigger themselves.
In-Process Inspection Procedure
4.2InspectionISO 9001 §8.6AS9100D §8.6
Operators perform first-piece inspection per WI-INSP-04. Where measurement equipment is used, calibration intervals must be current per the Calibration Program.
Start fast.
Import your existing documents, start from a template, or write from scratch — the editor gets you to a compliant, approved document as quickly as possible.
Import from Word or PDF
Drop in an existing document and AI cleans up the formatting, structure, and heading hierarchy automatically — ready to map and approve.
Templates
Pre-built starting documents with title, category, class, and initial content already set. Authors pick a template from the New Document modal and start writing immediately.
AI Compliance Mapping
Open the AI panel on any document and it reads your content against your active standards — surfacing covered requirements and flagging gaps before you submit for approval.
Rich editor
Slash commands, heading auto-numbering, live table of contents, and an automatic formal header — logo, version, owner, approver, and revision history generated for you.
Stays current automatically.
The hardest part of document control isn't writing documents — it's keeping them consistent when things change. QFormance handles that for you.
One glossary. Every doc updates.
Maintain one glossary for your organization. A document’s definitions table is rebuilt from the glossary each time the document is saved, so terms stay consistent without find-and-replace — and a revision always ships the definitions that were current when it was approved.
Write once. Embed everywhere.
Write a content block once — a standard scope statement, approved role definition, or compliance boilerplate — and embed it in as many documents as you need. Update the component and every document reflects it instantly.
Rename a doc. Every link follows.
Reference other documents by link inside the editor. When a document is renamed, every link that points to it updates automatically across the library.
The ones that govern you, controlled like the ones you author.
A customer’s quality specification. A regulator’s guidance note. A supplier’s certification. An industry body’s standard. These constrain your process as firmly as your own procedures do — and they usually live in somebody’s downloads folder.
Register them and they join the same register, the same categories and classes, the same approval chain, the same distribution and acknowledgement, and the same links out to changes, non-conformances and audits. The body is a PDF in a viewer rather than editable text. That is the only difference.
Capture who issued it, its reference and edition, the clause you care about, and a link back to the authoritative source — so the next person can check for a newer edition without hunting for where it came from.
A publisher can supersede a document before you adopt it.
So there are two statuses, deliberately independent. Yours — draft, under review, approved, obsolete — tracks your control of the copy. Theirs — current, superseded, withdrawn — tracks what the issuing body has done with it.
Which lets a document honestly read approved and superseded at the same time: still the controlled version your team works to, while everyone can see a newer edition exists and hasn’t been adopted yet. Collapsing those into one field is how a team ends up working to a withdrawn edition without noticing.
When a replacement file does arrive it enters draft and routes through the normal approval chain by default, so a reissued external document gets the same traceability as a change to your own procedure. On approval, a banner across the top of the page states what changed and which revision it supersedes.
Your status
ApprovedPublisher status
SupersededRevised to Rev 2.0 · approved 12 Jul 2026 · supersedes Rev 1.0
What changed: Adopted the 2024 amendment; clause 7.3 retitled.
The register answers questions, not just stores files.
Ask a question in plain English and get an answer built from your own controlled documents — internal procedures and registered external documents alike — with citations pointing at the specific heading or page that supports it. You verify the source rather than trusting a paraphrase.
It reads approved versions only, so a draft under review never leaks into an answer, and it reads only what you can read — two people asking the same question can legitimately get different answers if their access differs. If a cited document changes later, the citation is badged stale so nobody acts on superseded text.
A conversation can be attached to an NCR, MOC or audit, which freezes it into that record’s evidence trail. See how it works.
What’s our first-piece inspection requirement?
Operators perform first-piece inspection before a production run, with results recorded against the job. Measurement equipment must be within its calibration interval.
Cited from approved versions only · filtered to your access
Connected to your QMS.
Documents don't sit in isolation. Every approval, every change, and every reference reaches the right part of your quality system automatically.
Training Hub
When a document is updated and approved, team members are automatically prompted to acknowledge the change — with optional quizzes to confirm understanding, not just receipt.
Automatic MOC
Configure document types to automatically trigger a Management of Change record when a revision is submitted. Full change control traceability with no manual steps.
Compliance Mapping
Map individual sections to standard clauses as you write. The map feeds Gap Analysis, Audits, and AI automatically — one action, three systems updated.
Frozen evidence links
Evidence references in other modules can link to a specific approved version of a document — so audit reconstruction always shows what was in force at the time.
Full control, no compromise.
Two-step review and approval
Serial approval steps with per-step delegation. Routing rules auto-fill the right reviewer and approver based on facility, class, and category — or lock them so authors can't override.
Immutable revision history
Every approval writes a permanent revision record — version, date, approver, and revision type. Always complete, always accurate, included in every PDF export.
Access control
Documents can be organization-wide or restricted to specific users, roles, and access groups. Restricted documents are invisible to those without access.
PDF and Word export
Every export includes the formal header and full revision history table. What gets exported is exactly what was approved.
Document approvals share the same workflow.
The approval chain that runs document control is the same chain that runs MOC, JHA, and every other approval in QFormance — those modules route up to three steps; documents use reviewer then approver. Configure routing once, apply everywhere — every reviewer sees pending document approvals in the same My Approvals queue as the rest of their work.
Two-step serial chain
Each step has its own approver, delegate, and timestamp. Reject or request changes sends the chain back to the right step.
Routing rules pre-fill reviewers
Per facility, document class, and category — the right reviewer and approver are populated automatically, or locked so authors can't override.
One My Approvals queue
Reviewers see document approvals beside MOC, exemption, and course approvals — pending, completed, and rejected tabs all in one place.
Build your library the right way from day one.
Start your 30-day free trial. Import your existing documents, map compliance, and have your first approvals done before the week is out.