A bore log is only as strong as the way it’s used in the field.

A clean template doesn’t make a good bore log. A perfect PDF doesn’t make a good bore log. A neat spreadsheet doesn’t make a good bore log.

What makes a good bore log is how the information is captured while the job is moving.

Directional drilling is not a controlled environment. It’s not linear. It’s not predictable.

Conditions shift. Ground changes. Utilities appear. Steering corrections happen. Production speeds up or slows down. Problems show up without warning.

This is why most “example bore logs” online are useless, they show perfect conditions, perfect numbers, and perfect days. That’s not the real world.

Real HDD work looks like:

• clean shots
• messy shots
• unexpected rock
• unmarked utilities
• wet clay
• steering drift
• delays
• adjustments
• production swings

A real bore log captures all of it, not just the parts that look good.

The examples below show what real logging looks like when the job is actually happening, not when someone is trying to remember it later.

These are the kinds of entries that:

• defend your footage
• justify your hours
• explain your production
• protect your invoice
• shut down disputes

And when these entries are captured in real time using Boreva, they become even stronger, because they’re not summaries. They’re records.

Example 1: Straight Shot, Clean Conditions

Scenario

This is the type of shot every driller wishes they had all day long:

• open ground
• no congestion
• predictable soil
• no utilities in the way
• no steering corrections
• no environmental factors slowing production

A clean shot doesn’t mean the log can be lazy. A clean shot means the log must be tight, because this is the baseline the GC will compare everything else against.

If your clean shots are sloppy, the GC assumes your complicated shots are worse.

Bore Log Entry

Shot: 1

Entry: STA 0+00

Exit: STA 3+00

Planned Length: 300 ft

Actual Length: 298 ft

Depth: 48 in

Ground: Clay, dry

Start: 8:00 AM

End: 9:10 AM

Issues: None

Notes: Clean shot, no steering corrections

Why This Entry Works

This is exactly what a clean, professional bore log entry looks like. Here’s why:

1. The Footage Is Exact, Not Rounded

Most crews would write:

• “300 ft”
• “About 300 ft”
• “~300 ft”

Rounded numbers kill credibility.

298 ft shows:

• the crew counted rods
• the crew tracked actual footage
• the log reflects reality, not memory

When the GC sees exact numbers, they trust the rest of the log.

2. Conditions Are Logged Even When Nothing Changes

A weak log would skip the ground conditions because “nothing happened.”

A strong log still records:

• Clay, dry

Why?

Because this becomes the baseline for the rest of the day.

If the next shot slows down, the GC can see:

• Shot 1: dry clay → fast
• Shot 2: wet clay → slower
• Shot 3: mixed soil → slower

Without this baseline, the GC assumes the crew slowed down — not the ground.

3. The Time Window Makes Sense

Start: 8:00 AM End: 9:10 AM

A 298‑ft shot in 70 minutes is:

• believable
• consistent
• aligned with the conditions
• aligned with the footage

Nothing looks inflated. Nothing looks padded. Nothing looks suspicious.

This is the kind of entry that never gets questioned.

4. Notes Confirm the Shot Was Clean

“Clean shot, no steering corrections.”

Short. Direct. Field‑credible.

This note tells the GC:

• the crew was in control
• the ground was predictable
• the alignment held
• no adjustments were needed

This is exactly how a clean shot should be documented.

5. No Issues Logged And That’s Important

A lot of crews skip the “Issues” field when nothing happens.

A strong log explicitly says:

• Issues: None

This matters because:

• it shows the field actually reviewed the shot
• it confirms nothing slowed production
• it prevents the GC from inventing problems later

A blank field creates doubt. A “None” entry creates clarity.

What This Example Really Shows

This example isn’t about the shot. It’s about the discipline.

A clean shot is where most crews get lazy. A clean shot is where most logs fall apart. A clean shot is where inconsistencies start.

But a clean shot is also:

• the baseline for the day
• the comparison point for later delays
• the reference point for production
• the anchor for the GC’s expectations

If your clean shots are logged correctly, your complicated shots have a foundation to stand on.

This is why this example matters.

How Boreva Handles This Shot in the Field

With Boreva, this entry is captured:

• when the shot finishes
• with exact footage
• with the correct conditions
• with timestamps
• with notes added immediately

