Object types
Documents, case records and event records, each with its own fields, capture rules, accepted file types and labels in every language.
[ Industries ]
One core. Every audited industry.
A pharma plant, a bank, a court and a support desk keep different records for different auditors. The engine underneath is the same. Each industry is configuration.
01 Why one core
Each industry is configuration, not code.
No industry concept lives in the engine. A vertical is a configuration pack, shipped as an approved release, and the same engine runs every one of them.
01
02
Lifecycles
State machines you configure, checked for completeness before they load, with the signature meanings each step requires.
03
Policies
Who may do what, as policy that denies by default. For agents: allow, confirm or deny for each action.
04
Retention
Periods per record type, including permanent retention, above a minimum the deployment enforces, with holds and approved disposition.
Configuration changes ship as releases: reviewed as a diff, approved by people other than the author, checked against existing data, and live in seconds without a restart. The release in force is stamped on every audit entry, so the rules that applied are part of the record.
02 Same layers, different records
Three layers, ten vocabularies.
Every industry keeps documents, records, and the evidence about both. What changes is what they are called and which rules apply.
| Industry | A document | A case record | An event record |
|---|---|---|---|
| Life sciences | SOP-0042, equipment cleaning | Deviation DV-0193 | Temperature excursion, cold room 2 |
| Medical devices | Design input specification | Complaint investigation | Sterilization cycle |
| Banking | Credit policy | Customer due diligence file | Policy exception, credit limit |
| Insurance | Policy wording | Claim file | Reserve change |
| Government | Ordinance | Records request | Building inspection result |
| Legal | Legal hold notice | Matter | Hold acknowledgement |
| Law enforcement and courts | Court order | Incident case | Custody transfer |
| Energy | Operating procedure | Incident investigation | Pressure exceedance |
| Defense and aerospace | Drawing | Engineering change | First article inspection |
| Support and case management | Knowledge base article | Support case | Customer reply |
03 Every industry
Find yours.
01Life sciences and pharmaControlled documents, deviations, CAPA, and training records, designed for 21 CFR Part 11 and EU GMP Annex 11, and built for the human oversight the draft EU GMP Annex 22 expects for generative AI.02Medical devices and healthcareDesign history, complaints, and access records with controls that map to ISO 13485 and HIPAA.03Banking and financial servicesSystems of record where every decision, approval, and change remains verifiable for its full retention period.04InsuranceClaims files and underwriting records with long-term retention and lawful, verifiable destruction.05Government and public recordsRecords management for state, county, and city agencies, including records requests and disclosure tracking.06LegalMatter files with strict access controls, legal holds, and a verifiable chain of custody.07Law enforcement and courtsEvidence and case records with sealing and a tamper-evident history.08Energy, oil and gasProcedures, inspections, and incident records across sites, contractors, and regulators.09Defense and aerospaceControlled technical data, time-limited access for outside parties, and air-gapped deployments.10Support and case managementTickets and cases that retain their evidence long after they close.
[ Contact ]
Build your product on proof.
Tell us what you build and who audits it. We'll show you how Tabellix fits into your product and how it answers your auditors' most common questions.