About
Built inside a working laboratory in Sydney.
On real jobs, real instruments and real customers — from the first commit. Not a demonstration that grew into a product.
Software written beside a bench learns different lessons from software written beside a whiteboard.
It learns that a customer standing at the counter matters more than a counter that rolled over. It learns that an assessor opens the competence register first. It learns that the invoice and the certificate must be the same system, because the day they are not is the day a certificated item goes out unbilled.
Every refusal in CalibraWorks exists because somebody in a real laboratory needed it to. The engine recomputes the result at issue and refuses a mismatch. An inspection report will not take an accreditation mark. AI is kept away from anything that lands on a certificate.
And every clause of ISO/IEC 17025 the system supports is included on every plan, because a compliance feature that consults the price list is not a compliance feature.
Who
CalibraWorks is a product of SkilliHire, ABN 61 661 477 964. The software is built and supported from New South Wales, and what happens to your records whatever happens commercially is written down on the data ownership page exists.
Where the work happens
Sydney, Australia. The first customer is a Sydney calibration laboratory that calibrates and repairs hydraulic jacks, load cells, torque wrenches, pressure gauges and electrical test instruments, in the laboratory and on site. The system replaced an entirely file-based operation there, and every field it now covers was added because a laboratory asked for it.
What we will not claim
Accreditation is granted by an accreditation body assessing your laboratory. CalibraWorks makes the evidence exist and refuses the non-compliant case; it does not make anybody accredited.
How it is built
Six principles that decide most questions.
Written down because they are what a laboratory is buying. The feature list is on the capabilities page; this is why the features are shaped the way they are.
The database refuses; the application explains.
A rule that must hold is enforced where it cannot be bypassed, and the screen's job is to say why.
Derived, never stored.
Except what a document asserted when it was issued, which must survive the present changing.
The engine is pure and reproduces byte-for-byte.
Issuing a certificate recomputes the result from the stored inputs and refuses on a mismatch.
Test the acceptance next to the refusal.
A battery of passing refusals hides a path that never worked. That has been found three times.
The system does not invent facts about the physical world.
A master's calibration date, who is competent to sign, whether you are registered for GST — refused, never defaulted.
Nothing stops a laboratory working over a clerical matter.
Only seats refuse. The four hard blocks are all ISO/IEC 17025 clauses.
CalibraWorks covers 13 fields — 9 calibration and 4 inspection — and 57 instrument types, with 8 roles and 29 permissions enforced by the database. Every number on this site is exported from the code that has it.
The calculation engine that issues certificates is the same code behind the free tools on this site. A number computed on the uncertainty budget calculator is the number the certificate would carry.
The principle
Make the honest thing the easy thing.
The system should be pleasant to use on an ordinary Tuesday and unarguable on the day of an assessment. Those are the same requirement.
Start free. Thirty days, everything included.
No card. Nothing is deleted when a trial ends — the records are yours and stay readable.