Skip to main content
GullySystem
Other industries

Business solutions for Environmental testing laboratories

Explore software for work such as “Effluent and wastewater testing”. Review each business function below, including when it fits and what to check before implementation.

Environmental testing laboratories

How the business operates.

An environmental laboratory is asked one question about every sample. Can the result be trusted? The answer depends on who collected it, how long it waited, which instrument ran it and who checked the numbers. Much of that is written on paper forms, bench sheets and instrument printouts, then typed again into a report by someone who was not at the bench.

Sampling requests and field schedules

Plan sampling rounds by client, site and matrix, assign field staff, and prepare the bottle sets and preservatives needed for each visit before the vehicle leaves.

Chain of custody and sample receipt

Record collection details, handover signatures, arrival condition and temperature. The receipt desk gives each sample its laboratory number.

Test orders and holding times

Attach the methods ordered to each sample and show the date by which each test must start. The nearest deadlines come first.

Batches and quality control samples

Group samples into batches with blanks, duplicates and spikes. Each control is compared with its acceptance range.

Instrument and standards register

Hold calibration dates, maintenance, reference materials and their expiry. A batch cannot be started on an instrument that is overdue, so the gap is caught at the bench.

Result review and certificate of analysis

Enter or import results and route them to a reviewer. Compare them with client limits and issue a signed certificate in your own layout.

Orders, partner tests and invoicing

Quote by test and matrix, send selected tests to a partner laboratory with a tracked return, and invoice from the tests completed. Each completed test is billed once.

Reagent and standards stock

Reagents, reference standards and calibration gases are recorded with lot, opening date and expiry. Analysts record use against a run. The lab manager sees what needs replacing soon.

Method and detection limits

Every test method is listed with its reporting limit, unit, holding time and approved sample matrix. Reporting staff compare results to the limit. Revisions are dated and kept for audit.

Analyst competence records

An analyst’s approved methods, training dates and proficiency test results are held on file. Supervisors assign samples only to qualified people. Reassessment dates are shown on the roster.

The records that hold the operation together.

  • Clients, sites and permits. Keep each client’s sites, contacts, permit limits, reporting formats and billing terms on one record.
  • Sampling schedules. Plan field rounds by site, matrix and date, assign samplers and generate the bottle list for each visit.
  • Chain of custody. Capture collection time, location, preservative and each handover, from the field tablet to the receipt desk.
  • Sample receipt and labelling. Log arrival condition and temperature, assign laboratory numbers and print labels for bottles and aliquots.
  • Test menu and methods. Maintain the methods you offer, with units, detection limits, holding times and the price of each test.
  • Analytical batches and controls. Build batches with blanks, duplicates and spikes, and compare every control with its acceptance range.
  • Instruments and reference standards. Track calibration, maintenance, reference materials and expiry dates, and link each batch to the instrument and standards used.
  • Result entry and review. Enter or import results, calculate derived values, and route each batch to a reviewer for approval or return.

Operational bottlenecks to check

Chain of custody is on paper

Signatures go missing. Staff fill the custody form by hand in the field, the desk copies it into a register, and a blank signature surfaces only when the client chases the report.

Holding times pass unnoticed

Some tests must start within hours or days of sampling. Without a running list, a sample can wait on the bench until its result is no longer valid, and nobody notices before the report is drafted.

Instrument and quality records are separate

Calibration dates, reference standards and batch controls sit in logbooks and instrument folders. A reviewer must open the logbook, the reference standard file and the instrument folder before approving a single result, and the delay stacks up across a whole batch.

Reports are typed from bench sheets

Results are copied from spreadsheets into a report template. Each copy risks a transposed digit. Every correction needs a new version. The client must be told which one is current.

Turnaround is promised without a view of the queue

Sales agree dates with clients while the bench is already full, and analysts learn of the commitment only when the sample arrives at the receipt desk. Dates slip.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Order

    A client places an order by site and matrix, naming the methods needed. A sampling visit is planned or bottles are expected.

  2. 2. Collection and custody

    Field staff record time, place, preservative and condition at collection. Each custody transfer records who gave, who received and when.

  3. 3. Receipt

    The receipt desk checks the bottles against the order, records temperature and damage, and assigns laboratory numbers.

  4. 4. Analysis

    Samples are placed in batches with their quality controls and run on instruments that are in date. Results are entered or imported.

  5. 5. Review and approval

    A reviewer sees results, controls, instrument and analyst together. Approved results move on and queried ones go back to the bench.

  6. 6. Reporting and invoicing

    The certificate is issued with limits shown beside each value and signed by an authorised person. The invoice follows the tests completed.

Roles and responsibility boundaries.

For the laboratory manager

See samples by stage, the queue by analyst and instrument, work close to its holding time and reports due.

For field samplers

Open the day’s sampling list on a tablet, record custody details at each site and hand samples over with a signature.

For analysts

See the batches assigned to you, the methods and controls required, and the instruments that are in date.

For the quality manager

Review control charts, overdue calibrations, corrections issued and approvals given, with each change attributed.

For clients

Orders go in through the client’s own login, which also shows where each sample stands and holds issued certificates for download.

Reports your managers need.

  • Samples by stage and by days to holding limit
  • Turnaround by method and client
  • Quality control results by batch and analyst
  • Instruments and standards due for calibration or replacement
  • Reports issued, corrected and withdrawn
  • Revenue by client, matrix and test

Connections to scope

  • Instrument result files
  • Barcode and label printers
  • Email
  • Accounting software export
  • Field tablets
  • Client portal

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Your methods and detection limits

Test methods, units, limits and holding times are entered as your laboratory defines them.

Certificate layouts

Reports follow the layout your clients and your quality system expect, with the wording agreed by the laboratory.

Instrument connections

Where an instrument exports files, results can be imported into the batch. The connection is scoped instrument by instrument.

Client list and open samples migrated

Clients, sites, the test menu and samples still in progress come across from your current sheets or software.

Hosting and changes

GullySystem hosts the system. If a method, limit or certificate layout needs changing, our staff make the edit on request.

Limitations to settle before implementation

  • A laboratory that tests a few samples a week for a single client may manage with a logbook and a report template.
  • A clinical or pathology laboratory working on patient specimens will find the diagnostic lab product closer to its needs.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Effluent and wastewater testing
  • Stack emission and ambient air monitoring
  • Drinking water testing
  • Soil and solid waste testing
  • Noise and workplace monitoring
  • Annual testing contracts
  • Baseline studies for clearances
  • Sampling visits and field monitoring
  • Customer audit and supplier compliance reports
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements