Configure anything. Production stays validated.
nil is an electronic quality management system you configure freely: modules, record types, and workflows. A change reaches production only when a Configuration Validation that covers it is tested and approved.
Changeset CS-000014 · CAPA record type
Demo data · try it
1 · Changeset
Recorded
- Added:Field Containment action, long text, required in Investigation
- Changed:Investigation due after 30 days 20 days
Designed by Sam Ortiz
2 · Configuration Validation CV-000006
Testing
- T-1 Containment action is required to leave InvestigationRisk: High
- T-2 Investigation is due 20 days after it startsRisk: Medium
- T-3 Existing CAPAs keep their recorded valuesRisk: High
Unavailable due to:
- T-1 has not been run.
- T-2 has not been run.
- T-3 has not been run.
Tester: Lena Fischer. Approver: Morgan Mills, who neither designed nor tested the change
3 · Production
Unchanged
Unavailable due to:
- No approved Configuration Validation covers this change.
Trace Annex 11 §10 AC-cv-records-6 cv_
A complete eQMS, every module configurable
nil ships validated templates for the processes a regulated quality system runs. Each one is yours to reshape: its fields, phases, steps, assignments, due dates, and signature meanings. nil always shows exactly how your configuration differs from the template it started from.
| Module | Records | Status |
|---|---|---|
| CAPA | Corrective and preventive actions, from investigation to effectiveness check | Built |
| Nonconformance | Nonconforming product, the part affected, its disposition and approval | Built |
| Deviations | Planned and unplanned departures from procedure | Built |
| Complaints, Returns, and Feedback | Complaints assessed by vigilance for reportability, returns from authorization to disposition, and customer feedback | Built |
| Change Control | Change requests, their impact, and their implementation | Built |
| Audits | Internal and supplier audits and their findings | Built |
| Supplier Management | Supplier qualification and status, kept on the approved supplier list | Built |
| Document Control | SOPs, work instructions, and forms, revision by revision, with a Library | Built |
| Configuration Validation | Validation of every change to the configuration | Built |
| Training | Curricula tied to document revisions, assignments, and effectiveness checks | Planned |
Records that read like a batch record
Every record wears its state like a calibration tag, and reads like a form being completed: printed labels, entries in ballpoint blue, each phase closed by its signature. When a step is unavailable, nil says why before anyone presses it.
Investigation4 days left
- Phase due
- 19 Nov 2026
- Assigned
- Sam Ortiz
- Last signed
- Approval · Approved · Morgan Mills, 12 Nov 2026
2 · InvestigationDemo data
Root cause
Gowning procedure step 4 skipped at shift change
Containment action
Line 2 stopped; 40 units quarantined
Signed by
Lena Fischer
Meaning
Reviewed
Date and time
2026-11-13 09:51 UTC
Signature valid
The record tag and a form section, as nil draws them. Demo company data.
Validation documents, generated from the system
Validation evidence comes from the system’s own records and audit trail, not from screenshots pasted into templates. These are generated, versioned, and hashed:
- Vendor validation reportEvery nil release, its requirements traced to the tests that prove them, with each test’s result.
- Configuration specificationYour configuration, read from the live system: record types, workflows, access, settings.
- Test protocol and executed reportWritten from the requirements and runs on each Configuration Validation record.
- Traceability matrixRequirement to risk to test to run, per Configuration Validation.
- Validation summary reportThe conclusion, the incidents, and the signed approval, hashed into the release.
Precise about compliance
nil supplies the technical controls and the evidence that they work. Compliance also depends on your validation of nil for its intended use, your procedures, and your training. Each regulation is answered clause by clause, including what is planned and what remains yours.
- 21 CFR Part 11 Built 13Partly built 2Planned 1Gap 1Customer's procedure 3Open question 1Not applicable 2
- EU GMP Annex 11 Built 13Partly built 3Planned 4Customer's procedure 2Vendor 1Not applicable 3
- ISO 13485:2016 Built 11Partly built 4Planned 1
Pre-launch
nil is in development, ahead of its first customers. What is not built yet is marked Planned.