You don't call a wireline vendor when you're bored. You call because you're hungry for answers—formation pressure, fluid contacts, saturation, rock properties—and you usually need them before the rig moves. If you're on the operator side, that means running a compressed schedule, a late-arriving rig, or a well that just threw a curveball.
I coordinate urgent oilfield services for a living. In the last eight years, I've managed more than 50 rush orders for wireline, mud logging, and formation evaluation work. Some went smoothly. A few taught me painful lessons. This checklist is the one I use when a Schlumberger wireline job has to happen on a deadline without the process falling apart.
Who This Checklist Is For
This is for the person who has to make the service call count the first time. The drilling supervisor who needs a clean log before the next casing point. The completions engineer who needs pressure data to design a fracture. The procurement lead who gets a frantic call on a Friday afternoon and has until Monday to get a signed PO and a confirmed crew.
There are six steps here. Step 1 and Step 6 are the ones I see most often skipped. Step 3 is the one that surprises people—it's about the price you don't see yet.
The Emergency Checklist
Confirm what “Schlumberger WS” means for this specific job. In my world, WS usually means wireline services. But not always. In older files, WS might mean well services. If your operation is in Indonesia, the legal entity on the contract may be PT Schlumberger Geophysics Nusantara—or, in older paperwork, listed as Schlumberger Geophysics Nusantara PT. Make sure the PO, the insurance certificate, and the permit all match that entity. I once sent a PO to the wrong entity and changing it afterward took eight days of procurement red tape. So glad I caught it before mobilization—dodged a bullet, but barely.
Also specify whether you need open-hole or cased-hole logging, and whether data will be recorded in memory mode, real time, or both. A “wireline job” can mean three different things to three different engineers. Get it in writing.
Define the deliverable before you talk about the day rate. The biggest source of emergency project overruns is vague language. “We need a formation evaluation, quick.” What does that mean? Do you want a triple-combo log? A pressure survey with three formation-tester stations? A fluid sample? Data in LAS 3.0 format with a petrophysical interpretation report? If you leave it undefined, the service company's operations team will define it for you—and their definition will include extra runs, extra interpretation time, and a long list of “additional charges.”
I learned this the hard way. In 2023, I coordinated a rush job where we forgot to specify digital data delivery. It was $1,200—no, $1,400, I'm mixing it up with another project—either way, the data upgrade cost more than the mobilization fee. Now I always ask: “What's the minimum deliverable that lets us make the decision?”
Ask for the “not included” price list before approving anything. I've learned to ask “what's NOT included” before “what's the price.” In an emergency, the headline day rate becomes the anchor. But the final invoice will also include mobilization, demobilization, tool calibration, rig-up, wireline unit supervision, data transcription, maybe helicopter standby. Sometimes these are bundled; sometimes they're not.
The vendor who lists all fees upfront—even if the total looks higher—usually costs less in the end. I keep a folder of quotes where the “low bid” ended up 22% higher than the transparent quote because the low bid didn't include the 4 a.m. standby callout. The upside was $3,000 in savings. The risk was missing the deadline. I kept asking myself: is $3,000 worth potentially losing the rig slot? It wasn't.
Confirm the physical crew and unit status, not just the calendar availability. The scheduling system might say the wireline unit is available, but is it 120 miles away on another pad? Is the winch in the shop? Is the logging engineer already on 24-hour call? One of my biggest regrets: assuming availability meant readiness. The unit arrived at the wellsite with a missing pressure-control adapter, and we burned ten hours waiting for a replacement.
The numbers said the other crew could get there faster. My gut said stick with the Schlumberger unit that had run this exact tool string on the same field three weeks earlier. I went with my gut. The “faster” crew only had a thinner cable, and the job needed the heavier one. The gut call saved us a rerun. Since then, I always ask for the equipment sheet, not just the ETA.
Put data format and acceptance criteria in writing. You're probably thinking that's the geologist's job. It is, but the operations team needs to write it into the program. Specify the logging speed, repeat sections, and what constitutes an acceptable pass. If your well data has to go into a specific software package—say, a proprietary petrophysical platform—say so before the unit is rigged up. Otherwise, the job can be done perfectly and still be late, because the data isn't usable.
In March 2024, 36 hours before a deadline, I had to coordinate a memory-logging run because the real-time transmission couldn't get from the wellsite to the office. The client was angry. The service team was frustrated. We delivered, but we could have avoided the whole marathon by specifying memory mode in the original request.
Build a buffer into the schedule, even if it means paying for standby. This is the step most people skip. When you're under pressure, you pack the schedule tightly. Then you get a stuck tool, a failed pressure test, or a transmission drop, and the whole sequence collapses.
I now insist on a 24-hour buffer for any wireline job that is critical to a rig decision. The service company sometimes rolls their eyes; the drilling supervisor sometimes complains about the cost. Then they see what happens when the tool gets stuck at 3 a.m. The buffer saves the decision. For same-day turnarounds, I add a second buffer in the data processing step: the wireline crew sends raw data at the wellsite, but the interpreted curves can take hours. If you have a casing decision at noon, get a “preliminary raw data” commitment written into the job ticket.
Common Mistakes to Avoid
- Don't treat the day rate as the only number. The final invoice includes mobil, demob, fuel, standby, and any special tools. Ask for a full cost breakdown and a “what can change this price” list.
- Don't award based on a generic phone quote. An emergency can make you want to act quickly. But a quote that doesn't mention the well depth, pressure, temperature, or expected hole condition is just a starting point.
- Don't spread your contingency like peanut butter across too many vendors. It may feel safer, but it means no one has enough pull to get a crew to your rig during a weather window. Pick a primary and a backup, and give both the full scope.
- Don't let keyword noise redefine the scope. If someone hands you a search list that mixes “Schlumberger” with “what is Simparica” and “peanut butter,” ignore the noise. The same logic applies to service procurement: a low price from a broad search is not the same as a quote that actually matches the formation evaluation problem.
One final thought. According to SLB's website (slb.com), wireline logging is a core method for measuring rock properties in the wellbore. It is exactly the kind of data that becomes expensive when the scope is vague. The checklist won't make a failed pressure test disappear. It will make sure that when the pressure test fails, the right people are on site, the right data format is agreed, and the standby charges are already visible on the estimate.
If you're hungry for results, use the checklist. It's the best way to turn a rush job into a controlled operation—without feeding the invoice monster.