The system removes:

• rounding
• guessing
• rewriting
• end‑of‑day reconstruction

Example 2: Rock Encounter Mid‑Shot

Scenario

This shot starts in soft, predictable clay, the kind of ground where production is fast and steering is easy. But halfway through the alignment, the crew hits a rock seam.

This is a classic HDD scenario:

• the first half of the shot drills fast
• the second half slows down
• steering becomes harder
• penetration rate drops
• the crew must adjust the head
• the timeline shifts

If this isn’t documented correctly, the GC will assume the crew slowed down for no reason.

This is where a bore log either protects you or exposes you.

Bore Log Entry

• Shot: 2
• Entry: STA 3+00
• Exit: STA 6+00
• Planned Length: 300 ft
• Actual Length: 312 ft
• Depth: 52 in
• Ground: Clay transitioning to rock at 140 ft
• Start: 9:30 AM
• End: 12:15 PM
• Issues: Slowed drilling due to rock
• Notes: Steering adjustments made after rock encounter

Why This Entry Works

This is a textbook example of how to document a condition change that affects production.

Let’s break down why this entry is strong.

1. The Ground Transition Is Documented at the Exact Point It Occurred

“Clay transitioning to rock at 140 ft.”

This single line does more than most contractors realize:

• it explains the slowdown
• it explains the extra footage
• it explains the steering corrections
• it explains the longer timeline
• it proves the crew was paying attention

If you simply wrote “rocky conditions,” the GC would challenge it.

This note is specific. Specific notes hold up.

2. The Actual Length Increased and the Log Explains Why

Planned: 300 ft Actual: 312 ft

Extra footage is a red flag to a GC unless it’s documented.

Here, the extra footage makes sense because:

• the rock seam forced a slight alignment adjustment
• steering corrections added distance
• maintaining depth and clearance required a longer path

The log ties the footage to the conditions. That’s what makes it defensible.

3. The Timeline Matches the Conditions

Start: 9:30 AM End: 12:15 PM

A 312‑ft shot taking 2 hours and 45 minutes is completely reasonable in mixed clay/rock.

If the log didn’t mention the rock seam, the GC would assume:

• the crew slowed down
• the crew wasn’t efficient
• the hours are inflated

But with the condition change documented, the timeline becomes logical.

4. The Issue Is Logged Clearly and Directly

“Issues: Slowed drilling due to rock.”

Short. Accurate. Field‑credible.

This tells the GC:

• the slowdown had a cause
• the cause was geological
• the crew didn’t create the delay
• the production rate reflects the ground, not the crew

This is exactly how issues should be logged.

5. The Notes Explain the Crew’s Response

“Steering adjustments made after rock encounter.”

This note shows:

• the crew recognized the change
• the crew adjusted the head
• the crew maintained the alignment
• the crew stayed in control

GCs want to see that the crew responded appropriately, not blindly drilled through it.

This note proves that.

What This Example Really Shows

This example demonstrates the difference between:

• a bore log that protects your production, and
• a bore log that forces you to defend your production

A rock seam is not a problem, it’s a condition. But if it’s not documented, it becomes a problem later.

This entry:

• explains the slowdown
• explains the extra footage
• explains the steering corrections
• explains the timeline
• explains the production rate

Everything ties together.

This is what a strong bore log looks like.

How Boreva Handles This Shot in the Field

With Boreva, this entry is captured:

• the moment the rock seam is hit
• with the exact footage
• with the condition change logged immediately
• with the steering adjustments noted
• with timestamps that match the slowdown

The system removes:

• end‑of‑day guessing
• vague notes
• missing condition changes
• unexplained production swings

The log becomes a real‑time record, not a reconstruction.

Example 3: Utility Conflict and Delay

Scenario

This is the shot that separates disciplined logging from “we’ll remember it later.”

The crew is drilling through mixed soil, nothing unusual. Production is steady. Steering is controlled. Everything is on track.

Then at 180 ft, the locator picks up something that wasn’t on the prints:

• an unmarked utility
• shallow
• directly in the planned path
• requiring immediate action

This is a real HDD moment:

• drilling stops
• the crew potholes
• the inspector gets involved
• the alignment must be adjusted
• the delay grows
• the timeline shifts

If this isn’t logged correctly, the GC will absolutely challenge the hours.

