How it works

How WaitClock works

From the call for a load to a ticket your customer can check. Six steps.

1

Set up once

Add your trucks, drivers, customers, and leases. Put in the gate codes and directions your drivers need. Set standby rules for each customer: free time, billing increment, and rate. Each driver gets a company code and a 6-digit PIN.

2

Dispatch the load

Make a load: customer, lease, tank, barrels, and the SWD you plan to use. Assign a truck and driver. The load shows up on the driver's phone. The board shows every load and where each truck last reported in.

3

Drive it

The driver taps as the load moves: en route, at pickup, loaded, at disposal, unloading, done. Forgot to tap on arrival? If the load is "en route" and the truck pulls onto the lease, the load moves to "at pickup" on its own. If the load is "loaded" and the truck pulls into the SWD, it moves to "at disposal." This goes by the truck's position, so it can show up late where there is no signal. If a driver skips a step, the app takes the tap and notes the skip for the dispatcher.

Truck position comes from the driver's phone while the app is open on shift. If your trucks run Motive or Samsara, WaitClock can read truck position from them too. Your trucks' location data explains who sees it.

No signal on the lease road? The app keeps working. Taps and tickets wait on the phone and send when signal comes back.

A load from the lease, down the road, into the SWD line, then unloading. Lease fence Road In line Unloading SWD fence
Lease fence, road, SWD fence. Time inside the SWD fence is time on site. Where the driver taps "Unloading," it splits into time in line and time unloading.
4

Write the ticket

The driver fills out the ticket on the phone: lease, tank, opening and closing gauge, barrels, SWD, and the SWD drop slip number. Add a gauge photo or a drop slip photo. Get the signature on the screen.

Arrival, departure, and unloading times are stamped as they happen. WaitClock works out standby minutes from your rules for that customer, and keeps the times and visit record behind them.

5

Review and bill

Tickets land on the dispatcher's screen. Check them, fix what needs fixing, and approve. Print a ticket or export tickets for billing.

If a load was cancelled or given to another driver while the driver was out of signal, the ticket is still kept. It is flagged for review. It is never thrown away.

Operators check tickets against GPS and geofences before they approve them.1 Your tickets carry that record from the start. Your contract with the operator still decides what gets paid for standby.

6

See the line

Every truck on WaitClock that pulls into an SWD adds a visit to the line map. The map shows, for each SWD:

  • how many trucks are on site now,
  • the typical time on site over the last 3 hours,
  • how many visits that number is based on,
  • when it last updated.

What it measures. Time inside a fence we draw around the SWD. That includes unloading. Where drivers tap "Unloading," we can split time in line from time unloading. Coverage grows as more fleets join.

What it is not. It does not pick an SWD for you or send trucks anywhere. It is information. You and your dispatcher decide.

Why it matters: time in an SWD line is on-duty time for water haulers and burns the 14-hour clock.2

  • Under 30 min
  • 30 to 60 min
  • Over 60 min
  • Not enough trucks yet

Look at the demo map (demo data).

What stays private

Other haulers never see your trucks, drivers, customers, or leases. The line map shows counts and minutes only. Your trucks' visits count toward those numbers without your name on them.

Plain answers

Your trucks' location data

Truck position is what puts the times on a ticket and the minutes on the line map. Here is where it comes from, who owns it, and who sees it.

Where it comes from

  • Your trucks' ELD (Motive or Samsara), once you connect it in setup.
  • The driver app, only while the driver is signed in, on shift, and the app is open on the screen. A phone browser app does not send position from the background. Tapping "End shift" stops it right away.

The app works without it

A driver can say no to location. Taps and tickets still work. Location adds a record behind the times; it is not required.

Before the phone asks, the app shows one plain screen: what it collects, why, who sees it, and how to stop.

You own it

Your trucks' location data belongs to your company. WaitClock uses it to run your account and to work out anonymous line times. We never sell it. We never show it to another hauler.

Who sees what

  • Your owners and dispatchers: your own trucks.
  • Your drivers: their own loads and line times.
  • Other haulers: only anonymous line times at disposal sites, and only when trucks from at least 2 companies besides their own made visits in that window. Otherwise they see "Not enough trucks yet." Your company always sees its own trucks' numbers.
  • Your customers (operators): only the summary times on tickets you send them: arrived, in line, unloading, left, time on site, and how many position points back it up. Never the raw track.

How long we keep it

