Piling Records

Definition

Piling records are the pile-by-pile field log that documents exactly what happened at each foundation element the moment it went into the ground. Depths, sets, driving energies, torques, concrete volumes, cage lengths, tremie withdrawals, over-break, refusal — every measurable that describes whether the pile actually met the design intent. On any structural investigation, piling records are the first document the geotechnical engineer asks for and the last one anyone wants to admit was kept badly.

Why It Matters

A pile is invisible the moment the crew moves off it. Whatever went wrong during installation is entombed in concrete or soil, and the only remaining evidence is the record sheet the foreman filled in that afternoon. If that sheet is vague, incomplete, or copied-and-pasted from the previous pile, there is nothing to defend the foundation with when settlement shows up two years later. Insurance companies know this. Litigation lawyers know this. A tidy piling log has settled more disputes than any expert report.

What Goes on the Record

• Pile ID, grid reference, and reduced level of the working platform.
• Rig ID and operator's name — you will need to reach the operator again.
• Start and finish time of installation.
• For driven piles: hammer weight, drop, blow count per 250 mm, final set, energy delivered.
• For bored piles: casing depth, bore verticality check, spoil description at every metre, base cleaning method, tremie sequence.
• Concrete details — mix ID, slump, temperature, cube references, actual volume vs theoretical.
• Cage details — length, laps, spacer count, tie-in level.
• Any anomalies — overbreak, water ingress, collapse, refusal, cage-lift, tremie withdrawal above concrete.
• Signatures — foreman, quality inspector, engineer's representative.

Real-World Example

On a 22-storey residential tower in Manchester, a corner column began to show 11 mm of differential settlement six months after topping out. The forensic engineer requested piling records for the four raft piles under that column. Three of the four records were pristine — depths, sets, concrete volumes, all in agreement with the design. The fourth was a single-page sheet with the depth handwritten, the concrete volume left blank, and the foreman's name illegible. The contractor's own investigation, run under caution from their insurer, established that the pile had been terminated three metres shallow because the rig had hit an obstruction on a Friday afternoon and no engineer was on site to authorise a re-drive. The remedial jet-grout underpinning cost £1.4 million. The dispute was settled inside a month — the missing record was the case.

How to Run It Properly

1. Pre-print the log sheets with pile ID, design depth, design toe level and design concrete volume. The operator only fills in what actually happened, alongside the target.
2. One sheet per pile — no exceptions. A batch sheet with "20 piles as per design" is not a record.
3. Engineer's representative signs each sheet before the rig moves. If the rig has moved and the sheet is not signed, the pile is suspect until proven otherwise.
4. Reconcile concrete daily against the batching plant delivery tickets. A 15% overbreak on one pile is a soil condition; a systematic 15% is an accounting problem.
5. Trend the daily sheets weekly. Blow-count patterns, cut-off levels and concrete overbreak all cluster before they fail.
6. Integrity test the outliers. Any pile with an anomalous record gets a low-strain integrity test at minimum, before the pile cap is poured.

Practical Lessons Learned

• The last hour of the shift is where records get lazy. Have a mid-afternoon check-in — not to catch out the operator but to catch out fatigue.
• Friday piles are statistically the worst. Watch them closer, not looser.
• A concrete over-run is information, not embarrassment. Suppressing it hides the ground condition that will come back to haunt the next pile.
• Digital logging is worth the money. A rig with automatic depth-and-torque logging removes half the disputes before they start.
• The geotechnical engineer must have access to the records the day they are made, not the week after. Ground conditions revise faster than paperwork.

Expert Tips

• Photograph the pile head after casting, with the ID board visible. It costs 15 seconds and disarms most arguments about which pile is which.
• Cross-check the concrete volume trend against the driller's log — a tight bore in stiff clay should not consume 30% overbreak.
• Reject a pile early and cheaply rather than accept it and repair it late and expensively. A re-drive costs a shift; an underpin costs a project.
• Keep the original signed sheets on site in a fireproof box. Scans are for convenience; originals are for court.
• The geotechnical engineer's markup on each sheet — "accept," "accept with monitoring," "reject" — should be legally binding, not advisory.

Common Mistakes

• Batch-signing a week's worth of sheets on a Friday.
• Recording "as per design" instead of the actual measured values.
• No concrete reconciliation against batching-plant tickets.
• Rig moved before the engineer inspected the pile.
• Anomalies never followed up with integrity testing.
• Digital rig logs discarded because "the paper sheet is the record."

Key Takeaways

• The piling record is the only surviving evidence of what actually went into the ground.
• One sheet per pile, signed by the engineer before the rig demobilises from that position.
• Trend the sheets weekly — outliers are early warnings, not paperwork faults.
• Digital logging plus disciplined paper is the modern minimum.
• A missing record is a defect, whether or not the pile itself is defective.

Related Concepts

Interlocks with Method Statements, Concrete Pour Cards, NCRs, As-Built Drawings and Quality Management. Rig log templates at PMMilestone.org.