From Concrete Truck to Carbon Report — Every Delivery Captured Through WhatsApp
Every concrete pour generates a paper trail: the delivery docket, the slump test, the
cube samples, the lab report, the supplier invoice. On most projects that trail is scattered across paper
dockets in the site office, lab PDFs buried in an inbox, and a spreadsheet three weeks behind the actual
pours. Then three different teams need the same data — QA to prove every batch met spec, sustainability to
calculate embodied carbon, finance to check the supplier invoiced what actually arrived.
For several of our customers in Singapore, that entire trail now builds itself — from a
few WhatsApp photos. Here is the exact workflow, as it runs on live projects today.
Three steps, three source documents, one register — every step traceable back to the
photo or email it came from.
1 The truck arrives
Two photos, and the record exists
When a concrete truck reaches the site, the field team does what field teams everywhere already do: they
take photos and send them to the site WhatsApp group. One photo of the delivery docket,
one photo of the slump test. That's the entire job — no app, no form, no login, no data
entry at the end of a 10-hour shift.
Site WhatsApp Group
Delivery Order
DO-48213 · Grade C32/40
8.0 m³ · Batched 09:58
10:42 ✓✓
Slump test — truck 2
10:43 ✓✓
Wenti Agent Extracts
DO NumberDO-48213
Mix / GradeC32/40
Volume8.0 m³
Batched → Arrived09:58 → 10:37
Slump165 mm
Your SharePoint
DO No.GradeSlump
DO-48198C32/40170 mm
DO-48205C40/50160 mm
DO-48213C32/40165 mm
New row in concrete-register.xlsx — timestamped, linked to
the source photos, visible while the truck is still on site.
One detail that matters to every main contractor we work with: the data lands
in your SharePoint, in your Excel format. Not in our database. Not in another platform
your QA manager needs a license and a training session for.
2 Cube testing
The agent does the paperwork and the chasing
Concrete acceptance doesn't end at the slump test. Cubes go to an accredited lab — and this is where
records traditionally fall apart, because the handover between site, QA, and the lab is exactly the kind
of multi-party, multi-day process that paper and inboxes lose track of. Here's how it runs now:
The QA team sends three things into WhatsApp: the delivery order number, the
number of cubes, and the serial numbers of the test.
The agent links the cubes to the right delivery record, generates the test request form the
lab requires, and files it.
From the moment the cubes leave for the lab, the agent tracks expected result dates — and
automatically follows up with the lab until the results come back.
Day 0 · Agent
Cubes registered, lab request form generated
Day 7 · Agent
Follows up with lab, records 7-day result
Day 28 · Agent
Follows up with lab, records 28-day result
Closed
Every cube traceable, nothing left unreported
No QA engineer keeping a mental list of which 7-day and 28-day results are
due. No test that quietly never gets reported.
3 The lab report arrives
Results flow back to the same record
When the lab emails the test report, the agent reads it, extracts the strength result for each
individual cube, and records it against the original delivery in the same Excel register —
completing the loop from truck arrival to verified strength, with every step traceable to a source
document.
One Delivery, One Row, One Golden Record
Docket, slump, cubes, lab results — everything about a pour lives on one line, in
your own Excel register.
Illustrative register — values shown are representative, not from a live
project.
The Part Nobody Expects: Three Other Teams Run on This Data
Capturing concrete data cleanly is useful for QA. What makes it transformative is
who else uses the register.
Before Wenti
The same data, handled three times
Every team pulls from the same scattered paper, inboxes and spreadsheets — and
keeps its own copy, out of sync with the others.
→
With Wenti
One connected record
Captured once in WhatsApp, written to one register — the same three teams read
from a single source, no re-keying.
Uses volumes + mix designs
Sustainability
Calculates embodied carbon from actual deliveries, not estimates. As embodied-carbon
reporting becomes standard on major Singapore projects — BCA Green Mark, client ESG requirements — this
turns a painful annual data hunt into a live number.
Uses volumes + dockets
Finance
Reconciles supplier invoices against the register — verifying they're paying for exactly the
concrete that arrived, at the volumes the dockets show. Disputed quantities stop being
arguments about missing paper.
Asks the agent directly
Project Team
Gets pour history, supplier performance, and test compliance on demand — ask the agent a question in
WhatsApp, get the answer from the register.
And it isn't just concrete. The same teams use the same workflow for rebar
delivery orders — photo of the DO in WhatsApp, structured register in SharePoint — feeding the
same carbon and cost calculations.
Why WhatsApp, and Not Another Platform
There are platforms built to centralize concrete data — dashboards, supplier
integrations, sensors. They're genuinely useful if your site team adopts them. That's the
industry's oldest problem: most field workers never consistently adopt new construction software. Our
approach starts from the opposite end. The capture point is a photo in a WhatsApp group — behavior your
team already does dozens of times a day, in English, Chinese, or Vietnamese. The intelligence lives in the
agent; the output lives in your own systems; the field team changes nothing.
No app to download
Adoption is effectively 100% from day one — the field team keeps sending photos to the group they
already use.
No new database
The register is an Excel file in your SharePoint — your IT policy, your access controls, your format.
No manual follow-ups
The agent generates the lab forms and chases the results until every cube is reported.
The result on live projects: every delivery captured at
the gate, every test traceable to its docket, and a materials dataset that QA, sustainability, and finance
all trust — because it was created at the moment of delivery, not reconstructed at the end of the month.
FAQ: Concrete Data Capture on WhatsApp
How is the docket data captured — does the field team type anything?
No. They photograph the delivery docket and slump test and send the photos to the site WhatsApp group.
The AI agent extracts DO number, supplier, mix, grade, volume, timings, and slump automatically.
Where is the data stored?
In a structured Excel register in the customer's own SharePoint (or Google Sheets). Wenti does not hold
your project data on its servers.
Can it track cube tests through an external lab?
Yes. The QA team sends the DO number, cube count, and serial numbers via WhatsApp; the agent generates
the lab's test request form, tracks expected result dates, follows up with the lab, and records per-cube
results when the report arrives by email.
Can this data be used for embodied carbon reporting?
Yes — this is one of the main reasons our customers run the workflow. Volumes and mix designs from
actual deliveries feed the sustainability team's embodied-carbon calculations, replacing estimate-based
reporting.
Does it work for materials other than concrete?
Yes. The same workflow runs for rebar delivery orders today, and the pattern extends to any delivery
that arrives with a docket.
See the Concrete Workflow Running in WhatsApp
Wenti Labs deploys AI agents inside WhatsApp that turn site photos and messages into structured
operational records — concrete and rebar deliveries, safety, QA/QC, and progress — stored in your own
systems. Live today across Singapore's leading contractors.