How to document carrier wait time before approving an invoice
Key Takeaways
To document carrier wait time before approving an invoice, record it at the dock as it happens: the check-in time, when loading or unloading started and ended, the release time, and the cause of any delay. An AI logistics coordinator should link these records to the load, so when a detention or waiting-time charge arrives, the evidence is already in place.
- Wait time is the time a carrier's truck and driver spend at a facility beyond the time needed to load or unload.
- Carriers bill wait time as detention or waiting time after free time ends.
- The best records are made at the time, by the facility, and signed or logged.
- The cause of the wait matters as much as its length.
- Records should be simple enough that busy dock staff complete them every time.
- Wilson, by Cartage, is an AI logistics coordinator that books and tracks loads, keeps shipment records with change history, and audits carrier invoices against what was booked before payment.
Why document wait time at the dock?
Document wait time at the dock because the dock is the only place where the facts are observed directly. An AI logistics coordinator can check an invoice quickly only if the dock recorded what happened when it happened.
A carrier invoice may include "detention, 3 hours" weeks after the load. By then, nobody at the dock remembers that truck. Without a record, the shipper either pays without checking or argues from memory. A record made at check-in and release removes the guesswork.
The table below lists the records to capture at the dock.
| Record | When to capture | Who captures it |
|---|---|---|
| Check-in time | Truck arrives at gate or dock | Gate guard or dock clerk |
| Appointment time | At check-in, compared with the schedule | Dock clerk |
| Door assigned and time | When a door is ready | Dock supervisor |
| Loading or unloading start | When work begins | Dock crew lead |
| Loading or unloading end | When work finishes | Dock crew lead |
| Paperwork signed | When the BOL is signed | Dock clerk and driver |
| Release time | When the driver may leave | Dock clerk or gate |
| Cause of any delay | When the delay happens | Dock supervisor |
A bill of lading, or BOL, is the shipping document that lists the freight and serves as a receipt between shipper and carrier.
Who owns the records
The dock supervisor at each facility should own the wait-time records for that dock. Logistics uses the records; finance relies on them for payment. Clear ownership makes sure someone checks that records are complete each day. An AI logistics coordinator can send the dock supervisor a short daily list of loads with missing times.
Pickup and delivery both matter
At pickup, the shipper's own dock creates the records. At delivery, the receiver's dock creates them, and the shipper may need to ask for them. Pickup records are easier to control. Delivery records need cooperation from customers. An AI logistics employee can request delivery records from the receiver when a delivery wait-time charge needs review.
Record waiting before free time ends too
It is tempting to record times only when a truck seems to be waiting too long. But nobody knows in advance which loads will run past free time. Recording every load's times makes every audit possible and shows the normal pattern. An AI logistics coordinator can treat a complete record as the default for every load, not only the long ones.
Wait time is not always detention
Some wait time is within free time. Free time is the waiting time included in the base rate, often around two hours, depending on the carrier's terms. Only wait beyond free time becomes a charge. The records still matter for every load, because nobody knows in advance which loads will run long.
The cost of missing records
Missing records cost money in both directions. The shipper may pay detention it does not owe because it cannot prove otherwise. Or it may refuse valid detention and strain a carrier relationship because it cannot confirm the wait. Both outcomes are avoidable with a few timestamps per load. An AI logistics coordinator can show how many recent detention lines had no supporting records, which makes the cost visible.
Records help reduce wait time
Good records do more than support audits. They show where and why trucks wait. If most long waits happen on Monday mornings, or at one door, operations can fix the cause. An AI logistics coordinator can summarize wait times from the records and point to patterns.
Which records are strongest, and how should they be captured?
The strongest records are made at the time, by the facility, with a time and a signature or system entry. An AI logistics coordinator should collect them in a consistent format for every load.
Start with what the facility already has
Many facilities already capture some of these times: a gate guard's sheet, a door schedule, or a WMS entry. Start with those. Adding a new process is harder than using an existing one. An AI logistics coordinator can read the records the facility already keeps and point out which times are missing.
Gate logs
A gate log records when a truck enters and leaves the property. Many facilities use a guard or an electronic gate system. A gate log is strong because it is made at the time by someone independent of the carrier. If the facility has one, link it to each load by trailer number, carrier, and appointment.
Door assignment time
The time a door was assigned is often overlooked. A truck may check in on time but wait an hour for a door. That hour is usually the facility's responsibility. Recording the door time shows how much of the wait came from door availability. An AI logistics coordinator can compare check-in and door times to find where the wait started.
Signed BOL times
Drivers often write their in and out times on the BOL, and the dock signs it. A signed BOL with both times is strong evidence because both parties agreed to it. The dock should check that the times are filled in and correct before signing. An AI logistics employee can flag BOLs that arrive without times.
Electronic logging data from carriers
Carriers may share arrival and departure data from electronic logging devices. An electronic logging device, or ELD, records a truck's location and the driver's hours. This data can confirm or challenge the shipper's records. It is the carrier's record, so many shippers rank it below their own gate log. An AI logistics employee can use it as a supporting source when the shipper's record is missing.
Dock system entries
Some warehouses record door assignments and loading times in a warehouse management system. A warehouse management system, or WMS, is software that runs warehouse operations. These entries are precise and timestamped. If available, they are a strong source for loading start and end.
Common cause codes
A short list of cause codes keeps notes consistent: freight not ready, dock short-staffed, door not available, truck early, truck late, wrong equipment, paperwork missing, and other with a note. Codes are faster to record than free text and easier to report on. An AI logistics coordinator can read the code and apply the matching rule in the audit.
Cause notes
A cause note explains why a delay happened: freight not ready, short-staffed dock, truck arrived late, wrong equipment, or missing paperwork. Cause notes are what turn a time record into a fair decision. They should be short and specific, such as "freight staged at 2:40 p.m., production delay."
Driver acknowledgement
When the driver signs the BOL with in and out times, the carrier has agreed to the record. That agreement makes disputes rare. If the driver refuses to sign or writes different times, the dock should note it. An AI logistics employee can flag BOLs where the driver's times differ from the dock's, so the difference is resolved early.
Photos
Some facilities photograph the trailer and the BOL at check-in and release. Photos add evidence of the time and condition. They are helpful in disputes about damage or seals but are not required for every load. A seal is a numbered tag that locks the trailer door and shows whether it was opened.
Time zones and clocks
Facility clocks, gate systems, and carrier devices may not agree exactly. A few minutes' difference is normal. Records should use the facility's local time, with the time zone noted. An AI logistics employee can convert carrier times into the facility's time and allow a small tolerance when comparing sources.
Capture at the moment, not at the end of the shift
Records written at the end of the shift are often guesses. Times recorded at the moment are accurate. A simple process, such as a tablet at the dock door or a check-in form that captures the time automatically, makes this easier. An AI logistics coordinator can link these records to the load as they are made.
One record per stop
Each stop on a multi-stop load needs its own record. An AI logistics coordinator should keep them separate, so each stop's wait can be checked.
Hypothetical example: a record that settled a charge
This example is hypothetical and does not describe a real customer. A distributor's dock records check-in at 7:58 a.m. for an 8:00 a.m. appointment, loading start at 8:20 a.m., loading end at 9:40 a.m., and release at 9:55 a.m. Two weeks later, the carrier bills two hours of detention for that stop. The AI logistics coordinator compares the invoice with the dock record. Total time on site was about two hours, within free time. The coordinator disputes the line with the record attached, and the carrier removes it.
How should the records be linked to the invoice?
The records should be linked to the load at the time they are made, and the load should be linked to the invoice line when the invoice arrives. An AI logistics coordinator should make both links, so the audit can run without searching.
Scan paper records the same day
Paper gate sheets and BOLs should be scanned the same day. An AI logistics coordinator can then read and link them before they are lost.
Link records to the load
Each dock record should carry a reference to the load: the load number, the purchase order, the BOL number, or the appointment number. Without a reference, records cannot be matched later. An AI logistics employee can attach records to the load as they are created or scanned.
Ask carriers to reference the load
Ask carriers to include the shipper's load or BOL number on every invoice line. A routing guide can set this requirement. A routing guide is a document that tells carriers how to work with the shipper. Lines with the right reference match quickly; lines without one need extra work. An AI logistics coordinator can flag carriers that often omit references.
Link the invoice line to the load
Carrier invoices use their own reference numbers. The audit must match each line to the right load and stop. Matching by several fields, such as BOL number, date, and location, reduces errors. An AI logistics coordinator can match lines and flag those it cannot match.
Use a source preference order
When records disagree, a written order of preference decides which one counts. Many shippers use the gate log first, the signed BOL second, and the carrier's record third. Sharing this order with carriers in advance reduces disputes. An AI logistics coordinator can apply the order on every line and record which source it used.
Approve quickly when records match
When the records match the invoice, approve quickly. Fast payment of valid charges is part of a fair process. An AI logistics employee can approve matching lines within rules the same day the invoice arrives.
Compare and decide
With records and invoice linked, the audit compares the billed time with the recorded time under the carrier's terms. The result is approve, adjust, or hold. Wilson audits and reconciles each carrier invoice against what was booked. Payments above approval limits or outside the rules wait for a person.
Hypothetical example: matching a line to the right stop
This example is hypothetical and does not describe a real customer. A carrier invoice lists "detention, 2 hours" on a load with three stops but does not say which stop. The AI logistics coordinator compares the dock records for each stop. Two stops were under an hour. The third shows a three-hour wait caused by a late receiving crew. The coordinator matches the charge to the third stop, confirms it under the terms, and approves it.
Keep records with the shipment
Keep dock records with the shipment record at least until the invoice is paid and any dispute is closed. Many teams keep them longer for audit and analysis. Wilson keeps searchable shipment records with change history.
Records for customer recovery
When a delivery wait is caused by the customer's dock, the shipper may recover the cost under its sales terms. The receiver's records, or the carrier's evidence, support that recovery. An AI logistics employee can flag delivery waits at customer docks and attach the records, so finance can decide whether to bill the customer.
Common linking mistakes
- Records with no load reference. They cannot be matched.
- Paper logs never scanned. They are lost or unreadable.
- Times without dates. The record cannot be tied to the right day.
- Delivery records never requested. Delivery charges cannot be checked.
How do you make documentation a habit at the dock?
Make documentation a habit by keeping it short, building it into existing steps, and showing dock staff how it helps. An AI logistics coordinator can reduce the effort by capturing what it can automatically and asking people only for what they alone know.
Train new dock staff
New dock staff should learn the record steps on their first day. A one-page guide with the times to capture and the cause codes is enough. An AI logistics employee can flag records from new staff that are incomplete, so supervisors can coach early.
Keep it short
A dock record should take seconds, not minutes. Check-in time, door time, start, end, release, and a cause note when needed. Long forms get skipped. A short form gets done.
Build it into existing steps
Dock staff already check in trucks, assign doors, and sign BOLs. Add the time capture to those steps. For example, the check-in step records the time automatically, and the BOL signing step requires in and out times. No extra task is needed.
Make records visible to the dock
Dock staff are more careful when they see their records being used. A simple daily view of trucks checked in, times captured, and records missing helps. The view can also show trucks waiting longer than free time right now, so the dock can act before detention starts. An AI logistics coordinator can provide that view for each facility.
Use the facility's own systems
If the facility has a gate system or a WMS, use its timestamps. They are already captured. The AI logistics employee can read them and link them to the load, instead of asking staff to write the same times again.
Shift handoffs
Trucks that arrive near a shift change are the most likely to have missing records. The outgoing shift checks the truck in; the incoming shift loads it and forgets the times. A short handoff note for trucks on site at shift change helps. An AI logistics employee can list trucks on site at each shift change so the incoming lead knows which records to complete.
Show why it matters
Dock staff are more likely to keep records when they see the result. Share how records settled detention disputes or revealed a staffing problem on a certain shift. Records that lead to fewer complaints and better schedules earn support.
Celebrate complete records
Recognize docks with complete records. An AI logistics employee can report completion rates by facility each week.
Hypothetical example: a new habit
This example is hypothetical and does not describe a real customer. A food plant's dock rarely wrote times on BOLs. Detention disputes took weeks and usually ended with the plant paying. The plant adds a required in and out time field to its BOL and a quick door-assignment log. The AI logistics coordinator flags any BOL missing times the same day. Within a month, most BOLs have times, and detention disputes resolve in days.
How should you evaluate software that uses wait-time records?
Evaluate software by giving it dock records and carrier invoices for the same loads and checking whether it links them, uses the right times, and decides correctly. An AI logistics coordinator should make the records useful without adding work at the dock.
Demo tests for wait-time records
| Buyer requirement | Demo test | Evidence to see |
|---|---|---|
| Captures dock times | Load a gate log and signed BOL | Times linked to the load |
| Flags missing times | Submit a BOL without times | Flag sent the same day |
| Records causes | Add a "freight not ready" note | Cause saved with the load |
| Links invoice lines | Load a detention invoice | Line matched to the load and stop |
| Decides fairly | Bill time within free time | Line disputed with the record |
| Requests delivery records | Bill delivery detention | Receiver asked for records |
| Shows patterns | Review a month | Wait times by facility and cause |
Demo questions about wait-time records
- How does the AI logistics coordinator receive gate, BOL, and WMS times?
- How are records linked to loads?
- How are missing times flagged?
- How are cause notes captured?
- How are delivery records requested from receivers?
- Can we see wait time by facility, door, and shift?
Ask how records reach the load
Ask the vendor exactly how a gate time or a signed BOL reaches the load record. Is it scanned, read from email, pulled from a system, or typed? Each path has different reliability. The AI logistics coordinator should show where each time came from.
How to measure wait-time documentation work
Track the share of loads with complete dock records. Count detention charges settled by the records. Measure average wait time by facility over time. These measures show whether the AI logistics employee turns records into fair decisions and shorter waits.
Test a delivery charge
Include a delivery detention charge at a customer's dock. Watch whether the AI logistics coordinator requests the receiver's records and holds the line until they arrive. Delivery charges are where shippers have the least evidence by default.
Scoring the wait-time records demo
Score each test as pass, partial, or fail. A pass means records were captured, linked, and used correctly. A partial means records existed but had to be found by hand. A fail means invoices were approved without dock records.
Warning signs in a wait-time records demo
- The software expects dock staff to type times into a separate system.
- Records are not linked to loads.
- There is no flag for missing times.
- Delivery records are never requested.
Where does Wilson fit in documenting wait time?
Wilson, by Cartage, is an AI logistics coordinator that books and tracks each load it runs and keeps searchable shipment records with change history, including documents such as bills of lading and proofs of delivery. It audits and reconciles each carrier invoice against what was booked before payment.
Wilson replaces the TMS for freight execution and connects to the company's ERP through a method that fits the customer's environment. Customers use the Wilson Wallet to pay their carriers. Payments above approval limits or outside the rules wait for a person.
What Cartage asks about dock records in discovery
Cartage asks how each facility checks in trucks, whether it has a gate system or a WMS, how BOLs are signed, and how detention is reviewed today. These answers shape how an AI logistics coordinator collects and links wait-time records.
What Wilson does not do for wait-time records
Wilson does not run the facility's dock or replace its gate system or WMS. The records available depend on each facility's process. Specific connections to gate systems or WMS data should be confirmed in a demo. Exact ERP connection details depend on the customer's systems.
Reports on wait time
Over time, wait-time records show which facilities, doors, shifts, and carriers have the longest waits. Wilson can use shipment data from the loads it runs to produce carrier-performance reports on request. Operations can use those reports to change staffing and appointment slots where waits are longest.
Where teams start with wait-time records
Most teams start their AI logistics coordinator on a few lanes and expand from there. Timing depends on scope. Cartage helps identify the first workflow during discovery. Teams often start with their own busiest pickup dock, where they control the records.
Teams auditing before payment can read about freight invoice audit before payment. Teams reducing surprises can see how to check accessorial charges before booking. Both topics shape how an AI logistics coordinator handles wait-time charges. For the full cycle, review how AI handles freight invoice audit, reconciliation, and payment.
This article is part of our complete guide to driver arrival and detention records.
FAQs
How do you document carrier wait time before approving an invoice?
Record check-in, door, loading start and end, release, and the cause of any delay at the dock as it happens, and link the records to the load. An AI logistics coordinator can then compare them with the invoice.
Which wait-time records are strongest?
Gate logs, signed BOLs with in and out times, and WMS timestamps made at the time. An AI logistics employee should use them in a written order of preference.
Why record the cause of a delay?
The cause decides whether the wait is billable. An AI logistics coordinator should exclude carrier-caused waits under the terms.
How do you get delivery wait-time records?
Ask the receiver for its dock times or signed BOL. An AI logistics employee can request them when a delivery charge needs review.
Sources
- Cartage, Wilson product scope and pricing position, November 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator links your gate log and signed BOL times to each load, and uses them to approve or dispute a detention line: talk to the Cartage team.