-
When to Use This Checklist
-
1. Lock Down the Fact Sheet Before You Look at a Quote
-
2. Confirm NExT Training Requirements — Before Anyone Steps on the Rig
-
3. Verify Service Level Line-by-Line (The Package Adds Up Fast)
-
4. Put the Schlumberger Support Escalation Path in Writing
-
5. Fix the Data Delivery Format Before the Tool Is in the Ground
-
6. Confirm Equipment and Personnel Arrival Separately
-
7. Write a Site Scope Brief — Not a Job Title
-
8. Run a 48-Hour Post-Job Review
-
Common Mistakes That Will Cost You
Eight years of handling field service procurement orders, mostly wireline logging and formation evaluation tooling. I have personally made (and documented) eleven significant mistakes, totaling roughly $180,000 in wasted budget and — conservatively — 31 non-productive days across fourteen jobs. Now I maintain our team's pre-check list, which has caught 23 potential hold-ups in the past 14 months alone. This is that list.
When to Use This Checklist
Use this checklist when all three of the following are true:
- You are placing a service order with Schlumberger — wireline logging, formation evaluation, drilling, completion, performance optimization, whichever it happens to be.
- The single order is $25,000 or more. Below that threshold, the mistakes are cheaper to absorb.
- The order touches three teams at once: procurement, field operations, and the Schlumberger support side.
If you are placing a small, catalog-standard order, skip this. This checklist targets bundled, multi-service jobs that depend on coordinated support and training signoffs — which is where most of the pain lives.
1. Lock Down the Fact Sheet Before You Look at a Quote
In my first year (2017), I made the classic mistake: I accepted a verbal scope, sent it in, and only discovered later that the wellbore parameters on the quote did not match the well we were actually going to log. The quote had been prepared for a different casing size. That order was $45,000. We did not get the money back.
Now, before a single dollar figure enters the conversation, I write a one-page fact sheet with the following fields:
- Well identifier, depth range, and casing specification
- Tool string requirements (min/max diameters, temperature ratings)
- Service module — not the package name, the actual module code
- Completion date and non-negotiable rig schedule
- Ambient conditions (this matters more than people realize)
I have seen a Schlumberger quote arrive in front of an operator with a mud logging module that did not apply to the mud system on the rig. It looked correct on paper. It was not. The fact sheet would have caught it in four minutes.
2. Confirm NExT Training Requirements — Before Anyone Steps on the Rig
This is the step most people skip, and the one I regret the most. Schlumberger's NExT training program exists for a reason. For certain service tiers — specialty logging, formation pressure testing, advanced completions — Schlumberger requires certified personnel on both sides. If your field crew has not completed the NExT training modules relevant to the service, support defaults to remote mode. That is a real difference in a live job.
What happened to me: in Q1 2021, my team arrived on-site to observe a wireline run. Three of our field engineers had not completed the NExT orientation module that the service tier required. Schlumberger dispatched a support specialist, but the first two shifts ran by phone. Cost: roughly $6,800 in extra support hours and one shortened run. Not a catastrophe. But a real waste of time and money.
Now I check NExT compliance as a gate item. The rule is simple. If the training modules are not signed off, the order waits. No exceptions.
3. Verify Service Level Line-by-Line (The Package Adds Up Fast)
Saved $2,400 by skipping the elevated support add-on. Ended up spending $17,000 on rig time when the primary engineer was unreachable at 2:00 AM.
That trade taught me this: service level is not about “cheaper versus better.” It is about whether you have options when a job goes sideways. Every Schlumberger service order I have touched since 2022 includes a line-by-line breakdown — the modules, the add-ons, the specialty tooling, the support tier — reviewed against the fact sheet. The total looks like a 2024 Bentley GT more often than it should, but the line items are what matters. If the price has jumped $17,000 without a corresponding tool or service addition, something is wrong and you should ask why.
4. Put the Schlumberger Support Escalation Path in Writing
Here is the thing: the support escalation path is usually buried on page three of the quote attachment, and it is often out of date by the time you actually need it. I have had a job stop at 3:00 AM because our support contact number had rolled to a regional dispatcher who did not have access to our order notes.
So now the checklist requires:
- Named support contact with direct-line number and business hours in your time zone
- Escalation contact for the service line in question (not the account manager, the service line)
- 24/7 dispatch number with a note on when it actually picks up (hint: rarely during shift change)
- Internal contacts — who on our side is the single point of contact for each escalation level
When the support path is missed, the average resolution time is measured in hours. When it is in place, it is often measured in minutes. That is a real gap, not a hypothetical one.
5. Fix the Data Delivery Format Before the Tool Is in the Ground
Why did the Schlumberger daily report show up in a format our system could not ingest? Because the tool was transmitting in a format aligned with a different processing pipeline than the one our ops center uses.
This one kept costing me time across 2022 and 2023. The lesson was simple: the Schlumberger data delivery format is not a default. It is a specification. So before the tool goes in, we now confirm:
- Data format (LAS, DLIS, or proprietary) and version
- Transmission timing — real-time feed, end-of-run, or post-job
- Who is the receiving party, and who is responsible for the transformation step
- Any required post-session conversion, and who owns it
It also helps to dry-run a single sample file through your pipeline. I have learned that the hard way. Twice.
6. Confirm Equipment and Personnel Arrival Separately
This is the checklist item I have relied on the most, and the one I wish I had written down years earlier.
The tool arrives on one truck. The operator arrives on another. They are tracked by different systems. If you confirm only one, you are gambling.
In September 2022, a wireline truck arrived on-site at 06:00, but the certified operator did not show until 13:00. Six hours of standing rig time, $3,200 in delays, and a very patient toolpusher. Now the checklist requires:
- Equipment ETA and personnel ETA listed as two separate fields
- The name of the certified operator, verified against the service tier requirement
- Any transport or customs clearance variables flagged if the equipment is crossing borders
- A buffer window that accounts for realistic (not ideal) travel time
Service level confirmed. Tool specs matched. Personnel schedule — nope, that one slipped through. That is exactly the gap this step closes.
7. Write a Site Scope Brief — Not a Job Title
“Just wireline logging” is not a scope. It is a hope. In 2020, we had a cost dispute because the field engineer and our site supervisor had different interpretations of what “the job” included. The job was logged as complete. The invoice said so. Our site notes said otherwise. It took three weeks — or rather, closer to four with the internal review — to resolve.
Now the site scope brief covers:
- The specific run, interval, and number of passes
- On-site deliverables (raw logs, intermediate interpretation, final interpretation)
- Handover requirements at end of run — verbal and written
- Signature-required items, and exactly who signs what
- The boundary of support coverage during the run
If the brief cannot be stated in concrete terms, the job is not ready to be scheduled.
8. Run a 48-Hour Post-Job Review
Most teams skip this step. It is the cheapest step on the list. And it is the one that keeps the next order from carrying the same defects.
Forty-eight hours after the job closes, I sit down with the field lead and go through three questions:
- What did the Schlumberger support team handle that we assumed would be automated?
- What on the invoice surprised us, and why?
- What would we have caught in the pre-check if we had looked closer?
About one in four reviews turns up a real ordering flissue — a missing training signoff, a support path that was not documented, a data format that did not match the downstream system. Those notes become the standing checklist for the next order.
Common Mistakes That Will Cost You
A few things I have learned to say out loud, even when they feel obvious:
- Do not treat the NExT training as a checkbox. If your field team does not carry the required NExT modules, Schlumberger support will default to remote coverage, and the resulting delays are on you, not them.
- Do not assume the quote is a summary. The quote shows the headline. The attachment shows the operating requirements, the data format, the escalation path, and the terms of the service tier. All of those matter.
- Do not merge equipment ETA and personnel ETA. They are tracked separately because they travel separately. Confirm both.
- Do not chase a cheaper service tier without knowing the fallout cost. The discount is real, but the difference in support hours and rig time is where the money actually moves.
- Do not sign the invoice before the post-job review. The review is where you find out what to change for the next one.
Pricing references in this article are indicative and based on internal 2021–2024 order records; verify current Schlumberger catalog and service tier terms directly before applying them to your own order.