From sample to lab, without the paperwork

Scheduling lab tests has always been a spreadsheet job. You list your samples, decide which tests each one needs, total them up for the lab, and email the lot over with a chain of custody form stapled to the front. Then a sample reference changes, and you do it all again.

That round trip is where errors creep in. The schedule drifts from the data, the custody record lives in a filing cabinet, and the AGS the lab sends back never quite lines up. We wanted the schedule to be part of the project, not a document about it.

A schedule is a matrix

Build a testing schedule as a grid: samples down the side, tests across the top. Tick the cells you need, set a count and add a note where it matters. Every cell becomes a row when you export, so the schedule you see on screen is exactly what the lab receives.

Custody that travels with the sample

Raise a chain of custody record against the same samples to track them from site to laboratory. Your laboratories and the tests they offer are set up once in Product OS and reused on every project, so you are always picking from a known catalogue rather than retyping test names.

Straight to AGS

Export to AGS - CHOC for custody, LBSG and LBST for the schedule - or to CSV and PDF when the lab prefers it. Batch across multiple locations in one go. Because it is all driven from your project data, there is no separate spreadsheet to keep in sync.