This is where a bore log either protects your invoice — or destroys it.

Bore Log Entry

• Shot: 3
• Entry: STA 6+00
• Exit: STA 9+00
• Planned Length: 300 ft
• Actual Length: 287 ft
• Depth: 60 in
• Ground: Mixed soil
• Start: 1:00 PM
• End: 4:30 PM
• Issues: Utility conflict at 180 ft, 1.5‑hour delay
• Notes: Path adjusted to maintain clearance

Why This Entry Works

This is one of the strongest examples in the entire article because it shows how to document a delay in a way that cannot be disputed.

Let’s break down why this entry is airtight.

1. The Utility Conflict Is Logged at the Exact Footage

“Utility conflict at 180 ft.”

This is the difference between:

• a believable delay
• and a questionable delay

This single detail proves:

• the crew identified the conflict precisely
• the conflict occurred mid‑shot
• the delay had a real cause
• the crew was paying attention
• the log wasn’t filled out later

GCs trust specifics. They attack generalities.

This is specific.

2. The Delay Is Quantified, Not Estimated

“1.5‑hour delay.”

Not:

• “about an hour”
• “roughly 90 minutes”
• “some delay”

A quantified delay shows:

• the crew tracked the time
• the delay was real
• the delay was significant
• the delay was not padded

This is exactly how delay documentation should look.

3. The Actual Length Is Shorter And the Log Explains Why

Planned: 300 ft Actual: 287 ft

Shorter footage is just as important to document as longer footage.

Why?

Because it shows:

• the alignment was adjusted
• the exit point shifted
• the crew maintained clearance
• the path changed due to the utility

If the footage changed and the log didn’t explain it, the GC would assume:

• the crew mis‑drilled
• the footage is inaccurate
• the log is unreliable

This entry removes all doubt.

4. The Timeline Matches the Delay

Start: 1:00 PM End: 4:30 PM

A 287‑ft shot taking 3.5 hours is completely reasonable with:

• a utility conflict
• potholing
• inspector involvement
• alignment adjustments

The timeline aligns perfectly with the documented delay.

This is what makes the entry defensible.

5. The Notes Explain the Crew’s Response

“Path adjusted to maintain clearance.”

This note shows:

• the crew made the correct decision
• the crew followed safety and clearance requirements
• the crew didn’t force the alignment
• the crew maintained control
• the crew acted professionally

GCs want to see that the crew responded appropriately — not recklessly.

This note proves that.

What This Example Really Shows

This example demonstrates the core purpose of a bore log:

To explain why the day unfolded the way it did.

A utility conflict is not a mistake. A utility conflict is not a crew problem. A utility conflict is not a production failure.

A utility conflict is a condition.

But if it’s not documented:

• the GC will deny the delay
• the GC will question the hours
• the GC will challenge the footage
• the GC will reduce the invoice

This entry eliminates all of that.

It ties:

• the delay
• the footage
• the timeline
• the adjustment
• the conditions

…into one clean, defensible record.

This is exactly how a bore log protects your money.

How Boreva Handles This Shot in the Field

With Boreva, this entry is captured:

• the moment the utility is detected
• with the exact footage
• with the delay timer running automatically
• with the condition change logged immediately
• with notes added in real time
• with timestamps that match the slowdown

The system removes:

• forgotten delays
• vague descriptions
• missing footage changes
• end‑of‑day reconstruction
• “we think it was around an hour”

The log becomes a real‑time record, not a memory exercise.

This is the difference between:

• a delay the GC denies
• and a delay the GC pays

Example 4: Wet Conditions and Steering Difficulty

Scenario

This shot starts like a normal clay shot, predictable, steady, and easy to control. But as the crew progresses, the ground moisture increases. The clay becomes slick. The head starts to skate. Steering corrections become more frequent. Penetration rate drops. The bore path becomes harder to hold.

This is a classic HDD scenario where:

• the ground doesn’t change type
• the ground changes behavior

And if the log doesn’t capture that shift, the GC will assume the crew simply slowed down.

Moisture is invisible to the inspector unless you document it.

Bore Log Entry

