NEXUS Documents is the platform's memory: controlled documents with real revision discipline, approvals that are electronic signatures, controlled issue and effectivity, and periodic review that produces evidence. And a records side where what happened stays frozen, retrievable, and yours.
Plenty of software knows which revision is current. It cannot tell you why section 7.3 changed, what that change promised, or which crew is working against it right now.
NEXUS keeps documents in the same governed record as the work itself. Revisions carry the corrective actions that drove them. The field works from point-of-use verified copies. Your forms come back as controlled data instead of scans. Document control as part of operations, not a library beside it.
Every program has a section 7.3 that nobody remembers changing, or why. The revision is in the history; the reason retired with whoever wrote it.
In NEXUS, Document Control and Corrective Action share one record. A controlled change carries the corrective action that drove it and the commitment your team made, so the revision keeps the why and the promise stays visible until it is kept. Years later the auditor asks why this changed, and whether you did what you said. The document itself answers.
Change control that keeps the reason. Commitments that don't evaporate.
In most regulated shops the form outlives everything. Photocopied, filled by hand, scanned into a folder. The signature is real; the data dies in the PDF.
The Forms Studio takes the forms your program already trusts, your fields, your flow, your letterhead, and makes them governed templates: versioned and released like any controlled document, filled in like an app at the point of work, offline where the work is. Every completed form lands twice. Once as a controlled record, and once as machine-readable data your program can actually use: trend it, feed your boards, answer the auditor from the record instead of the file room.
Not a good-enough form from someone else's library. Yours, promoted to data.
| CHARACTERISTIC | REQUIRED | MEASURED | RESULT |
|---|---|---|---|
| Final torque, fastener 6 | 210 ± 5 ft·lb | 212 ft·lb | ✓ IN RANGE |
Drawing sets, procedures, and packages as a visual operational gallery, opening to what's assigned to you.
Immutable lineage and atomic supersession: superseded revisions stay reachable, labeled, never destroyed.
Release is an e-signature ceremony: intent, meaning, exact revision, identity, authority, time. Acknowledgment never unlocks release.
Deliberate issue, scheduled effectivity, and point-of-use currentness checks on every print, export, and offline package.
Attest against the exact revision: confirm, change, or retire. A no-change review creates evidence, not a fake revision.
The Forms Studio turns the forms your program already runs on, your fields, your flow, your letterhead, into governed, versioned, machine-readable instances. Faithfully yours, not someone else's good-enough form.
Lifetime custody: retention schedules, append-only holds, and disposition under human authority with signed, fingerprinted receipts, built for the retention-and-disposition regimes government-grade programs run on. What must be kept is kept. What is dispositioned is dispositioned on the record.
Approving a document for distribution and approving what it says are different acts, by different authorities. NEXUS refuses to collapse them.
Documents live and revise; records freeze and endure. The distinction is architecture here, not a naming convention.
Yesterday's revision cannot sneak into today's work, and it also cannot be quietly erased from the story. Both failure modes are closed.
Built around ISO 9001 §7.5 and NQA-1 records requirements as design targets.
The one with three "current" copies. We'll walk it into one controlled truth — revision chain, signature, effectivity, and all.