Concrete Compressive Strength Break Log
Track concrete cylinder break results at 7, 14, and 28 days with clear acceptance status, test details, and follow-up actions in one place.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Construction · Civil Engineering · Materials Testing · Concrete Supply
Overview
The Concrete Compressive Strength Break Log is used to record cylinder break results for concrete samples tested at common ages such as 7, 14, and 28 days. It captures the project and sample details, cylinder identification, curing method, test machine, measured load, calculated compressive strength, specified strength, and the final acceptance decision. That makes it useful for field technicians, lab staff, and QA/QC reviewers who need a clean record of how a result was produced and whether it met the project requirement.
Use this template when you need to compare test results against a specified strength, document multiple breaks from the same sample, or keep a defensible record for project files. It is especially helpful when several people touch the process: one person casts or tags the cylinders, another cures and tests them, and a reviewer signs off on acceptance or corrective action. The form also works well when a supplier, mix design, or location needs to be traced back after a low-strength result.
Do not use this log as a substitute for a full laboratory report when your workflow requires additional test methods, calibration records, or detailed specimen history. It is also not the right fit for non-concrete materials or for projects that only need a simple pass/fail note without supporting test data. If your team needs slump, air content, or batch ticket information, add those fields before rollout so the log matches your actual inspection process.
Standards & compliance context
- Use the log to preserve a traceable test record that supports project specifications, quality procedures, and laboratory review.
- Keep reviewer signoff and acceptance criteria visible so the record shows who approved the result and why.
- If the result is used for formal acceptance, align the fields with the testing and documentation requirements in your contract or local procedure.
- Retain attachments and notes with the record when they are needed to explain a failed or borderline break.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Project and Sample Information
This section ties each break to the right project, supplier, and mix so the result can be traced back later.
- Project Name
- Project Number
- Sample ID
- Sample Location / Placement Area
- Concrete Supplier
- Mix Design / Mix ID
Cylinder and Test Details
This section documents how the specimen was prepared and who performed the test, which is essential for repeatability.
- Cylinder ID
- Cylinder Size
- Cast Date
- Curing Method
- Test Date
- Technician Name
Break Age and Results
This section captures the actual test outcome and the numbers needed to calculate and verify strength.
- Break Age (Days)
- Test Machine ID
- Maximum Load (lbf)
- Compressive Strength (psi)
- Specified Strength (f'c) psi
- Strength Ratio (%)
Acceptance Evaluation
This section shows whether the result met the project requirement and what action followed if it did not.
- Acceptance Criteria
- Accepted
- Reason for Non-Acceptance
- Corrective Action / Follow-Up
Notes and Attachments
This section preserves supporting context, photos, and reviewer signoff for borderline or disputed results.
- Test Notes
- Supporting Documents
- Reviewed By
How to use this template
- 1. Enter the project, sample, supplier, and mix design details so each break can be traced back to the correct placement and specimen set.
- 2. Record the cylinder ID, size, cast date, curing method, and technician name before the specimen is tested.
- 3. Fill in the break age, test machine ID, maximum load, and calculated compressive strength immediately after the break.
- 4. Compare the result to the specified strength, apply the acceptance criteria, and mark the sample accepted or not accepted.
- 5. Document any failure reason, corrective action, notes, and attachments, then route the record to the reviewer for signoff.
Best practices
- Use one log entry per cylinder break so 7-day, 14-day, and 28-day results never get blended together.
- Record the curing method exactly as performed, because curing differences can explain strength variation.
- Verify the cylinder ID against the field tag before entering the result to avoid mismatched sample records.
- Calculate compressive strength from the actual break load and cylinder size, then check the math before review.
- Attach photos, fracture notes, or lab sheets when the result is borderline, failed, or disputed.
- Keep acceptance criteria tied to the project specification so reviewers do not rely on memory or informal thresholds.
- Have a second person review failed breaks and corrective actions before the record is closed.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this template used for?
This template records concrete cylinder break results for a specific sample and test age, along with the machine used, measured strength, and acceptance decision. It helps quality teams compare test results against the specified strength and document why a break passed or failed. Use it when you need a consistent record for lab testing, field verification, or project closeout.
How often should the log be completed?
Complete a new entry each time a cylinder is broken and tested, whether that is at 7, 14, or 28 days or another project-specific age. If a project requires multiple cylinders for the same sample, log each break separately so the results are easy to compare. This avoids mixing early-age and final acceptance data in one record.
Who should fill out this form?
A concrete testing technician, lab technician, or quality inspector usually completes the break data, while a supervisor or reviewer confirms the acceptance decision. The person entering the results should be the one who performed or directly observed the test. A separate reviewer is useful when the result affects acceptance, rejection, or corrective action.
Does this template support compliance or audit needs?
Yes, it creates a traceable record of the sample, curing method, test age, equipment used, and final disposition. That makes it easier to show how a result was obtained and who reviewed it. It is especially useful when project specifications, lab procedures, or contract requirements call for documented strength verification.
What are the most common mistakes when using a break log?
Common mistakes include entering the wrong sample ID, using the wrong break age, or forgetting to record the curing method. Another frequent issue is calculating compressive strength incorrectly or leaving the acceptance criteria blank. Missing reviewer information also makes the record harder to defend later.
Can this template be customized for different testing workflows?
Yes, you can add fields for slump, air content, batch ticket number, specimen condition, or laboratory report number. You can also adjust the acceptance section to match project specifications or local testing procedures. If your team tracks multiple cylinders per sample, add a field for replicate number or specimen position.
What integrations work well with this form?
This log works well with project management tools, QA/QC dashboards, document storage, and spreadsheet exports. Teams often connect it to a photo attachment workflow so cylinder labels and fracture surfaces are stored with the result. It can also feed reporting systems that summarize pass/fail status by project or mix design.
How should a team roll this out?
Start by defining the required fields, the acceptance rule, and who approves failed breaks. Then standardize naming for project numbers, sample IDs, and cylinder IDs so records stay searchable. Train technicians to enter results immediately after testing and to attach supporting notes when results are borderline or rejected.
How is this better than tracking breaks in ad hoc notes or spreadsheets?
A dedicated form keeps every break record in the same structure, which reduces missing data and makes review faster. Ad hoc notes often leave out the test machine, curing method, or acceptance reason, which makes later comparison difficult. A standardized log also makes it easier to audit trends across projects and mixes.
Related templates
Ready to use this template?
Get started with MangoApps and use Concrete Compressive Strength Break Log with your team — pricing built for small business.
