A fully native, in-app platform for running, calculating, and reporting construction materials tests — replacing Excel forever.
Today's process relies on a complex chain of Excel, SharePoint, and a custom add-in just to record and report test results. It works — but barely.
Every test report requires creating an Excel file in SharePoint, populating it via a custom add-in, then hoping the sync doesn't fail. One broken link stops work entirely.
Dry density ratios, moisture corrections, oversize adjustments — all calculated manually in spreadsheets with no validation. One formula error propagates to the client report.
Field technicians running density tests need a laptop and SharePoint access to enter results. There's no way to capture data on-site — it's all transcribed later, introducing delays and transcription errors.
Test results locked inside Excel files can't feed dashboards or business intelligence tools. Management has no visibility into test volumes, turnaround times, or trends.
Technicians enter measurements directly in theBOSSapp. No Excel, no SharePoint, no add-in. Works on any device, any browser, any location.
Every calculation — MDD, OMC, dry density ratio, moisture ratio — runs automatically in the system the moment data is entered. No formulas to break, no errors to miss.
Data entry lives in theBOSSapp — a web app that works on any browser, including mobile. Field technicians enter results on-site the moment the test is complete. No transcription, no delay.
All test data flows automatically into the data warehouse. Management gets live dashboards — test volumes, pass rates, turnaround times, trends by client and project.
The CMT Suite isn't a bolt-on. It's woven into the existing workflow — samples, jobs, projects, equipment, and deliverables all connected.
Step-by-step forms tailored to each test method. The system knows exactly what measurements to ask for and in what order — no training required.
Results are computed the moment data is entered. Dry density, moisture ratios, adjusted MDD — all calculated and validated in real time.
Client-ready PDF reports generated directly from the data. Logo, accreditation details, and signatory included automatically from the organisation profile.
Every report permanently records which version of each Australian Standard was applied. Historical reports are always reproducible — exactly as they were signed.
Select which balance, mould, and oven were used for each test. Equipment details and calibration status pulled directly from the existing equipment register.
Authorised signatories approve and sign reports in-app. Signing triggers automatic deliverable creation and notifies the project team.
All test results flow into the data warehouse automatically. No exports, no manual uploads — just live dashboards with the metrics that matter.
A single report combines multiple test standards — compaction, field density, moisture content — across multiple samples, exactly as per current practice.
Samples, test requests, jobs, projects, clients — the CMT Suite is fully embedded in the existing platform. No duplicate data entry, no context switching.
The entire testing workflow lives inside theBOSSapp — from the moment a sample arrives to the moment the client receives their report.
Select report type (e.g. Dry Density / Moisture Ratio). System sets up the required test methods and data fields automatically.
Attach the samples from the test request. Each sample gets its own data entry section per the report's required tests.
Technicians fill in measurements. Calculations run instantly. Equipment is logged. Pass/fail shown in real time.
Authorised signatory approves the report. PDF auto-generates, deliverable is created, client is ready to receive.
We're starting with the most common tests in the lab and building a foundation that makes adding new standards straightforward.
Determination of MDD and OMC using standard compactive effort (2.5 kg rammer)
Determination of MDD and OMC using modified compactive effort (4.9 kg rammer)
Field determination of dry density ratio — the core field compliance test
Determination of moisture content — used across compaction and field density tests
Correction for oversize particles — applied when fraction exceeds test limit
Field dry density using a nuclear surface moisture-density gauge
New standards can be added by developers without database migrations or downtime
When the Australian Standards are updated, historical reports remain untouched. New tests use the new version. Old tests always display exactly as they were performed.
The foundation is designed. Phase 1 starts with the most common tests, done right — then expands from there.
Read the Technical PlanCode-driven, version-safe, BI-ready. Designed to grow to dozens of test standards without architectural changes.
type maps to a PHP class that defines required tests, calculations, and PDF layout. standard_version locks the version at creation — never changes after signing.data is a JSON blob whose schema is defined and validated by the test method's PHP DTO class — strongly typed in application code, flexible in storage. equipment snapshots the selected equipment and its values at the time of data entry so the record remains stable.Each report type is a PHP class that declares which test methods it needs, how to assemble calculations across all samples, and how to render the PDF.
Each test method version has a typed DTO that defines its data shape. Old records always deserialize to their original DTO — never broken by future changes.
Each version of each standard is an independent class. The version in the database determines which class is resolved — automatically, every time.
The JSON data column is transformed per test method in dbt. Each test type gets its own clean model in Redshift — structured, typed, Power BI ready.
CmtTestResult stores its standard_version at the row level. The application resolves the exact DTO and calculation class for that version every time it reads the record. No migrations needed when standards update.equipment JSON column. If the equipment is later modified or recalibrated, historical test records are unaffected."Mould" with field "Volume"). A validation screen per organisation confirms all required equipment is correctly named and configured before any tests are run.TestRequestWorksheet / Excel / SharePoint pipeline is completely untouched. The CMT Suite runs alongside it for new test types. Teams migrate at their own pace.