Raw position points are deleted after 13 months, and so are the positions saved with status taps and each truck's visit times at leases and SWDs. Summary times stay with each ticket. The line map uses only the last 28 days of visits.

Take it with you

Owners can download the company's raw position points as a CSV file: Setup, then Company, then Download location history.

Questions haulers ask

Do other haulers see my trucks?

No. Other haulers never see your trucks, your drivers, your customers, or your leases. The line map shows only counts and minutes for each SWD: how many trucks are on site and the typical time on site. Your trucks' visits count toward those numbers without your name on them. That is how the map fills in. Another company sees your trucks in a reading only when trucks from at least 2 companies besides its own made visits there in that window.

One thing to know: at an SWD where very few trucks go, a count like "1 truck on site" names no one, but someone who knows the area might guess whose truck it is.

Where does truck location come from, and who owns it?

Two places: your trucks' ELD (Motive or Samsara) once you connect it, and the driver app while the driver is signed in, on shift, and the app is open. "End shift" stops the app right away. The app works without location; drivers can say no and still tap and write tickets.

Your company owns its trucks' location data. WaitClock uses it to run your account and to work out anonymous line times. It is never sold and never shown to another hauler. Raw position points, tap positions and site visit times are deleted after 13 months, and owners can download the raw position points as a CSV file. More on location data

What if there is no signal?

The driver app keeps working. Every tap and every ticket is saved on the phone with its time, and its position when the phone has one. When the phone finds signal again, it sends them. New loads from dispatch reach the phone once it has signal. If a load was cancelled or given to another driver while the driver was out of signal, the ticket is still kept and flagged for the dispatcher to review. It is not thrown away.

What does the line map actually measure?

Time on site. We draw a fence around each SWD. When a truck on WaitClock goes in and comes back out, that is one visit. The map shows the typical visit time over the last 3 hours, how many visits that is based on, how many trucks are on site now, and when it last updated.

Time on site includes unloading. Where drivers tap "Unloading," we can split time in line from time unloading.

The map is built from trucks on WaitClock, so coverage grows as more fleets join. An SWD gets a color once at least 2 trucks have left it in the last 3 hours, or when a truck there now has been on site 30 minutes or more: a long stay means a line, even before anyone leaves. One truck that just pulled in does not. Otherwise the SWD shows gray, "Not enough trucks yet," with how many trucks are on site now, instead of a guess. Some readings still rest on only two visits. Every reading shows its visit count, so you can tell.

It is information for you and your dispatcher. It does not pick an SWD or send trucks anywhere.

Do I need new hardware?

No. Drivers use the phone they already carry. If your trucks run Motive or Samsara, WaitClock can also read truck position from them.

Which ELDs?

Motive and Samsara. You make an access key in your ELD account and enter it in WaitClock setup. We store it encrypted. Then you match each ELD vehicle to your truck number. If you run a different ELD, or none, the driver app sends truck position from the phone while the app is open on shift.

Will this get my standby paid?

It gives you a record. Your contract with the operator decides what gets paid. Operators check tickets against GPS and geofences before they approve them.1 Your WaitClock tickets carry arrival, departure, and unloading times, and the visit record behind the standby minutes.

Why does time in the line matter so much?

Time in an SWD line is on-duty time for water haulers. It burns the 14-hour clock. Water haulers do not get the well-site waiting exemption.2

How do drivers get in?

Dispatch sends a link. The driver opens it and adds it to the phone's home screen. No app store. The driver logs in with your company code and a 6-digit PIN. If a phone is lost, dispatch can shut off that phone's access.

Can I get my tickets out?

Yes. Print any ticket, or export tickets for your billing.

What does it cost?

Pilot pricing: Fleet is $79 per truck per month. Owner-operator is $2 per ticket, no monthly minimum. Powder River Basin fleets pay nothing for the first 60 days. Month-to-month. No hardware. See pricing

Where does it work?

The pilot is for Powder River Basin fleets. The dispatch board, tickets, and driver app work wherever your trucks run. The line map only shows SWDs where trucks on WaitClock have been. The map on our site is a demo with made-up data, and it is labeled that way.

Start a pilot

Sources

  1. Enverus OpenTicket product page. https://www.enverus.com/products/openticket/
  2. FMCSA guidance, 77 Federal Register, June 5, 2012; 49 CFR 395.1(d)(2). https://www.govinfo.gov/content/pkg/FR-2012-06-05/html/2012-13584.htm