Boreva | Directional Drilling App for Bore Logs, Daily Reports, and Job Tracking

Everything That Happened. In One Place

Tag: field reporting

  • Bore Log Examples From Real Jobs (Directional Drilling Field Scenarios)

    Bore Log Examples From Real Jobs (Directional Drilling Field Scenarios)

    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.

  • Construction Daily Report Template

    Construction Daily Report Template

    A daily report is supposed to show what actually happened on the job, not what someone remembers at the end of the day.

    Most templates fail for one simple reason:

    They get filled out after the work is done.

    And once that happens, the report stops being a record and becomes a reconstruction.

    That’s where everything starts breaking:

    • Details get missed
    • Problems get forgotten
    • Numbers get rounded
    • Times get estimated
    • Conditions get generalized
    • Notes get vague

    Now the daily report isn’t a defense document. It’s a summary based on memory.

    And memory is the weakest form of documentation you can bring into a dispute.

    This is exactly why HDD contractors get burned:

    • The bore log says one thing
    • The daily report says another
    • The inspector’s notes say something else
    • The GC chooses the version that benefits them

    A daily report only protects you when it is built during the work, not after it.

    That’s the shift Boreva was designed to create.

    Boreva HDD logging, profit, and prevention app for crews
    Boreva Dashboard

    Instead of trying to remember the day, the system captures the day as it happens, shot by shot, issue by issue, note by note.

    By the time the crew clocks out, the report already exists.

    Nothing needs to be reconstructed. Nothing needs to be guessed. Nothing needs to be “filled in later.”

    This is what a real field‑ready daily reporting system looks like.

    What a Construction Daily Report Needs to Capture

    A daily report only has one job:

    Show exactly what happened on the job today.

    Not what the foreman remembers. Not what the inspector thinks. Not what the GC assumes. Not what someone reconstructs at 5:30 PM in the truck.

    A real daily report is a record, not a recap.

    And for HDD, that record must capture the five things that determine production, delays, and billing:

    1. Work Completed

    This is the backbone of the report.

    It must show:

    • Bore shots completed
    • Footage installed
    • Areas worked
    • What was started
    • What was finished
    • What was partially completed

    If this section is vague, the GC will assume:

    • Your production was low
    • Your hours were high
    • Your footage is questionable

    This is why Boreva ties the daily report directly to the bore log.

    When a shot is logged in the field, it automatically feeds the daily report. No rewriting. No re‑entering. No forgetting.

    The work completed section becomes exact, not estimated.

    2. Crew and Equipment

    The GC wants to know:

    • Who was on site
    • What equipment was used
    • What equipment failed
    • What equipment slowed production

    This section protects:

    • Labor hours
    • Equipment hours
    • Standby time
    • Delay justification

    If a drill went down for 42 minutes, that must be documented when it happens, not guessed later.

    Boreva captures:

    • Crew on site
    • Equipment used
    • Equipment issues
    • Timestamps

    …so the daily report reflects the real day, not the remembered day.

    3. Conditions

    Conditions explain production.

    If the ground changes, the production changes. If access changes, the timeline changes. If traffic changes, the pace changes.

    Conditions must capture:

    • Ground conditions
    • Site access
    • Traffic or environment
    • Weather impacts
    • Utility congestion

    Without conditions, the GC assumes:

    • Your crew was slow
    • Your hours are inflated
    • Your footage is padded

    With conditions, your production makes sense.

    Boreva forces condition notes at the shot level, not as an afterthought.

    4. Delays and Problems

    This is the section that protects your hours.

    If something slows the job down, it must be logged:

    • Utility conflicts
    • Equipment downtime
    • Weather delays
    • Waiting on approvals
    • Missing locates
    • Inspector delays
    • Traffic control issues

    The GC will not accept:

    • “We had delays.”
    • “We lost time.”
    • “We had issues.”

    They want:

    • What happened
    • When it happened
    • How long it lasted
    • What caused it
    • What the crew did

    Boreva logs delays with:

    • Timestamps
    • Descriptions
    • Photos (if needed)
    • Automatic placement in the daily report

    This is what protects you later.

    Directional drilling bore entry in Boreva app
    Real-time bore log entry showing shot details, footage, conditions, and notes

    5. Notes

    Notes are where the context lives.

    This is where you capture:

    • Inspector conversations
    • Customer interactions
    • Scope changes
    • Verbal approvals
    • Safety issues
    • Unexpected events

    Notes are the difference between:

    “Why did this happen?” and “Oh, that makes sense.”

    Boreva lets crews add notes in real time, not at the end of the day when details are fuzzy.

    Construction Daily Report Template

    Most daily report templates are built for the office. This one is built for the field.

    A real HDD daily report must follow the flow of the work, not the flow of a spreadsheet. It needs to match how drilling actually happens:

    • Crews arrive
    • Equipment gets set
    • Shots get drilled
    • Problems occur
    • Conditions change
    • Notes get made
    • Work gets completed

    A good template mirrors that sequence.

    A great system captures that sequence automatically.

    This is the difference between a template you fill out and a system that builds the report for you.

    Below is the field‑proven layout, the structure that works on real HDD jobs, with real crews, under real pressure.

    And this is exactly the structure Boreva is built around.

    1. Job Information

    This section sets the context for the day.

    It must include:

    • Job name
    • Location
    • Date
    • Weather

    Weather matters because it affects:

    • Ground conditions
    • Production rate
    • Access
    • Safety
    • Delays

    Boreva captures weather automatically, so crews don’t have to guess or skip it.

    2. Crew and Equipment

    This section protects your labor and equipment hours.

    It must show:

    • Crew members on site
    • Equipment used
    • Equipment issues

    If a drill goes down, if a vac truck fails, if a locator stops working, it must be documented.

    This is where most contractors lose money:

    • Equipment downtime isn’t logged
    • Crew changes aren’t recorded
    • Standby time isn’t documented

    Boreva logs:

    • Who was on site
    • What equipment was used
    • What equipment failed
    • When it failed
    • How long it affected production

    This is what makes your hours defensible.

    3. Work Completed

    This is the heart of the daily report.

    It must show:

    • Bore shots completed
    • Footage installed
    • Areas worked

    And here’s the critical part:

    This section must match your bore log exactly.

    If the bore log says 742 ft and the daily report says 800 ft, the GC will assume:

    • Your documentation is inconsistent
    • Your footage is inflated
    • Your hours are questionable

    Boreva eliminates this problem by pulling footage directly from the bore log entries made in the field.

    No rewriting. No re‑entering. No mismatches.

    The daily report becomes a reflection of the bore log, not a separate document.

    4. Conditions

    Conditions explain production.

    They must capture:

    • Ground conditions
    • Site access
    • Traffic or environment

    If production slows, conditions must explain why.

    If the path changes, conditions must explain why.

    If the timeline shifts, conditions must explain why.

    Boreva forces condition notes at the shot level, so the daily report always has the context needed to defend your production.

    5. Delays and Problems

    This section protects your hours and your schedule.

    It must include:

    • Utility conflicts
    • Equipment downtime
    • Weather delays
    • Waiting on approvals
    • Missing locates
    • Inspector delays

    If it slows the job down, it goes here.

    And it must be logged when it happens, not after.

    Boreva logs delays with:

    • Timestamps
    • Descriptions
    • Photos (optional)
    • Automatic placement in the daily report

    This is what protects you when the GC asks:

    “Why did this take so long?”

    6. Notes

    Notes are where the story of the day lives.

    They capture:

    • Inspector conversations
    • Customer interactions
    • Scope changes
    • Verbal approvals
    • Safety issues
    • Unexpected events

    These notes often become the deciding factor in a dispute.

    Boreva lets crews add notes instantly, not at the end of the day when details are fuzzy.

    Construction daily report summary generate from field data
    Daily report automatically generated from real time field entries

    Why This Layout Works

    This layout works because it follows the natural flow of HDD work.

    It doesn’t force the crew to think like office staff. It lets them document the day the same way they live it.

    And Boreva takes it one step further:

    • The bore log feeds the daily report
    • The delay log feeds the daily report
    • The notes feed the daily report
    • The equipment log feeds the daily report

    By the time the crew clocks out, the daily report is already built.

    No reconstruction. No guessing. No gaps.

    Just a clean, defensible record of the day.

    Job Information

    Job information seems basic, almost too basic to matter.

    But this is the section that:

    • anchors the report
    • ties it to the correct job
    • establishes the conditions
    • sets the context for production
    • protects you when the GC compares days

    When job information is wrong, missing, or inconsistent, the GC immediately questions the rest of the report.

    This is why the first section of a daily report must be clean, accurate, and consistent every single day.

    Here’s what it needs to capture and why Boreva makes this effortless.

    1. Job Name

    This is the identifier that ties the report to the correct project.

    If the job name is wrong or inconsistent:

    • reports get mixed
    • quantities get misapplied
    • delays get questioned
    • production gets misaligned

    Crews often abbreviate or shorten job names differently each day:

    • “AT&T 12th St”
    • “ATT 12th”
    • “12th St AT&T”

    GCs hate this because it creates ambiguity.

    Boreva eliminates this by pulling the job name directly from the project setup. Crews don’t type it. They select it.

    No variations. No mistakes. No confusion.

    2. Location

    Location matters because:

    • inspectors change by location
    • conditions change by location
    • access changes by location
    • utilities change by location
    • production changes by location

    If the GC asks:

    “Where exactly was the crew working on this day?”

    Your daily report must answer that instantly.

    Boreva logs the location automatically based on the job and the shot entries. The daily report always reflects the correct work area.

    3. Date

    This seems obvious, until it isn’t.

    Crews sometimes:

    • forget to change the date
    • reuse yesterday’s template
    • enter the wrong day
    • fill out the report the next morning

    When the date is wrong, the GC assumes:

    • the report wasn’t filled out in real time
    • the details may not be accurate
    • the hours may not match the work
    • the footage may not match the day

    Boreva timestamps every entry automatically. The date is never wrong because the system records the day as the work happens.

    4. Weather

    Weather is not a filler field. It’s a production field.

    Weather affects:

    • ground conditions
    • drilling speed
    • mud performance
    • access
    • safety
    • downtime

    If production slows and the weather section is blank, the GC assumes:

    • the slowdown was the crew
    • not the conditions

    If weather is logged accurately, the GC sees:

    • rain
    • mud
    • freezing temps
    • wind
    • heat
    • lightning delays

    Boreva pulls weather automatically based on the job location and timestamp.

    No guessing. No skipping. No “sunny” written on a day it rained.

    Why This Section Matters More Than People Think

    Job information is the foundation of the daily report.

    If this section is sloppy:

    • the GC questions the entire report
    • the report looks like it was filled out later
    • the report loses credibility
    • the report loses defensive value

    If this section is clean and consistent:

    • the report looks professional
    • the GC trusts the documentation
    • the rest of the report carries more weight
    • your hours and footage become easier to defend

    Boreva ensures this section is always accurate because the system fills it in automatically as the day unfolds.

    The crew doesn’t have to think about it. The system handles it.

    Crew and Equipment

    If the GC is going to challenge your hours, this is the section they use to do it.

    Most contractors think the “Crew & Equipment” section is just a roll call. It’s not.

    It’s the section that:

    • justifies your labor hours
    • justifies your equipment hours
    • explains your production
    • explains your delays
    • protects your standby time
    • ties your costs to the work performed

    If this section is incomplete or inaccurate, the GC immediately questions:

    • your hours
    • your production
    • your delays
    • your invoice

    This is why the Crew & Equipment section must be clean, exact, and captured in real time, not reconstructed at the end of the day.

    Here’s what it needs to include, and how Boreva makes it bulletproof.

    1. Crew Members on Site

    This is not just a list of names. It’s the foundation of your labor hours.

    It must show:

    • who was on site
    • when they were on site
    • what role they performed
    • when they left
    • any crew changes

    If the GC sees:

    • a 4‑man crew listed
    • but only 3 people in the inspector’s notes

    …they assume your hours are inflated.

    If the GC sees:

    • a locator listed
    • but no locating activity documented

    …they assume your labor is padded.

    Boreva eliminates this by letting crews:

    • check in
    • check out
    • log roles
    • track changes

    …all from the field.

    The daily report reflects the actual crew, not the remembered crew.

    2. Equipment Used

    Boreva equipment list that reflects daily cost, usage, hours, and whose operating it
    Boreva Equipment List

    Equipment hours are money.

    If equipment is on site, the GC wants to know:

    • what equipment
    • when it was used
    • how it was used
    • whether it was productive
    • whether it was down
    • whether it was on standby

    This protects:

    • drill hours
    • vac truck hours
    • locator hours
    • support equipment hours

    If equipment is listed but not tied to the work, the GC questions the hours.

    Boreva ties equipment usage directly to:

    • bore shots
    • delays
    • notes
    • timestamps

    The equipment section becomes a record, not a guess.

    3. Equipment Issues

    This is where most contractors lose money.

    If equipment goes down and it isn’t documented:

    • the GC will not pay standby
    • the GC will not accept delays
    • the GC will not justify lost production

    Equipment issues must capture:

    • what failed
    • when it failed
    • how long it was down
    • what caused it
    • what the crew did
    • how it affected production

    Examples:

    • “Locator battery failure — 14 minutes downtime”
    • “Drill head packed with clay — 22 minutes to clear”
    • “Vac truck hose split — 38 minutes repair”

    If this isn’t logged in real time, it becomes:

    • “We had some downtime.”
    • “The drill was acting up.”
    • “We lost about an hour.”

    GCs don’t pay for vague.

    Boreva logs equipment issues with:

    • timestamps
    • descriptions
    • optional photos
    • automatic placement in the daily report

    This is what makes your downtime defensible.

    Work Completed

    This is the section the GC looks at first.

    It’s the section they compare against:

    • their inspector’s notes
    • their expectations
    • the schedule
    • the bore log
    • the as‑built
    • your hours

    If this section is vague, incomplete, or inconsistent, the GC immediately questions:

    • your footage
    • your production
    • your hours
    • your delays
    • your invoice

    This is why the “Work Completed” section must be exact, not estimated and it must match your bore log perfectly.

    Here’s what it needs to capture, and how Boreva makes it airtight.

    1. Bore Shots Completed

    This is the backbone of HDD production.

    It must show:

    • each shot completed
    • the order they were drilled
    • the footage for each shot
    • the area or alignment
    • any partial shots

    If the GC sees:

    • 3 shots in the daily report
    • but 4 shots in the bore log

    …they assume your documentation is unreliable.

    If the GC sees:

    • a 310‑ft shot
    • but the inspector wrote 280 ft

    …they assume your footage is inflated.

    Boreva eliminates this by pulling shot data directly from the bore log entries made in the field.

    When a shot is logged:

    • the footage
    • the conditions
    • the notes
    • the timestamps

    …all flow into the daily report automatically.

    No rewriting. No re‑entering. No mismatches.

    2. Footage Installed

    This is the number that gets challenged the most.

    Footage must be:

    • exact
    • traceable
    • tied to shots
    • tied to rig readings
    • tied to rod count
    • tied to the as‑built

    If the daily report says:

    • 742 ft installed

    …but the bore log says:

    • 700 ft drilled

    …the GC will reduce your quantity to the lowest number.

    If the daily report says:

    • “About 800 ft”

    …you’ve already lost.

    Boreva removes the guesswork by:

    • pulling exact footage from the bore log
    • tying it to timestamps
    • tying it to the shot sequence
    • tying it to the rig readings

    The daily report becomes a mathematically defensible record, not a rounded estimate.

    3. Areas Worked

    This section shows:

    • where the crew worked
    • what alignment they were on
    • what segment was completed
    • what segment was started
    • what segment is next

    This matters because:

    • inspectors change by area
    • utilities change by area
    • conditions change by area
    • access changes by area
    • production changes by area

    If the GC asks:

    “Where exactly did the crew work today?”

    Your daily report must answer that instantly.

    Boreva ties each shot to a location, so the daily report always reflects the correct work area.

    Why This Section Must Match the Bore Log

    This is the #1 rule of HDD documentation:

    The daily report and the bore log must match exactly.

    If they don’t, the GC assumes:

    • the report was filled out later
    • the numbers were estimated
    • the footage is inflated
    • the hours are padded
    • the delays are questionable

    Boreva eliminates this risk by making the bore log the source of truth.

    The daily report is not a separate document. It is a reflection of the bore log.

    This is what makes your documentation defensible.

    Why Boreva Makes This Section Unbreakable

    Boreva turns “Work Completed” into a real‑time record by:

    • capturing shots as they happen
    • pulling footage directly from the field
    • tying everything to timestamps
    • aligning the daily report with the bore log
    • eliminating end‑of‑day reconstruction
    • removing human error
    • preventing mismatches

    By the time the crew clocks out, the “Work Completed” section is already finished and it’s accurate.

    No guessing. No rounding. No rewriting. No inconsistencies.

    Just a clean, defensible record of the day’s production.

    Conditions

    Conditions are the why behind your production.

    If the GC is going to challenge your footage, your hours, or your timeline, this is the section they look at to understand:

    • why production slowed
    • why the path changed
    • why the footage increased
    • why the timeline shifted
    • why the crew needed more time

    Most daily reports fail here because conditions get written at the end of the day and by then, the details are gone.

    Crews write things like:

    • “Hard ground”
    • “Bad access”
    • “Wet”
    • “Slow drilling”

    These notes don’t explain anything. They don’t defend anything. They don’t justify anything.

    Conditions must be specific, timed, and tied to the work.

    Here’s what this section needs to capture and how Boreva makes it automatic.

    1. Ground Conditions

    Ground conditions directly affect:

    • penetration rate
    • steering difficulty
    • tool wear
    • mud performance
    • production speed

    If the ground changes, the production changes.

    Examples of strong ground condition notes:

    • “Transition from clay to cobble at 110 ft — slowed penetration rate.”
    • “Wet sand pocket caused sloughing — required clearing.”
    • “Hardpan seam at 62 ft — reduced drilling speed.”

    Examples of weak notes:

    • “Hard ground.”
    • “Slow drilling.”

    Weak notes look like excuses. Strong notes look like documentation.

    Boreva forces condition notes at the shot level, so the daily report always reflects the real conditions that shaped the day.

    2. Site Access

    Access affects:

    • setup time
    • equipment movement
    • safety
    • production rate

    If access is restricted, production slows and the GC needs to see that.

    Examples:

    • “Traffic control delayed setup by 18 minutes.”
    • “Equipment staging limited, required additional repositioning.”
    • “Narrow easement slowed vac truck movement.”

    These details matter because they explain why the day unfolded the way it did.

    Boreva lets crews log access issues instantly, not hours later.

    3. Traffic or Environment

    Traffic and environmental factors can:

    • slow movement
    • delay setup
    • restrict equipment
    • impact safety
    • reduce production

    Examples:

    • “Heavy traffic on 4th St — slowed vac truck repositioning.”
    • “Pedestrian congestion required spotter — reduced drilling pace.”
    • “Wind gusts required slower rod handling.”

    These aren’t excuses, they’re conditions.

    And conditions explain production.

    Why Conditions Matter So Much

    Conditions are the bridge between:

    • the footage you drilled
    • the hours you logged
    • the production you achieved
    • the delays you recorded

    If conditions are vague, the GC assumes:

    • your crew was slow
    • your hours are inflated
    • your footage is padded
    • your delays are questionable

    If conditions are detailed, the GC sees:

    • the environment
    • the challenges
    • the adjustments
    • the impact

    This is what makes your daily report defensible.

    Why Boreva Makes This Section Bulletproof

    Boreva captures conditions:

    • at the shot level
    • in real time
    • tied to timestamps
    • tied to footage
    • tied to delays
    • tied to production

    This eliminates:

    • end‑of‑day guessing
    • vague notes
    • missing details
    • mismatched reports

    By the time the crew clocks out, the conditions section is already complete and it’s accurate.

    No reconstruction. No memory. No gaps.

    Just a clean, defensible record of the conditions that shaped the day.

    Delays and Problems

    If there is one section that protects your hours more than any other, it’s this one.

    Delays are the difference between:

    • getting paid for the time you spent
    • or eating the cost because the GC says “we don’t see it in your report”

    Most contractors lose delay disputes for one simple reason:

    Delays get logged at the end of the day.

    And when delays are logged at the end of the day:

    • times get rounded
    • durations get estimated
    • causes get simplified
    • details get forgotten
    • context gets lost
    • credibility disappears

    The GC doesn’t need to prove your delay didn’t happen. They only need to prove your documentation is weak.

    This is why the “Delays and Problems” section must be:

    • specific
    • timestamped
    • tied to the work
    • tied to the conditions
    • tied to the equipment
    • logged in real time

    Here’s what this section must capture and how Boreva makes it bulletproof.

    Logging jobsite issues and delays in real time
    Real time logging of delays with timestamps and descriptions

    1. Utility Conflicts

    Utility conflicts are one of the most common and most expensive, sources of delay.

    Examples:

    • “Unmarked gas service encountered at 42 ft — drilling paused 31 minutes.”
    • “Fiber line depth inconsistent — required potholing before continuing.”
    • “Unknown duct bank — alignment shifted 6 ft right.”

    If this isn’t logged when it happens, the GC will say:

    • “We didn’t see that.”
    • “Our inspector didn’t note it.”
    • “We can’t justify the delay.”

    Boreva logs utility conflicts with:

    • timestamps
    • descriptions
    • optional photos
    • automatic placement in the daily report

    This is what makes your utility delays defensible.

    2. Equipment Downtime

    Equipment downtime is money, but only if it’s documented.

    If the drill goes down for 42 minutes and it isn’t logged, the GC will not pay for it.

    Downtime must capture:

    • what failed
    • when it failed
    • how long it was down
    • what caused it
    • what the crew did
    • how it affected production

    Examples:

    • “Drill head packed with clay — 22 minutes to clear.”
    • “Vac truck hose split — 38 minutes repair.”
    • “Locator battery failure — 14 minutes downtime.”

    If this is logged at the end of the day, it becomes:

    • “We had some downtime.”
    • “The drill was acting up.”
    • “We lost about an hour.”

    GCs don’t pay for vague.

    Boreva logs downtime in real time with exact timestamps.

    3. Weather Delays

    Weather delays are legitimate, but only if they’re documented correctly.

    Examples:

    • “Lightning delay — 27 minutes.”
    • “Heavy rain — drilling paused 18 minutes.”
    • “Wind gusts required slower rod handling — reduced production.”

    If weather delays aren’t logged when they happen, the GC assumes:

    • the crew was slow
    • not the conditions

    Boreva automatically pulls weather data and ties it to the delay.

    4. Waiting on Approvals

    This is one of the most common and most disputed, delays.

    Examples:

    • “Waiting on inspector approval — 19 minutes.”
    • “Waiting on traffic control — 26 minutes.”
    • “Waiting on locate verification — 34 minutes.”

    If this isn’t logged in real time, the GC will say:

    • “We don’t see that delay.”
    • “Our inspector didn’t note it.”
    • “We can’t justify the time.”

    Boreva timestamps these delays automatically.

    5. Any Event That Slows the Job Down

    If it slows the job down, it belongs in this section.

    Examples:

    • mud pump issues
    • vac truck repositioning delays
    • traffic congestion
    • site access restrictions
    • safety stand‑downs
    • material delivery delays

    If it costs you time, it must be documented.

    If it isn’t documented, it didn’t happen, at least in the GC’s eyes.

    Why This Section Is the Most Important for Protecting Your Hours

    Delays are where contractors lose the most money.

    Not because the delays didn’t happen. Because the delays weren’t documented correctly.

    A delay that is:

    • vague
    • estimated
    • rounded
    • written later
    • missing timestamps
    • missing context

    …is a delay the GC will deny.

    A delay that is:

    • specific
    • timestamped
    • tied to the work
    • tied to the equipment
    • tied to the conditions
    • logged in real time

    …is a delay the GC cannot argue with.

    This is the difference between:

    • getting paid
    • or getting reduced

    Boreva makes this section unbreakable by capturing delays:

    • in real time
    • with timestamps
    • with descriptions
    • with optional photos
    • automatically inserted into the daily report

    By the time the crew clocks out, the delay log is already complete and it’s accurate.

    No reconstruction. No guessing. No gaps.

    Just a clean, defensible record of every delay that affected the day.

    Notes

    Notes are the most underrated part of a daily report.

    Most crews treat notes like an optional field, something they fill in if they remember, or if something “big” happened.

    But in HDD, notes are the difference between:

    • a report that explains the day
    • and a report that leaves the GC guessing

    Notes are where the context lives. Context is what makes your documentation defensible.

    Without notes, your report is just numbers. With notes, your report becomes a story the GC can follow and verify.

    Here’s what this section must capture, and how Boreva makes it effortless.

    1. Inspector Conversations

    This is one of the most important things to document.

    Inspectors:

    • give approvals
    • give instructions
    • change expectations
    • request adjustments
    • confirm footage
    • confirm alignment
    • confirm delays

    If you don’t document these conversations, the GC will default to the inspector’s version, not yours.

    Examples of strong notes:

    • “Inspector approved alignment shift at 10:42 AM.”
    • “Inspector confirmed depth at 162 ft mark.”
    • “Inspector requested pothole before continuing — 19‑minute delay.”

    These notes protect you when the GC asks:

    “Who told you to do that?”

    Boreva lets crews log these notes instantly, not hours later.

    2. Customer Interactions

    Customer interactions matter because they often:

    • change the plan
    • change the sequence
    • change the alignment
    • change the timeline

    Examples:

    • “Customer requested bore start moved 12 ft east.”
    • “Customer asked for additional pothole before continuing.”
    • “Customer approved extended working hours.”

    If you don’t document these, the GC will say:

    • “We didn’t authorize that.”
    • “We didn’t request that.”
    • “We didn’t approve that.”

    Boreva timestamps these notes so you always have proof.

    3. Scope Changes

    Scope changes are money, but only if they’re documented.

    Examples:

    • “Added second shot due to obstruction.”
    • “Extended bore path 48 ft to avoid duct bank.”
    • “Changed exit point per customer request.”

    If scope changes aren’t documented, the GC will say:

    • “That wasn’t part of the plan.”
    • “We didn’t approve additional footage.”

    Boreva makes scope changes easy to log in real time.

    4. Safety Issues

    Safety issues affect:

    • production
    • delays
    • crew movement
    • equipment use

    Examples:

    • “Safety stand‑down due to lightning — 27 minutes.”
    • “Spotter required due to pedestrian traffic.”
    • “Restricted access due to nearby excavation.”

    These notes explain why the day unfolded the way it did.

    5. Unexpected Events

    This is the catch‑all category for anything that doesn’t fit neatly into the other sections but still matters.

    Examples:

    • “City inspector arrived late — 14‑minute delay.”
    • “Traffic control arrived without proper signage — slowed setup.”
    • “Material delivery delayed — crew staged equipment.”

    These notes often become the deciding factor in a dispute.

    Why Notes Matter So Much

    Notes are the glue that holds the daily report together.

    They explain:

    • why production changed
    • why delays happened
    • why decisions were made
    • why the timeline shifted
    • why the footage is what it is

    Without notes, the GC fills in the blanks with their own assumptions.

    With notes, the GC sees the full picture.

    Why Boreva Makes Notes Unbreakable

    Boreva captures notes:

    • in real time
    • tied to shots
    • tied to delays
    • tied to conditions
    • tied to timestamps
    • tied to the daily report

    This eliminates:

    • forgotten details
    • vague summaries
    • end‑of‑day guessing
    • missing context
    • mismatched reports

    By the time the crew clocks out, the notes section is already complete and it’s accurate.

    No reconstruction. No memory gaps. No “I think this happened around noon.”

    Just a clean, defensible record of the day’s context.

    Why Most Daily Reports Fail

    Most daily reports don’t fail because the crew doesn’t care. They fail because the process is broken.

    The traditional daily report depends on one thing:

    Memory.

    And memory is the weakest, most unreliable, most inconsistent documentation method you can bring into a construction dispute.

    Here’s the truth:

    Crews don’t forget because they’re lazy. They forget because the job moves fast.

    • Shots get drilled
    • Conditions change
    • Problems happen
    • Equipment fails
    • Inspectors show up
    • Customers call
    • Traffic shifts
    • Utilities surprise you

    By the time the crew sits down to fill out the daily report, the details are already fading.

    This is why most daily reports fail and why they can’t defend anything when the GC starts asking questions.

    Let’s break down the real reasons.

    1. They’re Filled Out at the End of the Day

    This is the #1 failure.

    End‑of‑day reporting creates:

    • rounded numbers
    • vague notes
    • missing delays
    • incorrect times
    • mismatched footage
    • forgotten conversations
    • incomplete conditions

    The GC can spot an end‑of‑day report instantly.

    It looks like a summary, not a record.

    Boreva eliminates this by building the report during the work, not after.

    2. Details Get Missed Because the Day Moves Too Fast

    A foreman juggling:

    • drilling
    • locating
    • traffic
    • inspectors
    • customers
    • equipment
    • safety
    • crew questions

    …is not going to remember:

    • the exact time a delay started
    • the exact moment conditions changed
    • the exact footage at each shot
    • the exact conversation with the inspector

    It’s not realistic.

    Boreva captures these details in real time, so nothing depends on memory.

    3. Problems Get Forgotten Because They Don’t Seem Big at the Time

    Most delays don’t feel like delays when they happen.

    Examples:

    • clearing a packed drill head
    • swapping locator batteries
    • waiting for a vac truck to reposition
    • potholing an unexpected utility
    • waiting for an inspector to walk over

    Each one feels small.

    But add them up and you’ve lost:

    • 30 minutes
    • 45 minutes
    • an hour
    • more

    If these aren’t logged, the GC will say:

    “We don’t see any delays in your report.”

    Boreva logs delays with timestamps the moment they occur.

    4. Numbers Get Rounded Because Exact Numbers Aren’t Written Down

    When crews fill out reports later, they write:

    • “About 300 ft”
    • “Roughly 800 ft today”
    • “Around 4 hours drilling”

    Rounded numbers destroy credibility.

    GCs assume:

    • the report wasn’t filled out in real time
    • the footage is inflated
    • the hours are padded

    Boreva pulls exact numbers from the bore log and rig readings — no rounding, no guessing.

    5. Daily Reports Don’t Match the Bore Log

    This is the GC’s favorite leverage point.

    If the bore log says:

    • 742 ft

    …but the daily report says:

    • 800 ft

    …the GC will reduce your quantity to the lowest number.

    If the bore log says:

    • 3 shots

    …but the daily report says:

    • 2 shots

    …the GC will question your documentation.

    Boreva eliminates this because the bore log feeds the daily report automatically.

    No mismatches. No inconsistencies. No leverage for the GC.

    6. Notes Are Added Later and Lose Their Meaning

    Notes written at the end of the day become:

    • vague
    • generic
    • incomplete
    • inaccurate

    Examples of weak notes:

    • “Talked to inspector.”
    • “Had some issues.”
    • “Slow drilling.”

    These notes don’t defend anything.

    Boreva captures notes in real time, tied to:

    • shots
    • delays
    • conditions
    • timestamps

    Now the notes actually explain the day.

    7. The Report Doesn’t Tell a Story

    A daily report must tell a clear, traceable story:

    • what happened
    • when it happened
    • why it happened
    • how it affected production

    Most reports don’t tell a story. They list numbers.

    Numbers without context are easy to challenge.

    Boreva builds the story automatically because it captures the day as it unfolds.

    What Real Daily Reporting Looks Like in the Field

    Daily reporting fails when it’s treated like paperwork.

    Daily reporting works when it’s treated like part of the work.

    The job doesn’t happen at the end of the day. It happens throughout the day, minute by minute, shot by shot, problem by problem.

    A daily report should be built the same way.

    Real daily reporting is not:

    • sitting in the truck at 5:30 PM
    • trying to remember what happened
    • guessing at times
    • rounding footage
    • summarizing problems
    • filling in blanks

    Real daily reporting is:

    • capturing the day as it unfolds
    • logging shots when they’re drilled
    • logging delays when they occur
    • logging conditions when they change
    • logging notes when conversations happen

    This is the difference between:

    a summary and a record

    A summary can be questioned. A record cannot.

    This is exactly why Boreva exists.

    How Real Daily Reporting Works in the Field

    Here’s what it looks like when a crew uses a real‑time system instead of a template.

    1. Bore Shots Get Logged as They Happen

    The moment a shot is completed:

    • footage is entered
    • conditions are noted
    • notes are added
    • timestamps are captured

    This becomes the backbone of the daily report.

    No rewriting. No re‑entering. No mismatches.

    2. Problems Get Recorded When They Occur

    When something slows the job down:

    • equipment failure
    • utility conflict
    • weather delay
    • inspector delay
    • access issue

    …it gets logged immediately.

    Not later. Not “when we get a minute.” Not “we’ll remember it.”

    Real‑time logging turns delays into defensible documentation.

    3. Notes Get Added in Real Time

    When the inspector says something important, the crew logs it.

    When the customer gives direction, the crew logs it.

    When the alignment changes, the crew logs it.

    These notes become the context that protects your hours and footage.

    4. The Daily Report Builds Itself

    By the time the crew clocks out:

    • the bore log is complete
    • the delays are logged
    • the conditions are documented
    • the notes are captured
    • the footage is exact
    • the timeline is accurate

    And the daily report is already built.

    Nothing needs to be remembered. Nothing needs to be reconstructed. Nothing needs to be guessed.

    This is what real daily reporting looks like.

    Why Boreva Makes This Possible

    Boreva isn’t a template. It’s a field system.

    It captures:

    • shots
    • footage
    • conditions
    • delays
    • notes
    • equipment issues
    • timestamps

    …as the work happens.

    The daily report isn’t something the crew fills out. It’s something the system builds automatically from the day’s activity.

    This is why Boreva reports hold up when the GC challenges them.

    They aren’t summaries. They’re records.