What is a concrete pour register?
A concrete pour register is the site record of every concrete pour: the member and location, grade, the volume worked out from the drawings, the volume actually received from each truck or batch, start and finish times, and the cube samples taken. It is what a pour is checked against when a quantity or a strength result is questioned.
This workbook keeps the pour and its deliveries on two linked sheets, so the accepted volume of a pour is always the sum of the loads logged against it, and a rejected truck is on record without being counted.
What is in the concrete pour register workbook?
- Project Details — project particulars, the RMC supplier, and the settings the checks use: your volume threshold and, if you have one, a maximum time from batching to discharge.
- Pour Register — one row per pour, with accepted volume, variance, duration, samples required and status calculated.
- Delivery Log — one row per RMC truck or site batch: challan, truck, grade on the challan, quantity, batching, arrival and discharge times, slump, and accepted or rejected.
- Filled Sample — three pours and their fourteen loads, worked through.
How does the concrete pour register sheet calculate?
- Accepted volume = the sum of the accepted loads on the Delivery Log with the same pour number. A load marked Rejected counts as zero.
- Variance = accepted volume − theoretical volume, and variance % = variance ÷ theoretical volume.
- Samples required follows the minimum frequency in IS 456 Cl 15.2.2, applied to each pour: 1 sample for 1-5 cum, 2 for 6-15, 3 for 16-30, 4 for 31-50, and 4 plus one for each further 50 cum or part above that.
- Batching to discharge = discharge completed − batching time, in minutes, checked against your limit if you entered one.
- Status reports, in order: no delivery logged, samples short, a flagged load, accepted volume below theoretical, or accepted volume above theoretical by more than your threshold. Otherwise OK.
Worked example from the sample sheet: pour P-01, a first-floor slab, took eight accepted loads totalling 44.5 cum against 43.6 cum on the drawings — 2.1%, inside the 3% threshold set for the sample. One truck was returned for high slump and counts for nothing. 44.5 cum needs 4 samples, and 4 were taken, so the pour is OK. Pour P-02 took 6 cum, which needs 2 samples; only 1 was taken, so it shows SAMPLES SHORT.
How do you use the concrete pour register template?
- Fill in Project Details, including your volume threshold and, if your specification or RMC agreement sets one, the maximum time from batching to discharge.
- Before each pour, add it on Pour Register with a pour number, member, location, grade, source and the theoretical volume from the drawings, and record who cleared the pre-pour checklist.
- Log every truck or batch on Delivery Log against the pour number as it arrives, with its challan, quantity, times and slump, and mark it Accepted or Rejected with the reason.
- After the pour, enter the start and finish times, the number of cube samples taken and their set IDs.
- Read the Status column and close every flag before the pour is signed off.
What should you check before relying on the concrete pour register?
- The sample count is the minimum in IS 456 Cl 15.2.2, read per pour. Your specification may ask for more, and IS 456 asks for at least one sample from each shift at a continuous production unit such as an RMC plant.
- The theoretical volume is only as good as the take-off. Work it out from the drawing for the panel or members actually poured.
- The volume threshold is your figure for when a pour needs explaining. It is not a permitted wastage.
- Slump limits and the batching-to-discharge limit come from your specification or RMC agreement; the template supplies neither.
What does each column mean?
| Column | What goes in it |
|---|---|
| Pour No. | Your number for the pour, used to tie every truck or batch on the Delivery Log to it. |
| Member / Location / Grade / Source | What was poured and where, the grade of concrete, and whether it came from an RMC plant or was batched on site. |
| Theoretical Volume (cum) | The volume worked out from the drawings for exactly the panel or members being poured. |
| Accepted Volume (cum) | Auto-calculated. The total of the accepted trucks and batches logged against this pour. Rejected loads count for nothing. |
| Variance (cum) / Variance % | Auto-calculated. Accepted volume less theoretical volume, and that difference as a share of the theoretical volume. |
| Start / Finish / Duration | Times entered as hh:mm; the duration in hours is worked out, including a pour that runs past midnight. |
| Samples Required | Auto-calculated from the accepted volume, using the minimum sampling frequency in IS 456 Cl 15.2.2. |
| Samples Taken / Cube Set IDs | Entered by you. The set IDs are the ones you use in the cube test register. |
| Status | Auto-calculated. OK, or the first thing that needs an answer: no delivery logged, samples short, a flagged load, or a volume below or too far above the theoretical. |
| Delivery Log: Batching to Discharge (min) | Auto-calculated from the batching time and the time discharge was completed, checked against your own limit if you set one. |
| Delivery Log: Accepted / Rejected and Check | Mark every load. The check flags a pour number that is not in the register, a grade on the challan that differs from the pour, or a load over your time limit. |
A pour is closed by its test results. The samples taken here go into the cube test register under the same cube set IDs, and the pour itself is part of that day's daily progress report.
Get the quantities from your drawings
A progress record is measured against the estimate it reports against. Upload your drawings and InstaBOQ builds the measured BOQ — so "work executed today" can be tracked line by line against a real quantity.