Rock Drill Compliance Requirements: The Problem Shows Up Months After Delivery

The Delivery Was Fine. The File Wasn't.

In March 2024, a contractor I work with took delivery of 40 rock drills. Good price, good timing, no visible defects. The crew had them on site the following week and everyone moved on.

Then a site audit pulled the technical file. The Declaration of Conformity on record described a feed frame and rotation unit that didn't match the machines actually in front of them. Not a safety problem — the units were built to the right spec for that job. But the file described a different configuration, and an auditor reads files, not machines.

It took ten working days to untangle. I say working days because nobody counts the weekend when a container is sitting on the dock accruing storage.

The equipment was never the issue. In my experience, it almost never is.

What Most Buyers Think "Compliant" Means

When a contractor or a distributor asks me about rock drill compliance requirements, the question usually boils down to one thing: does it have the mark?

And yes, the mark matters. So does everything behind it — the risk assessment, the technical file, the Declaration of Conformity, the harmonised standards the manufacturer claims to have applied. On the jobsite side you layer on OSHA or MSHA exposure depending on the operation. There's a real list, and it's longer than most purchase orders suggest.

But the mark is the last step, not the first. It's a claim that a documented process happened. If the documentation is thin, the mark is a sticker.

Here's the mental model most buyers carry: supplier builds the machine, supplier certifies it, machine shows up with a folder, folder goes in a drawer, drawer stays shut until something goes wrong.

That model holds up right until it doesn't.

The Real Problem: Nobody Actually Wrote the Spec

The first question I ask when a compliance issue lands on my desk is who wrote the specification.

Nine times out of ten, the answer is the supplier.

Think about what that means. The buyer defines the acceptance criteria by accepting criteria that the seller drafted. That isn't a compliance failure in the technical sense. It's a purchasing failure that only surfaces as a compliance failure later, usually at the worst possible moment.

I've watched this play out with rock drill distributors who genuinely know their market. They can tell you torque, feed force, hole diameter, air consumption, the whole sheet. But ask them which standard the unit was type-tested against, and which revision of that standard, and the answer gets vague fast.

I have mixed feelings about how much of this to put on the buyer. On one hand, a distributor buying 200 units a year can't audit a technical file for every SKU. On the other, the buyer is the one who eats the delay when the file doesn't hold up. The supplier just resends a PDF.

So the honest framing is this: you don't need to write the spec yourself. You need to read it before you sign, and you need one person on your side who is allowed to say no.

Reason Two: The Private Label Responsibility Gap

This one catches people who are otherwise careful.

A distributor wants their own brand on the machine. Fine — OEM and private label work is normal in this industry and it isn't inherently riskier. But the branding change also changes who is legally the party placing the product on the market in a lot of jurisdictions. In the EU, for instance, putting your own name on machinery typically makes you the manufacturer for compliance purposes, with the obligations that follow.

I should mention: this isn't a loophole and it isn't a technicality. It's how the framework is designed. Someone has to be answerable, and if you rebranded it, that someone is probably you.

The reason it goes wrong so often is that the conversation about branding and the conversation about compliance happen in different rooms, months apart. Sales settles the logo. Nobody settles the declaration.

When we handle private label orders at abi, the branding question and the documentation question get answered on the same call, because separating them is how you end up with a distributor whose name is on a Declaration of Conformity they've never read.

Reason Three: Version Drift

This is the one that gets experienced buyers, which is why it's worth spelling out.

A model number stays stable. The machine inside it doesn't.

Suppliers swap a component for a functionally equivalent one when a sub-supplier changes, when lead times slip, when a customer asks for a small modification. Each change is reasonable in isolation. String twenty of them together across three years and the technical file on your server describes a machine that no longer exists in that configuration.

The technical file was accurate when it was issued. It's just not accurate now, and nothing in the paperwork tells you when that stopped being true.

I'm not being dramatic about this. I've seen it on our own side — a feed frame revision that went into production in early 2023 and didn't make it into the documentation until someone asked a direct question in August. Nine months. Nothing was wrong with the units. The file was simply running behind reality.

What the Gap Actually Costs

People assume the cost of a compliance problem is the cost of fixing it. It isn't. The fix is usually the cheapest part.

Here's roughly how a mid-sized incident breaks down, based on what I've seen on our side:

• Storage and demurrage. Containers sitting while you argue about paperwork. Rates vary by port and by carrier — check your current tariff, don't rely on a number you heard two years ago — but it compounds daily.
• Reassessment. Getting a third party to review and reissue documentation on an already-delivered batch. Slow, and it can't start until you've figured out what's actually different.
• Schedule slippage. This is usually the biggest line item and the one nobody puts in the writeup. Crews standing around, or a project milestone missed by two weeks.
• Contract exposure. Penalty clauses attached to delivery dates don't care that the delay was administrative.
• Internal time. The hours your own people spend chasing PDFs instead of doing their jobs. Real, invisible, and never budgeted.

We lost a contract in 2022 over something along these lines. Not a huge one — around $40,000 — because we tried to save a few hundred dollars by skipping a pre-shipment documentation review on a rush order. The file arrived three weeks after the equipment did, and by then the client had sourced elsewhere. That's when we stopped treating documentation as a follow-up task and started treating it as a gate.

Worth saying plainly: the money you save on a lighter spec review is not real savings. It's a deferred cost with interest attached.

What Actually Fixes This

The fix is boring, which is probably why fewer people do it than should.

1. Review the supplier's spec sheet as your own. Not skim. Read it line by line, with someone who knows the standards, before the PO is issued. If you can't do that in-house, pay someone once to build you a checklist you reuse forever.
2. Demand a document list, not a document. Ask for the specific items: technical file index, Declaration of Conformity, test reports with the standard and revision number, and a change log. A folder with a mark on it tells you nothing.
3. Put a name on it. One person on your side who is accountable for the file and authorised to hold a shipment. If that person doesn't exist, the responsibility defaults to whoever is least busy, which is nobody.
4. Add a change-notification clause. Any component change on a running SKU triggers a documentation update. This is the single highest-value line you can add to a supply agreement, and most suppliers will agree to it without a fight.
5. Test it once. On your first order, run a third-party review. It costs more up front. It tells you whether your supplier's process is real.

None of this is exotic. It's the same logic as any other quality process — catch the problem upstream where it's cheap, instead of downstream where it's expensive.

Where I'd push back on the efficiency argument is custom work. If you're ordering one machine for a specific geology and a specific rig, standardised documentation templates can only take you so far. Highly customised units genuinely need case-by-case handling, and pretending otherwise just moves the failure. The right answer depends on your order profile, not on a general principle.

The Short Version

Rock drill compliance problems are rarely about rock drills. They're about a specification nobody owned, a responsibility gap nobody flagged, and a file that quietly went stale.

The equipment will do what it says on the sheet. The paperwork is the part that needs a process.

If you're sourcing a drilling rig or negotiating a rock drill distributor agreement and the compliance conversation hasn't happened yet, that's the conversation to have first. Before the deposit, not after the container lands.