• Shot: 4
• Entry: STA 9+00
• Exit: STA 12+00
• Planned Length: 300 ft
• Actual Length: 305 ft
• Depth: 50 in
• Ground: Wet clay
• Start: 8:00 AM
• End: 11:45 AM
• Issues: Steering difficulty due to wet conditions
• Notes: Slower advancement, additional corrections required

Why This Entry Works

This is exactly how to document moisture‑related production changes in a way that holds up under review.

Let’s break down why this entry is strong.

1. “Wet Clay” Is a Real Condition, Not a Throwaway Note

Most crews write:

• “Wet ground”
• “Moist soil”
• “Soft conditions”

Those notes mean nothing to a GC.

“Wet clay” is specific and meaningful because:

• wet clay behaves differently than dry clay
• steering becomes harder
• the head slides instead of biting
• corrections increase
• production slows
• the bore path becomes more sensitive

This note tells the GC exactly what changed.

2. The Timeline Reflects the Conditions

Start: 8:00 AM End: 11:45 AM

A 305‑ft shot taking 3 hours and 45 minutes is completely reasonable in wet clay.

Without the moisture note, the GC sees:

• long shot
• slow production
• no documented reason

That’s when they start asking questions.

With the moisture note, the timeline makes sense.

3. The Actual Length Increased and the Log Explains Why

Planned: 300 ft Actual: 305 ft

Wet clay often forces:

• micro‑corrections
• slight path adjustments
• small deviations to maintain depth
• additional steering inputs

Those adjustments add footage.

If the log didn’t explain the moisture and steering difficulty, the GC would assume:

• the crew drifted
• the footage is inaccurate
• the log is unreliable

This entry ties the footage to the conditions.

4. The Issue Is Logged Clearly and Directly

“Issues: Steering difficulty due to wet conditions.”

This is exactly how an issue should be documented:

• cause
• effect
• impact

It shows:

• the crew identified the problem
• the problem was environmental
• the slowdown was justified
• the production rate reflects the ground, not the crew

GCs trust logs that show cause‑and‑effect.

5. The Notes Explain the Crew’s Response

“Slower advancement, additional corrections required.”

This note shows:

• the crew stayed in control
• the crew adjusted their drilling approach
• the crew maintained the alignment
• the crew didn’t force the head
• the crew worked safely

GCs want to see that the crew responded appropriately — not recklessly.

This note proves that.

What This Example Really Shows

This example demonstrates how to document behavioral ground changes, not just material changes.

Wet clay is still clay, but it drills completely differently.

This entry:

• explains the slower production
• explains the extra footage
• explains the steering corrections
• explains the timeline
• explains the conditions

Everything ties together.

This is what a strong bore log looks like.

How Boreva Handles This Shot in the Field

With Boreva, this entry is captured:

• the moment the steering difficulty starts
• with the correct ground condition selected
• with the slowdown timestamped
• with notes added immediately
• with footage tied to the shot in real time

The system removes:

• vague “wet ground” notes
• forgotten steering issues
• unexplained production swings
• end‑of‑day reconstruction

The log becomes a real‑time record, not a memory exercise.

This is the difference between:

• a moisture‑related slowdown the GC denies
• and a moisture‑related slowdown the GC accept

Example 5: Poor Logging vs Proper Logging

This is the most important example in the entire article because it shows the truth:

Most bore logs don’t fail because the job was complicated. They fail because the logging was weak.

Two crews can drill the same shot. One produces a log that protects their invoice. The other produces a log that gets questioned, reduced, or denied.

This example shows exactly why.

🔴 Weak Entry

“Drilled 300 ft. Slow conditions.”

This is the kind of entry that gets contractors in trouble.

Here’s why it fails:

1. No Shot Number

The GC can’t tie it to the alignment.

2. No Entry/Exit Stations

There’s no location reference.

3. No Actual Footage

“300 ft” is a rounded guess, not a measurement.

4. No Ground Conditions

The GC has no idea what the crew drilled through.

5. No Depth

Depth is critical for clearance, safety, and production.

6. No Timeline

Without start/end times, the GC will challenge the hours.

7. No Issue Description

“Slow conditions” is meaningless. Slow compared to what? Why slow? What caused it?

8. No Notes

Nothing explains the situation.

This entry forces the GC to fill in the blanks — and they will always fill them in against the contractor.

This is how disputes start.

Strong Entry

