Compliance statement: ISO/IEC 17025:2017 and 21 CFR Part 11
For an assessor, an accreditation body, or a regulated customer's auditor. It says what CertaCal does for each requirement, how, and what stays with the company that uses it.
What CertaCal is
CertaCal is calibration management software for calibration and scale service companies: the office app, the technician app (which works offline), the customer portal, certificates with Digital Calibration Certificates (DCC), and the records behind them. It's a hosted service; each company's records are kept apart from every other company's.
It is designed for ISO/IEC 17025:2017, the standard for the competence of calibration laboratories, and designed for 21 CFR Part 11, the FDA's rule for electronic records and electronic signatures, for companies whose customers are FDA-regulated (food, drugs, supplements, medical devices).
No software is "Part 11 certified" or "17025 accredited". Accreditation belongs to the laboratory; Part 11 compliance belongs to the regulated company and how it uses its systems. CertaCal supplies the controls; section What stays with you lists the rest.
ISO/IEC 17025:2017: where CertaCal supports each clause
| Clause | What the standard asks | What CertaCal does |
|---|---|---|
| 6.4 Equipment | Equipment fit for use, calibrated, its status known | Test weights and reference standards with their certificates and due dates; weights past their certificate blocked or warned (your choice); intermediate checks; a failed check takes the item out of use |
| 6.5 Metrological traceability | An unbroken chain to SI units | Each calibration records the standards used, their certificates and traceability; the certificate prints them |
| 7.2 Methods | Validated methods, used as written | Controlled procedures and work instructions with issues kept; locked, versioned, approved tolerance rule sets; every result judged by the server and kept with the rule version it was judged by |
| 7.5 Technical records | Records enough to repeat the work, changes traceable | Readings as found and as left, environment, standards, technician, photos; every change in the audit trail with before and after |
| 7.6 Measurement uncertainty | Uncertainty evaluated | An uncertainty budget for each scale calibration, with your coverage factor |
| 7.7 Ensuring the validity of results | Monitoring, review | Independent review before issue; jobs approved only after the share you set is audited; nobody approves their own work |
| 7.8 Reporting | Certificates with everything 7.8.2 requires; amendments identified | A layout can't be published while a required item is missing; issued certificates locked; corrections are amendments with a new revision, the replaced copy kept |
| 7.10 Nonconforming work | Identify, evaluate, act | Nonconformances with significance, impact on earlier results, customer notification and verified corrective action; impact reviews opened automatically when a standard is found out of tolerance |
| 7.11 Control of data and information management | Data protected, integrity checked | Role-based access enforced on the server; a tamper-evident, chained audit trail; certificates fingerprinted and checked every night; encrypted backups |
| 8.3, 8.4 Control of documents and records | Approved, current, retained | Procedures, rule sets, certificate wording and company policies locked, versioned and approved; records kept for the life of the account and exportable |
The company decides which of these it uses: a company that isn't accredited can switch off what it doesn't need.
21 CFR Part 11: clause by clause
Part 11 applies to the records a company keeps for its FDA-regulated customers. In CertaCal the CertaCal administrator offers it to a company, and the company's owner or Quality Manager switches it on per customer. For those customers' records, everything below applies; other customers keep the simpler workflow.
| Clause | Requirement | How CertaCal meets it |
|---|---|---|
| 11.10(a) Validation | Accuracy, reliability, consistent intended performance | An automated test suite (several thousand tests) runs on every change, on the same database the service uses; a dated test-evidence report per release is available on request (see Validation) |
| 11.10(b) Copies | Accurate, complete copies, readable and electronic | Certificates as PDF/A-3 with the DCC XML inside; the audit trail of a calibration, or of a customer's calibrations over a period, exports as PDF or CSV, with the electronic signatures |
| 11.10(c) Protection and retention | Records protected and retrievable for the retention period | Issued records locked in the database; nightly encrypted backups; certificates fingerprinted and checked every night; full exports and DCC archives at any time |
| 11.10(d) Limiting access | Only authorized people | Individual accounts and roles enforced by the server; each role sees only the pages it can act on; customers only in the portal; accounts locked after repeated wrong passwords; sign-out after a set idle time in the office app and portal, and a password lock in the technician app (which keeps unsent work on the device) |
| 11.10(e) Audit trails | Secure, computer-generated, time-stamped; changes don't obscure earlier values; kept as long as the records | Every change recorded automatically with who, when, which app, the values before and after; entries chained so alteration or removal is detected; a reason required for every change to a finished calibration of a Part 11 customer, kept in the audit entry |
| 11.10(f) Operational checks | Steps in the permitted order | The workflow enforces it: the technician finishes, a different person reviews, the certificate is issued, then it's locked; a correction is an amendment |
| 11.10(g) Authority checks | Only authorized people sign, alter records or use the system | Approval limited to reviewers and management, never one's own work; the role is checked again at each signature |
| 11.10(h) Device checks | Valid sources of data input | Records come only from the company's own technician app and office, signed in; each audit entry names the app it came from |
| 11.10(i) Training | People are trained | The company's responsibility (see What stays with you); CertaCal provides help guides per role and a training company for practice |
| 11.10(j) Written policies | People are accountable for their electronic signatures | The company's policy; a template is in Policy template |
| 11.10(k) System documentation | Controlled documentation | Help guides published with each release; release notes; this statement versioned with the product |
| 11.30 Open systems | Encryption and integrity for records over open networks | HTTPS for every connection; certificate fingerprints and the public verification page (the QR code on each certificate) |
| 11.50 Signature manifestations | Printed name, date and time, and meaning | Each signature shows the signer's printed name, the date and time with the company's time zone, and its meaning (approved, returned for rework, approved with the job, amendment approved) on the certificate, in the DCC, on the review and history pages and in the audit-trail export |
| 11.70 Signature/record linking | Signatures can't be removed, copied or transferred | Each signature stores a fingerprint (SHA-256) of exactly what was signed; if the record changes afterwards, CertaCal shows Changed after signing; signatures can't be edited or deleted through any part of the service |
| 11.100 General requirements | Unique to one person, never reused or reassigned; identity verified | Usernames are unique; accounts are switched off, never deleted; an account that has signed keeps its username; identity checks before an account is made are the company's procedure |
| 11.200 Electronic signature components | Two components, both entered at each signing | The person types their username and password at every signature; a short-lived, single-use token binds that signature to one person, one meaning and one record |
| 11.300 Controls for identification codes and passwords | Uniqueness, aging, loss management, safeguards, reporting attempts | Unique usernames; minimum password length; common and all-number passwords refused; optional password expiry with the last 5 refused; accounts lock after wrong passwords and the company's managers are emailed when one locks; two-step sign-in for office staff; password-reset links that work once and expire |
Signatures and the technician in the field. A technician often works without signal, and a password check needs the server, so the reviewer's approval is the Part 11 signature. The technician is identified on every record by their own sign-in and the audit trail. The technician's finger signature and sticker are not Part 11 signatures.
Automatic approval never applies to a Part 11 customer's records: a signature needs a person.
What stays with you
- Accreditation and its scope, competence, impartiality and your own procedures (ISO/IEC 17025).
- The letter to FDA certifying that your electronic signatures are the legal equivalent of handwritten ones (11.100(c)), where your customer or you must send it.
- Training your people, and keeping records of it (11.10(i)).
- Written policies making people accountable for their electronic signatures (11.10(j)); see Policy template.
- Checking identity before you make someone an account, and reviewing who has access from time to time.
- Your own validation of how you use CertaCal for your intended use. CertaCal's validation evidence supports it (see Validation); it doesn't replace it.
- Retention: keeping records for the periods your customers and regulators require, including exporting them before an account ends.
Switching it on
- The CertaCal administrator offers 21 CFR Part 11 to your company (ask your CertaCal contact). That sets idle sign-out to 30 minutes unless you've chosen a time.
- Your owner or Quality Manager opens each regulated customer and switches on 21 CFR Part 11: electronic signatures on this customer's records.
- Optionally, in Settings › Security: password expiry, two-step sign-in for office staff, the idle time.
- Train your reviewers on the signing dialog and reasons for change (Help › Office › 21 CFR Part 11 records).
Validation
CertaCal is validated the risk-based way FDA's Computer Software Assurance guidance (September 2025) describes: the most testing where a failure would change a result, a signature or a certificate. On request, your CertaCal contact provides:
- the validation package: intended use and requirements, the risk assessment, and the traceability from each requirement to the automated tests that cover it;
- the test-evidence report for the release you use: the date, the version, the commit, and how many tests ran and passed;
- the release notes for that version.
Policy template
A starting point for the policy 11.10(j) asks for. Adapt it to your company.
> Electronic signatures policy > > 1. Everyone who signs records electronically in CertaCal has their own account and never shares their username or password. > 2. An electronic signature in CertaCal is the legally binding equivalent of the signer's handwritten signature. Signers are accountable and responsible for actions initiated under their electronic signatures. > 3. Before an account is made, [role] confirms the person's identity against [identification]. > 4. A person who leaves, or no longer needs access, has their account switched off on their last day. Accounts are never reused or renamed. > 5. [Role] reviews who has access, and their roles, every [period], and records the review. > 6. Anyone who suspects their password is known to someone else changes it at once and tells [role]. > 7. Signers are trained on signing, reasons for change and this policy before they first sign, and the training is recorded. > 8. This policy is reviewed every [period] by [role]. > > Approved by: ____________ Date: ________
About this statement
This statement describes CertaCal as released. It's updated with the product; the version you're reading is the one in the help of the release you use.