Sign-Off on a Screen: A Remote Pre-Pour Review Protocol for Istanbul-Sourced Concrete
Photo: construction engineers video conference call reviewing drawings laptop site office, via www.cfisherconstruction.com
The pre-pour conference has always been something of a ritual in domestic work: a short call, a review of a mix design everyone has already seen, a signature collected for the file. Overseas sourcing changes the calculus. When the batching plant sits several time zones away and the approval chain runs through a submittal register rather than a job trailer, the video call becomes the last moment at which a person with authority can stop an error before it is cast into a wall.
That is a heavy load for a meeting most teams schedule carelessly. What follows is the protocol we recommend to U.S. contractors preparing to place concrete batched to an Istanbul-approved design — not as a substitute for physical testing, which it cannot replace, but as a control on the documentation and decisions that testing depends on.
The call is not a courtesy
A mix design approved across eleven emails has, in practice, been reviewed by nobody. Each message answers the previous one; no single reader ever holds the whole file at once. A structured call forces the file into one frame, in one hour, in front of the people who will be accountable for it.
Treat attendance as a quorum question rather than a politeness question. The call should not proceed without the supplier's quality control manager, an individual empowered to commit the supplier commercially, the contractor's project manager or field engineer, a representative of the testing agency, and a translator if any participant is not working in their first language. The engineer of record, or a delegate with written authority, should attend the first call of any project and at least the first call after any mix revision.
Agenda item one: revisions since submittal
Ask the supplier to share the current mix design on screen alongside the revision log, and confirm that the revision date precedes the submittal date. Verbal revisions — a cement substitution described in conversation but never issued — are the most common source of drift between what was approved and what is batched. If a revision exists, it needs a number, a date, and an approver before the call ends.
Agenda item two: the admixture package
Request the full admixture list with ASTM C494 type designations, dosages, and manufacturer batch references. Pay particular attention to superplasticizer chemistry, since polycarboxylate and naphthalene-based products behave differently in placement and finishing, and to retarder dosage, which may be tuned for a longer transit or a warmer climate than the destination site. Extended set is not a free good; it buys placing time at the cost of finishing window and early strength. Ask directly what field history the supplier has with the specific cement source and admixture combination, and whether that history includes hot-weather and cold-weather placements.
Agenda item three: test-method equivalence
Slump, air content, and compressive strength are not self-defining terms. Confirm which standard governs each acceptance test — ASTM C143 against EN 12350-2, ASTM C231 against EN 12350-7, ASTM C39 against EN 12390-3 — and require a written equivalence statement rather than a conversion factor. Ask the question that settles disputes later: if a result falls outside the limit, which standard decides, and who pays for the re-test?
Agenda item four: batch-ticket review
Have the supplier screen-share a ticket from a comparable pour. Walk the fields: batch time, individual weights, aggregate moisture correction, water added at the plant, admixture batch numbers, truck departure time. Then confirm which of those fields will be delivered in English and which will remain in Turkish. A ticket that cannot be read on arrival is a ticket that will be reconstructed from memory six months later.
Agenda item five: named sign-offs
Every function needs a name attached: mix design approval, ticket release, test result certification, and shipment authorization. Roles are not sufficient. A distribution list is not a signature.
The checklist
- Current mix design and complete revision log displayed on screen
- Cement source and mill certificate date confirmed
- Admixture list with ASTM C494 types, dosages, and batch references
- Retarder dosage and intended placing window discussed
- Test-method equivalence statement accepted in writing
- Governing standard for failing results named
- Sample batch ticket reviewed field by field
- Translation responsibility for tickets and reports assigned
- Testing agency introduced and sampling plan agreed
- Named signatories recorded for approval, release, and shipment
- Escalation contacts and working hours exchanged
- Minutes to be circulated within one business day
Red flags that should pause the order
Certain answers should stop a shipment rather than merely concern the room. A mix revised within days of loading with no re-review. An admixture substitution described as equivalent without documentation. Inability to name the individual who releases the batch. A ticket format lacking moisture correction. Discussion of tolerances or slump limits as usual practice rather than as a referenced standard. Reluctance to have the testing agency on the call at all. Any one of these is worth a delay; several together suggest a supplier whose internal controls are informal.
Close the loop in writing
Circulate minutes within one business day, attach them to the submittal file, and note any dissent rather than smoothing it over. The value of the call is not the conversation. It is the record that a specific person approved a specific document on a specific date — which is exactly what a project needs when a cylinder breaks at twenty-eight days and everyone reaches for the file.