search
close
For example "Webinars"

From Approved Quote to Wellsite: Dispatching an Oilfield Job When the Plan Refuses to Hold Still

Third in a series on the oilfield job playbook. Between a sold job and a crew on location sit an approval, a handoff, and a dispatch board that never stops moving. How well you run those three decides your mobilization, your margin, and whether the customer waits.
In the first two articles of this series, I made the case that an oilfield job is a chain from quote to cash, and that pricing is the first link, the one that quietly decides your margin before a tool ever moves. This article is about the next stretch, and it is the stretch where more operations break than anywhere else: getting a sold job approved, handed to the field, and dispatched to the wellsite.
The job is sold. The rate is set. To a lot of people in the building, the hard part is over. It is not. The job now has to clear an approval, cross cleanly from sales into operations, and get turned into a crew, the right serial-numbered equipment, and a truck headed to the right lease. And it has to do all of that inside an environment that refuses to hold still. The plan you build at six in the morning is rarely the plan you run at noon. Getting good at this stretch is less about executing a plan and more about absorbing change without dropping the job.
Approvals come first, before operations ever touches the job
A sale is not a green light on its own. Before a job crosses into operations, it should clear an approval, because operations should never inherit a job that has not been qualified. That approval is doing three jobs: margin control, scope control, and credit control. A job priced below a margin threshold, a scope above a certain value, or a customer with credit exposure needs a decision from the right person before anyone commits a crew and a truck to it.
Putting the approval before the handoff, rather than somewhere in the middle of dispatch, matters more than it looks. It means operations only ever works approved jobs. The dispatcher is never holding a job that might get pulled back for a pricing problem or a credit hold after the equipment is already staged. The approval is the line between a sold job and an operations job, and keeping that line clean upstream keeps the churn out of the field.
The discipline that makes approvals work is routing. The job should go to the right approver automatically, based on its value, its department, or its line of business, and it should show up as a task that someone owns, not an email that someone might see. The failure mode is the approval that sits, because an approval waiting on someone who is in a truck or away from a desk is a job not moving. The fix is to take approvals off the desk. When an approver can see the job, see the margin, and approve it from a phone in the time it takes to read it, the gate stays fast and the handoff is never waiting on it.
The handoff: a complete record, including the certifications the customer requires
Once a job is approved, what needs to move into operations is a complete, structured job record, not a hallway conversation and a half-finished email thread. That record is where the single job reference is born, the one that travels all the way to the invoice. Everything that gets dispatched, captured in the field, and billed inherits from it, so if it is thin or wrong at the handoff, every stage after it inherits the error.
A complete handoff carries, at minimum:
  • The customer and the authorized site representative.
  • The exact location: well, lease, pad, and field, not just a town.
  • The scope of equipment and services, item by item.
  • The pricing or agreement that applies, so the field and billing inherit the agreed rate.
  • The customer’s AFE, purchase order, or cost coding, because an invoice without it gets rejected no matter how good the work was.
  • The committed start date and any window constraints.
  • The technical requirements of the job: pressure ratings, environment, configuration, anything the equipment has to satisfy.
  • Site and safety requirements specific to that operator and location.
And one more that gets missed constantly, with expensive results: the certifications the customer requires.
Most operators will not let a company or a crew onto their location without proof of specific qualifications. That can mean contractor prequalification status, safety training tickets, a compliant drug and alcohol program, current insurance certificates, operator-specific site orientations, and individual certifications for the people assigned. These requirements are not yours, they are the customer’s, and they vary by operator and sometimes by site. A crew that shows up without the certification that operator demands gets turned away at the gate, and now you have missed the job with a truck already rolling and the mobilization clock already spent.
That is why customer-required certification belongs in the handoff, not discovered at the gate. The handoff should confirm that the company holds the operator’s prequalification and that the specific crew being assigned carries the specific certifications that operator requires for that site. Matching qualified, certified people to a customer’s requirements is a scheduling input, not an afterthought, and verifying it before dispatch is far cheaper than verifying it at a locked gate three hours away.
Why fast and why accurate. Speed matters because oilfield work runs on lead times, and every hour a job sits between approved and dispatched is an hour subtracted from the mobilization window. Accuracy matters because the handoff sets the job reference, and a wrong location, a missing AFE, or an unverified certification does not hurt today, it hurts later, when it is most expensive to fix. Fast and wrong is not better than slow and wrong. The target is fast and right, which is only reliable when the handoff is a structured record with required fields, not a matter of who remembered to mention what.
image
Scheduling: every parameter that decides who goes where, and when
Scheduling is where the approved, handed-off job meets the reality of finite equipment and finite crews. A good schedule is the product of weighing a specific set of parameters, and the operations leaders who run tight boards weigh all of them.
  • Customer priority and the committed start time. Some windows are firm and some are soft, and the board has to know which is which.
  • Equipment availability by status. Not what is in the fleet, but what is actually available right now, read from each unit’s current state.
  • Crew competency and certification. The right qualified people, matched by ticket, by certification, and by the customer’s requirements for that site.
  • Overtime and fatigue exposure. Assigning a crew already deep into overtime is a cost and a safety decision, not a neutral one.
  • Travel time and staging location. Where the crew and the iron start from, and what that does to the start time.
  • Multi-job conflicts. The same unit or crew requested for overlapping windows, flagged early enough to resolve with a substitution instead of a failure.
  • Mobilization lead time by equipment category. Pressure control, complex assemblies, and simple rentals do not need the same notice.
  • Backup resources. A designated fallback for high-demand units and critical crews, so a single problem does not become a missed job.
