Concrete Compressive Strength Break Log

This template records concrete cylinder break results by sample, mix, and test date so you can compare measured strength against the specified strength. It also captures acceptance status, specimen condition, and supporting attachments in one place. Use it to document routine quality checks and to create a clear audit trail when a break is borderline or fails.

Use it each time cylinders are broken at the project’s scheduled intervals, commonly 7, 14, and 28 days. It works best as a running log for a single project or pour sequence, rather than as a one-time summary at the end. If your project has special acceptance criteria, record them alongside the break results so the evaluation is traceable.

A lab technician, field technician, quality inspector, or concrete testing coordinator usually completes it, depending on your workflow. The person entering the log should have the test data, specimen identifiers, and acceptance criteria available. If multiple people handle sampling, curing, and testing, assign one owner for final review to avoid mismatched fields.

No. This log is a working record for tracking results and acceptance decisions, while the lab report remains the source document for the test data. The best use is to link or attach the supporting report, photos, and any nonconformance notes so the log and source documents stay aligned. That makes it easier to review the full test history during QA closeout.

Mark the break as nonconforming or pending review, then add notes explaining the deviation and any follow-up action. Common follow-up steps include verifying specimen labeling, checking curing conditions, confirming the test age, and escalating to the project engineer or QA lead. Keep the original result in the log rather than overwriting it, so the audit trail stays intact.

The template is focused on project and specimen data, so it avoids collecting unnecessary personal information. If you add technician names or signatures, keep the fields limited to what you actually need for accountability and access control. For public-facing or shared workflows, use role-based identifiers where possible and only collect PII with a clear purpose.

Yes. You can add or remove break intervals, change the specimen condition options, or expand the break results section to match your lab’s reporting format. If your process uses additional ages, such as 3-day or 56-day breaks, add them as separate result rows or conditional fields so the log stays readable.

This log pairs well with document storage for lab reports, photo attachments, and project records, plus spreadsheet or database exports for trend review. If your team uses a quality management system, map the sample ID and project number to the same identifiers used elsewhere. That reduces duplicate entry and makes it easier to search the full test history.

A dedicated template keeps the same fields in the same order every time, which reduces missed data and makes acceptance review faster. It also supports clearer validation, attachment handling, and status tracking than scattered emails. Compared with an ad-hoc spreadsheet, it is easier to standardize across projects and easier to audit later.