For accredited laboratories
You passed. The evidence is in forty workbooks, and the next cycle asks the same questions of a bigger pile.
Where accredited laboratories get caught
The questions that grow with the pile.
You know the clauses. What changes each cycle is how long the answers take to assemble.
The master that came back out of tolerance
ISO/IEC 17025 §6.5 and ISO/IEC 17025 §7.10 between them require you to know which results a lapsed or failed reference standard touched, and to decide what to do about each. On a spreadsheet the first half is a hunt through job sheets; the second half is a phone call you would rather not make without knowing the scale.
The recall nobody sent
A recall is revenue and it is also the customer's own compliance. A reminder that lived in somebody's calendar stops the day they leave. One that was sent to an address nobody confirmed bounced silently a year ago.
The register written on the Friday before
An assessor can tell a register that was kept from one that was compiled. The dates cluster; the entries are tidy. ISO/IEC 17025 §8.7 wants the record made when the cause was found, not when the visit was booked.
The mechanism
What the software does, by name.
What is reference standard quarantine?
A master whose calibration has lapsed cannot be selected for a run. Not a warning at issue — a refusal at the bench, enforced by the database. The master's own recall is tracked like a customer's, with its external certificate number and date, and the readiness screen reports a master with no history rather than assuming one.
What is reverse traceability?
Every calibration run records the reference standards it used. When one fails, the list of affected certificates, customers and dates is a query the system runs for you and records that it ran. Whether to notify is your decision under ISO/IEC 17025 §7.10; the scale of it is no longer a guess.
What is the recall ladder?
Seven rungs from the first reminder to the last, each sent to an address the customer confirmed, each logged with its message id, bounces heard back and recorded. A recall that cannot be delivered is reported, not silently dropped — an empty log is not the same as a quiet night, and the system knows the difference.
How do the registers stay honest?
They are written by events. A complaint exists the moment it is raised; a nonconformance the moment a result fails review; a corrective action the moment a cause is recorded. Every entry is dated by the work and attributed to the person, and the audit log holds the before and after of every change. There is no Friday before.
Legacy identifiers stay searchable forever. The first laboratory's history carried six competing numbering schemes; every one of them resolves to the instrument it named.
What it costs
$549.00 a month, against the days each cycle costs you.
Count the days spent preparing for the last assessment and the days spent answering it. The Laboratory plan is priced as a fraction of that, with every clause the system supports included.
Pricing has the metered lines and the estimator. Migration of your history is part of guided onboarding, and it is priced as a service, not hidden in the subscription.
The questions people ask before they start
- We passed our last assessment on spreadsheets. Why change?
- Because the next one asks the same questions of a bigger pile. Every cycle adds certificates, masters and staff, and the reconstruction an assessor's question triggers grows with them. The laboratories that move are not the ones that failed; they are the ones that counted the days spent preparing.
- Our certificates have our numbering scheme. Does it survive?
- Yes. Legacy identifiers are indexed and stay searchable forever, however many schemes you have accumulated. Six competing schemes were found in the first laboratory's history; all six resolve.
- What about the certificates already issued — can they be re-issued from the new system?
- They should not be, and the software will not pretend they were computed here. An issued certificate is a record of what it said. It is imported as a document with its number, its date and its signatory, and it is verifiable as that.
- Does moving mean re-validating our methods?
- Your methods are yours and are recorded as approved procedures with an approver who is not the author. What the software validates is itself: the calculation engine carries a validation dossier written for the clause on software validation, and every certificate is recomputed at issue and refused on a mismatch.
- What happens to our records if you stop trading?
- They are exportable at any time as a complete archive; a release cannot ship if a table is missing from it. Certificates are held immutably with their hash, and verification is never gated on payment. The data ownership page states all of it, and so does the agreement.
Import the register first.
Thirty days, no card. Bring the reference standard register and the instrument list as CSV; the first useful screen is the one that says which masters are due.