Site operations
Concrete pre-pour checklist: coordinate readiness before the first delivery
Plan a concrete pour readiness review with named owners, clear hold points and a worked handover example, using the concrete pour and formwork templates.
By Reldro · · 6 min read
What is a concrete pre-pour checklist for?
A concrete pre-pour checklist brings the people, records and unresolved questions for one planned pour into a shared review before the first delivery. Its useful output is not simply a row of ticks. It is a clear account of what has been checked, what is still open, and who has authority to resolve the remaining questions.
If you manage a concrete team, you know how quickly the plan can become disconnected. The delivery is booked, access changes overnight, and a formwork review lives in somebody else's paperwork. The checklist helps you connect those dependencies without pretending that one supervisor can approve every discipline.
This guide is about coordination and records, not concrete design, formwork engineering or permission to place concrete. Use your approved method, project inspection and test plan, manufacturer instructions and responsible specialists for technical decisions. The examples below are illustrative, not customer results.
Define one pour, one location and one review
Before collecting answers, make the scope unmistakable. Identify the project, pour reference, exact area, planned date and review time. Reference the current drawings and relevant project records. If your company is working on two sites with a slab labelled B, the site name is as important as the slab label.
Define what the checklist covers and what it references. A coordination review can point to a specialist inspection without reproducing it. For example, record the formwork inspection reference, reviewer and current status; do not translate an unanswered engineering question into a general yes.
Keep quality acceptance and safety readiness connected but distinguishable. The concrete specification, inspection evidence and delivery documentation may sit in separate project records. Linking them makes the readiness review useful; calling one short checklist a complete quality-control plan makes it misleading.
- Pour identity: project, area, reference, planned start and reviewer.
- Supporting records: current drawing references, applicable work plan and required inspection records.
- Readiness questions: observed status, responsible reviewer and evidence location.
- Open items: specific issue, owner, next decision and review time.
- Review outcome: what was agreed, by whom, and what remains unresolved.
Work backwards from the delivery booking
Start with the decisions that have the longest lead time. Ask which documents or specialist reviews must be available before the readiness meeting. Give each dependency an owner rather than sending everyone a general request to be ready. A booking confirmation only establishes a booking; it does not establish that the area is ready.
Then review the practical interfaces: where the delivery will be received, who coordinates with the pump or truck team, how access is communicated, and which other trades may be affected. The Reldro concrete template includes setup, overhead clearance, walkways, washing facilities, agreed signals and lighting as prompts. Use those prompts to involve the right reviewers, not as a substitute for their assessment.
Tell each owner what kind of answer is needed. Received, reviewed, accepted under the project process, and awaiting clarification are different states. If a review is pending, the record should say who is reviewing it and when a response is expected. That helps operations decide whether to keep, change or question the delivery plan.
Record exceptions before the meeting ends
A useful exception is narrow enough for another person to act on. Write the location, observed problem, affected dependency and person being asked to respond. Avoid entries such as access bad or formwork not done. Those hide both the question and the owner.
Agree how unresolved items are handled under your project process. A deadline is a coordination tool, not a reason to bypass a required review. Do not label an item closed because somebody has been told about it. Record the response and the supporting evidence, then have the appropriate person review the outcome.
For checks you cannot answer, use an explicit unresolved status rather than choosing not applicable. If a field really is not applicable, record why and who made that determination. The next reviewer should be able to distinguish an intentional exclusion from a skipped question.
A worked example: an access change before a slab pour
Imagine a concrete contractor preparing a level-one slab pour. The delivery is planned for the morning. During the readiness review, the supervisor learns that another trade has stored materials along the agreed delivery approach. The specialist formwork record is also awaiting a response to one observation.
The access entry reads: Level one, east approach, materials occupy the route shown in the delivery plan. Site coordinator asked at 14:20 to confirm a revised arrangement or clearance. Response required before the next booking review. Supporting reference: marked location photograph and current delivery plan.
The formwork entry is separate: Inspection reference FW-14, reviewer response outstanding on recorded observation 3. Responsible specialist to provide the disposition through the project process. Supervisor to check the updated record, not approve the technical matter themselves.
The supervisor gives the operations coordinator both open items, their owners and the next review time. Operations can discuss the booking with the responsible project team using the actual constraints. Nobody has to infer readiness from a message saying checklist completed.
Keep changes visible after the review
If conditions change between the meeting and the planned pour, identify which part of the earlier review is affected. A revised access arrangement might change the delivery interface; a new drawing might affect referenced inspection records. Ask the responsible person which checks or approvals need revisiting under the project process.
Preserve the earlier record and add the later update with a time and author. A reviewer needs to know what was agreed when the plan was made, as well as what happened next. Do not silently replace yesterday's unresolved entry with today's yes.
At handover, give the incoming supervisor the current scope, open items and latest decisions. A photograph without a location or a document without a revision can create another round of clarification. The few minutes spent making those references precise save guesswork when the delivery team is waiting.
Use the templates as connected starting points
Begin with the concrete pour pre-checklist and review the formwork template with the people responsible for that work. The concrete-placement JHA can support your task-planning discussion, but it needs adaptation and competent review for the actual job. None of these templates approves engineering, authorizes a pour or replaces your project requirements.
The template pages can be viewed publicly. Follow the library's demo request if you want to discuss using a template with your team; this guide does not promise a downloadable form or free operational use. In your own process, keep the completed checklist connected to assigned follow-up and the records it references.
The takeaway
A useful pre-pour review identifies the exact pour, connects the required records and gives every unresolved dependency a named owner. A completed checklist is a record of the review, not permission to bypass a technical decision.