• Shot: 5
• Entry: STA 12+00
• Exit: STA 15+00
• Actual Length: 296 ft
• Ground: Mixed clay and sand
• Issues: Steering drift at 200 ft, corrected
• Notes: Additional time required to maintain path

This is the exact same shot — but documented correctly.

Let’s break down why this entry is bulletproof.

Why This Entry Works

1. Exact Footage (296 ft)

Not rounded. Not estimated. Not “about 300.”

Exact footage shows:

• rods were counted
• the crew tracked the shot
• the log reflects reality

GCs trust exact numbers.

2. Entry and Exit Stations

STA 12+00 → STA 15+00

This ties the shot to:

• the alignment
• the plan
• the as‑built
• the inspector’s notes

It proves the crew drilled where they were supposed to.

3. Ground Conditions Are Specific

“Mixed clay and sand.”

This matters because:

• mixed ground causes drift
• drift requires corrections
• corrections slow production

The GC now understands the environment.

4. The Issue Is Documented Clearly

“Steering drift at 200 ft, corrected.”

This shows:

• the crew identified the problem
• the problem had a specific cause
• the crew corrected it
• the alignment was maintained

This is exactly what a GC wants to see.

5. Notes Explain the Impact

“Additional time required to maintain path.”

This ties everything together:

• the drift
• the corrections
• the slower production
• the timeline

The GC now understands why the shot took longer.

What This Example Really Shows

This example proves a simple truth:

Weak logs create questions. Strong logs answer them.

A weak log forces the GC to:

• guess
• assume
• challenge
• reduce
• deny

A strong log:

• explains the conditions
• explains the problems
• explains the corrections
• explains the timeline
• explains the footage

A strong log removes the GC’s leverage.

This is the difference between:

• a contractor who gets paid
• and a contractor who gets picked apart

How Boreva Handles This Shot in the Field

With Boreva, the strong entry becomes the default because the system:

• forces exact footage
• forces shot‑by‑shot entries
• forces condition selection
• forces issue documentation
• timestamps everything
• ties notes to the moment they happen

The weak entry becomes impossible.

The strong entry becomes automatic.

This is how Boreva eliminates disputes before they start.

What All Strong Bore Logs Have in Common

Every strong bore log — no matter the job, the ground, the crew, or the conditions — follows the same structure.

It doesn’t matter whether the shot is:

• clean
• messy
• long
• short
• in clay
• in sand
• in rock
• in mixed ground
• in wet conditions
• in congested utilities

The pattern is identical.

Weak contractors think bore logs are “notes.” Strong contractors know bore logs are records.

Here’s what every strong bore log has in common.

1. Each Shot Is Logged Separately

A weak log lumps the entire day into one line:

“Drilled 900 ft today.”

That’s not a bore log. That’s a summary.

A strong bore log breaks the day into:

• Shot 1
• Shot 2
• Shot 3
• Shot 4
• etc.

Each shot has:

• its own conditions
• its own problems
• its own timeline
• its own footage
• its own notes

This is how you show the GC exactly what happened — and when.

2. Footage Is Exact, Never Rounded

Weak logs use:

• “300 ft”
• “~300 ft”
• “about 300 ft”

Rounded numbers scream:

• guessing
• memory
• end‑of‑day reconstruction

Strong logs use:

• 298 ft
• 312 ft
• 287 ft
• 296 ft

Exact footage shows:

• rods were counted
• the crew tracked the shot
• the log reflects reality

GCs trust exact numbers. They attack rounded ones.

3. Conditions Are Clear and Specific

Weak logs say:

• “hard ground”
• “wet”
• “slow drilling”

These notes mean nothing.

Strong logs say:

• “Clay transitioning to rock at 140 ft.”
• “Wet clay causing steering drift.”
• “Mixed soil with sand pockets.”

These notes:

• explain production
• explain delays
• explain corrections
• explain footage changes

Conditions are the why behind the numbers.

4. Problems Are Recorded When They Happen

Weak logs say:

• “some delays”
• “equipment issues”
• “slow conditions”

These notes are useless.

Strong logs say:

• “Utility conflict at 180 ft — 1.5‑hour delay.”
• “Steering drift at 200 ft — corrected.”
• “Rock seam encountered — slowed penetration rate.”

These notes:

• document the cause
• document the impact
• document the timeline

