To measure detention and dwell time at your own docks, record the same eight clock events for every truck visit, each from a named source: arrival, check-in, door assigned, docked, loading or unloading started, finished, paperwork released and check-out. Dwell time is check-out minus arrival. Detention is the part of that time beyond the free time in your carrier agreement, counted from the moment your agreement says the clock starts. Store your own timestamps, split dwell into segments that show where the wait happened, and reconcile them with the in and out times on the bill of lading before you approve or dispute a charge.
The reason to build this yourself is that nobody else has the data. In a January 2018 audit, the US Department of Transportation’s Office of Inspector General found that “accurate industrywide data on driver detention do not currently exist because most industry stakeholders measure only time spent at a shipper or receiver’s facility beyond the limit established in shipping contracts” (DOT OIG, ST2018019). The same report found that available electronic data “cannot readily discern detention time from legitimate loading and unloading tasks.”
Your gate, yard and warehouse systems can see what carrier data cannot: when the truck was called to a door, when the first pallet moved and when the paperwork was ready. This guide defines the terms, lists the events and their sources, shows how to split dwell into segments, walks through a detention dispute, and covers the reports and system changes that make the numbers stick.
Dwell time and detention are different numbers
Dwell time is all the time a truck spends at your facility. Detention is only the part of it that the carrier can bill, or that counts as delay, under the agreement between you and the carrier. If your facility reports dwell and the carrier bills detention, the two numbers will never agree, and neither side is wrong.
| Term | Working definition | Where the definition comes from |
|---|---|---|
| Dwell time | “The total time spent by a truck at a facility” | DOT OIG, ST2018019 |
| Detention (carrier view) | “The period of time that a driver spends waiting for a shipment to be loaded or unloaded beyond the agreed-upon time” | Old Dominion Freight Line, carrier guidance |
| Detention (research view) | “Any time spent waiting at a shipper or receiver’s facility that is not spent performing” loading, unloading, paperwork, inspection and securing tasks | DOT OIG, ST2018019, full report |
| Free time | The loading or unloading time your agreement allows before charges start | Your carrier contract or the carrier’s rules tariff |
There is no single legal definition. FMCSA said so directly in 2023: “there is currently no standard definition of detention time,” but the industry, the government and academic research “have typically used dwell time … exceeding 2 hours to define when detention time occurs” (88 FR 58060). The OIG’s report adds that contracts “may entitle carriers to fees for any additional time spent at facilities, typically 2 hours,” and notes that “not all shipping contracts include detention pay clauses.”
Why the billable number hides the problem
The OIG report gives an example worth repeating. A driver arrives, waits one hour, and needs one more hour to load. Under a contract allowing two hours, the driver is unlikely to record the hour of waiting as detention, because nothing was billable. That hour of queueing is still a cost: it is labor on the carrier’s side, a door not turning on yours and part of the driver’s working day.
If you only track billed detention, you see the trucks that crossed the threshold and none of the waiting that came before it. Measure dwell for every visit, split into segments, and treat billable detention as one report among several.
When the clock starts depends on the appointment
Your carrier agreement should say exactly when free time starts. These are the choices to settle in writing, with what each means for measurement:
| Situation | Option to agree in the contract | What your system must record |
|---|---|---|
| Truck arrives before its appointment | Free time starts at the appointment time, not at arrival | Appointment time and arrival time |
| Truck arrives on time | Free time starts at arrival or check-in | Arrival time and its source |
| Truck arrives after its appointment | Free time starts when you assign a door, or the appointment is treated as forfeited | Arrival time, door assignment time, late flag |
| Drop trailer, no driver waiting | No driver detention; any trailer hold charge follows its own terms | Trailer drop and pickup times |
Whatever you agree, the measurement must store the raw events, not only the computed result. If the contract changes, you can recompute history; if you stored only “billable minutes,” you cannot.
Why detention matters beyond the invoice
Detention costs a carrier hours it cannot get back, and federal hours-of-service rules make those hours scarce. Under 49 CFR 395.3, a property-carrying driver needs 10 consecutive hours off duty before driving, may not drive after 14 consecutive hours since coming on duty, and may drive a total of 11 hours in that period. The 14 hours run consecutively, so time spent waiting at your dock uses them up whether or not the truck moves.
The OIG estimated the wider effects in its 2018 report, using 2013 dwell data and the assumption that dwell beyond two hours represented detention:
- “A 15-minute increase in average dwell time … increases the average expected crash rate by 6.2 percent.”
- Detention “is associated with reductions in annual earnings of $1.1 billion to $1.3 billion” for for-hire drivers in the truckload sector.
- For truckload carriers, detention “reduces net income by $250.6 million to $302.9 million annually.”
The OIG also recommended that FMCSA collect “reliable, accurate, and representative data on the frequency and severity of driver detention times,” and FMCSA concurred. FMCSA’s 2019 request for information summarized its own earlier study: drivers “experienced detention time during approximately 10 percent of their stops for an average duration of 1.4 hours beyond a commonly accepted two-hour loading and unloading period” (84 FR 26932). It added that the studies “were not able to separate normal loading and unloading times … from detention time,” which it called “a critical data gap.”
FMCSA’s follow-up study is designed around that gap. Its 2023 notice describes collecting 12 months of data from up to 80 carriers with up to 2,500 vehicles, drawn from “electronic logging devices (ELDs), transportation management systems (TMS), vehicle telematic systems, safety records, and answers to questions delivered through the carriers’ dispatching systems” (88 FR 58060). The federal study still has to infer what happened inside your gate from outside it. You do not.
Regulators are still working on the problem. In September 2025, FMCSA proposed a “Split Duty Period Pilot Program” under which about 256 participating drivers could extend the 14-hour window with one pause of 30 minutes to 3 hours taken at a pickup or delivery location, “including what is sometimes called ‘detention time’” (90 FR 44872). In October 2026 it published the pilot’s information collection for comment, with comments due December 7, 2026 (91 FR 63640). None of this changes what you owe a carrier, but it is part of why carriers care how long your facility holds their drivers, and why your dock times are worth getting right.
The clock events to record at your dock
Record eight events for every visit. Each one needs a precise definition, because “arrived” can mean the street, the gate queue or the guard shack, and those can be far apart in time.
| # | Event | Definition to write down | Best source | Backup source |
|---|---|---|---|---|
| E1 | Arrived | Truck enters your property or joins the gate queue | Geofence entry from the carrier’s tracking feed, or a gate camera | Driver’s stated time at check-in |
| E2 | Checked in | Gate transaction completed: driver, trailer, seal and reference captured | Gate or yard system | Guard log |
| E3 | Door assigned | Driver told which door to use | Yard or dock scheduling system | Text or radio log |
| E4 | Docked | Trailer at the door and secured | Dock lock or leveler sensor, door scan | Dock lead’s entry |
| E5 | Work started | First pallet moved on or off the trailer | First receiving or loading scan in the WMS | Dock lead’s entry |
| E6 | Work finished | Last pallet moved; trailer ready to close | Last scan, or trailer closed in the WMS | Dock lead’s entry |
| E7 | Paperwork released | Bill of lading or receipt signed and handed to the driver | Shipping or receiving system release | Signature time on the bill of lading |
| E8 | Checked out | Truck leaves through the gate | Gate system | Geofence exit, guard log |
For drop trailers, replace E3 to E6 with the trailer’s own moves: dropped at a yard spot, pulled to a door, unloaded, returned to the yard and picked up. The driver’s dwell ends at drop; the trailer’s dwell continues.
Waiting you cannot see from the gate
Some waiting happens before E1 by your definition. Drivers who arrive early may park at a truck stop or on the street until their slot, and a queue that backs out of your gate onto the road is invisible to a gate system that starts at the guard shack. Decide whether your arrival event is the property line, the queue or the gate, and if the queue regularly leaves your property, use a geofence drawn around the approach as the arrival source. Also count the visits that never happen: trucks turned away for missing appointments or rescheduled because doors were full. They are not dwell, but they are the same problem showing up as a rebooked load instead of a detention invoice.
Rules that make the events usable
- One visit ID ties all eight events together, created at check-in and printed on the gate pass.
- Every event stores its source, such as “gate system,” “WMS first scan” or “driver statement.” When two sources disagree, you need to know which one you used.
- Every time carries a time zone. A facility near a time zone line, or a carrier system that reports in UTC, will otherwise create phantom hours.
- Corrections are new records. If a supervisor fixes a missed scan, keep the original, the correction, who made it and why.
- Missing events stay missing. Do not fill gaps with averages. A visit without E5 and E6 is still useful for total dwell, but not for segments.
Where each timestamp comes from
Your own systems are the best source for everything that happens inside the gate. Carrier feeds and ELD-based location are best for arrival and departure, with known precision limits. The bill of lading is the paper record both sides already sign.
| Source | Events it can prove | Who controls it | Precision and limits |
|---|---|---|---|
| Gate or yard system | E1 (if the queue is inside the gate), E2, E3, E8 | You | As good as your process; a guard who keys times later tends to produce round numbers |
| Dock door sensors or door scans | E4 | You | Precise if every door has one; manual entries drift |
| WMS scans | E5, E6 | You | Precise for scanned freight; floor-loaded cartons may be scanned after the trailer is empty |
| Shipping or receiving system | E7 | You | Release time is clear only if the signature is captured in the system |
| Carrier tracking feed with a geofence | E1, E8 | The carrier or its visibility provider | Depends on the device; FMCSA’s own detention study uses “GPS data and geofenced shipper/receiver facility data to obtain arrival and departure information” |
| ELD records | Duty status changes near your site | The carrier | The ELD specification puts reported position accuracy on the order of plus or minus 1 mile and allows a clock deviation from UTC of up to 10 minutes |
| X12 214 status messages | Arrival, loading or unloading completed, departure | The carrier | The carrier’s own report; timing depends on the driver or device that triggers it |
| Bill of lading in and out times | E1 or E2, and E8 | Written by the driver, signed or not by your staff | The OIG found drivers “may note times of arrival and departure on bills of lading,” but shipper representatives “do not always sign” |
The ELD limits come from the federal functional specification. Appendix A to subpart B of part 395 requires position measurement accurate to ±0.5 mile and says that, combined with reporting precision, “position reporting accuracy will be on the order of ±1mile.” It also allows ELD time to deviate from UTC by up to 10 minutes. Under 49 CFR 395.26, the ELD records location at duty status changes and makes an intermediate recording when the vehicle has been in motion for an hour without one. An ELD log is built for hours-of-service compliance, not for telling your yard from the business next door. Carrier tracking that uses a separate GPS feed and a drawn geofence around your property is better suited to arrival and departure.
Which 214 codes describe a dock visit
If carriers send you X12 214 Transportation Carrier Shipment Status Messages, these status codes from the X12 release 4010 list for element 1650, as reproduced in Stedi’s public EDI reference (a secondary source), map to your events:
| Code | X12 meaning | Your event |
|---|---|---|
| X3 | Arrived at Pick-up Location | E1 at a shipping dock |
| X8 | Arrived at Pick-up Location Loading Dock | E4 at a shipping dock |
| CP | Completed Loading at Pick-up Location | E6 at a shipping dock |
| AF | Carrier Departed Pick-up Location with Shipment | E8 at a shipping dock |
| X1 | Arrived at Delivery Location | E1 at a receiving dock |
| X5 | Arrived at Delivery Location Loading Dock | E4 at a receiving dock |
| D1 | Completed Unloading at Delivery Location | E6 at a receiving dock |
| CD | Carrier Departed Delivery Location | E8 at a receiving dock |
Each carrier’s 214 implementation guide says which of these it sends. Treat them as the carrier’s claim and your gate records as yours.
Choosing the time of record
When sources disagree, pick the time of record by a fixed rule written in advance, not case by case. A workable order of preference for arrival is: your gate system, then a carrier geofence entry, then the 214 arrival status, then the bill of lading. For departure: your gate system, then geofence exit, then the 214 departure status. For the events inside the gate, only your own systems qualify. Publish the rule to carriers along with your appointment procedure, so a dispute starts from agreed evidence.
Splitting dwell into segments that point at causes
A single dwell number tells you that trucks wait; segments tell you where and who can fix it. Split each visit into six segments using the eight events, then report the segments separately.
| Segment | Formula | Usually owned by | What a long segment suggests |
|---|---|---|---|
| Gate queue | E2 − E1 | Gate or security | Check-in steps that take too long, one guard for many arrivals |
| Yard wait | E3 − E2 | Dock scheduling | Doors full, appointments overbooked, early arrivals |
| Docking | E5 − E3 | Dock lead | Driver slow to find the door, no crew ready, equipment missing |
| Work | E6 − E5 | Receiving or shipping crew | Freight type, labor short, freight not staged, mixed pallets |
| Paperwork | E7 − E6 | Shipping or receiving office | Bill of lading not ready, counts disputed, signatures waiting |
| Exit | E8 − E7 | Gate or security | Exit checks, seal verification, queue at the gate |
These causes line up with what carriers themselves told FMCSA. In the comments summarized in its February 2024 notice, commenters described “understaffed shipper/receiver facilities leading to backups,” “difficult driver check-in procedures,” “products being processed at loading,” “shippers/receivers not honoring appointment times,” “lack of room in storage facilities for products to be unloaded” and “appointment times scheduled for facility shift changes or breaks” (89 FR 12413). Every one of those shows up in a specific segment.
Reading segments by group
Report each segment by the groupings that suggest a fix:
- Dock activity: inbound live unload, outbound live load, drop and hook.
- Arrival status: early, on time and late against the appointment.
- Hour of arrival and shift: to find shift changes and breaks.
- Carrier and supplier: to separate facility problems from partner problems.
- Freight type: floor-loaded, palletized, mixed pallets.
Use medians and the 90th percentile, not averages. One trailer stuck for nine hours during a system outage will move an average far more than it describes your normal day.
Example (fictional). A distributor measures one month of live visits at a single DC. Median minutes per segment:
| Segment | Inbound live unload | Outbound live load |
|---|---|---|
| Gate queue and exit | 14 | 10 |
| Yard wait | 48 | 21 |
| Docking | 9 | 7 |
| Work | 62 | 55 |
| Paperwork | 12 | 38 |
After the work itself, inbound trucks spend longest in the yard, and the early-arrival group explains much of it: trucks arriving early wait for doors that are still busy with earlier appointments. Outbound trucks lose time on paperwork, because bills of lading are printed only after loading ends and then wait for a supervisor’s signature. The two problems have different owners and different fixes, which a single dwell average would have hidden.
Reconciling your times with the bill of lading and the carrier’s claim
Settle a detention charge by comparing three records for the same visit: your event log, the in and out times on the bill of lading, and the carrier’s evidence (214 statuses, geofence times or the driver’s notes). The questions to settle are which arrival time counts and whether free time started at arrival or at the appointment.
The bill of lading matters because it is the one document both parties already handle at the dock. The OIG describes it as a document that must contain, at minimum, the shipper and receiver, origin and destination, number of packages, description of freight and weight, volume or measurement. Detention times are not on that list. They get there when a driver writes them in, and the OIG found that shipper representatives “do not always sign.” FMCSA’s 2024 notice also records commenters’ “difficulties obtaining verified documentation of detention time due to complicated paperwork.”
You can remove most of that friction yourself: print your system’s check-in time on the gate pass, and print check-in and paperwork release times on the bill of lading or receiving document your staff signs at release. Then the driver leaves with your times on a signed document, and the dispute, if any, is about the contract, not the clock.
What to put in the carrier agreement
Clear contract terms take the most arguable questions out of a dispute before it starts. Before measuring against an agreement, make sure it answers these questions in writing:
- Free time per activity. Live unload, live load and drop and hook can carry different allowances.
- When the clock starts for early, on-time and late arrivals, as in the table earlier in this guide.
- Which record counts. Name your time-of-record rule and the evidence a carrier must attach to a detention charge.
- Notice before charges. Whether the carrier must alert your dock when a truck approaches the end of free time, so someone can act before the charge starts.
- Billing unit and rounding. Whether detention is billed per started hour or per minute after free time, and how partial periods are rounded.
- Dispute window. How many days you have to dispute a charge and how many the carrier has to respond.
- Drop trailer terms. How long a dropped trailer may stay before any hold charge, measured from which event.
A carrier’s rules tariff may already define some of these. Check whether your contract incorporates that tariff; if it does, the tariff’s detention terms can matter wherever the contract is silent, so read both before the first dispute.
A dispute procedure
- Match the invoice line to a visit. Use the bill of lading or PRO number on the carrier’s invoice to find the visit ID.
- Pull the event log with sources: E1, E2, E7 and E8 at minimum, plus the appointment time.
- Apply the contract rule for when free time starts, using the time-of-record rule you published.
- Compare with the carrier’s times. Differences of a few minutes, within the 10 minutes of clock deviation the ELD specification allows, are noise, not evidence of anything.
- Classify the difference using the table below.
- Approve, adjust or dispute in writing, attaching your event log and the signed document.
- Record the outcome and reason code so you can report which carriers and causes produce the most disputes.
| What you find | Likely reason | Usual action |
|---|---|---|
| Carrier’s arrival is earlier than your check-in by more than the gate queue you measured | Driver arrived at the wrong entrance, or the geofence covers a neighboring site | Ask for the geofence evidence; rely on your gate record |
| Carrier counted from arrival; truck was early for its appointment | Contract starts free time at the appointment | Adjust to the appointment time |
| Truck arrived late and waited for a door | Contract rule for late arrivals applies | Apply the agreed rule; flag repeated late arrivals to the carrier |
| Your paperwork release was late | Facility cause | Approve; fix the paperwork segment |
| Your times and the carrier’s agree within a few minutes | No real dispute | Approve and move on |
Example (fictional). A carrier bills 1 hour 30 minutes of detention for PRO EX-778120, counting from a 6:50 arrival to a 10:20 departure with two hours free. The facility’s log shows a 7:40 gate arrival, an 8:00 appointment, paperwork released at 10:12 and check-out at 10:20. The carrier’s 6:50 geofence entry turns out to be the truck stop across the road, whose lot falls inside the carrier’s geofence. Applying the contract (free time from the appointment for early arrivals), detention is 20 minutes. The facility pays 20 minutes, sends the event log, and asks the carrier to tighten its geofence. It also notes that 8 of those 20 minutes were its own exit queue.
Turning the measurements into fewer detained trucks
Fix the largest segment first, and judge the fix by that segment’s median and 90th percentile, not by total detention billed, which also depends on contracts and carrier behavior. Each segment has its own set of levers.
Gate queue and exit. Shorten check-in to the fields you need: driver, trailer, seal, bill of lading or appointment number. Let drivers pre-register on arrival from the cab where your gate process allows it. Staff the gate to the arrival curve by hour, which your E1 data now shows.
Yard wait. Measure appointment adherence on both sides: carriers arriving inside their window, and your facility getting trucks to a door within an agreed time of the appointment. If early arrivals drive the yard wait, decide whether to work them in when doors are free or hold them to their slot, and tell carriers which. Spread appointments away from shift changes and breaks.
Docking. Have a crew and equipment at the door before the truck is called. Assign doors by freight type, so a floor-loaded trailer does not get a door with no conveyor.
Work. Stage outbound freight before the truck is called. For inbound, a ship notice with pallet labels lets receivers scan pallets instead of counting each item; our guide to inbound shipment visibility from PO to receipt covers that change and how to tie appointments to POs.
Paperwork. Print the bill of lading when loading starts, not when it ends, and correct counts at the end. Give dock leads authority to sign, so release does not wait for an office.
Drop trailers. Where volume allows, preloaded outbound trailers and dropped inbound trailers take the driver out of the wait entirely. They move dwell from the driver to the trailer, so measure trailer dwell separately.
Testing whether a fix worked
Change one thing at a time and compare like with like. Pick the segment you are attacking, record its median and 90th percentile for four weeks before the change, then four weeks after, within the same groups (dock activity, arrival status, shift). Check the neighboring segments too: printing bills of lading earlier should shrink paperwork without lengthening work, and working in early arrivals should cut yard wait without pushing on-time trucks back. If total dwell does not move while one segment shrinks, the time has moved somewhere else, and the segment report will show you where.
For trucks still inside the gate past free time, the response is an exception with an owner: a dock lead gets an alert when a visit crosses a threshold, with the segment it is stuck in. Thresholds, owners and response times for that alert belong to your shipment exception management rules.
Metrics and reports to publish weekly
Publish a small, fixed set of measures every week with the same definitions, so a change in the number means a change at the dock and not in the math.
| Measure | Definition | Group by |
|---|---|---|
| Median dwell | Median of E8 − E1 across live visits | Dock activity, arrival status |
| 90th percentile dwell | Value that 90 percent of visits fall under | Same |
| Share of visits past free time | Visits whose computed detention is above zero ÷ live visits | Carrier, dock activity |
| Segment medians | Median of each of the six segments | Dock activity, hour, shift |
| Carrier on-time arrival | Visits arriving inside the appointment window ÷ visits with appointments | Carrier |
| Facility on-time service | Visits docked within the agreed time of the appointment ÷ on-time arrivals | Shift, door group |
| Detention billed vs measured | Billed minutes ÷ minutes computed from your log | Carrier |
| Event completeness | Visits with all eight events from preferred sources ÷ all visits | Event, source |
Two of these keep the system honest. Facility on-time service measures your side of the appointment, which is the half a carrier experiences as waiting. Event completeness tells you whether the other numbers can be trusted: if half of visits are missing E5 and E6, the work segment is a guess.
Watch sample sizes. A carrier with four visits in a week can show a 90th percentile that is really one bad afternoon, so show the visit count beside every carrier-level figure and compare carriers over a month or a quarter, not a week. Compare the same weeks year over year where seasonal peaks change the arrival pattern.
Avoid a single “detention rate” without its definition. “Detention rate fell” can mean shorter waits, longer free time in new contracts or fewer visits counted.
Building it: from a gate log to connected systems
You can start measuring next week with a disciplined gate log and grow into connected systems as the data proves its value. Build in stages, keeping the same event definitions throughout so history stays comparable.
- Gate log with fixed fields. A guard or clerk records E1, E2 and E8 with the trailer, carrier, bill of lading and appointment number. A shared spreadsheet works for a few weeks if the fields are fixed and times are entered at the moment, not later.
- Dock entries. Dock leads record E3 to E7 on a handheld or tablet against the visit ID from the gate pass.
- WMS scans. Replace manual E5 and E6 with the first and last receiving or loading scans for the visit’s POs or loads, which requires the visit ID to link to them.
- Carrier feeds. Add 214 statuses and geofence events as secondary sources for E1 and E8.
- Reports and alerts. Weekly measures, then live alerts for visits past a threshold.
The data model is small. Each visit needs these fields:
| Field | Example (fictional) | Notes |
|---|---|---|
| Visit ID | V-2026-04811 | Created at check-in |
| Carrier and SCAC | EX Freight, EXFR | From the appointment or bill of lading |
| Trailer and seal | TR-55102, seal 441208 | Seal checked at check-in and release |
| References | BOL, PRO, PO or load numbers | Links the visit to POs, shipments and invoices |
| Appointment | 8:00 to 8:30 window | Original and any rescheduled time |
| Dock activity | Inbound live unload | Live, drop or drop and hook |
| Events E1 to E8 | Time, time zone, source, who entered it | Corrections kept as new records |
| Free time rule | Two hours from appointment if early | Copied from the contract in force on the day |
Clocks, time zones and sync
Segment math fails quietly when clocks disagree. Keep gate terminals, handhelds and servers synchronized to a network time source, and store every timestamp in UTC with the site’s time zone alongside it. Display local time to people, but compute in UTC. Expect carrier times to differ from yours by a few minutes even when both are right: the ELD specification itself allows up to 10 minutes of deviation from UTC. A daylight saving change during a visit should never produce a negative segment or an hour of phantom detention; test that case before go-live.
The events are tracking milestones like any other, so they belong in the same model as your inbound and outbound milestones. You can list them alongside the rest with the tracking milestone map, and connecting gate, dock, WMS and carrier events into one record is the kind of interface work behind shipment tracking software built around your systems. In our engagements we start by walking the gate and the docks with the people who work them and writing the event definitions down before anything is built, as in the first two stages of how we run an engagement, because the definitions are what both you and your carriers will be held to.
What to do next
Start with the definitions and a month of data, then decide what to build. A short checklist:
- Write the eight event definitions for your site, including exactly where “arrived” is.
- Read your carrier agreements and record, for each carrier, the free time and when it starts for early, on-time and late arrivals.
- Choose and publish the time-of-record rule for arrival and departure.
- Put a visit ID on the gate pass and start the gate log with fixed fields.
- Add dock entries for door assigned, docked, work started, work finished and paperwork released.
- Print your check-in and release times on the document your staff signs for the driver.
- After four weeks, report segment medians and 90th percentiles by dock activity and arrival status, and pick the largest segment to fix first.
- Track billed versus measured detention per carrier, and use the dispute procedure for every invoice line that does not match.
If you want help defining the events and connecting your gate, WMS and carrier data into one visit record, you can tell us how your docks run today and we will start from the events you already capture.
