The building blocks

nil is made of a small set of parts. Every module, nil’s own templates included, is built from them, and every one is configuration: yours to change, and validated before it reaches production.

Module · Complaints, Returns, and Feedback nil’s template, version 5

Data types · all modulesParts, Suppliers, Instruments

Roles and groupsWho may create, see, design, and sign each record type

One shipped module, drawn from its definition: three record types, each a form and a workflow, two of them filled in from the others when created from them.

Modules

A process area, and the menu entry people see.

A module groups the record types of one process with their option lists and a dashboard of tables. nil ships nine as validated templates. Design rights can be granted per module, so a supplier quality engineer can shape Supplier Management and nothing else. nil always shows how a module differs from the template it was installed from.

ModulesDemo data

Record types

The kind of record: a form and its workflow.

A complaint, an RMA, an SOP. Each record type numbers its records with its own prefix, gives them a title, and decides whether they can be voided or are revision-controlled. Changes are drafted, then published as a numbered version; records keep what they recorded under earlier versions, and every version is printed in the configuration specification, in sentences.

Record type · ComplaintCMP

  1. v1PublishedAs installed from nil’s template, version 5
  2. v2DraftField “Region” added

Fields

What a record holds, and when.

Every field has a type, a permanent key, and three rules for each phase: whether it is shown, whether it can be edited, and which steps require it. A rule is a tick in a grid, or a condition on other fields. Personal and sensitive fields are marked, and masked whenever records are copied out of production.

  • Short text
  • Long text
  • Number
  • Date
  • Choice
  • Yes/No
  • Person
  • Record link
  • Data object
  • Document
  • File

2 · AssessmentDemo data

Reportable to authorities

Yes

Report reference

MDR-2026-0051

Rule Report reference is shown, and required to confirm the complaint, when Reportable to authorities is Yes.

Phases

Where a record stands, and who has it.

A phase is assigned to the record’s creator, to the person named in one of its fields, or to a role or group, with one or all of them acting. It has a due date, from a fixed number of days or set by whoever sends the record there; reassigning and extending ask for a reason. Every record wears its phase like a calibration tag.

Assessment3 days left

Phase due
21 Nov 2026
Assigned
Morgan Mills, vigilance reviewer

Steps

How a record moves, and what moving it asks for.

A step leads from one phase to another. It can ask for a reason, for the fields it requires, and for an electronic signature with its meaning. It can also set fields of a data entry, such as a supplier’s status. A step never acts behind anyone’s back: before it is taken it says what it will do, and a step that isn’t available lists every reason why.

Steps from AssessmentDemo data

Unavailable due to:

  • Reportable to authorities is required.

Signed, meaning Reviewed. Needs why it isn’t a complaint and the resulting customer feedback.

Rules

Conditions, checked by the server.

One small formula language decides when a field is shown, editable, or required, and which records a dashboard table lists. A rule is written point-and-click or as a formula, stored in one canonical spelling, and printed as a plain sentence in the configuration specification. It reads only the record’s own fields and the date.

RuleAs printed

severity >= 4 and capa_required = false

Root cause is required when Severity is 4 or more and CAPA required is No.

Data types

The reference data records are filled from.

Parts, suppliers, and instruments ship on every instance; customers add their own types and fields. Entries are audited, or approved by a second person with a signature. A record picks an entry and keeps a copy of the values it needs, marked with the entry’s version; once that phase is signed, the copy never changes. A date field can make an entry expire, so a supplier past its requalification isn’t offered.

1 · DraftDemo data

Part

P-10021 Pump housing H-4, front

Copied from P-10021, version 1

Revision affected

C

Roles and groups

Who may do what, and why.

Roles grant permissions, allow-only: create and see a record type’s records, design a module, approve data changes. Groups nest and carry roles. Phases can be assigned to either. Every person’s access is explained with its full chain, and the impact of a change is shown before it is made.

Why Lena can design Supplier ManagementDemo data

Lena Fischerrole Supplier QualityManage record types, in Supplier Management only

Every block is validated configuration

A change to any of them is recorded, tested and approved in a Configuration Validation, and only then released to production.

How validation works