Calibration lab software for ISO/IEC 17025 labs
For independent calibration labs accredited to ISO/IEC 17025, with about 3 to 30 people, that calibrate instruments for machine shops, medical device makers, aerospace suppliers and process plants. Your measurements may already be automated; the recall list, your own standards, the quality records and the customer letters often aren't. We build a web system around your scope, your procedures and your customers' decision rules, beside the automation software you already run. A typical build costs $8,000 to $25,000 at a fixed price, and hosting and support start at $350 a month, with no per-user fee and no charge for customer logins.
Last reviewed: November 11, 2026
The day one of your standards fails
When one of your reference standards is found out of tolerance, ISO/IEC 17025 asks you to find every certificate it was used on since it was last known good, assess the effect, and tell the customers whose results it could change. In most labs that means searching every past job for one serial number, then writing the letters by hand.
The system records which standard, and which part of it, every reading used. So the search is arithmetic: every certificate the standard touched, narrowed to the readings on the faulty part, then to the ones where a pass or fail could change once its measured error is applied. In the demo, hundreds of certificates narrow to the 6 where a decision could change. The AI drafts the impact assessment and the customer notices from those results, and your quality manager edits and approves every notice before it's sent.
What accredited labs need that templates and spreadsheets handle badly
- Reverse traceability in minutes, not a week of searching.
- Certificates checked before they go out. A2LA's list of the most common calibration certificate findings includes an uncertainty smaller than the lab's CMC, a missing date of issue, missing results before and after adjustment, too many significant figures and undocumented decision rules (A2LA). Each is easy for a template to let through, and each is checked before release.
- A bench that keeps to your scope: no lapsed standard, no uncertainty below your accredited CMC, no technician working outside their authorization.
- Recall that builds itself, with due notices sent in one click.
- New customers' gauge lists taken in from whatever spreadsheet they send, without retyping.
- Your reassessment, with the authorization matrix, proficiency tests and records ready before the assessor arrives.
The rules behind the work
Accreditation is voluntary in law but required by customers: purchase orders in medical devices, aerospace and automotive name it. Each screen in the demo answers one ISO/IEC 17025:2017 requirement, and shows it:
- Authorized people (6.2.6): a technician not authorized for the instrument, its review or its release is refused.
- Equipment in calibration (6.4.4, 6.4.8, 6.4.13): every standard labeled in calibration, due soon or lapsed, and a lapsed one refused.
- Defective equipment and nonconforming work (6.4.9, 7.10.1): a failed standard leaves service, and every certificate it touched is listed with the customers to tell.
- Decision rules (7.1.3, 7.8.6): pass or fail decided under the rule agreed with each customer, and stated on the certificate.
- Original observations (7.5): a corrected reading keeps the original and the reason.
- Certificates and amendments (7.8): the required elements checked before release, and an amendment issued as a new revision with its reason.
- Proficiency testing (7.7.2) and confidentiality (4.2): results tracked, and one customer's records kept from another's.
- Software validation (7.11.2): every rule ships with its test.
What we build for a calibration lab
The demo shows each piece working for a fictional lab, Tessaline Metrology. The scope, procedures, decision rules and certificate layout are your own.
- Reverse traceability: a failed standard leaves service at once; every certificate it touched since it was last known good is listed and narrowed, and the AI drafts the impact assessment for the nonconforming work record, a notice to each customer whose decision could change, and one notice for those whose results stand. The AI writes from the system's results, never its own guesses, and never decides which certificates are affected.
- A bench that enforces the scope: as-found and as-left readings drawn against their tolerance bands, decided under each customer's agreed decision rule (simple or guarded acceptance, or results only). A lapsed standard, an uncertainty below your CMC or a technician not authorized for the instrument is refused. A correction keeps the original reading and the reason.
- Ten checks before release, covering the certificate elements ISO/IEC 17025 requires and A2LA's common findings. Certificates print as a page and a PDF, and an amendment is a new revision that names the original.
- Beside your automation software: results arrive as a file from your procedure-automation station, such as MET/CAL, and pass the same checks as readings typed at the bench. A result for an instrument nobody checked in, or one reporting an uncertainty below your CMC, is held for a person.
- A customer's spreadsheet, taken in: a new customer's emailed list of gauges, with messy headers, makers spelled three ways and duplicates. The AI maps the columns and matches the models, your rules find duplicates and items outside your scope, and the front desk confirms before anything is created.
- A customer portal with no per-seat fee: customers read and acknowledge notices, download certificates with any amendment's trail, see what falls due next quarter, and ask for a pickup. Every contact at every customer can have a login.
- The quality view: the technician authorization matrix with re-witness dates, proficiency tests with En values, and a countdown to your reassessment with a readiness list worked out from the records.
- Excel everywhere: every list exports to Excel.
The AI drafts; the arithmetic decides; a person approves. You own all of it: the code, the data and the address.
What it holds, and what it doesn't claim
- No claim of accreditation or compliance. The system keeps the records your accreditation asks for. You, your quality manager and your assessor decide whether the lab complies.
- Your uncertainty budgets and scope stay yours. The system applies them; it doesn't work them out.
- Instruments, readings and certificates only: what was measured, not what your customer makes with it.
Validation, and the software you already run
ISO/IEC 17025 asks you to validate software before use and after every change. Every rule in the demo already has an automated test tied to its clause, and a build's validation pack starts from those, run on your own data, and run again with every change.
The system sits beside your procedure-automation software and imports its results; it doesn't replace it. Mapping your own export is part of planning the build.
What it costs, and how long it takes
A calibration lab system is a fixed-price build, typically $8,000 to $25,000, then hosting and support from $350 a month, whatever the number of users or customer logins. The price depends on your scope, your certificate formats, your automation exports and how your history is kept today, and you see it in writing before anything starts.
| Blueprint | From $1,500: the written plan and the fixed price for the build, credited in full to it |
|---|---|
| Build | Fixed price per phase; most projects $8,000 to $25,000 |
| Included | The first 3 months of Standard support |
| After that | Support plans from $350 a month, hosting included, month to month |
Your current system keeps running beside the new one until the day you switch.
How it compares with the alternatives
| Option | Cost | Fits best when |
|---|---|---|
| Spreadsheets, Word templates and an in-house database | Staff time | A small lab where one person remembers every standard's history |
| Calibration lab software (IndySoft, Metquay and others) | Often priced per user, per month | You want a product as it comes, and the per-seat cost works for your team |
| Metrology department suites (Fluke MET/TEAM and others) | Quoted per lab | A large metrology department or lab |
| Rowhouse Systems | $8,000 to $25,000 once, then from $350 a month, with no per-user fee | You want your own scope, rules and customers in one system you own, with every customer login free |
These products all offer certificates, recall and a portal. The difference is fit to your own lab, cost at the small end, and owning your data. Prices change, so check each vendor's own quote.
See it working
The demo is Tessaline Metrology, a fictional accredited calibration lab. Sign in with one click as the quality manager, a technician, the front desk or a customer. Record a failed gauge block set and follow it to approved customer notices, run a calibration at the bench, and take in a new customer's messy gauge list. The data resets every night, so you can't break anything.
A guide for this trade
When a reference standard fails: finding every affected certificate: When a reference standard fails, find every certificate it touched, narrow to readings on the faulty part, then to decisions that could change.
Questions
How is this different from IndySoft, MasterControl (formerly Qualer) or MET/TEAM?
It does the same jobs for your lab only, built around your scope, your procedures and your customers' decision rules, with no fee per user and nothing locked in a vendor's database.
When one of our standards fails, what does it actually do?
It lists every certificate the standard touched since it was last known good, narrows them to the readings on the faulty part, works out each decision again, and drafts the notices for you to approve.
Does the AI decide anything about our results?
No. The arithmetic decides which certificates are affected and how. The AI writes the assessment and the letters, and a person approves every word before it's sent.
We run MET/CAL. Do we have to give it up?
No. The system imports the results your automation exports and checks them against the same rules as the bench.
How do we validate it for our assessor?
Each rule has an automated test tied to its clause. A build comes with those tests and a validation pack you run on your own data, and every change is tested again.
Can our customers really log in for free?
Yes. Portal users have no per-seat cost; every contact at every customer can have a login.
What about our existing customer lists and history?
Customers' instrument lists come in through the same intake the demo shows, and your past certificates can be imported as part of the build.
What does it cost, and who owns it?
A fixed-price build, typically $8,000 to $25,000, then from $350 a month for hosting and support, whatever the number of users. The system, the code and the data are yours, with an export to Excel at any time.