BOQ Builder·Auto-BOQ from dimensions, DSR ratesNEWBidEasy·Government tenders, searchableLIVEInfraLens App·Free on Play Store, offline-readyNEW
Formats  › Site Execution  › Daily Concrete Pour
Register · FMT-SIT-015

Daily Concrete Pour Register

5 fields across 2 sections. Master concrete log — feeds RA billing + monthly progress + QC traceability.
5 Fields
2 Sections
Daily entries; monthly summary
QC Engineer, Site Engineer

Format Preview

S.No.Field / CheckpointReferenceStatus
A. DAILY POUR ENTRIES
A1Date + element + grade + volume + cube IDs
Acceptance: All pours logged
Daily log
OK
NC
NA
A2RMC supplier + truck count + total m³
Acceptance: Reconciled with bills
Tally with delivery challans
OK
NC
NA
A3Slump + cube results (link to test log)
Acceptance: Traceable
Cross-referenced
OK
NC
NA
B. MONTHLY SUMMARY
B1Total m³ per grade + per element type
Acceptance: Tally with BOQ qty for billing
Aggregated
OK
NC
NA
B2Open NCRs from failed cubes
Acceptance: Closure progress
Tracked separately
OK
NC
NA
A. DAILY POUR ENTRIES
A1Date + element + grade + volume + cube IDs
Daily log
All pours logged
OKNCNA
A2RMC supplier + truck count + total m³
Tally with delivery challans
Reconciled with bills
OKNCNA
A3Slump + cube results (link to test log)
Cross-referenced
Traceable
OKNCNA
B. MONTHLY SUMMARY
B1Total m³ per grade + per element type
Aggregated
Tally with BOQ qty for billing
OKNCNA
B2Open NCRs from failed cubes
Tracked separately
Closure progress
OKNCNA
Approval / Sign-Off
APPROVED
HOLD — REVISIONS REQUIRED
REJECTED
Overall Verdict
Name / Sign / Date
Prepared By — Name / Sign
Name / Sign / Date
Reviewed By — Name / Sign
Name / Sign / Date
Approved By — Name / Sign
Name / Sign / Date
Date & Time
Name / Sign / Date
Remarks
Name / Sign / Date

Engineer's Notes — Daily Concrete Pour Register

Why the Daily Concrete Pour Register matters

Concrete is the most consequential trade on every Indian RCC project — once poured, defects are nearly impossible to fix without demolition. The Daily Concrete Pour Register is the per-pour record that captures every fact about a concrete placement event: location, time, volume, grade, slump, batch ticket, cube samples, temperature, curing start.

This register is the audit trail when concrete fails strength tests (cube < specified) — the engineer traces back: which RMC batch? what mix design? was placement within 30 minutes of batching? what was ambient temperature? was vibration adequate? Without this register, root-cause analysis is impossible; concrete is rejected and demolished blindly.

What goes in the register

Per-pour entry: - Pour ID + member reference (Column C-15 / Slab S-4 / Beam B-12) - Date + start time + completion time - Concrete grade (M20 / M25 / M30 / M35 / etc.) - Volume placed (m³) - Source: RMC (with plant name + delivery slip numbers) or site-mixed - Mix design reference - Slump test results (per IS 1199 Part 2) — typical specification 75 ± 25 mm - Cube samples taken: 6 cubes (3 for 7-day, 3 for 28-day) per IS 456 Cl. 16.1 - Cube IDs for later strength tracking - Ambient temperature + weather - Curing method + start time - Placement crew + supervisor - Sign-off by site engineer + PMC + (for premium / structural) structural consultant

Linked documents: batch tickets attached; cube test certificate cross-referenced when received.

Common pour-day issues

1. No cube sampling — IS 456 Cl. 16.1 mandates 6 cubes per 50 m³ (or part thereof) per grade per shift. Sites that skip cubes have no strength compliance evidence.

2. Cube ID confusion — cubes not labelled per pour; on testing day, can't correlate to which pour the cubes belong. The register's cube ID column prevents this.

3. Wrong slump for placement — slump too low (< 50 mm) for slab pour → poor compaction; too high (> 100 mm) for vertical members → segregation. Register's slump value flags issues.

4. Placement > 30 min after batching — concrete loses workability + strength after batch time + 30 min (extended only with retarder). Register's start time vs batch ticket time catches this.

5. Hot weather pour without precautions — pour at > 35°C ambient causes plastic-shrinkage cracking. Register's temperature column flags hot-weather pours; cold-mix-water + curing-start-immediately + sun-shading required.

6. Inadequate curing — concrete cured 3-7 days vs IS 456-mandated 14+ days for water-retaining; site QA engineer + PMC sign-off forces compliance.

7. No cube test certificate filing — cube tested but certificate not attached to register; gap in audit trail.

Cross-references

Companion formats: - Formwork Removal Schedule (FMT-SIT-024) — pour → curing → formwork strip - Curing Register (FMT-SIT-025) — curing duration tracking - Slump Test Log (FMT-SIT-014) — detailed slump records - Cement Consumption Register (FMT-STR-007) — cement reconciliation

Codes: - IS 456:2000 — RCC code; Clause 16 (acceptance criteria); Clause 13 (curing) - IS 10262:2019 — Concrete mix design - IS 1199 Parts 1-7 — Sampling fresh + hardened concrete - IS 516 Part 1 Sec 1:2021 — Compressive strength test - IS 9013:1978 — Accelerated curing

More related