Bulk

Materials testing lab software. Sample in, certificate out, traced.

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.

  • Results from the rig
  • Certificate generation
  • Calibration & competency
  • Sample & job traceability

This is your floor. These are the modules on it.

Where Bulk fits best.

Technician lifting a tensile specimen from a sample box at a lab bench

Specimens you must answer for

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

Tensile specimen clamped in the grips of a universal testing machine

Readings that still get re-typed

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

Technician writing a reading from a fatigue rig onto a clipboard

Certificates customers are waiting on

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

Two lab staff pulling a calibration record binder from a shelf

An accreditation to hold

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

From specimen to certificate, one thread.

Log the sample

Goods-in registers the specimen against job, customer and batch. Custody starts at the door.

See data thread
Specimens registeredGoods-in · Job 4187 · today 08:12

Batch 7711-C · 5 tensile specimens · customer drawing attached

Chain of custody open

Today's reality: built on paper.

Line drawing of a results clipboard, calibration binder, certificate and sample box
  • Readings, re-typed

    Rig to sheet to spreadsheet to cert: four chances to transpose a digit.

  • Certs take days

    Hunting results and calibration records across folders while the customer waits.

  • Accreditation chasing

    Proving the rig was in calibration means a scramble the week before audit.

Cobalt 3D render of a tensile specimen with a sample tag

The blocks that hold an accreditation.

  • Results from the rig

    The value lands once at the bench and flows to the cert unchanged.

    Quality
  • Certificate generation

    Result, method and calibration assemble the cert, reviewed and out in minutes.

    Documents
  • Calibration & competency

    Expiries tracked on rigs and people; a lapsed rig cannot issue a result.

    Training
  • Sample & job traceability

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

    Data thread
  • Test scheduling

    See the backlog against rigs and people; give the customer a real date.

    Scheduling
  • Audit-ready records

    When the assessor asks, the evidence already exists. Nothing is reconstructed.

    Audits

The cert goes out the same day.

71%Time to issue a certificate at Meridian Test Labs
99.4%First-time-right on issued results
0Re-keys between rig and certificate
“Tensile and fatigue results flow straight from the rig into the cert, no re-keying, no transcription errors. Turnaround went from a bottleneck to a selling point.”
MT
Lab manager at Meridian Test LabsMaterial testing, UKAS accredited

Questions, answered.

01

Is Bulk a LIMS?

No, 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.

02

How does Bulk handle ISO 17025 and UKAS evidence?

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.

03

Can results flow straight from the test rig?

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.

04

Does Bulk replace our ERP or accounts system?

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.

05

How long does rollout take for a single-site lab?

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.

06

What does it cost for a lab like ours?

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.

Let’s run one method through.