Loading...
quality

Soil Compaction Density Test Log

Log soil compaction density tests with Proctor reference data, lift details, field results, and acceptance status in one place. Use it to document pass/fail decisions and track rework or retests.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Construction · Civil Engineering · Utilities · Infrastructure

Overview

This Soil Compaction Density Test Log template records the information needed to verify whether a soil lift meets the required compaction target. It brings together project identifiers, test location, lift thickness, soil classification, Proctor reference data, wet and dry density readings, moisture content, passes made, and the final acceptance decision.

Use it when you need a repeatable field record for earthwork, backfill, subgrade, or embankment testing. It is especially useful when multiple people touch the process: one person collects the field reading, another reviews the result, and a third signs off on acceptance or requests rework. The template also supports retest tracking when a lift fails and needs additional compaction.

Do not use this log as a substitute for a lab report or specification sheet. It is meant to document the field test and the decision made from it, not to define the project’s compaction criteria. If your workflow does not require formal acceptance, or if you are only tracking general site observations without density measurements, a simpler inspection note may be a better fit. Keep the form focused on the fields that affect the result so it stays fast to complete and easy to audit.

Standards & compliance context

  • Keep the form aligned with the project specification and the applicable compaction acceptance criteria so the recorded result matches the governing requirement.
  • Use clear required versus optional fields and accessible labels to support WCAG 2.1 AA expectations for any public-facing or shared form.
  • Limit the form to the minimum data needed for the test record to support GDPR data minimization and reduce unnecessary collection.
  • If the log is used in a regulated quality workflow, preserve the reviewer signature, review date, and supporting files as part of the audit trail.

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 identifies the job, the test point, and the person who performed the check so the record can be traced without ambiguity.

  • Project Name (required)
  • Project Number
  • Test Date (required)
  • Test Time
  • Test ID
  • Inspector Name

    Optional for internal traceability. Do not collect more PII than needed.

Soil and Lift Details

This section captures the physical conditions being tested, which is essential for comparing the result to the correct placed layer.

  • Test Location (required)
  • Material Type (required)
  • Lift Number
  • Lift Thickness (inches) (required)
  • Soil Classification
  • Test Method (required)

Proctor Reference Data

This section stores the lab baseline used to judge compaction, which is what turns a field reading into an acceptance decision.

  • Proctor Method (required)
  • Maximum Dry Density (required)

    Enter the lab reference dry density used for acceptance.

  • Optimum Moisture Content (%) (required)
  • Required Compaction (%) (required)

Field Test Results

This section records the actual density and moisture measurements that determine whether the lift passes or needs rework.

  • Wet Density (required)
  • Dry Density (required)
  • Field Moisture Content (%) (required)
  • Compaction Achieved (%)
  • Number of Roller Passes

Acceptance and Follow-Up

This section documents the decision, any observations, and the next action when the test does not meet the requirement.

  • Test Result (required)
  • Acceptance Status (required)
  • Observations and Notes
  • Corrective Action
  • Retest Date

Attachments and Sign-Off

This section preserves supporting evidence and reviewer approval so the log functions as a complete audit trail.

  • Supporting Files

    Upload lab reports, calibration records, photos, or field notes.

  • Reviewer Signature
  • Review Date

How to use this template

  1. 1. Enter the project and test information first, including the test date, location, inspector name, and a unique test ID so the record can be traced later.
  2. 2. Record the soil and lift details exactly as observed in the field, using the correct lift number, thickness, soil classification, and test method.
  3. 3. Add the Proctor reference data from the applicable lab result, then confirm the required compaction percent before calculating acceptance.
  4. 4. Capture the field test results, including wet density, dry density, field moisture content, compaction percent, and the number of passes made at the test point.
  5. 5. Mark the acceptance status, note any observations or corrective action, and schedule a retest date if the lift does not meet the requirement.
  6. 6. Attach supporting files and complete the reviewer signature and review date so the log becomes a usable audit trail.

