What’s the real reason good drillers and offsiders don't always stick around?

Your driller finishes a brutal 12-hour shift and the day still isn't over. They're standing at the ute trying to remember exactly when the water truck turned up, what got used, and why the last two hours went sideways. That reconstruction happens on sites everywhere, every single shift.

It rarely shows up on a resignation letter, but ask around and it's usually somewhere in the mix. Here's what's actually happening in the moments many contractors never see, and what can change with the right tools in hand.

1. An end-of-shift marathon nobody signed up for

Drillers and offsiders already have a physically demanding job. By the time a shift wraps, reconstructing the whole day from memory and a stack of handwritten notes is the last thing anyone wants to be doing.

A system that lets the crew capture data as the shift happens changes that completely. Metres drilled and consumables used get entered on a mobile app in the moment, using fields that are already loaded with standard options rather than a blank box waiting to be typed into. How many rods got pulled three hours ago is already sitting in the record, tapped in the moment it happened.

Drilling's hard enough on its own. The reporting side of the job shouldn't feel like a second job stacked on top of it.

Tip: Find a mobile tool that lets drillers and offsiders log metres and delays as they happen, during the shift itself.

2. The Plod has to be interpreted by someone in the office

Paper Plods and free-text spreadsheets create their own mess. Wrong hole IDs and inconsistent activity names are common, and someone in the office ends up decoding handwriting no one else can read. And when a client spots numbers that don't match what they captured, it's the office admin left fielding the complaint.

Pre-loaded fields fix this at the source. A driller or offsider selects a standard option instead of typing it from scratch, so the record's clean the first time.

Tip: Use a system with pre-loaded fields for holes and activities, so crews pick from a list instead of typing something someone else has to decode later.

3. Delays that turn into blame

Shifts don't always go to plan. Ground conditions change, equipment breaks, and a crew can lose metres for reasons entirely outside their control.

If the only record is a messy paper Plod, the driller can end up wearing that blame. A system built to log exactly why downtime happened and when a delay started and ended gives the crew a clear way to show the difference between poor performance and a legitimate site or ground issue.

Tip: Find a platform that lets crews record the exact reason behind every delay, tied to the time it happened.

4. Maintenance issues disappear into a form

An offsider flags a maintenance problem during a pre-start. On paper, that form goes into a folder and nobody sees it again until something breaks.

When that same flag generates a follow-up action automatically, the crew learns something different fast: reporting a problem actually leads to someone doing something about it. That distinction matters more than it sounds, because the alternative teaches people that raising issues is pointless.

Tip: Use a system where a flagged maintenance issue automatically creates a follow-up action, rather than sitting in a form nobody revisits.

5. Handovers that starts every shift from zero

A good handover matters. If the next crew doesn't know what happened on the previous shift, they waste time getting oriented or repeat a problem someone already solved.

Digital shift records fix this by making the last shift visible. The incoming crew can see where the hole's up to and what's already been flagged to the office, rather than piecing it together from a rushed five-minute chat at the ute.

Tip: Find a tool that shows the incoming crew exactly where the hole's up to and what's already been flagged, before they even reach the rig.

6. A gap between what the field knows and what the office sees

A lot of site frustration comes from the distance between what happens at the rig and what the office thinks happened. When field data is delayed or manually re-entered, the office starts questioning the crew, and the crew starts feeling unheard.

Once a Plod syncs to a shared platform, supervisors and admin teams review and approve from the same record the crew created. Clients get updates from that same source too, instead of a compiled report days later. Everyone's looking at the same picture.

Tip: Use a platform where the same shift record supervisors see is also what gets shared with the client, with nothing separate written up after the fact.

What this actually adds up to

Take each of those on its own and it looks like an admin improvement. Put them together and the pattern's obvious. A crew that gets their evening back and stops wearing blame for things outside their control already has an easier job. Add issues that get followed up on and shifts that start with real context, and that's a genuinely different day-to-day experience.

That's what decent field tech does, and it's what CorePlan is built around: capturing what actually happened on site so admin and handovers stop being the parts of the job that wear people down.

Good pay gets someone through the door. A job that feels manageable day to day is what keeps them past the first year.

FAQs: tech, retention, and drilling crews

Does better field tech actually help with staff retention?

Yes, mainly by removing the parts of the job crews find most draining: end-of-shift paperwork and being blamed for things outside their control. Retention often comes down to daily friction more than pay.

How does digital Plod capture help drillers day to day?

It replaces reconstructing a shift from memory with logging metres and consumables as they happen, using pre-loaded fields instead of free text. That cuts errors and end-of-shift admin at the same time.

What happens to maintenance issues raised during a pre-start?

In a connected system like CorePlan, a flagged issue generates a follow-up action automatically rather than sitting in a form nobody revisits. Crews notice quickly whether reporting a problem actually leads to something happening.

Why does a clean handover matter so much?

The next crew starts the shift already knowing where the hole's up to and what's unresolved, instead of losing the first hour getting oriented or repeating a problem someone already solved.

Download the checklist here

CorePlan vs Krux: What's the difference?

Explore powerful features that outperform Krux.

Click here

How to keep good drillers and offsiders without relying on pay alone

Download the checklist here

Continue reading