A laboratory flags a question about one sample or one test. The issue may be small: a condition needs clarification, a sample seems unsuitable for the assigned test to it, or an instruction appears inconsistent with the available material.
Geotechnical laboratory query management is how that question is raised, assigned, answered and recorded. Done badly, a five-minute decision becomes a chain of emails, a coordination call and several people searching for the same context.
The expensive part is rarely the question. It is rebuilding the context around it.
Why small laboratory queries become multi-party coordination
Geotechnical site investigation (SI) is inherently multi-party. The laboratory may need input from the SI contractor, consultant or client before proceeding. When communication is separated from the test record, each person has to reconstruct the context before they can answer.
An email may mention a sample ID but not show the latest assignment. A meeting invitation may include people who are not decision makers. A screenshot may already be superseded by a later change.
The result is more recipients, more explanation and more time before the laboratory receives a usable instruction.
Keep the query with the test, not around the organisation
The most efficient place to resolve a laboratory question is beside the entity it concerns. If the query sits with the sample or test, the relevant conditions, status, history and earlier comments are already there.
That reduces the context copied into emails or repeated in calls. It also narrows participation: the people who need to act can respond without pulling in the whole project team.
Just as importantly, the decision stays available. Nobody has to search for the email that finally closed the point.
Faster resolution does not mean weaker governance
Speed should not bypass technical review or authority. A structured workflow can still require the correct reviewer or approver to act before the laboratory proceeds.
The gain comes from removing the administrative steps around the decision. The responsible person sees the query in context, responds, and the action becomes part of the record.
This matters most when a question affects test conditions, sample suitability or scope, where the history may later matter to interpretation or commercial discussions.
How LabHarmony keeps laboratory queries in context
LabHarmony supports comments and assignments against the relevant sample, test or other project entity. The discussion sits beside the operational record instead of in a separate channel.
Permitted stakeholders can see the current test state, approved conditions, previous decisions and chain of custody where relevant. The audit trail shows what changed and when.
Many routine issues can therefore be resolved asynchronously. Complex technical matters can still be escalated to a meeting when professional judgement benefits from live discussion.
Query or status? Two different problems
A status question asks where something stands. A query asks someone to decide or clarify something specific. Live visibility handles the first (see How Many Status Emails Does Your Laboratory Answer?). The second needs a place where the question, the responsible person and the answer sit together.
Example: a three-hour project meeting avoided
GEOxyz reported a practical case: an issue settled in minutes through LabHarmony would otherwise have required at least three hours of meeting time for the full project team.
The point is not that meetings are bad. Complex decisions still deserve them, as we argue in Meet for Decisions, Not Status. The point is that a small query should not need one simply because it has nowhere better to live.
Resolve the issue, then keep the trail
A good laboratory workflow makes the question, the response, the decision and the resulting action visible without reconstructing an email chain. That also supports the traceability discussed in Who Set the Test Conditions: fewer unnecessary calls today, and a clear explanation of what happened months later.
See how LabHarmony keeps laboratory queries in the workflow. Request a free demo.