Problems don’t hurt you. Undocumented problems hurt you.

5. Notes Explain the Situation, Not Just the Result

Weak logs say:

• “slow shot”
• “tough ground”
• “took longer than expected”

Strong logs say:

• “Additional corrections required due to wet clay.”
• “Alignment adjusted to maintain clearance.”
• “Steering adjustments made after rock encounter.”

Notes are where the GC learns:

• what happened
• why it happened
• how the crew responded

Notes turn numbers into a story — and stories are defensible.

Why This Pattern Matters

This pattern is what makes a bore log:

• credible
• consistent
• defensible
• professional
• impossible to argue with

GCs don’t reduce strong logs. They reduce weak ones.

A strong bore log:

• explains the day
• protects the hours
• justifies the footage
• documents the conditions
• records the problems
• shows the corrections
• ties everything together

This is how contractors stop losing money on paperwork.

How Boreva Enforces This Pattern Automatically

With Boreva, this pattern becomes the default because the system:

• forces shot‑by‑shot entries
• forces exact footage
• forces condition selection
• forces issue documentation
• timestamps everything
• ties notes to the moment they happen

Weak logs become impossible. Strong logs become automatic.

This is how Boreva eliminates disputes before they start.

What This Looks Like in the Field

Everything in the examples above has one thing in common:

They only work if they’re logged when the work happens.

A bore log is not a form. A bore log is not paperwork. A bore log is not something you “fill out later.”

A bore log is a real‑time record of the shot.

And that’s exactly how Boreva is built, not as a template, but as a field system that captures the job as it unfolds.

Here’s what these examples look like when they’re actually happening in the field.

1. Shots Are Logged the Moment They Finish

In the field, the driller or locator doesn’t wait until the end of the day.

The moment a shot is completed:

• the footage is entered
• the conditions are selected
• the notes are added
• the timestamp is captured automatically

This eliminates:

• rounded numbers
• forgotten details
• mismatched footage
• “we’ll fill it out later” errors

The bore log becomes a live record, not a reconstruction.

2. Condition Changes Are Captured When They Happen

When the ground shifts:

• clay → rock
• dry → wet
• sand pockets appear
• steering becomes harder
• penetration rate changes

The crew logs it immediately.

This is critical because:

• conditions explain production
• conditions explain delays
• conditions explain footage changes
• conditions explain steering corrections

If you wait until the end of the day, these details disappear.

Boreva forces the crew to capture them in the moment.

3. Problems and Delays Are Logged With Timestamps

This is where most contractors lose money.

Delays get forgotten. Problems get summarized. Timelines get rounded. GCs challenge everything.

With Boreva, when a problem occurs:

• the crew taps “Add Issue”
• the delay timer starts
• the description is added
• the timestamp is locked
• the duration is calculated automatically

This turns:

• “We had a delay” into
• “Utility conflict at 180 ft — 1.5‑hour delay.”

GCs don’t argue with timestamps.

4. Notes Are Added During the Work, Not After

Notes are where the context lives.

In the field, notes get added:

• when the inspector says something
• when the customer gives direction
• when the alignment changes
• when the ground shifts
• when the crew makes a correction

These notes explain:

• why the shot took longer
• why the footage changed
• why the production slowed
• why the alignment shifted

Boreva ties each note to:

• the shot
• the time
• the conditions
• the issue

This is what makes the log defensible.

5. The Daily Report Builds Itself Automatically

By the time the crew clocks out:

• every shot is logged
• every condition is documented
• every delay is timestamped
• every note is tied to the moment it happened
• every issue is recorded
• every timeline is accurate

The daily report is already complete.

There is no:

• rewriting
• guessing
• reconstructing
• filling in blanks
• “what time did that happen?”
• “how long were we down?”

The report is built from real‑time field entries, not memory.

This is the difference between:

• a report the GC questions
• and a report the GC accepts

Why This Matters

The examples in this article are strong because they follow the rules of real‑time logging.

Boreva makes those rules automatic.

It turns:

• clean shots
• messy shots
• rock encounters
• utility conflicts
• wet conditions
• steering drift
• delays
• corrections

…into structured, timestamped, defensible entries.

This is what real HDD documentation looks like.

This is what protects your hours. This is what protects your footage. This is what protects your invoice.