A laboratory completes a test and sends the result to the project team. Someone reviews the file and replies: “Looks good.”
Weeks or months later, the result is being used in interpretation or design and geotechnical test result approval suddenly matters:
Who actually approved this result?
Was “looks good” a technical comment or a formal approval? Which revision did it refer to? Was the PDF approved, the AGS data, or both? Was a later revision issued after the email? And when did the result become final for the project?
On many geotechnical site investigation programmes, these answers still have to be reconstructed from inboxes, attachments and file names. Result review has happened, but the approval record is separated from the result itself.
That creates avoidable uncertainty at exactly the point where laboratory data starts to become an input to engineering decisions.
A submitted result is not necessarily an approved result
The distinction sounds obvious, but it is often blurred in practice.
A laboratory may complete a test and issue a result. A consultant may carry out the geotechnical test result review . The client may need to approve it. Comments may require a revision before the result is accepted for use.
These are different workflow states:
• Submitted — the laboratory has issued the result for review.
• Under review — a reviewer is checking the result and may raise comments.
• Revised — comments have been addressed or the submission has been corrected by the laboratory.
• Approved — an authorised reviewer has accepted the applicable result or revision.
When these states are managed through email, their boundaries can become unclear. A short reply may be interpreted differently by the laboratory, consultant, SI contractor and client.
The question is not whether people communicated. The question is whether the project can identify the formal status of the result and the exact record to which the approval applies.
The “looks good” email problem
Email is convenient for discussion. It is much less reliable as the approval workflow for a laboratory result.
Consider a common sequence. The laboratory sends a result attachment. A reviewer comments by email. A revised result follows. Someone replies “looks good”. A further correction is then made to the file or data package.
Which version was approved?
The difficulty becomes greater when several people are copied into the thread, when PDFs and AGS files are issued separately, or when a result is downloaded and forwarded outside the original email chain.
Even where the approval exists, the evidence may be difficult to connect to the exact result later. The team may need to compare timestamps, attachment names and email history to work out what happened.
That is not a technical review problem. It is a workflow and traceability problem.
When the history matters, the email may be months old
Result approval can seem like a small administrative step while a project is moving quickly. Its importance becomes much clearer later.
A consultant may be preparing the Ground Investigation Report and need to confirm which approved geotechnical test results are cleared for interpretation. A designer may query an unexpected strength or stiffness value. A client may ask why a particular result was accepted. A laboratory may need to demonstrate that a revised submission was reviewed after comments were addressed.
At that point, the project needs to answer several simple questions:
• Who submitted the result?
• Which revision was reviewed?
• Who approved it?
• When was it approved?
• Were there comments or revisions before approval?
If those answers live in separate email threads and folders, reconstructing them takes time and can still leave room for disagreement.
Approval delays are difficult to manage when they are invisible
There is another consequence: results can sit waiting for review without the wider project having a clear view of the geotechnical laboratory test status.
The laboratory may believe its work has been submitted and is waiting on the project team. The consultant may not realise that a result is ready for review. The client may assume that the result is already final because the test itself is shown as complete somewhere else.
On a large testing programme, a handful of these gaps can become a growing queue of results awaiting review or approval.
The issue is not solved by another spreadsheet listing outstanding results. That simply creates another record to maintain.
The approval status should sit with the result itself.
Geotechnical test result approval should be part of the laboratory workflow
LabHarmony treats result submission, review and approval as workflow actions so laboratory test result approval is no longer a separate email events.
The result is associated with the relevant test. Permitted users can review it in the shared project environment, and the approval action is recorded against the result rather than left in an inbox.
This creates a clearer sequence:
Test conducted → result submitted → reviewed → revised if required → approved
The current status is visible to the stakeholders who need it. The project retains the revision history and a complete geotechnical laboratory audit trail showing who performed each action and when.
If a revised result is issued, the history remains connected to the same test rather than relying on file names such as final, final_v2 or final_revised to explain what changed.
One approval record, different needs
The value of a clear result approval workflow is different for each party.
Asset developers and clients gain confidence that results being used by the project have passed the required review and approval process.
Consultants get a clearer boundary between a result that has merely been received and one that has been formally accepted for the project.
For the Site Investigation (SI) contractor, SI laboratory result approval becomes visible: which laboratory deliverables are complete, which are still under review and where action is outstanding.
For the laboratory, it provides a clear record of what was submitted, whether comments were raised, and when the applicable result was approved.
And for the wider project team, it reduces the risk of different people working from different assumptions about whether a result is final.
Traceability does not replace technical judgement
A structured approval workflow should not turn professional review into a box-ticking exercise.
Geotechnical results still require competent technical judgement. Reviewers still need to assess whether the data are credible, whether the test has been carried out appropriately, whether comments need to be resolved and whether the result is suitable for its intended use.
The purpose of the workflow is to make the outcome of that judgement clear and traceable.
Instead of asking months later, “Who approved these results?”, the project should already have the answer as part of the result record.
From “looks good” to a clear approval record
A geotechnical laboratory result can influence ground models, design parameters and engineering decisions. Its geotechnical test result approval should therefore be more durable than a two-word email reply.
The project should be able to identify the approved result, the relevant revision, the reviewer or approver and the timing of the decision without searching old correspondence.
With LabHarmony, result submission and approval become part of the same shared laboratory workflow used to manage the test.
Submit it. Review it. Approve it. Keep the record.
If your site investigation programme still approves laboratory results through email threads and file attachments, see how LabHarmony can provide a clearer and more traceable result approval workflow.
Request a free LabHarmony demo