A quality system people can read

nil is an electronic quality management system for regulated life-sciences companies. It is dense where your work is dense, plain where it should be, and never acts behind anyone’s back.

Configured, not customized

Every module is built from the same parts, and every part is yours to set: no code, no vendor services.

  • ModulesCAPA; Nonconformance; Deviations; Complaints, Returns, and Feedback; Change Control; Audits; Supplier Management; Document Control; and Configuration Validation ship as validated templates. Training is planned.
  • Record typesFields of every common type, option lists, record links, required and editable rules per phase, and calculated rules the server checks on every save.
  • WorkflowsPhases and steps, who is assigned each phase, due dates, and what each step asks for: a rationale, an electronic signature and its meaning, or a person to assign.
  • Reference dataParts, suppliers, and instruments as controlled lists, audited or approved by a second person. Records pick from them and keep a copy of what they picked; a signed step can set an entry’s fields, such as a supplier’s status.
  • Resulting recordsA CAPA created from a nonconformance, or a return from a complaint, starts with exactly the fields you mapped for that pair of record types, and nothing else.
  • Your template, comparednil shows exactly how your configuration differs from the templates and data types it started from.

Records people can trust at a glance

A record says where it stands, who has it, and what happened, without anyone digging.

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 tagThe phase and time left in words, the due date, who is assigned, and the last signature, like a calibration tag.
  • The form by phaseEach phase’s fields in a ruled section, closed by the signatures that approved them. A value changed in a later phase says so in its cell.
  • Explained before it happensEach step says what it will do and to whom; an unavailable one lists every reason. Access, assignments, and due dates trace back to the rule that produced them.
  • LinksWhat a record originated from, what resulted from it, and what relates to it: a CAPA names the nonconformance it came from.

Controlled documents

SOPs, work instructions, policies, and forms, revised and released under the same signatures as any record.

WI-000001 · revision 1 → revision 2 Demo data
  1. Check the driver’s calibration label is in date.
  2. Set the torque to the value on the product’s routing card.
  3. Run three five test fastenings on the test block and record the readings.
  4. Start production only if all three five are within the tolerance on the routing card.
  5. Wear gloves when handling the test block.

Change request CR-000002 Approved Morgan Mills · effective 20 Nov 2026

  • The LibraryEveryone reads the revision in effect; it takes effect on its date.
  • RevisionsFrozen and numbered, with redlines of each change, stamped PDFs of released revisions, and earlier revisions marked unmistakably as not in effect.
  • Periodic reviewA signed review on each document’s own interval; withdrawal to Obsolete is signed too.
  • ImportExisting documents come in through a dry run that checks every row; the import is all or nothing, with a hashed report.

Data integrity by construction

The controls an inspector looks for are not settings that can be switched off.

Audit trail · entry 48213 Demo data
When
2026-11-12 14:03:27 UTC
Who
Morgan Mills · QA Manager, Approver
What
Changed CAPA-000017 Due date 19 Nov 2026 26 Nov 2026
Why
Supplier lot analysis needs a further week; agreed with QA.
Hash
9f3c41a7e20b6d18 ← chains to 27be5d0c91fa3e64

Intact Chain verified at 03:10 UTC today

  • Audit trailAppend-only and hash-chained, written with the change itself: who with their roles, what with old and new values, when in UTC, and why. Verified daily and on demand; exported with its hashes.
  • Electronic signaturesThe password on every signature, the meaning and time shown wherever the signature is, and a hash of exactly what was signed: “Signature valid” means the content has not changed since.
  • Nothing disappearsNothing is hard-deleted: records are voided, accounts deactivated, documents withdrawn, each with a reason.
  • AccessAllow-only roles and groups, each person’s access explained with its full chain, impact previewed before any change, signed periodic access reviews, two-factor sign-in, and lockout after repeated failures.
  • Microsoft Entra IDOptionally, people sign in with their Microsoft account, under your tenant’s policies, and each signature takes the signer through a fresh Microsoft sign-in. One emergency administrator account keeps a password, and every use of it is audited.

Work that reaches the right people

People open nil to do and sign their work, and it is ready for them.

  • DashboardsWaiting on you, due and overdue in words, and tables an administrator defines for each module.
  • Jump anywhereCtrl+K finds a record, a document, or a page, listing only what the person may see.
  • A training sandboxA copy of production’s configuration with sample records, where people practice without touching real records.
  • Built for thousandsPaged lists, search, and type-ahead pickers hold up with thousands of people and records.

How a change reaches production

Every configuration change is tested and approved in a Configuration Validation before it is released.

How validation works