Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

PRD: CXT & GigSafe Integration

1. Executive Summary

One-sentence positioning

Continuously verified, policy-aware dispatch" that turns compliance into a competitive advantage by preventing the assignment of non-compliant drivers in real-time.

Problem We’re Solving

Currently, compliance management is manual, reactive, and fragmented across custom fields. Dispatchers lack immediate visibility into driver status, leading to the risk of assigning orders to drivers with expired credentials (licenses, insurance, etc.)5. This creates significant legal and insurance liability, particularly for regulated healthcare and pharma logistics.

Proposed Solution (High Level)

An API-first integration where GigSafe acts as the "System of Record" for driver onboarding and compliance. Verified data is automatically synced into CXT, updating driver profiles and imposing "hard stops" in dispatch logic to prevent non-compliant assignments

Primary Value Delivered

  • Risk Reduction: Automatically blocks non-compliant drivers from handling sensitive orders.

  • Operational Efficiency: Eliminates manual auditing and "chasing" drivers for documents.

  • Revenue Enablement: Allows customers to rapidly scale into regulated markets (Healthcare, Pharma) with minimal administrative friction.

Who This Is For

  • Buyer: Last-mile carriers and 3PLs operating in regulated/enterprise accounts.

  • Primary Users: Dispatchers, Operations Managers, and Fleet Managers.

2. Strategic Context & Alignment

2.1 Why Now

Regulatory requirements (e.g., FMCSA DOT, HIPAA) are increasing, and customers need documented compliance at dispatch time. The current architecture, proven by the CXT <-> Dropoff
<-> GigSafe pilot, is ready to be productized into a scalable marketplace offering.

2.2 Strategic Alignment

  • Marketplace Strategy: This reinforces CXT's Marketplace by adding a high-value "Featured" integration that drives add-on revenue.

  • Differentiation: Offers a unique "Compliance Guard" capability that competitors relying on manual uploads cannot match.

2.3 Non-Goals (Phase 1)

  • Two-Way Sync: We are not pushing settlement or performance data back to GigSafe in Phase 1.

  • In-App Onboarding: Drivers will not yet complete GigSafe steps directly inside the CXT Driver Mobile App.

  • SSN Sync: Social Security Numbers are explicitly flagged as "Do Not Sync" for security compliance.

3. Problem Statement & Opportunity

3.1 Current State

  • Fragmented Data: Compliance data is stored in brittle USER_DEFINED_FIELDS (e.g., HIPAA status in Field 12 vs Field 4), making standard integrations impossible.

  • Manual Workarounds: Dispatchers must manually cross-reference external files or spreadsheets to verify if a driver is clear to take a job.

3.2 Impact

  • Business Risk: High exposure to lawsuits and insurance claims if an unlicensed driver causes an incident.

  • Inefficiency: Significant administrative time spent manually updating expiration dates and onboarding drivers.

3.3 Opportunity

By solving this, CXT becomes the only platform that offers "Compliance-aware dispatch," a massive differentiator for winning enterprise medical and pharma contracts.

4. User Experience: End-to-End Journey

This section describes how users discover, enable, and live with the feature over time.

4.1 Feature Discovery

  • Marketplace: Users discover the "GigSafe" tile in the "Featured" section of the CXT Marketplace.

  • In-App: Pendo Guide/announcement highlight the new "Compliance Guard" capabilities.

4.2 Activation & Access Control

  • Setup: A self-service Partner workflow (opens externally) linked from the Marketplace.

  • Automation: The system automatically creates necessary API users (e.g., InetUser) so customers don't have to manage credentials manually.

  • Configuration: Users select "Warn vs. Enforce" modes for compliance failures during the rollout phase.

4.3 Post-Activation Experience (Steady State)

  • Visual Dispatch Board: Dispatchers see visual signifiers (icons/badges) indicating compliance status directly on the board.

  • Drivers Page: Clear status indicators for "Active," "Suspended," or "Non-Compliant" based on GigSafe data.

  • Failure States: If a driver is non-compliant, the system enforces a hard stop, preventing order assignment.

5. Scope & Phasing

