Built around ASTM C31 · C39 · C143 · C231 and ACI 318
Concrete quality control that holds up to an audit
Tickets from the pour, cylinders from the lab, acceptance against the spec — with each company's data sealed behind its own wall and every edit signed.
- 4
- access roles
- 0
- cross-company reads
- 100%
- edits audited
What it keeps track of
Every field a technician fills in has a standard behind it, and every number the app reports can be traced back to the person who entered it.
Delivery tickets
Ticket number, mix, truck, slump, air, temperature and unit weight — with the ticket photo attached as the record of origin.
Cylinders end to end
Field techs cast the set at the pour under ASTM C31. Lab techs record each break under C39. The handoff mirrors the paperwork you already run.
Strength computed, not typed
psi is derived from load and diameter by the database itself, so a mistyped strength cannot enter the record.
ACI 318 acceptance
Running three-test averages and the individual low-test limit evaluated automatically against the specified f′c.
One company, one wall
Every row carries a company ID and the database refuses to return anything outside yours — a policy in Postgres, not a filter in the app.
Every edit attributable
An append-only audit trail records who changed what and when — the paper spine of any accreditation audit.
Access that matches the job
Nobody edits data outside their own step. The people who sign off on results cannot change them — which is the whole point.
Field Technician
Lab Technician
Viewer
Company Admin
Where is this mix heading?
Enter a 7-day break and see the projected 14, 28 and 56-day strengths on the ACI 209R curve. Nothing you type here is stored or sent anywhere.
Strength gain estimator
One early break, projected across the curve — no account needed.
Estimated at 28 days
4,295psi
3,000 psi at 7 d is 70% of the expected 28-day strength.
14 days
3,755
+25% vs measured
28 days
4,295
+43% vs measured
56 days
4,628
+54% vs measured
90 days
4,768
+59% vs measured
This is an estimate, not a test result. It fits the ACI 209R-92 strength–age curve for Type I cement under moist curing. Real strength depends on the mix design, w/cm and curing history, and scatter is normal. A 7–14 day break is the most reliable basis for a 28-day projection. Never report a projected value as a strength test — break the cylinders. For a specified 4,000 psi mix, ACI 318-19 §26.12.3.1(b) puts the individual-test floor at 3,500 psi.
Built on a job site, not in a boardroom
For almost a year I worked as a Construction Materials Testing technician for an engineering consulting firm — running slump, air content and density on concrete, and geotechnical tests out in the field.
If you have ever stood on a hot job site handling crumpled, wet, coffee-stained paper tickets while trying to log pour data by hand, you know the problem I lived every single day: operational friction, administrative backlog, and the constant risk of a transcription error nobody catches until it matters.
As a Civil Engineering student at UCF, I decided to stop complaining about the problem and build the solution. TepuyQC is that solution — a secure, cloud-backed quality assurance platform built specifically to digitise field data collection and concrete cylinder testing, from the ticket at the truck to the acceptance check against the spec.
Greco Pinzón
Founder
Civil Engineering, UCF
· Former CMT technician
Why “Tepuy”? A tepuy is one of the flat-topped mountains that rise out of the Venezuelan highlands — some of the oldest, most stubbornly solid rock on the planet. I am Venezuelan, and it seemed like the right thing to name a platform whose whole job is making a record that holds.
Standards first
Every field maps to an ASTM or ACI procedure. The app does not invent its own way of recording a test.
Your data is yours
Row-level security in Postgres, not a WHERE clause in application code. Export whenever you want.
Audit-ready by default
The append-only trail exists from the first record, not as a feature you remember to switch on.
Built for the field
Works on the phone a technician actually carries, in the sun, with gloves on.
A note on accreditation. Accreditation under AASHTO re:source or CCRL is granted to a laboratory — its personnel, equipment calibration and procedures — never to software. TepuyQC is built to make that record-keeping defensible, not to substitute for it.
TepuyQC is production-ready. Now it needs job sites.
Significant time, capital and engineering has gone into making this real. Two kinds of conversation move it forward from here.
Pilot it in your operation
Engineering consulting firms, ready-mix suppliers and general contractors looking to streamline a QA/QC department. Bring one crew and one project — that is enough to see whether it earns its place.
Start a pilot →Build it with me
Strategic partnerships and co-founders who care about ConTech and want to help scale this. If you know this industry from the inside and have wanted to fix the same things, I would like to hear from you.
Get in touch →See it against your own data
Tell us a little about how your lab or crew works and we'll walk you through the parts that matter to you — casting a set at a pour, recording breaks, and what an acceptance check looks like on a real spec.
- 🗓️
About 30 minutes
Screen share, no install, no obligation.
- 🧪
Your workflow
Bring a real ticket and a real set — we will use those.
- 🔐
Your data stays yours
Nothing you show us gets stored in a demo account.
Support the project
TepuyQC is built and maintained independently. If it saves you time, or you would just like to see it keep going, a contribution goes directly into hosting, development and keeping the standards library current.
Contributions are voluntary and are not a purchase — they buy no licence, feature or support commitment.