SkilliHireAustralia's AI Venture Builder

    Calibration Software Built Around the Evidence

    For Australian laboratories working to ISO/IEC 17025. The parts that decide an assessment — certificate integrity, standard history, scope, competence and change control — designed in rather than bolted on.

    Most calibration software stores results. Assessment is about evidence.

    A laboratory can record every reading correctly and still struggle at assessment, because the questions are not about the readings. They are about whether a standard was in tolerance when it was used, who was competent to sign, what changed and when, and whether a measurement sat inside the accredited scope.

    That evidence usually exists. It is spread across a calibration system, a spreadsheet of masters, a training folder and somebody's inbox — and pulling it together is what turns an assessment into a fortnight of preparation.

    This is built the other way round: the record that satisfies the clause is a by-product of doing the work, not a report assembled afterwards.

    What it covers

    Grouped by the clause it answers, because that is the language your assessor uses.

    Signed calibration certificates

    Certificates carry a cryptographic signature tied to the signatory, not just a hash. Anyone holding a certificate can verify it against a public page, so a customer can confirm a document is genuine without contacting the lab.

    §7.8 Reporting

    Reference standard history

    Every master keeps its full calibration history rather than having its fields overwritten. That is what lets a lab answer the last-known-good question when a standard is later found out of tolerance.

    §7.10 Nonconforming work

    Accreditation scope

    Work is mapped against your accredited scope, and certificates show whether a given measurement falls inside it. Endorsement is applied from that mapping rather than left to whoever is issuing.

    §7.8.2

    Role-based access, enforced server-side

    Permissions are checked in the server action and again at the database, not hidden in the interface. A technician cannot approve their own work by finding another route to the endpoint.

    §6.2.4 Competence

    Immutable audit log with a viewer

    Every change is recorded and readable by the quality manager, so evidence of change control is something you show rather than something you assemble the week before an assessment.

    §8.4 Control of records

    Assessment evidence pack

    Generates the compliance matrix, evidence register, gap list, master register, competence register and document register as one pack. This is the part labs tell us costs them a fortnight of preparation each cycle.

    §8.9 Management review

    Automatic recall and review sweeps

    Recall dates, document reviews, training expiry, competence monitoring and standard due dates are swept on a schedule and digested into one notification, rather than depending on somebody remembering.

    §6.2, §8.3

    Subcontracting register

    Subcontracted work is recorded against the job with the customer notification it requires, so externally provided results are traceable rather than informal.

    §6.6 Externally provided services

    Customer feedback capture

    Feedback is collected and analysed inside the system, so the evidence exists when it is asked for instead of being reconstructed from an inbox.

    §8.6.2

    Repair as a first-class job

    Repairs get their own job type, report and as-left verification, because for many labs repair is a real revenue line rather than an exception to calibration.

    Operational

    Uncertainty methodology, documented

    Written uncertainty methodology per template family, kept with the system rather than in somebody's spreadsheet. Assessors ask for this and it is a common reason a first assessment stalls.

    §7.6 Measurement uncertainty

    What we do not claim

    We are not accredited to ISO/IEC 17025 and we do not hold NATA accreditation. No software vendor can — those apply to laboratories, not to the companies that build their software. If a vendor tells you their product is NATA accredited, that is worth asking about.

    We also publish no accuracy percentages, client counts or time-saving figures for this system. Any number we gave you would be one we had not measured in your laboratory, and you would be right not to trust it.

    What we will do is show you the system, walk through how a specific clause is evidenced, and tell you honestly where it would and would not fit how you work.

    Questions labs ask

    Bring us a certificate and your scope

    Not a requirements document. We will look at what you issue today, what your assessors have raised before, and where the manual work actually sits. Thirty minutes, free, and you will get a straight answer about whether this is worth building for you.

    Book a Technical Consultation

    SkilliHire Assistant

    Ask me anything

    Hi! I'm the SkilliHire assistant. Ask me about AI development, custom software, our products, or how a project usually starts.

    Powered by SkilliHire AI