Concrete Compressive Strength Break Log
Log concrete cylinder break test results at 7, 14, and 28 days, record acceptance status, and keep the project details needed to review strength compliance in one place.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Construction · Civil Engineering · Materials Testing · Infrastructure
Overview
This Concrete Compressive Strength Break Log template records the project, sample, mix, specimen, and break-result details needed to track concrete cylinder tests at common ages such as 7, 14, and 28 days. It is designed for quality control workflows where you need a clear record of what was tested, when it was tested, what the measured strength was, and whether the result was accepted.
Use this template when you need a repeatable log for lab or field review, project documentation, or acceptance decisions tied to a specified compressive strength. It is especially useful when multiple cylinders, multiple pours, or multiple test ages need to be compared against the same project requirements. The sign-off section helps preserve accountability by showing who submitted the record and when.
Do not use this template as a substitute for the actual laboratory report or for unrelated material testing. If your process does not require acceptance review, you may not need the corrective_action or reviewer_comments fields. Keep the form focused on the minimum necessary data: project identifiers, specimen details, measured results, acceptance basis, and supporting attachments. If a result is outside tolerance or the specimen age is unusual, document that in break_age_notes rather than burying it in a general comment field.
Standards & compliance context
- This template supports an audit trail by separating the measured result, the acceptance basis, and the final sign-off.
- For quality documentation, keep only the minimum necessary project and specimen data needed to identify the test and evaluate acceptance.
- If the log is shared across contractors or labs, limit access to the supporting attachments and reviewer comments to authorized reviewers only.
- Use consistent field validation for dates, numeric strength values, and specimen age so the record remains usable for later review.
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 the break result to the correct project, sample, and test event so the record is traceable.
- Project Name
- Project Number
- Sample / Cylinder ID
- Sample Location / Placement Area
- Test Date
- Tested By
Concrete Mix and Specimen Details
This section captures the mix and curing context needed to interpret whether the specimen should meet the target strength.
- Specified Compressive Strength (psi)
- Mix Design ID
- Cylinder Size
- Curing Method
- Specimen Age at Break (days)
Break Results
This section stores the actual compressive strength data and any notes needed to explain the test age or condition.
- Break Results by Age
-
Notes on Break Ages Tested
Use this field to explain any missing 7-day, 14-day, or 28-day breaks, retests, or unusual test conditions.
Acceptance Evaluation and Supporting Details
This section records the decision, the rule used to make it, and any follow-up action or evidence.
- Acceptance Status
- Acceptance Basis
-
Corrective Action / Follow-Up
Describe any retest, investigation, NCR, or disposition action if the result is rejected or pending review.
-
Supporting Attachments
Upload lab sheets, calibration records, photos, or other supporting documentation.
- Reviewer Comments
Sign-Off
This section shows who submitted the log and when, which supports accountability and review.
- Submitted By
- Signature
- Submission Date
How to use this template
- Enter the project_name, project_number, sample_id, sample_location, test_date, and tested_by fields so the break record is traceable to a specific pour and specimen.
- Fill in the concrete mix and specimen details, including specified_strength_psi, mix_design_id, cylinder_size, cure_type, and specimen_age_days, using the actual test setup rather than estimates.
- Record each measured break result in break_results and note any age-related context or irregularities in break_age_notes, especially when the test age differs from the planned schedule.
- Set acceptance_status and acceptance_basis after comparing the result to the project requirement, then add corrective_action and reviewer_comments if the specimen does not meet the expected outcome.
- Attach the supporting lab report or related evidence in supporting_attachments, then complete submitted_by, submission_signature, and submission_date to finalize the log.
Best practices
- Use the exact specimen age in days instead of a free-text description so the log can be reviewed against the test schedule without guesswork.
- Mark required fields clearly and keep optional fields optional, especially when the record is being completed in the field or by a lab technician.
- Capture the specified strength and mix design ID on every entry so acceptance decisions can be traced back to the correct project requirement.
- Use break_age_notes for unusual curing, delayed testing, or damaged specimens rather than mixing those details into the main result field.
- Attach the source lab report or certificate whenever the acceptance status depends on a formal test record.
- Use conditional logic to show corrective_action only when the result is not accepted, which keeps the form shorter and reduces completion errors.
- Keep reviewer_comments focused on the decision and next step, not on repeating the measured values already stored in break_results.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this Concrete Compressive Strength Break Log template used for?
Use it to record concrete cylinder break results at the planned test ages, along with the project, sample, mix, and acceptance details needed to review strength performance. It is meant for quality control and project documentation, not for replacing the lab report itself. The log helps you compare results against the specified strength and keep the review trail in one place.
Which test ages does this template support?
This template is built around common 7-day, 14-day, and 28-day break checks, but it can be adapted for other specimen ages if your project or lab uses a different schedule. The specimen_age_days and break_results fields let you document the actual age tested. If you only run one acceptance break, you can still use the same structure and leave the unused ages out through customization.
Who should fill out this log?
It is usually completed by a lab technician, quality inspector, field engineer, or project administrator who has the test results and project context. A reviewer or supervisor should then confirm the acceptance status and add comments if the result needs follow-up. The sign-off section makes it clear who submitted the record and when.
What should be included in the break results field?
Include the measured compressive strength for each break, the test age, and any notes needed to interpret the result, such as specimen condition or unusual curing conditions. Use the field to capture the actual data, not a narrative summary. If your workflow needs more detail, attach the supporting lab report rather than overloading the log.
How does this template help with acceptance decisions?
The acceptance_status and acceptance_basis fields separate the result from the rule used to judge it, which makes reviews easier to audit later. That is useful when the decision depends on project specs, mix design requirements, or a governing standard. If the result is not accepted, the corrective_action field gives you a place to document the next step.
What are the most common mistakes when using this log?
Common mistakes include entering the specimen age in free text without a clear day count, omitting the specified strength, and leaving the acceptance basis vague. Another frequent issue is recording the break result without linking it to the project or sample ID, which makes traceability difficult. The template is designed to reduce those gaps by separating project, specimen, result, and review fields.
Can this template be customized for different labs or projects?
Yes. You can add fields for batch ticket number, curing room ID, technician initials, or additional break ages if your process requires them. If your organization uses conditional logic, you can show corrective_action only when acceptance_status is not accepted, which keeps the form shorter and easier to complete.
What attachments should be linked to the log?
Attach the supporting lab report, photos of broken cylinders if your process requires them, and any project correspondence tied to the result. The supporting_attachments field is there so the log points to the evidence rather than storing everything in the body of the form. That helps preserve a cleaner audit trail.
How is this better than tracking breaks in a spreadsheet or email thread?
A dedicated log keeps the same fields in the same order every time, which reduces missing data and makes review faster. It also supports clearer validation, sign-off, and attachment tracking than scattered emails or ad hoc spreadsheets. For teams that need traceability, that structure is usually easier to maintain.
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.
