Soil Compaction Density Test Log
Soil Compaction Density Test Log template for recording field density, moisture, Proctor reference data, and pass/fail decisions in one place. Use it to document acceptance, track corrective action, and keep a clear audit trail.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Construction · Civil Engineering · Geotechnical Testing · Utilities
Overview
The Soil Compaction Density Test Log template records the field data used to judge whether a compacted lift meets the project specification. It brings together project identifiers, test location, lift thickness, material type, Proctor reference data, wet and dry density, field moisture, compaction percentage, and the final acceptance decision.
Use this template when you need a repeatable record for earthwork, subgrade, backfill, trench restoration, or any other work that depends on measured compaction. It is especially useful when multiple technicians test different areas and you need a consistent audit trail that ties each result to a specific lift and reference report. The form also supports follow-up by capturing corrective action details and reviewer comments when a test does not pass.
Do not use this template as a general site diary or a high-level project status form. It is not meant for unrelated inspections, and it should not be overloaded with fields that are not needed for the compaction decision. If a project does not require a Proctor reference, density calculation, or acceptance review, a simpler field log may be a better fit. For public-facing or shared workflows, keep required fields limited to what is necessary, use clear validation, and avoid collecting extra PII beyond the technician sign-off and project record.
Standards & compliance context
- The template supports an audit trail by linking field results, reference data, reviewer comments, and supporting files in one record.
- Use data minimization by collecting only the project, test, and sign-off fields needed to determine acceptance and avoid unnecessary personal data.
- If the form is shared publicly or used on mobile devices, design labels, validation, and error states to meet WCAG 2.1 AA accessibility expectations.
- If technician names or signatures are collected, disclose how that information will be used and retained before submission.
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 Test Information
This section anchors the record to one project, one date, and one technician so the test can be traced later without ambiguity.
- Project Name
- Project Number
- Test Date
- Technician Name
- Test Method
Location and Lift Details
This section identifies the exact lift and site conditions being tested, which is essential for finding the same spot again and understanding the result.
- Test Location / Station
- Area / Lot / Structure
- Lift Number
- Lift Thickness (in)
- Material Type
- Weather Conditions
Proctor Reference Data
This section captures the benchmark used to judge compaction, so the field result can be compared against the correct lab reference.
- Proctor Type
- Maximum Dry Density (pcf)
- Optimum Moisture Content (%)
- Laboratory Report Reference
Field Test Results
This section holds the measured values that determine whether the lift meets the specification and whether the result needs follow-up.
- Wet Density (pcf)
- Dry Density (pcf)
- Field Moisture Content (%)
- Compaction (%)
- Test Result Notes
Acceptance and Follow-Up
This section records the decision, the specification requirement, and any corrective action so the outcome is clear and actionable.
- Acceptance Decision
- Specification Requirement (%)
- Corrective Action Required?
- Corrective Action Details
- Reviewer Comments
Attachments and Sign-Off
This section preserves supporting evidence and the inspector signature, creating a reviewable audit trail for closeout.
- Supporting Files
- Inspector Signature
How to use this template
- Enter the project name, project number, test date, technician name, and test method so the log is tied to one specific field test.
- Record the exact test location, area or lot, lift number, lift thickness, material type, and weather conditions to show where and under what conditions the test was taken.
- Add the Proctor reference data, including proctor type, maximum dry density, optimum moisture, and lab report reference, so the field result can be compared against the correct benchmark.
- Capture the wet density, dry density, field moisture, and compaction percentage immediately after the test, then write any notes that explain unusual conditions or borderline results.
- Select the acceptance decision, list the specification requirement, and document corrective action details and reviewer comments if the test fails or needs follow-up.
- Attach supporting files and collect the inspector signature after the record is complete so the form becomes a usable audit trail.
Best practices
- Use a date picker for test_date and numeric inputs for density, moisture, and lift thickness so the record stays clean and easy to validate.
- Keep required fields limited to the data needed to make the acceptance decision, and use progressive disclosure for corrective action fields only when the test fails.
- Record the test location with enough detail to find the exact spot later, such as station, offset, lot, or grid reference.
- Match the test method and Proctor type to the same material and lift being evaluated, or the compaction percentage may be misleading.
- Document weather conditions when they affect moisture or test reliability, especially after rain, drying wind, or freezing conditions.
- Attach the lab report or supporting file that backs the Proctor reference so reviewers can verify the benchmark without searching elsewhere.
- Write corrective action details in concrete terms, such as rework, recompact, dry out, or retest, rather than vague notes like 'fix later'.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this Soil Compaction Density Test Log template cover?
It covers the core data needed to evaluate a compacted lift: project details, test location, lift thickness, material type, Proctor reference data, field density, moisture, acceptance decision, and follow-up actions. It is designed to capture the test result and the context behind it, not just a single pass/fail mark. The attachments and sign-off section also supports an audit trail for review and closeout.
When should this log be used during construction?
Use it each time a field density test is performed on a compacted lift, especially before the next lift is placed or before an area is accepted. It is useful for earthwork, subgrade, backfill, trench restoration, pads, and other work where compaction specifications must be verified. If the work is not being tested against a compaction requirement, this template may be more detail than you need.
Who should complete and review this form?
A field technician, inspector, geotechnical representative, or quality control staff member typically completes the test log. A supervisor, project engineer, or reviewer can then confirm the acceptance decision and any corrective action. The template works best when the person taking the test records the data immediately at the site and the reviewer signs off after checking the specification requirement.
How often should compaction tests be logged?
Log a separate entry for each test location or each lift that is tested, rather than trying to summarize multiple tests in one record. If a project has repeated lifts, each lift should have its own test result so the record stays traceable. This makes it easier to compare results by area, identify patterns, and show which sections were accepted or reworked.
What common mistakes does this template help prevent?
It helps prevent missing Proctor reference data, unclear test locations, and incomplete acceptance notes. It also reduces the risk of mixing wet density, dry density, and compaction percentage fields or using the wrong lift thickness. Another common issue is skipping the corrective action details after a failed test, which leaves no clear record of what was fixed.
How does this template support compliance and documentation quality?
The log supports a clear audit trail by linking field results to the reference test, reviewer comments, and supporting files. It also encourages data minimization by collecting only the project, test, and acceptance details needed for the compaction decision. For public-facing or shared workflows, the form should use clear field labels, required-versus-optional markers, and accessible validation consistent with WCAG 2.1 AA.
Can this template be customized for different specifications or materials?
Yes. You can adjust the acceptance threshold, add material-specific fields, or rename the test method and Proctor reference fields to match your project standard. If your workflow needs branching, conditional logic can show corrective action fields only when the test fails, which keeps the form shorter and easier to complete.
What should happen after the form is submitted?
The submission should create a dated record that is available for review, attachment storage, and follow-up action if the test fails. If your workflow includes approvals, the reviewer should be notified so they can confirm acceptance or request rework. A clear confirmation message helps the technician know the log was received and filed.
Related templates
Ready to use this template?
Get started with MangoApps and use Soil Compaction Density Test Log with your team — pricing built for small business.
