Soil Compaction Density Test Log
Track soil compaction tests in one place, from Proctor data and lift details to pass/fail results and corrective actions. Use it to document acceptance clearly before the next layer goes down.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Construction · Civil Engineering · Geotechnical Services · Infrastructure
Overview
The Soil Compaction Density Test Log is built for documenting field density checks on earthwork, backfill, subgrade, and other placed soils. It ties together the project details, test location, soil type, lift thickness, moisture condition, Proctor method, and measured results so the test can be reviewed against the project specification.
Use this template when you need a clear record of whether a lift meets acceptance criteria before the next layer is placed. It is especially useful on jobs with repeated testing, multiple lifts, or several inspectors working the same site, because it keeps each test tied to a specific date, location, and lift number. The form also gives space for corrective action and field observations, which helps explain why a test failed and what was done next.
Do not use this as a substitute for a lab report, a geotechnical engineer’s recommendation, or a project specification. If the work does not require density verification, or if the only need is a simple daily note, this form may be more detailed than necessary. It is most valuable when acceptance depends on measured compaction and moisture results, and when the project team needs a traceable record of who tested what, where, and under which criteria.
Standards & compliance context
- Use the project specification reference to show that the test was performed against the correct acceptance standard for the work.
- Keep the inspector sign-off and review notes complete so the record supports quality assurance and project audit trails.
- If the project is subject to agency or owner inspection requirements, retain the log with the related test reports and field documentation.
- When corrective action is required, document the retest or rework outcome so the final acceptance decision is traceable.
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 test to the correct job, date, location, and specification so the result can be traced without guesswork.
- Project Name
- Test Date
- Test ID
- Test Location Description
- Specification Reference
Soil and Lift Details
This section records the material and placement conditions that determine whether the density result is meaningful for that lift.
- Soil Type
- Lift Number
- Lift Thickness (inches)
- Moisture Condition
- Proctor Method
Test Results
This section captures the measured values needed to calculate compaction and compare the field result to the lab benchmark.
-
Maximum Dry Density
Enter the maximum dry density from the Proctor test.
- Optimum Moisture Content (%)
- Field Moisture Content (%)
- Field Dry Density
- Compaction Percentage (%)
- Number of Roller Passes
Acceptance and Observations
This section explains whether the lift passed, what standard was used, and what happened if the result needed correction.
- Acceptance Criteria
- Lift Accepted?
- Corrective Action Required
- Field Observations
Inspector Sign-Off
This section shows who completed the test, who reviewed it, and any notes needed to close out the record.
- Inspector Name
- Company Name
- Inspector Signature
- Review Notes
How to use this template
- 1. Enter the project name, test date, test ID, location, and specification reference so the test can be traced back to the correct work area and requirement.
- 2. Record the soil type, lift number, lift thickness, moisture condition, and Proctor method before you take field measurements so the test context is clear.
- 3. Fill in the maximum dry density, optimum moisture content, field moisture content, field dry density, compaction percentage, and test passes from the actual test results.
- 4. Compare the result to the acceptance criteria, mark whether the lift was accepted, and describe any corrective action if the lift did not meet the requirement.
- 5. Add field observations and inspector sign-off after the test is complete so the record reflects what was seen on site and who reviewed it.
Best practices
- Record the lift number and exact test location before leaving the area so the result cannot be confused with another section of the site.
- Use the same Proctor method referenced by the project specification so the field result is compared against the correct lab basis.
- Document moisture condition at the time of testing, especially when the soil is near wet or dry limits that can affect compaction performance.
- Note the number of passes only when the project uses pass-based acceptance or when passes help explain the achieved density.
- Describe corrective action in plain terms, such as reworking, moisture conditioning, or retesting, so the next reviewer can see what changed.
- Capture field observations while the crew and equipment are still on site, since surface condition, pumping, or segregation can be missed later.
- Keep acceptance criteria visible in the form instead of relying on memory, especially when multiple specs or agencies apply to the same project.
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 cover?
It captures the core details needed to document a compaction test: project information, test location, soil type, lift thickness, moisture readings, density results, and acceptance status. It also leaves room for corrective actions and field observations so you can explain why a lift passed or failed. This makes it useful as both a field record and a review document.
How often should this log be completed?
Complete it each time a density test is performed, not after the fact from memory. If a project has multiple lifts or repeated tests at the same location, create a separate entry for each test event. That keeps the record tied to the exact lift and condition being evaluated.
Who should fill out the form?
It is usually completed by the field inspector, geotechnical technician, or quality control staff performing the test. A supervisor or project manager may review the entry before acceptance is finalized. The person recording the test should be the one who observed the field conditions and measured the results.
Does this template help with compliance or inspection requirements?
Yes, it supports documentation practices commonly expected on construction and earthwork projects. The log helps show that the test was performed against a named specification, with recorded acceptance criteria and sign-off. It is not a substitute for project-specific engineering requirements, but it creates a clear audit trail.
What are the most common mistakes when using a compaction log?
Common issues include missing the specification reference, mixing up lift numbers, or recording moisture and density values without the associated test method. Another frequent problem is marking a lift accepted without noting the corrective action taken after a failed test. Incomplete observations can also make it hard to defend the result later.
Can I customize this log for different soil types or test methods?
Yes, and that is one of its main strengths. You can adjust the soil type field, add project-specific acceptance thresholds, or expand the observations section for granular fill, cohesive soils, or special backfill requirements. You can also rename fields to match your lab or inspector workflow.
What should this log integrate with in a real workflow?
It works well alongside lab Proctor reports, survey records, daily reports, and photo documentation. Many teams also connect it to project management systems or shared folders so test results are easy to retrieve during review. The goal is to keep the field result linked to the project record and the corrective action history.
How does this compare with ad-hoc notes or text messages from the field?
Ad-hoc notes are easy to lose and often omit the details needed to explain a pass or fail result. This template standardizes the same information every time, which makes review faster and reduces back-and-forth when a lift is questioned. It also gives you a cleaner record for handoff between field staff, supervisors, and clients.
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.
