Pour Cards and Checklists That Protect Your Billing
Lesson 47 of 60 · 7 min read

The client's QS is reviewing your RA bill. Against "RCC M25 in slab, second floor" he writes one line: "No inspection record. Quality certification pending. Item held." The slab exists. The concrete was fine. But you cannot prove the rebar was checked, the cubes were cast, or the quantity delivered matches the quantity billed — so 17 m3 of concrete sits unpaid for another billing cycle. The cure costs one page per pour: a pour card backed by a pre-pour checklist. This lesson shows exactly what goes on that page and how it becomes billing armour.
What a pour card is
A pour card (some sites call it a pour permit or concrete pour record) is a single sheet raised for every concrete pour, signed before the pour begins and completed as the pour happens. It ties together in one place what would otherwise be five scattered pieces of evidence:
| The pour card records | Which later proves |
|---|---|
| Pour ID, date, element and location | Which bill item this evidence belongs to |
| Concrete grade and source (RMC plant / site mix, mix ref) | The specified material was used |
| Theoretical quantity vs delivered quantity (challan numbers) | The billed quantity is real — and wastage is visible |
| Slump measured per truck at delivery | Workability was checked, not assumed |
| Cube sample IDs cast from this pour | The 28-day results trace back to this element |
| Pre-pour approvals: rebar, formwork, MEP — with signatures | The work was inspected and released for casting |
| Start and finish time, weather | Cold joints and delays are explainable |
| Curing method and start date | The quality obligation continued after the pour |
One signed pour card answers, in a dispute, the three questions every bill reviewer asks: how much (theoretical vs delivered), was it checked (approvals), and was it good (slump and cube traceability).
The pre-pour checklist
The approvals block on the pour card is backed by a physical checklist walked on the element before concrete is ordered. A workable pre-pour checklist for a residential slab:
- Formwork: line, level and plumb checked; props and bracing tight; joints sealed against slurry loss; release agent applied; soffit cleaned of debris and wire off-cuts.
- Levels: slab top level marked on columns/shuttering; thickness verified at edges and mid-span (thickness pads or level dots — not guesswork).
- Reinforcement: bar diameters and spacing against the bar bending schedule; laps, anchorage and hooks in position; chairs and cover blocks giving the specified cover everywhere — including the top steel, which dies when workers walk it down.
- Embedments: electrical conduits, sleeves, hook bars for future work, chajja and staircase starter bars — cast-in items cannot be added tomorrow.
- Logistics: vibrators (plus one standby), sufficient labour for the pour duration, lighting if the pour will run into evening, curing material ready, cube moulds cleaned and oiled on site.
- Concrete plan: ordered grade and slump, truck spacing agreed with the plant, slump cone and thermometer at the gate, who casts cubes and when.
The inspection itself follows a simple protocol: the contractor raises a Request for Inspection (RFI) — commonly 24 hours before the pour — the engineer inspects jointly, comments are closed, and the checklist plus pour card are signed. No signature, no concrete.
Site-mix sites: the card changes, the discipline does not
RMC is a metro convenience. On plenty of tier-2/tier-3 and self-builder sites, concrete comes from a one-bag mixer fed by farma (gauge box) — and the pour card adapts rather than disappears. Instead of challan numbers it records: batch count, bags of cement consumed, farma proportions actually used, and water discipline (a marked water drum, not a free hosepipe). Theoretical cross-check: a 17.11 m3 pour of nominal-mix M20-equivalent at roughly 8 bags per m3 should consume on the order of 135–140 bags — if the mixer crew reports 110 bags gone for the "same" volume, either the volume is short or the mix is lean, and both are your problem tonight, not at reconciliation. Where the owner buys cement on dealer credit, the bag count on the pour card is also what keeps the dealer's khata honest against the store register.
Worked example: catching 2 m3 before it becomes a dispute
Second-floor slab pour, M25 by RMC. Before ordering, the QS computes the theoretical volume from the drawing:
| Element | Calculation | Volume |
|---|---|---|
| Slab 10.4 m x 9.6 m x 125 mm | 10.4 x 9.6 x 0.125 | 12.48 m3 |
| Beam webs below slab: 62 m total length, 230 wide x 325 deep below soffit | 62 x 0.23 x 0.325 | 4.63 m3 |
| Theoretical total | 12.48 + 4.63 | 17.11 m3 |
| Ordering allowance ~2 percent (pump line, spillage) | 17.11 x 1.02 | 17.45 m3 |
The pour consumes 19.5 m3 across five challans — 2.05 m3 (about 12 percent) over theoretical. Because the pour card carries both numbers side by side, the excess is visible the same evening, not at project-end reconciliation. Investigation with a level and tape finds average slab thickness ~140 mm against 125 mm designed: 99.84 m2 x 0.015 m = 1.50 m3 explained by extra thickness; the balance ~0.55 m3 is beam bulge and pump-line waste.
Now the QS can act while it matters: fix thickness control before the next slab (the third floor pours the same way next month), and know that at an indicative Rs. 5,400 per m3, the site just consumed Rs. 11,070 of concrete nobody will pay for — the client pays drawing quantities, as Lesson 1 established. Without the pour card, this money disappears silently into "concrete consumption seems high this project."
How the paper trail protects your bill
Trace the chain: RFI → signed checklist → pour card → MB entry → RA bill annexure. Each RA bill item for concrete carries its pour card numbers; each pour card points to its cube IDs in the cube register; the cube register carries the 28-day results. When the reviewer asks "prove this 17 m3 of M25 was placed, checked and passed," you hand over three sheets and the discussion is over.
The same chain protects the contractor too — this is not one-sided paperwork. A signed pre-pour approval means the client cannot later claim the rebar was never checked; a recorded slump per truck means a borderline cube result becomes a technical discussion, not an accusation. Both parties should want this file to exist.
The RERA era raises the stakes on both sides. A RERA-registered developer carries a defect-liability obligation for years after possession (commonly cited as five years for structural and workmanship defects — confirm the position under your state's rules and your agreement), so today's pour card is the document that answers an allottee's complaint in year four. For an owner building with a thekedar, the pour card is the only thing standing between you and "sab theek tha, ab paisa do" — the thekedar's memory of quality is always excellent; your file has to be better.
Two disciplines make the chain hold:
- Same-day completion. A pour card filled a week later from memory is worth little more than no pour card. Slumps, challan numbers and times go on the card as they happen.
- Serial numbering, no gaps. Pour cards PC-001 onward, RFIs numbered, cube IDs sequential. Gaps in a series invite the question "what happened to PC-014?" — and in an audit, an unexplained gap taints the whole series.
Common mistakes
- Treating the checklist as a signature formality — walking it from the office chair. The checklist only has value if a failed item actually stops the pour.
- No theoretical quantity on the pour card, so over-consumption is invisible until reconciliation.
- Casting cubes from the first truck only. Sample per the sampling plan (next lesson) — the last truck of an evening pour is the one nobody checks and the one that fails.
- Letting the pump operator decide when the pour starts, before top steel and cover are re-checked after the crew walked over it.
- Filing pour cards by month instead of by element — you bill by element, so file by element.
What comes next
The pour card records slump values and cube IDs — but what slump is right for which work, how many cubes does IS 456 actually require, and what happens when a 28-day result comes back low? That is the next lesson: concrete quality from the slump cone to the acceptance criteria.
Key takeaways
- A pour card proves quantity, inspection and quality traceability on one signed page per pour.
- Compute the theoretical volume before ordering; recording theoretical vs delivered exposes over-consumption the same day.
- No signature, no concrete: a checklist only protects you if a failed item actually stops the pour.
- Chain the evidence — RFI, checklist, pour card, MB, cube register — so every RA bill item traces to signed documents.
- Fill pour cards during the pour and number them serially; reconstructed or gap-ridden records lose their evidentiary value.
- The paper trail protects both parties: signed approvals shield the contractor as much as the client.
Verify on site
- Raise or demand the RFI at least 24 hours before every pour, and inspect jointly.
- Verify rebar diameter, spacing, laps and cover against the BBS before signing the rebar approval.
- Check slab thickness control (level dots or thickness pads) at edges and mid-span before release.
- Confirm cast-in items — conduits, sleeves, starter bars — are placed; they cannot be added after casting.
- Record slump for every truck at delivery and note challan numbers on the pour card immediately.
- Enter the pour in the MB with the pour card number the same day, and file the card by element.
Check your understanding
4 questions. Answering them marks this lesson complete — results stay on your device.
Want the free certificate?
The whole course is free and open — no signup needed to learn. Enter your details only if you want us to track your progress on this device and issue a named certificate after the final assessment.