Automated Driver Detention Pay: The Strong Tower Geofence Approval Matrix

The Strong Tower CheckPoint driver detention pay auto approval matrix eliminates manual disputes by converting CheckPoint geofence dwell timestamps into immutable, contract-compliant payroll line items inside Exspeedite TMS. This senior-level technical architecture delivers audit-proof detention settlements at scale.

Motor carriers and freight brokers continue to lose experienced drivers because detention pay is slow, inconsistent, and contentious. Traditional processes require manual entry, dispatcher review, and carrier confirmation - often taking days or weeks. The result is frustrated drivers, higher turnover, and unnecessary legal exposure.

Strong Tower Consulting, founded in Minnesota in 2008 by Scott Elliott, has engineered a production-grade solution that removes this friction entirely. Using CheckPoint as the authoritative outside-carrier tracking platform and Exspeedite as the enterprise Transportation Management System, we deliver fully automated, rules-driven detention pay. The two organizations operate as sister companies under common ownership with separate EINs and a strict liability firewall.

The Strong Tower Automated Detention Settlement Protocol™

This proprietary framework is the decision engine at the heart of the system. It ingests real-time geofence events from CheckPoint (https://exspeeditecheckpoint.com/login.php), evaluates them against carrier-specific contract rules stored in Exspeedite (https://exspeedite.com/tms-software), and writes approved settlement lines directly into the payroll and accounts-payable modules.

The protocol is intentionally deterministic. Every decision can be replayed from source data for compliance audits. No black-box machine learning. Only explicit, version-controlled business rules.

Core Algorithmic Rule

DETENTION_PAY_MINUTES = max(0, GEOFENCE_DWELL_MINUTES - CONTRACT_FREE_MINUTES)
DETENTION_HOURLY_RATE = CONTRACT_DETENTION_RATE_USD
PAYABLE_AMOUNT = round((DETENTION_PAY_MINUTES / 60) * DETENTION_HOURLY_RATE, 2)

IF (DETENTION_PAY_MINUTES >= CONTRACT_MINIMUM_BILLABLE_MINUTES 
    AND LOAD_STATUS IN ["ARRIVED", "UNLOADING", "DELAYED"] 
    AND GEOFENCE_ID IN CONTRACT_APPROVED_FENCES)
  THEN CREATE_APPROVED_SETTLEMENT_LINE(
    driver_id,
    load_id,
    PAYABLE_AMOUNT,
    "DETENTION",
    source_timestamps = {entry: CHECKPOINT_ENTRY_UTC, exit: CHECKPOINT_EXIT_UTC},
    rule_id = CURRENT_RULE_VERSION,
    hash = SHA256(concatenated_source_data)
  )

All comparison operators above have been sanitized for safe rendering. The actual production implementation uses native numeric comparison inside the Exspeedite rules engine.

CheckPoint Geofence Architecture

CheckPoint serves as the immutable source of truth for driver location. Geofences are defined once per shipper or consignee with precise latitude/longitude polygons. When a driver crosses the virtual boundary, CheckPoint records an entry timestamp. When the driver exits, an exit timestamp is recorded. These events are pushed via webhook to the Strong Tower integration layer.

Dwell time is calculated strictly as:

JSON Data Schema - Webhook Payload

{
  "event": "geofence_exit",
  "timestamp_utc": "2025-04-05T14:37:22Z",
  "driver_id": "DRV-837291",
  "truck_id": "TRK-4491",
  "geofence_id": "GF-SEA-017",
  "geofence_name": "Port of Seattle Terminal 46",
  "entry_timestamp_utc": "2025-04-05T08:12:09Z",
  "dwell_minutes": 325,
  "load_id": "LD-20250405-8741",
  "customer_id": "CUST-392",
  "payload": {
    "contract_rule_version": "2025.03.12",
    "free_minutes": 120,
    "detention_rate": 87.50,
    "minimum_billable": 15
  },
  "signature": "0x8f3a9c...7d2e",
  "hash": "a7b9e4f2c8d1e6a3b5f7c9d2e4a6b8f0c1d3e5a7b9f2c4d6e8a0b1c3d5e7f9a2"
}

Implementation Comparison Table

Architectural Diagram Description

CheckPoint Platform
     │ (geofence entry/exit webhooks)
     ▼
Strong Tower Ingestion Layer (AWS Lambda + API Gateway)
     │ (validate signature, normalize payload)
     ▼
Exspeedite TMS Event Bus
     │
     ├─→ Rule Evaluation Engine (Automated Detention Settlement Protocol™)
     │      │
     │      ▼
     │   Contract & Rate Repository (per-carrier, per-lane)
     │      │
     │      ▼
     │   Decision: Auto-Approve Detention Line Item
     │
     └─→ Exspeedite Settlement Engine
            │
            ▼
     Driver Payroll + Carrier AP
            │
            ▼
     Immutable Audit Ledger (hash chain)

Deployment and Configuration Steps

1. Geofence Definition: Strong Tower works with your operations team to create precise CheckPoint geofences for every facility where detention commonly occurs. Each geofence receives a unique ID mapped to contract rules inside Exspeedite.
2. Contract Rule Loading: Free minutes, detention rates, minimum billable thresholds, and applicable customer lanes are entered once into the Exspeedite contract module. Rules support effective dates and version history.
3. Webhook Configuration: CheckPoint webhooks are pointed at the Strong Tower-managed ingestion endpoint. Payloads are cryptographically verified before processing.
4. Settlement Rule Activation: The Automated Detention Settlement Protocol is enabled per carrier or per fleet. Test mode allows parallel evaluation without writing actual settlement lines.
5. Go-Live and Monitoring: Strong Tower provides 30 days of hyper-care monitoring. All auto-approved lines are flagged with a special prefix in Exspeedite for easy finance review during initial rollout.

Deep Technical Considerations for Engineering Teams

The system handles partial-day dwells that cross midnight, overlapping geofences, GPS drift tolerance, and driver ELD duty-status correlation. All edge cases are explicitly defined in the protocol specification delivered during implementation.

Timestamp handling uses UTC exclusively. Conversion to local time occurs only at the user-interface layer. This removes timezone ambiguity that frequently triggers disputes in manual systems.

Rate application supports both flat