Signature-gated sign-off
Password, a valid training certificate and membership of the responsible party. A role checkbox is not enough.
Massive Dynamic · Immutable record
Once it is recorded, it stays recorded.
Commissioning evidence is only worth something if nobody can quietly change it later. Massive Dynamic keeps every sign-off, checklist line, comment and bypass in a record that cannot be edited or deleted.
Audit trail
Immutable by design
The audit trail is insert-only. There is no path to update or delete an entry, not in the app and not in the database behind it. It is immutable by omission: the operation simply does not exist.
That matches the audit-trail expectations of 21 CFR Part 11 (§11.10(e)), and it is the same record a client, an auditor or an inspector can read.
- Every sign-off
With the signer's password, training certificate and party membership checked, and the e-signature recorded.
- Every checklist line
Who ticked what, and when, down to the individual line.
- Every comment and mention
Once posted, never edited or removed.
- Every bypass
A forced sign-off automatically raises an issue, so the exception stays visible until it is closed.
Bypass
Forced, but never hidden
Real sites sometimes need a stage signed off before every document has arrived. Massive Dynamic allows it, but only openly: the dialog lists exactly what is missing, a reason is required, the signer’s password is asked again, and the bypass is raised as an issue automatically.
The exception stays in the audit trail for good, and on the issue list until someone closes it.
On the record
Every bypass becomes an issue
Shared checklists
One test, one record.
On a real project, one test often covers many assets: a bay-level function test, a busbar walkdown, a group of AHUs. Copying that checklist onto every asset creates copies that drift apart the moment someone updates one of them.
In Massive Dynamic a shared checklist is one record. Results, notes and completion are shared across every asset it covers. Nothing is copied, so nothing can disagree.
- Multi-party items
Each party signs its own part of the same shared record.
- Same on mobile
The field app works on the shared record, not a local copy.
- Found in one click
Dirac selects every asset on the same checklist as a given asset.
- Joint tasks in the schedule
A shared test can be one joint task in the Gantt, completing when every member signs off.
- Tagging checklists
One shared checklist per stage can carry the sign-off for the whole group: fewer signatures, the same per-asset record and the same gate — a missing item is excused only by a raised issue.
Safeguards
Built so the record stays trustworthy
No sign-off on mobile
Sign-off needs a live credential check that a weak site connection cannot guarantee.
Documents from evidence
DQ, IQ, OQ and PQ documents are generated from the record and e-signed, never retyped.
Version history
Autosave with saved versions you can return to, and protection against two tabs overwriting each other.
Access enforced twice
Permissions are enforced in the application and again in the database, per project and per role.
AI cannot overrule it
Dirac shows every change first and runs it only after you confirm. Sign-off rules stay in code.
In the app
From record to validation document
Show it to your QA team
We will walk your quality team through the audit trail, shared checklists and document generation on a demo project.