On nonresidential construction projects, materials testing sits on the critical path more often than most project teams account for. A concrete break that takes four days, instead of one, to reach the general contractor can hold up a pour schedule, delay a post-tension release or stall a floor slab handoff. When that happens, the cost rarely shows up on the testing invoice. It shows up in idle crews, compressed follow-on trades and a schedule that has to be rebuilt around a delay nobody budgeted for.
Most contractors evaluate testing firms the way they’d evaluate any subcontractor: price per test, proximity to the site, availability. Those factors matter, but they answer the wrong question. The question that actually predicts whether testing will cost a project time is how a firm handles the information after the test is run, not the test itself. Most contractors don’t ask about that until a delay has already happened.
Consider a common scenario: A post-tension slab is poured on a Friday, with strand release scheduled for the following Tuesday, contingent on strength results. If the technician who ran the break on Monday doesn’t get the number to the field until Wednesday, the release slips two days. The crew scheduled to strip formwork sits idle and the trades stacked behind that slab lose their place in the sequence. Multiply that across a multistory structure and the lost days compound fast without a single test ever actually running late.
Where the Delay Actually Happens
It’s a common assumption that testing delays come from the lab, that a break takes days to process because the physical test is slow. In most cases, that isn’t true. A standard concrete compressive strength test, run to ASTM C39, takes minutes once a cylinder is in the machine. Curing periods are fixed and known in advance. The seven-day and 28-day break dates are on the schedule from the day the concrete is placed.
The delay almost always happens after the test, in the gap between a result existing and a result reaching the person who needs to act on it. A technician runs a break at the lab, records the number on a paper form or a spreadsheet, and that data has to move through a reporting process before a superintendent, an engineer of record or an inspector ever sees it. If that process depends on someone transcribing field notes at the end of a shift, batching reports once a week or waiting for a supervisor to review and sign off before anything goes out, the test result can sit finished for days before it does anyone any good.
That gap is invisible until it isn’t. A slab that’s ready to take load, a post-tension strand that’s ready for release or a pour that’s staged to continue all wait on a number that technically existed 48 hours earlier. The test wasn’t the bottleneck. The reporting was.
What to Ask Before Awarding the Work
Because the delay lives in the reporting process, that’s where the pre-award questions should focus. A few are worth asking every testing firm before signing a contract, not after a schedule slips:
How fast do preliminary results reach the field and in what form?
A firm that can commit to same-day or next-day preliminary results, delivered directly to the project team, including the ready-mix producer themselves, rather than batched into a weekly report, is telling a contractor something real about its internal process. A vague answer here is itself an answer.
How are field reports actually delivered?
Paper forms driven back to an office, then typed up later, introduce a full extra step and a full extra day, sometimes more, into every single test. Firms with digital field data collection, where a technician’s entry populates a report the same day, have already removed that step.
What is the chain of custody for a sample, from field to lab to result?
This matters for schedule and for defensibility. A sample with a clear, documented custody trail is one nobody can credibly dispute later. A sample handed off informally, with the trail reconstructed after the fact, is a liability waiting for a claim to surface it.
What happens when a break fails?
Every firm should have a clear protocol. Who gets notified, how fast and through what channel? A failed break isn’t itself a crisis. A failed break nobody hears about for three days can be.
The answers to these questions cost nothing to obtain and tell a contractor more about the schedule risk in a testing contract than the price sheet does.
Documentation and a Contractor’s Position in a Dispute
Testing documentation does more than confirm material strength. It becomes part of the project record, and project records are what disputes and claims get decided on.
When a schedule slips and the cause is disputed, whoever has the clearest, most contemporaneous documentation is in the stronger position. A time-stamped result, delivered through a system that logs when it was sent and to whom, supports a contractor’s position that the delay originated with a late report rather than a late pour or a failed sequencing decision. A test result reconstructed from memory or a handwritten log carries far less weight and, in some cases, none at all.
On projects with liquidated damages clauses, that distinction can carry real financial weight. A contractor able to show precisely when a result was available and when it reached the field has a documented basis for challenging a delay claim. A contractor without that record is left arguing from memory against a schedule that speaks for itself.
The same logic applies to failed breaks. Clear documentation of what failed, when the failure was reported and what corrective action followed protects a contractor against a claim that a known deficiency was ignored. Sparse documentation leaves that same contractor with no way to demonstrate what actually happened.
This is worth factoring into how a testing contract gets evaluated up front, not just how it’s escalated after a dispute begins. A firm with strong reporting discipline is producing usable defense documentation on every single test, whether or not it’s ever needed.
Coordination Steps That Reduce Rework on Both Sides
A few practical steps, agreed to before work starts, remove most of the friction that turns a routine testing relationship into a schedule risk.
Put the testing firm in the preconstruction meeting, not just the schedule. A testing firm that understands pour sequencing, critical dates for post-tension release or slab loading, and which results are truly time-sensitive can prioritize accordingly instead of treating every sample the same.
Agree on a reporting format and cadence in writing, before the first sample is taken. Specify how fast preliminary results need to arrive, who receives them and through what channel. Verbal understandings drift. Written ones hold.
Establish a single point of contact on each side. When a result is late or a break fails, the contractor shouldn’t be tracking down who’s responsible for a response, and the testing firm shouldn’t be guessing who on the project team needs the information first.
Build a short escalation path for failed tests into the contract itself: who gets notified, within what timeframe and what the next step is. Deciding this in advance, rather than improvising it during an actual failure, is what keeps a failed break from becoming a bigger delay than the failure itself.
Where possible, build testing milestones directly into the project’s master schedule rather than tracking them separately. When a break date, a testing result deadline and a release date all live in the same schedule, the misunderstandings and missed deadlines can be avoided. The project team is already watching and, worse case, a slipping result becomes visible immediately, instead of surfacing only after a crew is already standing idle.
These steps don’t require reinventing the way materials testing is performed. The technology to support faster reporting, better documentation and clearer communication already exists and is within reach for today’s testing firms. What matters is putting that technology into a workflow that treats materials testing as what it actually is on most nonresidential projects: a critical-path activity, not a line item that only matters when something goes wrong.
The contractors who ask about reporting speed, documentation and escalation before awarding the work, and the testing firms that can demonstrate how their processes support those expectations, are the ones less likely to discover the hard way what a four-day gap between a break and a report can cost.
SEE ALSO: CONCRETE AND MORTAR QUALITY ASSURANCE
