
Specimens you must answer for
Every specimen is tied to its job, batch and customer from the door.
Every reading gets read off the rig, written down, typed up and copied into the cert, four chances for a transposed digit. Bulk takes it once, with calibration and competency already attached, so the cert goes out the same day.

Every specimen is tied to its job, batch and customer from the door.

The result lands once at the rig and flows to the cert unchanged.

Result, method and calibration record build the cert the same day.

Calibration, competency and method evidence assemble as the work happens.

Goods-in registers the specimen against job, customer and batch. Custody starts at the door.
See data threadBatch 7711-C · 5 tensile specimens · customer drawing attached

The queue plans against rigs and qualified people; a lapsed calibration blocks the booking.
See schedulingRig 2 calibration due in 41 days · S. Patel competent on method

The result lands once (fed from the rig or typed at the bench), never re-keyed.
See qualityUTS 612 MPa · elongation 21.4% · read from rig 2

The cert builds itself from result, method and calibration record, out the same day.
See documentsMethod rev 4 · rig 2 calibration · competency evidence attached

Rig to sheet to spreadsheet to cert: four chances to transpose a digit.
Hunting results and calibration records across folders while the customer waits.
Proving the rig was in calibration means a scramble the week before audit.

The value lands once at the bench and flows to the cert unchanged.
QualityResult, method and calibration assemble the cert, reviewed and out in minutes.
DocumentsExpiries tracked on rigs and people; a lapsed rig cannot issue a result.
TrainingEvery specimen tied to job, batch and customer from the door to the cert.
Data threadSee the backlog against rigs and people; give the customer a real date.
SchedulingWhen the assessor asks, the evidence already exists. Nothing is reconstructed.
AuditsNo, and that’s deliberate. A LIMS manages samples and results; Bulk runs the operation around them too: scheduling against rigs and people, calibration and competency gates, NCRs, documents and the certificate itself. Labs that already run a LIMS keep it; most labs our size replace spreadsheets, not systems.
Evidence is captured at source: every result carries the method revision, the rig’s calibration state and the technician’s competency at the moment of test. When an assessor asks, the trail already exists. Nothing is reconstructed.
Where the rig exposes data (sensor, PLC or file drop), yes. The value lands once and is never re-typed. Where it doesn’t, the technician enters it at the bench and the same single-entry rule applies downstream.
No. Bulk runs the lab floor and its records; invoicing can draw from the same job data, but your accounts platform stays. This is the layer between the bench and the back office, not a rip-and-replace project.
One method end to end first (specimen to certificate), proven on real work in weeks, then the rest of the methods follow on the same pattern. Never a big-bang cutover.
One per-site price with every module included, no per-module upsell, hosting and rollout in the figure. Early-access labs work directly with the build team.