Concrete Pour Lot Evidence Dossier: Link the Plan, Delivery, Tests and Closeout

Keep the ITP plan distinct from the field record

The ITP states what will be checked, when, against which controlled source, by whom, and what record will result. The formwork, reinforcement or pour record captures the actual location, inspection, evidence, issue and disposition. Some project forms combine these functions; if so, make the planned requirement and actual result distinguishable.

A checklist tick is not the governing acceptance criterion. Cite the actual approved drawing, specification, approved shop detail or project procedure and its revision/locator in the plan. Record observations and attachments in the event record; retain original reports rather than replacing them with a summary tick.

Build the dossier around one pour or lot identifier

Start with the project-defined lot boundaries and pour identifier. Use that same key on the ITP record, pre-pour checks, delivery docket index, sample register, laboratory report, curing record, inspection photos, nonconformance and closeout transmittal. If a project divides a pour into lots or samples, preserve those relationships rather than collapsing them into one untraceable folder.

A compact index can show document ID, revision/date, element or pour, evidence type, originating party, status, and the related ITP row. Keep original controlled documents and reports as attachments or stable document-control references; an index points to evidence but does not replace it.

Use a delivery-to-curing evidence crosswalk

For every concrete delivery included in the lot, retain the docket or project-required delivery evidence and connect its batch/mix identity to the receiving element and pour. Link applicable fresh tests and specimen IDs to that delivery. When laboratory results arrive, link the original report, specimen identity, stated test age and project review/disposition. Keep the source requirement and any decision by the assigned authority visible; do not rewrite a report as an unqualified ‘pass’ if it contains qualifications or unresolved results.

Continue the same key into placement and curing/protection records. Record only the project-required observations and actual event data. Do not invent a testing rate, sampling basis, slump or strength limit, delivery-time window, curing period, or acceptance rule to fill a blank.

Close the lot without hiding unresolved evidence

Before transmittal, reconcile expected records against what has actually arrived. Mark each item received, not applicable with a scope basis, outstanding, under review or closed with a reference. A pending strength report, missing docket, unresolved test, open NCR or unconfirmed instruction stays visible with owner, next action and affected lot.

Where the contract requires a release, witness or hold-point record, include the prescribed evidence and its formal status. A contractor’s dossier review is a completeness check; it does not itself accept nonconforming work, approve a design change, certify strength or release a contractual hold point. Follow the contract’s clarification, nonconformance and transmittal process.

Practical FAQ

**Does the ITP itself prove the inspection happened?** No. It defines the planned control. The associated record or a progressively completed form must capture the actual event and evidence, as the project procedure requires.

**Can formwork and reinforcement sit in the same pour dossier?** Yes, if each check remains identifiable by stage, location, governing source, assigned role and record. Keep separate plan rows or linked records where triggers, sources, roles or control points differ.

**What if a laboratory report is not available at closeout?** List it as outstanding, identify the samples and affected pour/lot, name the follow-up owner and due/status under the project process, and transmit with the open item clearly stated if that process permits. Do not mark the test closed or infer acceptance.

**Can a checklist replace a required test report?** Only if the governing project requirement explicitly accepts that record for the required evidence. Otherwise link and retain the original report; a tick or transcribed result is not its substitute.

Fictional example: reconcile one pour dossier before submission

Fictional workflow illustration only. IDs and status are invented. No engineering value, actual test result, project acceptance or release is represented.

1. Create an index for fictional pour P-17 and list its ITP rows for formwork, reinforcement/embeds, receipt/testing, placement and curing, each with the project source locator to be verified.
2. Link the completed formwork and reinforcement records to P-17 and their actual drawing revisions; place any unresolved detail in the project query/NCR route rather than writing an assumed acceptance.
3. Index each delivery docket and batch against P-17; link actual fresh-test entries and specimen IDs, then add original laboratory reports when received.
4. Cross-reference placement and curing records, photos if required, deviations and written dispositions using the same identifier.
5. Run the expected-versus-received reconciliation. Show one pending report as open with its sample IDs, follow-up owner and status; do not label the dossier complete until the project’s stated closure condition is satisfied.