Two disciplines turn those parameters into a working schedule. Reserve specific serial-numbered units to the job, so the thing you scheduled is the thing that ships. And run the board as a live view that catches conflicts before they reach the field, because a conflict caught on the board is a phone call, and the same conflict caught on location is a failed job.
Dispatch is a moving target, and that is the whole point
Here is the part no scheduling theory prepares you for. The plan does not survive contact with the day.
You build a clean board at six in the morning. By nine, the operator has pushed the start to tomorrow. Your lead hand calls in sick. The tool that was supposed to clear its final test at seven is still on the bench. And the truck that was rolling to the pad picks up a flat on the highway. On a slow day you get one of these. On a busy day you get all four before lunch, across different jobs, at the same time.
This is what dispatch actually is. It is not executing a plan, it is re-planning continuously while the clock runs and the customer watches. Every one of those events forces a decision: reassign a crew, pull a backup unit, resequence two jobs, renegotiate a window, reroute a truck. And every decision has to reach everyone it affects, fast, without breaking the single job reference that ties the whole thing together.
A dispatch process built on phone calls and paper cannot absorb that. Every change becomes a round of phone tag, a stack of call-backs, and a set of people working off information that went stale an hour ago. The plan and reality drift apart, and the gap is where jobs get missed and money leaks.
This is exactly where mobile apps and team chat stop being conveniences and become the thing that keeps you standing.
Mobile dispatch. When the full job package lives on the crew’s phone, the work order, the load list, the site and safety requirements, the certifications, a reassignment is instant. Reassign the job and the new crew has everything the old crew had, without a reprint or a handoff meeting. Status, arrival confirmations, signatures, photos, and consumed materials come back the same way, in real time, even without signal, syncing when it returns. The office sees the job move without making a single call to ask where it stands.
Field chat and messaging. When the operator moves the window, one message reaches the whole crew and the office at once, with an acknowledgment you can see. When the lead hand is out, the reassignment goes to the replacement and the customer contact in the same thread. The flat tire becomes a two-line update and a rerouted backup, not thirty minutes of voicemails. Group coordination that used to eat a dispatcher’s morning resolves in seconds, and it leaves a documented trail anyone can read later.
The cost argument is direct. Every manual phone call, every re-keyed form, every status nobody can see, and every change that has to be chased down by hand is process cost: administrative labor, delay, and the errors that come from passing information by memory in a hurry. Mobile dispatch and field messaging let a dispatcher absorb a morning full of changes without the process falling apart, which means fewer missed jobs, faster mobilization, and more of your lead time converting into billable days. The same dispatcher who drowns in six jobs on phone and paper runs ten cleanly on a phone and a chat thread. That is not a software talking point. On a day when everything changes at once, it is the difference between holding the board together and losing it.
Job preparation: the four steps that clear before anything ships
While the crew and the schedule come together, the equipment has to be made ready. Job preparation is a quality gate with four named steps, and none of them is optional.
Assembly. Multi-component equipment gets built against a controlled bill of materials with a parent-child structure, so every component, seal, fitting, and tool is confirmed against the job scope. Critical assemblies get a second-person verification, and a substitution gets recorded, not improvised.
Pick tickets and staging. The components and consumables for the job get pulled and staged against the specific job, using a pick ticket or pull sheet. Kitting consumables to the job is what lets you reconcile, after the fact, what was issued against what was actually used and billed, which is where consumables revenue is either captured or quietly lost.
Inspection. Every asset passes a documented pre-job inspection before it ships, tied to its serial number, the technician, the date, a pass or fail result, and photos. This is not a yard formality. It is your evidence months later when a customer disputes return condition, and it is the cheapest insurance in your operation.
Equipment compliance check. Before release, every unit clears a compliance check: certifications current, pressure test records valid and retrievable, calibration in date, load ratings confirmed. Non-compliant equipment never leaves the yard, because the cost of a certification failure on location is not a line item, it is a shutdown.
The gate that ties these together is worth enforcing without exception: nothing advances to dispatch until assembly, staging, inspection, and compliance are all complete and visible. And because the day keeps moving, the readiness state has to be visible in real time, so that when a tool fails its final test at seven, the dispatcher knows before the truck is loaded, not after.
The takeaway
Getting a sold job to the wellsite is three disciplines stacked on top of each other. Approve first, so operations only ever runs qualified jobs. Hand off a complete record, including the certifications the customer requires, so nothing is discovered at a locked gate. Then dispatch inside an environment that will not hold still, where the customer moves the date, the crew calls in sick, the tool is not ready, and the truck gets a flat, often all at once. The companies that run this well are not the ones with a perfect plan. They are the ones whose approval, handoff, and dispatch can absorb change in minutes, because mobile tools and live coordination keep the plan and reality from drifting apart. Do this stretch fast and clean, and you have bought yourself a job that runs the way it was sold.
Next in the series: field operations. What happens on location, how labor and equipment time get captured, and why the field ticket is the document that every dollar of revenue depends on.

Recent posts

Show all
close
Subscribe to blog