Decide which records need electronic controls
Start with the rules and procedures that require your calibration records, then decide which electronic records you will rely on to meet those requirements. Part 11 is about the applicable electronic records and signatures, not a generic product certification. FDA’s scope guidance discusses when Part 11 applies and its limited enforcement discretion. It does not remove applicable recordkeeping obligations under predicate rules.
List where raw readings, equipment status, calibration results, reviews, and deviations are kept. If a browser register only helps locate assets and the approved record remains elsewhere, document that boundary. A pilot should not quietly become the system of record because staff find it more convenient.
A login or an edit is not an electronic signature
For signatures covered by Part 11, § 11.50 calls for showing who signed, when, and what the signature means, such as review or approval. Section 11.70 addresses linking the signature to its record. In validation, sign a sample calibration, then correct it. A later reviewer should distinguish the approved version from the amended one and see how it was handled.
CaliberOS records who changed an asset, but it does not offer a Part 11 electronic signature workflow. Sign and approve calibration records in your existing controlled system. Do not treat an account name, an asset edit, or an audit entry as an approval.
Ask what the hash-chained log actually covers
For applicable closed-system controls, read § 11.10 in full. For change history, test a correction end to end: can someone see both versions, attribute the change, and retrieve the evidence over the retention period? A log that merely reports that a value was edited is less useful than one that preserves what changed. Verify the human review and retrieval process as well.
CaliberOS logs asset creation, changes, and archive events with actor, timestamp, and before-and-after data. Linking entries with hashes helps make unauthorized alterations detectable when checked against trusted evidence. That does not cover signed calibration results or replace controls for record retention, backups, access, validation, or inspection-ready copies.
Verify that roles match your responsibilities
Assign individual accounts. Decide who may read records, enter or correct asset information, and archive an instrument. Test access with the lowest-privilege user instead of testing only with a system administrator. Include role changes and departures in your periodic review. If your procedure requires a second person to approve a calibration, verify that an editor cannot bypass that approval in your controlled system.
CaliberOS includes admin, technician, and viewer roles. Viewers cannot create or edit assets, and only admins can archive them. The roles control asset access and changes; they are not a two-person approval workflow or a substitute for a regulated electronic signature.
Limit the first pilot to a defined use
Use sample or non-production records first. Ask a technician to find equipment, confirm its due date, and correct a deliberately inaccurate location. Have a reviewer verify the original value is still available through approved evidence and that a read-only account cannot make the same edit. Record which steps are performed outside the pilot.
The beta is free and flat team pricing is planned afterward; no post-beta price is published. In any total-cost comparison, include access reviews, validation effort, archival and export tests, and the cost of running two systems while gaps remain. Do not retire a validated process based on a pilot price alone.
References: 21 CFR Part 11 text (eCFR) · FDA guidance on Part 11 scope and application.