Pile Driving Daily Log
Record pile driving progress, blow counts, refusal criteria, hammer performance, and embedment measurements in one daily field log. Use it to document production, flag exceptions, and create a clean sign-off trail.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Construction · Civil Engineering · Infrastructure · Marine Works
Overview
This Pile Driving Daily Log template is a field form for recording the core facts of a pile driving shift: when the work happened, which pile was driven, what hammer was used, how far the pile advanced, whether refusal criteria were met, and whether any equipment issues or exceptions occurred.
Use it when you need a consistent daily record for foundation work on bridges, wharves, retaining structures, or other projects where pile performance matters. The template helps crews capture production details in a format that can be reviewed by the superintendent, QC lead, or project engineer without piecing together handwritten notes. It also supports a cleaner audit trail when there are questions about refusal, alignment, or hammer performance.
Do not use this as a generic site diary if you are not actually tracking pile driving. It is also not the right form for geotechnical borings, concrete placement logs, or general equipment maintenance. If your project does not require refusal criteria, embedment measurements, or hammer performance tracking, a simpler daily report may be a better fit. The structure is intentionally focused so the crew only records what matters for pile driving decisions and acceptance.
What's inside this template
Log Details
This section anchors the record to one date, project, location, and shift so the rest of the data can be reviewed in context.
-
Log Date
Select the date the pile driving work was performed.
-
Project Name
Enter the project or site name.
-
Work Location
Enter the specific area, structure, or station where pile driving occurred.
- Shift
Pile and Driving Setup
This section captures the pile and hammer configuration before driving starts, which is essential for interpreting the results later.
-
Pile ID
Enter the pile identifier or mark number.
- Pile Type
- Hammer Type
-
Lead and alignment verified?
Confirm the leads, alignment, and positioning were checked before driving.
Driving Progress
This section records the time window and embedment achieved, giving the team a clear production snapshot for the day.
-
Driving Start Time
Record when driving began for this pile.
-
Driving End Time
Record when driving stopped for this pile.
-
Embedment Depth Achieved
Enter the total embedment achieved during this log period.
- Embedment Unit
Blow Counts and Refusal Criteria
This section shows whether the pile met the specified driving threshold and provides the key acceptance comparison.
-
Blow Count for Last 10 Inches/25 cm
Enter the number of blows required for the last 10 inches or 25 cm of penetration.
-
Refusal Criteria Reference
Enter the project specification or acceptance criterion used for refusal.
- Refusal reached?
-
Acceptance criteria met?
Indicate whether the pile met the specified driving criteria.
Hammer Performance
This section documents whether the hammer delivered the expected energy and whether any equipment problems affected driving.
-
Rated Hammer Energy
Enter the rated energy used for the hammer during this operation.
- Energy Unit
-
Hammer Performance
Rate hammer performance during the shift.
-
Hammer Issues or Downtime
Describe any malfunctions, delays, or maintenance issues affecting driving.
Exceptions and Sign-Off
This section records deviations, corrective actions, and the final sign-off so the log becomes a usable audit trail.
-
Exceptions or Unusual Conditions
Document weather, obstructions, refusal anomalies, or other unusual conditions.
-
Corrective Actions Taken
Describe any corrective actions taken in response to exceptions or equipment issues.
-
Submitted By
Enter the name or role of the person completing this log.
-
Field Sign-Off
Optional signature for field verification and audit trail.
How to use this template
- 1. Enter the log date, project name, location, and shift at the start of the work period so the record is tied to one specific driving session.
- 2. Record the pile ID, pile type, hammer type, and whether lead alignment is acceptable before driving begins.
- 3. Fill in the start time, end time, embedment depth, and embedment unit as the pile is advanced, using the correct unit field rather than free text.
- 4. Document the last 10 blow counts, the refusal criteria specification, and whether refusal was reached so the observed driving can be compared to the project requirement.
- 5. Note rated energy, hammer performance, and any hammer issues, then describe exceptions and corrective actions before submitting the log for sign-off.
Best practices
- Record the pile ID and pile type before the first blow so the log cannot be confused with another location or element.
- Use the exact refusal criteria from the project specification, not a paraphrase, so the acceptance check is unambiguous.
- Capture embedment with the correct unit and keep the unit consistent across the project to avoid conversion errors.
- Document hammer issues as specific observations, such as loss of energy or misfire, and pair each issue with the corrective action taken.
- Mark lead alignment as not OK when it is out of tolerance and add an exception note instead of leaving the field blank.
- Complete the log during the shift, not from memory at the end of the day, so blow counts and times stay accurate.
- Keep the form focused on pile driving data and avoid adding unrelated site notes that make the record harder to review.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this Pile Driving Daily Log template used for?
This template captures the daily record of pile driving work, including pile identification, hammer setup, embedment depth, blow counts, refusal criteria, and any exceptions. It is meant to document what was driven, how it performed, and whether the work met the specified criteria. Use it as the field record for each shift or driving session.
How often should this log be completed?
Complete it once per shift or once per driving session, depending on how your crew organizes production. If conditions change during the day, update the log at the time of the change rather than waiting until the end. That keeps the record accurate and reduces missing details.
Who should fill out and sign this form?
The field superintendent, pile driving foreman, or designated inspector usually completes the log, with sign-off from the person responsible for the work record. The key is that the person entering the data understands the pile type, hammer setup, and refusal criteria being used. If your project requires a separate inspector, use the signature field to capture that review.
Does this template support refusal criteria and acceptance checks?
Yes. The template includes fields for refusal criteria, whether refusal was reached, and whether the criteria were met. That makes it easier to compare the observed driving behavior against the project specification and avoid relying on memory or informal notes.
What are the most common mistakes when using a pile driving log?
Common mistakes include leaving out the pile ID, using vague refusal language, and recording embedment without units. Another frequent issue is noting hammer issues in free text without stating the corrective action taken. This template is structured to reduce those gaps by separating the key fields.
Can this template be customized for different pile types or hammer setups?
Yes. You can add conditional logic for concrete, steel, or timber piles, or for diesel, hydraulic, or vibratory hammer types. If your team tracks additional inspection points, such as splice checks or cushion condition, those can be added as optional fields without changing the core daily log.
How does this compare with ad hoc notes or a spreadsheet?
Ad hoc notes often miss one of the critical items needed for later review, such as refusal criteria, embedment depth, or the time window for the shift. This template gives you a consistent field order, clearer validation, and a more reliable audit trail. That makes it easier to review production and resolve disputes later.
What should be shared with the project team after submission?
After submission, the log should be routed to the project engineer, QC lead, or construction manager, depending on your workflow. The important part is that the record is available quickly enough to support same-day decisions if driving behavior changes. If your process includes attachments, you can also link photos or test results to the log.
Related templates
Ready to use this template?
Get started with MangoApps and use Pile Driving Daily Log with your team — pricing built for small business.