Best practices

  • Use the same Proctor method and reference values for every test tied to the same specification so the acceptance decision stays consistent.
  • Record the lift thickness in inches and the exact test location before leaving the area, because those details are easy to lose after the next test point.
  • Separate wet density, dry density, and compaction percent into distinct fields so the reviewer can verify the calculation without guessing.
  • Document the number of passes made at the test point, not just whether the lift was compacted, because pass count often explains borderline results.
  • Use conditional logic to show corrective action and retest fields only when the test fails, which keeps the form shorter and easier to complete.
  • Attach photos, lab reports, or ticket references when they help explain the result, but avoid collecting unnecessary PII or unrelated project data.
  • Require a reviewer signature only after the result and supporting files are complete so the audit trail reflects a final, checked record.

What this template typically catches

Issues teams running this template most often surface in practice:

The wrong Proctor reference is entered, which makes the compaction percentage unreliable even when the field reading is correct.
Lift thickness is omitted or recorded inconsistently, making it hard to judge whether the test point represents the placed layer.
Wet density and dry density are confused, which can produce a false pass or false fail.
The number of passes made is left blank, removing a key clue when a lift fails acceptance.
Corrective action is not documented after a failed test, so the retest has no clear link to the original issue.
Supporting files are attached without a clear label or date, which weakens the audit trail during review.

Common use cases

Civil Inspector on a Road Base Lift
A field inspector logs density tests for each compacted lift before the next course is placed. The record ties the test point to the lift number, Proctor data, and acceptance status so the crew knows whether to proceed.
Utility Contractor Backfill Verification
A utility foreman uses the template to document trench backfill tests after each lift is compacted. If a section fails, the corrective action and retest date stay linked to the original test record.
Geotechnical QA for Building Pad Prep
A geotechnical technician records field density readings for a foundation pad and attaches supporting photos or lab references. The reviewer can sign off once the compaction result matches the project requirement.
Municipal Project Closeout Documentation
A public works team keeps a standardized log for embankment and subgrade acceptance during closeout. The template creates a consistent file for review, handoff, and later audit requests.

Frequently asked questions

What is this Soil Compaction Density Test Log used for?

This template records the details needed to evaluate whether a soil lift meets the required compaction standard. It captures project information, lift thickness, test method, Proctor reference data, field density results, and the final acceptance decision. Use it when you need a consistent record for earthwork quality checks, backfill verification, or subgrade acceptance.

When should a compaction test be logged?

Log the test as soon as the field reading is taken, while the lift location, moisture condition, and equipment passes are still fresh. It is especially useful after each placed lift, before covering work, and before requesting approval from the reviewer or inspector. If a test fails, the same log should also capture the corrective action and retest date.

Who should fill out this template?

A field inspector, geotechnical technician, or quality control lead typically completes the log, depending on the project workflow. The reviewer or supervisor can then sign off after checking the results and supporting files. If your process separates data collection from approval, this template supports that handoff cleanly.

Does this template support different soil test methods?

Yes. The template includes a field for test method so you can record the approach used for the density check, along with the matching Proctor reference method. That matters because the acceptance result depends on comparing the field reading against the correct laboratory baseline. If your project uses multiple methods, keep the method field consistent across all logs.

What are the most common mistakes when using a compaction log?

Common mistakes include leaving out the lift number, mixing up wet and dry density, or recording the wrong Proctor reference values. Another frequent issue is documenting the result without noting the actual passes made or the corrective action after a failed test. This template helps prevent those gaps by separating field data, acceptance, and follow-up into distinct sections.

How does this template help with compliance and documentation?

It creates a clear audit trail showing what was tested, where it was tested, which reference values were used, and who reviewed the result. That supports quality control records and makes it easier to explain acceptance decisions later. If your project has formal inspection or closeout requirements, the attachments and sign-off fields help keep the record complete.

Can I customize the log for different project types?

Yes. You can add fields for project phase, stationing, grid coordinates, material source, or specification reference if your workflow needs them. Keep the form focused on the data you actually use so it stays aligned with data minimization and remains quick to complete in the field. Conditional logic can also hide follow-up fields until a test fails.

What should happen after I submit the log?

After submission, the reviewer should confirm the acceptance status, check any attached photos or lab reports, and assign corrective action if the test failed. If a retest is required, the retest date should be scheduled and linked to the original record. This keeps the log useful as both a field record and a follow-up tracker.

Go deeper on the topic

Related concepts
  • A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
  • Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
Related guides

Ready to use this template?

Get started with MangoApps and use Soil Compaction Density Test Log with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?