Appearance
Governance & Assumptions
Document ID: PLCY-GOV-001
Version: 1.0
Effective Date: December 22, 2025
Last Review: December 22, 2025
Owner: Hop And Haul Team
CONFIDENTIAL
This document is CONFIDENTIAL and for internal use only. Do not distribute outside the organization.
1. Foundational Assumptions
This documentation assumes the following operational model:
1.1 Hop And Haul is an Independent SaaS Company
Hop And Haul operates as a standalone software company providing matching services under contract. Hop And Haul is NOT:
- A fleet operator
- An employer of drivers
- A motor carrier
- Responsible for DOT/FMCSA compliance of customer operations
Hop And Haul provides software as a service. The customer (fleet operator) retains full operational control and liability.
1.2 Customer Relationship Model
| Aspect | Hop And Haul Role | Customer Role |
|---|---|---|
| Matching algorithm | Provide and maintain | Configure, accept/override |
| Driver eligibility | Query customer systems | Define requirements, authorize drivers |
| Safety policies | Enable platform controls | Define and enforce policies |
| Liability | Software errors/negligence only | Full operational liability |
| Regulatory compliance | Support through features | Bear responsibility |
| Employment relationship | None | Employer of all drivers |
| Vehicle ownership | None | Owner/lessor of all vehicles |
| Insurance | None | Maintain required coverage |
1.3 Customer Operational Authority
Customers retain FULL operational control:
| Capability | Description |
|---|---|
| Match override | Customer can override or reject any automated match |
| Global visibility | Full dashboard access to all operations in real-time |
| Dispatching mode | Can switch to manual dispatch at any time |
| Configuration | All safety parameters are customer-configurable |
| Integration | Hop And Haul integrates INTO customer workflow, not the reverse |
1.4 Autonomous Operation (Default Mode)
The platform's core value proposition is autonomous matching:
- Matches drivers on routes requiring minimal deviation
- Pre-validates safety, HOS, insurance automatically
- Executes matches without manual dispatcher intervention
- Logs all decisions for customer review and audit
Customer can disable autonomy at any time and operate in full manual dispatch mode where every match requires explicit dispatcher approval.
1.5 Liability Structure
| Event Type | Liable Party | Hop And Haul Role |
|---|---|---|
| Driver accident | Customer (employer) | Provide incident detection and logging |
| HOS violation | Customer | Provide validation; customer owns ELD data |
| Insurance gap | Customer | Query insurance system; customer maintains policy |
| Matching algorithm error | Hop And Haul | Fix defect, document issue |
| Platform downtime | Hop And Haul (per SLA) | Restore service, credits per contract |
| Regulatory violation | Customer | Provide compliance-supporting features |
| Data breach (platform) | Hop And Haul | Security remediation, notification |
| Data breach (customer credentials) | Customer | Customer security responsibility |
2. Role Assignments
2.1 Hop And Haul Platform Team
All policy documents are owned and maintained by the Hop And Haul Team.
2.2 Customer Organization Roles (Fleet Operator)
The customer (fleet operator) is responsible for all operational roles:
| Role | Responsibility | Where Defined |
|---|---|---|
| Safety Director | Driver safety policies, DOT compliance, training | Customer's policies |
| Operations Manager | Dispatching decisions, driver management, scheduling | Customer's policies |
| Legal Counsel | Liability management, employment law, claims handling | Customer's policies |
| Compliance Manager | FMCSA/DOT regulatory compliance, audit response | Customer's policies |
| Fleet Manager | Vehicle maintenance, inspections, DVIR compliance | Customer's policies |
| HR Manager | Employment, driver qualifications, background checks | Customer's policies |
2.3 Role Clarification in Existing Documents
Where existing policies reference "Safety Director" or "Operations Director" in operational contexts, these refer to the CUSTOMER's roles, not Hop And Haul staff.
- "Safety Director" reviewing incidents = Customer's Safety Director
- "Operations Director" approving overrides = Customer's Operations Manager
- "Legal Counsel" managing claims = Customer's Legal Counsel
Hop And Haul provides the platform capabilities; the customer makes operational decisions.
3. How to Read Hop And Haul Policy Documents
3.1 Platform Policies vs Customer Responsibilities
| Document Type | What It Describes | Who Decides |
|---|---|---|
| Safety Buffers (PLCY-BUF-001) | Platform capabilities and defaults | Customer configures for their fleet |
| Communication Protocol (PLCY-COM-001) | Available methods and safety features | Customer chooses which to use |
| Pre-Transaction Validation (PLCY-VAL-001) | Validation framework and checks | Customer defines requirements |
| Incident Response (PLCY-INC-001) | Platform incident detection and alerting | Customer responds to operational incidents |
| Accident/Liability (PLCY-LIA-001) | Reference framework for customer use | Customer bears liability |
| Voice Agent (PLCY-VOI-001) | Voice capabilities and constraints | Customer enables/configures |
3.2 Language Interpretation Guide
When reading Hop And Haul policy documents:
| Document Says | Interpretation |
|---|---|
| "Hop And Haul will..." | Platform capability, not customer mandate |
| "The Company..." | Refers to Customer (fleet operator), not Hop And Haul |
| "Safety Director" | Customer's Safety Director (unless context is platform security) |
| "Operations Director" | Customer's Operations Manager |
| "Must" / "Shall" for operations | Customer's obligation; platform supports |
| "Required before match" | Platform enforces; customer defines requirements |
3.3 Autonomous vs Manual Mode
All operational policies describe the AUTONOMOUS mode where Hop And Haul makes matching decisions automatically. In MANUAL mode:
| Aspect | Autonomous Mode | Manual Mode |
|---|---|---|
| Match decisions | Platform decides | Dispatcher approves each |
| Validation | Automatic blocking | Automatic + dispatcher override |
| Speed | Instant matching | Dispatcher response time |
| Platform role | Decision-maker | Tool/assistant |
| Customer role | Oversight/override | Active dispatching |
The same safety validations apply in both modes, but in manual mode the customer makes the final call on every match.
4. Contract & Service Boundaries
4.1 What Hop And Haul Provides
| Service | Description |
|---|---|
| Matching Platform | Algorithm that matches drivers on compatible routes |
| Validation Engine | Pre-transaction checks against customer data sources |
| Communication Infrastructure | Voice agent, messaging, push notifications |
| Dashboard & Visibility | Real-time view of all operations |
| Audit Trail | Complete logging of all platform decisions |
| Integration APIs | Connect to customer HR, ELD, insurance systems |
| Support | Platform support and customer enablement |
4.2 What Hop And Haul Does NOT Provide
| Not Included | Customer Responsibility |
|---|---|
| Driver employment | Customer employs all drivers |
| DOT/FMCSA compliance | Customer is the motor carrier |
| Insurance coverage | Customer maintains policies |
| Vehicle maintenance | Customer maintains fleet |
| Driver training | Customer trains drivers |
| Incident investigation | Customer investigates (platform provides data) |
| Claims handling | Customer handles claims |
| Regulatory filings | Customer files all reports |
4.3 Data Ownership
| Data Type | Owner | Hop And Haul Role |
|---|---|---|
| Driver PII | Customer | Process per customer instruction |
| GPS/telematics | Customer (via ELD provider) | Query for matching |
| Match history | Customer | Store and provide access |
| Audit logs | Customer | Generate and retain per policy |
| Platform logs | Hop And Haul | Maintain for debugging/support |
5. Document References
| Document | Relevance |
|---|---|
| PLCY-IDX-001 Policy Index | Complete list of all policy documents |
| PLCY-SYS-001 System Description | Technical architecture overview |
| PLCY-ORG-001 Organization & Domains | Multi-tenant customer setup |
| PLCY-LIA-001 Accident & Liability | Liability framework for customer use |
6. Revision History
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | December 22, 2025 | Hop And Haul Team | Initial release |