Phase 1: MVP / Initial Release

  • Direction: One-way data sync (GigSafe → CXT).

  • Core Capability: Auto-creation and activation of drivers in CXT upon GigSafe onboarding.

  • Enforcement: "Hard-stops" in dispatch logic if compliance fails.

  • Data Model: Migration to standardized System Constants for key attributes.

Phase 2: Future Enhancements

  • Bi-Directional Sync: Pushing settlement data back to GigSafe.

  • Native Mobile Experience: Drivers completing GigSafe onboarding within the CXT driver app.

6. Functional Requirements

6.1 Core Behaviors

  • System of Record: GigSafe is the authoritative source for all driver credential data.

  • Lifecycle Automation:

    • Creation: When a driver completes onboarding in GigSafe, a CXT Driver Profile is automatically created.

    • Activation: Driver status is set to "Active" only when fully compliant.

    • Deactivation: If a document expires (e.g., insurance), the driver status in CXT immediately updates to inactive/suspended.

6.2 System Standardization

  • Requirement: Engineering must replace custom USER_DEFINED_FIELDS with standardized System Constants for: License Expiration, Insurance Status, Background Check, and Drug Test.

7. System Architecture & Technical Considerations

7.1 Data Flow

  • Source: GigSafe

  • Destination: CXT Driver & HR Records (via CXT WebServices)

  • Mechanism: APIs and webhooks; no custom stored procedures or file retrievals.

7.2 Key Technical Decisions

  • Standardization: Moving away from custom fields to a standardized data model to support robust API integrations.

  • API Usage: Integration should be designed to not consume customer API credits.

8. Data Model & Schema Strategy

The integration will standardize the following critical data points using new System Constants.

Category

Data Attributes

CXT Mapping / Action

Identity

Name, Email, Phone, DOB, Address

Create Driver Profile (HR > General Tab)

 

Vehicle

Make, Model, Year, VIN, Type

Sync to Vehicle Profile / Vehicle Record

 

Compliance

Driver License (Exp Date), CDL

Sync to System Constants (HR > Advanced Tab)

 

Background

Background Check Status, MVR

Sync to System Constants

 

Insurance

Commercial Auto, Cargo, Occ. Acc.

Sync to System Constants (HR > Dates Tab)

 

Training

HIPAA, Bloodborne, HazMat

Sync to Capabilities / Custom Critical Dates

 

Status

ActivatedAt, DeactivatedAt

Trigger Driver Status Change (Active/Terminated)

 
Note: SSN, Bank Info, and other PII are explicitly excluded from sync.

9. Monetization, Packaging & Enablement

9.1 Pricing & Packaging

  • Model: Marketplace Listing + Manual Setup with GigSafe.

  • Billing: No direct customer billing. GigSafe and CXT have a pending revenue sharing agreement for remuneration.

  • Pricing Unit: Per active driver / month.

9.2 Enablement

  • Sales: Co-sell motion with GigSafe providing back-to-back SLA and support playbooks.

  • Support: Operations app and dispatch issues handled by CXT; credential sourcing/validation issues routed to GigSafe.

10. Success Metrics

Primary Metrics

  • Adoption: % of customers enabling the integration via Marketplace (Target: Net new installs/week).

  • Revenue Protection: Zero instances of non-compliant drivers executing regulated orders.

  • Market Impact: Win-rate lift in regulated deals (Healthcare/Pharma).

Partner Metrics

  • Pipeline: Referred pipeline $, SQLs, and attach rate of the add-on.

11. Risks & Tradeoffs

11.1 Operational Risks

  • False Positives: A "false positive" compliance failure could disrupt operations.

    • Mitigation: Add "Warn vs. Enforce" modes and an override capability with an audit trail.

  • Legacy Data: Existing drivers may have data in custom fields.

    • Mitigation: Need a migration plan to map legacy USER_FIELD data to new System Constants. This can be done on a case-by-case basis when customers are configured.

11.2 Business Risks

  • Liability: Confusion over who is liable for a bad driver.

    • Mitigation: Clear demarcation—CXT enforces the policy, but GigSafe attests to the credential status.

12. Delivery Plan

13. Appendix & Links

PRD Quality Bar (Checklist)

Before marking this PRD “Ready”:

  • Clear user journey from discovery → mature state
  • Explicit non-goals documented
  • System boundaries defined
  • Activation and permissions clearly stated
  • Success metrics agreed upon