A complete, traceable product definition for SiteFleet OS—beginning with the executive story, business assumptions, key variables, major risks, and roadmap before moving into the detailed capabilities, requirements, engineering transition, and source record.
SiteFleet OS is not simply dispatch or fleet-management software. It is the proposed operating infrastructure for a multi-company, franchise-enabled field-services platform—designed to generate demand, convert it into qualified work, coordinate trucks and operators, document execution, invoice customers, distribute economics, and produce the intelligence required to scale nationally.
Executive Reading Path
Strategic Thesis
The platform creates value by centralizing the administrative, commercial, operational, compliance, fleet, and financial burden that would otherwise sit with individual franchisees or operating companies. This allows local operators to focus on equipment execution, customer service, and territory growth while SiteFleet maintains consistency, qualification controls, data visibility, and national oversight.
Core advantage:
one shared operating platform can support multiple subsidiaries, service categories, franchise territories, corporate-owned assets, national accounts, and future SiteFleet operating companies without recreating the business system each time.
Target Business Outcome
Create a repeatable and scalable operating model that improves customer conversion, dispatch reliability, truck utilization, franchise economics, compliance, billing speed, customer retention, and management visibility.
Consistent customer experience across every subsidiary and territory
Qualified work matched to qualified operators and equipment
Corporate fleet capacity as a service-level safety net
Complete digital record from lead through payment
Operational and financial data available for continuous improvement
Executive Priorities
01
Launch the Operating Foundation
Support lead intake, estimating, contracting, work orders, dispatch, field completion, invoicing, and payment tracking.
02
Synchronize Software and Truck Delivery
Align onboard hardware, telematics, connectivity, mobile workflow, testing, support, and truck deployment.
03
Design for Franchise Scale
Make territories, qualifications, compliance, revenue allocation, and performance management configurable from the beginning.
04
Preserve the Data Advantage
Capture reusable operational and financial data once, with stable identifiers, audit history, and API-accessible services.
Core Business Assumptions
SiteFleet will operate through both franchise and corporate-owned capacity.
Multiple subsidiaries will share common platform capabilities while retaining differentiated customer experiences.
National accounts may span subsidiaries and franchise territories.
Every job follows a traceable lifecycle from lead through payment.
Work eligibility depends on territory, equipment, operator credentials, insurance, licensing, certifications, and safety status.
External financial, payment, telematics, mapping, and compliance systems will remain important integration partners.
Technology Assumptions
Cloud-native, modular, multi-company, and API-first architecture.
Role-, company-, territory-, and customer-based access controls.
Mobile-first field execution with intermittent connectivity and low-bandwidth support.
Executive decision required:
confirm the business assumptions, owners, risk ratings, critical success measures, and Phase 1 release boundary before detailed architecture, budget, resource, and delivery commitments are finalized.
02 / Executive Foundation
Vision, Purpose & Governing Principles
SiteFleet OS is the centralized operating infrastructure for SiteFleet Holdings and its current and future subsidiary companies. It connects customers, franchise operators, corporate fleet assets, field personnel, equipment, administrative teams, and management through one integrated technology ecosystem.
Authoritative Intent
Platform Purpose
Provide franchise operators with a complete lead-generation, customer-management, dispatch, compliance, operations, fleet-management, invoicing, and payment platform so they can focus on operating equipment, completing work, serving customers, and growing territories.
Long-term objective:
create a technology-enabled franchise ecosystem that is difficult for traditional service companies or independent operators to replicate.
Supported Operating Companies
SiteVac Hydro X
SiteFuel
Site Environmental Solutions
SiteH2O
SiteHaul
SiteDrilling Services
SiteCoil Services
Future SiteFleet companies and franchise systems
Governing Principles
One Platform
Shared core services with subsidiary-specific experiences.
Truck-Aligned Delivery
Software readiness must synchronize with hardware, connectivity, testing, and truck deployment.
Franchise Simplicity
Shift front-office and back-office burden away from local operators.
Qualification by Design
Only properly equipped, insured, licensed, and certified operators receive work.
Complete Traceability
Every feature, decision, release, workflow, and engineering artifact uses stable references.
Data as an Asset
Capture operational and financial data to improve pricing, scheduling, profitability, safety, and service.
03 / Business Capability Map
What the Platform Must Be Able to Do
The source outline has been consolidated into eleven durable product domains. Select a domain to jump to its detailed module specification and feature inventory.
11 Modules
04 / User Model
Primary User Personas
The platform requires distinct permissions, dashboards, responsibilities, and workflows for six primary user groups.
Role-Based Experience
01
Customers
Request, price, contract, monitor, approve, and pay for services through a consistent digital experience.
Create and maintain accounts
Submit service requests and files
Review estimates and sign contracts
Track mobilization and job progress
Approve work, receive invoices, and pay
02
Franchise Owners
Manage territories, operators, equipment, compliance, schedules, economics, and available work.
Maintain company and compliance profile
Register operators, trucks, and equipment
Review and accept qualified jobs
Build operating schedules
Monitor revenue, profitability, and utilization
03
Operators & Field Personnel
Execute assigned work safely and capture the complete operational record from mobilization through completion.
Review assignments and requirements
Navigate, mobilize, and check in
Complete safety and equipment inspections
Record production, materials, photos, and incidents
Capture signature and submit completion package
04
Corporate Operations
Maintain national oversight, resolve unclaimed work, protect service levels, and deploy corporate capacity.
Monitor all work orders
Assign corporate-owned assets
Support emergency dispatch
Manage escalations and national accounts
Oversee quality, pricing, utilization, and performance
Manage fees, commissions, credits, and collections
Track receivables and disputes
Integrate with accounting platforms
06
System Administrators
Secure and configure the platform across companies, territories, users, services, integrations, and records.
Create users and permissions
Configure services, pricing, entities, and territories
Manage integrations and platform settings
Review logs and monitor security
Maintain platform-wide governance
05 / Operating Model
End-to-End Business Process
SiteFleet OS must support the complete commercial and operational chain rather than a collection of isolated features.
Lead to Cash
Lead
→
Service Request
→
Scope & Estimate
→
Contract
→
Work Order
→
Qualification
→
Schedule & Dispatch
→
Field Execution
→
Approval
→
Invoice & Payment
Corporate fleet safety net:
when qualified franchise capacity does not accept or cannot perform the work, the platform expands the search, alerts corporate dispatch, assigns corporate capacity, informs the customer, and escalates unresolved demand.
06 / Product Definition
Product Modules & Capabilities
Each module below is a durable product domain. Expand a module to review its purpose, source-derived capabilities, and feature volume.
Platform → Module → Capability → Feature
07 / Authoritative Feature Catalog
Searchable Feature Inventory
Every granular requirement bullet from source Sections 4 through 32 is retained as a feature record with a stable preliminary ID and source reference. Release and classification fields remain reviewable planning metadata.
830 Records
Feature ID
Module
Capability
Feature / Requirement
Classification
Release
Source
08 / Product Roadmap
Source-Defined Development Phases
The original outline defines four phases. These cards preserve that intent. Feature-level assignments below are provisional until business, architecture, truck-build, dependency, cost, and resource alignment are complete.
4 Phases
Phase 1
Core Minimum Viable Platform
Establish the operational foundation required to generate work, execute jobs, and invoice customers.
Customer intake
Service selection
Lead capture
Basic estimating
Contract generation
Electronic signatures
Work-order creation
Franchise job board
Operator qualification
Basic scheduling
Customer notifications
Mobile field workflow
Completion approval
Invoicing
Payment tracking
Corporate fleet assignment
Basic dashboards
Phase 2
Franchise & Fleet Operations
Add the controls and asset capabilities required to scale the franchise and truck network.
Franchise management
Advanced scheduling
GPS integration
Telematics
Maintenance management
Compliance management
Customer document delivery
Revenue-sharing calculations
Franchise scorecards
Route optimization
National account controls
Phase 3
AI & Automation
Automate analysis, customer interaction, back-office work, validation, and intelligent matching.
AI scope analysis
Automated estimating
Front office AI assistants
Back office AI assistants
AI document review
Automated invoice validation
Dynamic pricing
Predictive maintenance
Lead qualification
Customer cross-selling
Intelligent job matching
Phase 4
Enterprise Intelligence
Create enterprise-level forecasting, optimization, benchmarking, and decision support.
Enterprise analytics
Predictive forecasting
Territory optimization
Franchise benchmarking
Equipment investment analysis
Customer profitability
AI decision support
Advanced national account management
Automated operational recommendations
Feature Release Matrix
Feature ID
Feature
Phase 1
Phase 2
Phase 3
Phase 4
Alignment Required
09 / Product Impact
Channel & Technology Impact Matrix
This first-pass matrix identifies likely impacts to truck systems, mobile, office applications, customer experiences, integrations, and AI. Flags are derived from source language and should be validated during architecture workshops.
Preliminary Assessment
Feature ID
Feature
Truck
Mobile
Office
Customer
Integration
AI
Source
10 / Engineering Transition
Required Next-Stage Deliverables
The original outline explicitly requires these artifacts to translate the product definition into executable architecture, design, delivery, testing, deployment, and support plans.
18 Deliverables
01
Formal product requirements document
Required
02
Platform architecture diagram
Required
03
User-role and permission matrix
Required
04
Customer journey map
Required
05
Franchise operator journey map
Required
06
Field operator workflow
Required
07
Work-order lifecycle diagram
Required
08
Data model
Required
09
Integration architecture
Required
10
Security architecture
Required
11
AI assistant requirements
Required
12
Telematics requirements
Required
13
Minimum viable product feature list
Required
14
Development sprint plan
Required
15
Budget and resource estimate
Required
16
Testing plan
Required
17
Deployment strategy
Required
18
Support and maintenance plan
Required
11 / Product Governance
How This Specification Is Maintained
The HTML becomes the living master for product intent. Planning workbooks and execution systems should reference stable feature and capability IDs rather than redefine the product.
Canonical Working Record
Hierarchy
Stable Product Model
Platform → Module → Capability → Feature → Enhancement. IDs remain stable even when scope, release, owner, design, or implementation changes.
Lifecycle
Controlled Feature Status
Proposed → Approved → Planned → In Development → Testing → Released → Deferred or Retired.
Change Control
Decision Traceability
Record requestor, rationale, impacted features, dependencies, timing, cost, approval, and target release.
Release Gate
Truck Readiness
No operational release is complete until installed hardware, connectivity, field workflow, support, and end-to-end acceptance testing are ready.
Definition of Done
Whole-Product Completion
Business approval, UX, data, API, security, truck/mobile, integration, testing, documentation, deployment, support, and training.
Planning Layer
Excel Follows Alignment
Once structure and intent are approved, model value, priority, complexity, dependencies, timing, resources, and cost in Excel.
12 / Complete Source Record
Original Preliminary Software Development Outline
All 35 original sections are retained below so reviewers can verify that the living specification preserves the source document without leaving this HTML. This is the content assurance layer for future presentation and structural refinement.
44 Pages Preserved
1. Platform Purpose
SiteFleet OS will serve as the centralized operating system for SiteFleet Holdings LLC and all current and future subsidiary companies. The platform will be the operational backbone of the SiteFleet franchise model, connecting customers, franchise operators, corporate-owned fleet assets, field personnel, equipment, administrative teams, and management through one integrated technology ecosystem.
The primary objective of SiteFleet OS is to provide franchise operators with a complete lead-generation, customer-management, dispatch, compliance, operations, fleet-management, invoicing, and payment platform. The system should allow franchisees to focus primarily on operating equipment and completing work while SiteFleet OS manages much of the front-office and back-office administrative burden.
The platform will support multiple subsidiary companies and service categories, including:
SiteVac Hydro X
SiteFuel
Site Environmental Solutions
SiteH2O
SiteHaul
SiteDrilling Services
SiteCoil Services
Future SiteFleet operating companies and franchise systems
The platform must be designed as a scalable, modular, multi-company, and multi-territory system capable of supporting a national franchise network.
2. Core Platform Objectives
SiteFleet OS should be designed to accomplish the following primary objectives:
Generate qualified customer leads for every SiteFleet subsidiary.
Allow customers to request, price, contract, schedule, monitor, and approve services through one platform.
Convert customer requests into formal work orders.
Match work orders with qualified franchise operators.
Maintain corporate-owned trucks and equipment on the platform to provide coverage for work orders not accepted by franchisees.
Verify that franchisees possess the required licenses, insurance, certifications, equipment, and operator qualifications for each job.
Automate customer communications, document collection, contracting, invoicing, and payment tracking.
Provide real-time fleet, equipment, operator, and work-order visibility.
Track equipment utilization, service intervals, maintenance needs, and diagnostic information.
Provide SiteFleet corporate management with complete oversight of the national operating platform.
Create a repeatable and scalable operating model for franchise owners.
Capture operational and financial data that can be used to improve pricing, scheduling, profitability, safety, and customer service.
3. Primary User Groups
SiteFleet OS will require separate permissions, dashboards, and workflows for multiple user types.
3.1 Customers
Customers may include:
General contractors
Utility companies
Municipalities
Oil and gas operators
Industrial facilities
Commercial property owners
Environmental contractors
Engineering firms
Government agencies
Residential customers
National account customers
Emergency response customers
Customer users should be able to:
Create an account
Maintain company and billing information
Submit service requests
Upload project files
Receive estimates
Review and sign contracts
Track mobilization and job progress
Communicate with SiteFleet representatives
Approve completed work
Receive invoices
Make payments
View historical jobs and documentation
3.2 Franchise Owners
Franchise owners should be able to:
Manage their company profile
Manage territories
Maintain insurance and licensing records
Manage operators and employees
Register trucks and equipment
Review available jobs
Accept qualified work orders
Build operating schedules
Monitor revenue and profitability
Track equipment utilization
Review invoices and payments
Access performance reports
Maintain franchise compliance
3.3 Operators and Field Personnel
Operators should have a mobile application or mobile-responsive interface that allows them to:
View assigned work orders
Review job requirements
Navigate to job locations
Confirm mobilization
Complete safety documentation
Record arrival and departure
Upload photographs and videos
Enter production information
Record material quantities
Capture customer signatures
Report incidents
Complete equipment inspections
Submit job completion reports
3.4 SiteFleet Corporate Operations
Corporate users should be able to:
Monitor all work orders
Assign corporate-owned equipment
Review unclaimed jobs
Manage customer escalation
Monitor franchise compliance
Support emergency dispatch
manage national accounts
review service quality
manage pricing rules
approve franchise territories
oversee fleet utilization
monitor financial performance
3.5 Administrative and Finance Users
Administrative and finance users should be able to:
Review contracts
manage customer accounts
process invoices
track receivables
manage franchise fees
reconcile payments
manage commissions
approve credits
monitor collections
export financial data
integrate with accounting software
3.6 System Administrators
System administrators should be able to:
Create and manage users
configure permissions
establish service categories
modify pricing rules
manage subsidiary settings
configure territories
manage integrations
review system logs
monitor security
manage platform-wide settings
4. Customer Lead Generation and Service Request Module
The customer-facing platform should function as a lead-generation and service-conversion system.
4.1 Customer Entry Points
Customers should be able to enter the SiteFleet ecosystem through:
SiteFleet corporate website
Individual subsidiary websites
Search-engine landing pages
Digital advertising campaigns
Franchise-specific web pages
Customer mobile application
Referral links
National account portals
QR codes
Sales representative links
Emergency service request lines
All lead sources should be tracked so SiteFleet can measure customer acquisition costs, conversion rates, and marketing performance.
4.2 Customer Account Creation
The customer should be able to create an account using:
Email and password
Mobile phone verification
Company credentials
Single sign-on for national accounts
Google or Microsoft authentication, if appropriate
The account profile should include:
Customer name
Company name
Billing address
Service locations
Primary contacts
Accounts-payable contacts
Tax-exempt information
Insurance requirements
Purchase-order requirements
Credit terms
Preferred communication method
Historical work orders
Saved project locations
4.3 Service Selection
The platform should guide customers through a structured service-selection process.
The customer should first select the applicable subsidiary or service category. The system should then dynamically present questions based on the selected scope of work.
Examples may include:
Hydro excavation
Daylighting
Slot trenching
Potholing
Debris removal
Tank cleaning
Industrial cleaning
Waste hauling
Water hauling
Fuel delivery
Environmental remediation
Water separation
Emergency response
Roll-off services
Material transport
Specialty drilling support
4.4 Scope-of-Work Intake
The customer should be able to provide:
Description of requested work
Project address
GPS coordinates
Requested service date
Requested completion date
Estimated work volume
Site-access information
Working-hour restrictions
Required equipment
Known hazards
Utility information
Environmental conditions
Soil or material type
Disposal requirements
Water availability
Traffic-control requirements
Permitting requirements
Union or prevailing-wage requirements
Customer safety requirements
Purchase-order information
Photographs
Videos
Plans
Drawings
Site maps
Bid documents
Other attachments
The intake system should use conditional logic so customers are only asked questions relevant to the selected service.
5. AI-Assisted Scope Analysis
SiteFleet OS should use artificial intelligence to analyze the customer’s service request and translate it into a preliminary scope of work.
The AI should evaluate:
Written descriptions
Uploaded documents
Site photographs
Project plans
Customer answers
Geographic location
Historical job data
Equipment requirements
Expected labor
Travel requirements
Disposal requirements
Required certifications
Anticipated job duration
Similar completed projects
The AI should identify missing information and prompt the customer for clarification before producing an estimate.
The AI should also flag requests that require human review due to:
Complex engineering
Unusual risk
Hazardous materials
Regulatory requirements
Large project value
Incomplete documentation
Unclear scope
Emergency conditions
Unusual equipment requirements
High mobilization costs
6. Estimating and Pricing Module
The estimating system should generate a preliminary or binding estimate based on established pricing rules.
6.1 Pricing Inputs
The estimate may include:
Mobilization
Travel time
Equipment hourly rates
Operator labor
Additional crew labor
Fuel
Water
Disposal
Environmental fees
Permits
Traffic control
Materials
Subcontractors
Equipment attachments
Standby time
Overtime
After-hours premiums
Emergency-response premiums
Franchise territory adjustments
Regional labor adjustments
Distance from available equipment
Minimum service charges
Taxes
Administrative charges
6.2 Pricing Methodologies
The software should support:
Hourly pricing
Daily pricing
Unit pricing
Fixed-price contracts
Cost-plus pricing
Time-and-material pricing
Subscription pricing
National account pricing
Volume discounts
Emergency pricing
Franchise-specific pricing within approved parameters
6.3 Estimate Confidence Rating
The software should assign an estimate confidence level, such as:
High confidence
Moderate confidence
Human review required
Site visit required
The confidence rating should be based on the completeness and quality of the customer information.
6.4 Human Estimate Approval
Certain estimates should require review by:
SiteFleet corporate estimating
Franchise management
Engineering
Environmental compliance
National account management
Risk management
The platform should record all pricing changes and approvals.
7. Contract Generation and Electronic Approval
Once the estimate is accepted, SiteFleet OS should generate the appropriate contract or work authorization.
The contract should include:
Customer information
Contractor or franchise entity
Scope of work
Pricing
Estimated duration
Equipment requirements
Mobilization terms
Payment terms
Cancellation terms
Change-order process
Customer obligations
Site-access requirements
Safety requirements
Insurance provisions
Limitation-of-liability language
Environmental and disposal terms
Applicable exhibits
Electronic signature fields
The platform should maintain different contract templates for:
Residential customers
Commercial customers
National accounts
Municipal customers
Oil and gas operators
Industrial customers
Emergency work
Master service agreements
Purchase-order-based work
Franchise-specific engagements
The customer should be able to electronically sign the agreement. Once signed, the system should automatically create a formal work order.
8. Work Order Creation and Job Board Queue
Once a contract is approved, the work order should move into the SiteFleet job board.
8.1 Work Order Information
Each work order should include:
Work-order number
Customer
Service location
Scope of work
Estimated revenue
Estimated cost
Estimated duration
Requested date
Required arrival window
Required equipment
Required operator qualifications
Required licenses
Required insurance
Required certifications
Safety requirements
Disposal requirements
Attachments
Customer contact
Payment terms
Special instructions
Priority level
8.2 Job Board Visibility
Work orders should be visible only to franchise operators who meet the required criteria.
Visibility may be based on:
Franchise territory
Equipment availability
Operator credentials
Insurance coverage
License status
Certification status
Customer rating
Franchise performance rating
Distance from the job
Availability
Equipment type
Safety record
Job size
National account approval
8.3 Work Order Statuses
Suggested statuses include:
Draft
Estimate pending
Customer review
Contract pending
Approved
Posted to job board
Offered to preferred franchisee
Accepted
Scheduled
Mobilizing
Arrived
Work in progress
On hold
Change order pending
Completed
Customer approval pending
Approved for invoicing
Invoiced
Paid
Closed
Disputed
Cancelled
9. Franchise Operator Qualification and Rating System
Each franchisee and operator should maintain a detailed qualification profile.
9.1 Franchise Profile
The franchise profile should include:
Legal business name
Franchise territory
Ownership information
Business licenses
Insurance policies
Safety records
Equipment inventory
Operator roster
Certifications
Customer ratings
SiteFleet performance rating
Financial standing
Franchise agreement status
Approved service categories
Approved industries
National account approvals
9.2 Operator Profile
Each operator profile should include:
Name
Photograph
Contact information
Employee identification
Driver’s license
Commercial driver’s license classification
Medical card
Training history
Equipment certifications
OSHA certifications
HAZWOPER certification
First-aid and CPR certifications
Drug-testing status
Motor vehicle record
Customer-site approvals
Operator performance score
Incident history
Expiration dates
9.3 Qualification Rules
The software should automatically prevent a franchisee or operator from accepting work if required credentials are missing or expired.
Examples include:
Inadequate insurance limits
Missing environmental certification
Expired CDL
Missing customer-specific orientation
Lack of hazardous-material approval
Inadequate equipment capability
Territory restrictions
Safety suspension
Outstanding franchise compliance issue
9.4 Franchise Rating System
Ratings should consider:
Customer satisfaction
On-time arrival
Job completion percentage
Safety performance
Equipment condition
Documentation quality
Invoice accuracy
Communication quality
Acceptance rate
Cancellation rate
Response time
Franchise compliance
Payment performance
Operator performance
The rating may affect:
Job-board priority
Access to premium work
National account eligibility
Territory expansion
Financing opportunities
Equipment allocation
Franchise renewal
10. Corporate Fleet Safety Net
SiteFleet will maintain corporate-owned trucks and equipment on the platform to ensure that customer work can be completed even when franchisees do not accept the work.
10.1 Corporate Fleet Assignment Logic
Corporate fleet resources should automatically be considered when:
No franchisee accepts a work order within the required period
The work is located outside an active franchise territory
The customer is a protected national account
The work requires specialized equipment
The job is an emergency
The franchisee cancels
Corporate execution is more economically appropriate
SiteFleet wishes to establish a new market
10.2 Escalation Process
The platform should create automated escalation steps:
Offer work to qualified franchisees.
Notify preferred operators.
Expand the geographic search radius.
Alert SiteFleet corporate dispatch.
Assign corporate equipment.
Notify the customer of assignment.
Escalate unresolved work to operations management.
10.3 Corporate Fleet Dashboard
Corporate operations should be able to view:
Available equipment
Equipment location
Operator availability
Maintenance status
Scheduled work
Unassigned work
Emergency capacity
Mobilization distance
Equipment utilization
Revenue by asset
11. Scheduling and Dispatch Module
The scheduling module should help franchisees and corporate operations manage equipment and crews.
Features should include:
Daily, weekly, and monthly calendar views
Drag-and-drop scheduling
Operator scheduling
Equipment scheduling
Territory views
Route optimization
Mobilization planning
Job conflict alerts
Required-rest-period alerts
Overtime alerts
Maintenance conflict alerts
Weather alerts
Customer arrival notifications
Estimated time of arrival
Emergency dispatch
Replacement-equipment assignment
The system should recommend the most appropriate available equipment based on:
Distance
Capability
Operator qualifications
Existing schedule
Fuel efficiency
Maintenance status
Job profitability
Customer preference
Franchise territory
12. Customer Communication and Front Office AI Assistant
SiteFleet OS should include AI-powered front office assistants that manage routine customer interactions.
12.1 Front Office Assistant Responsibilities
The front office assistant should:
Answer basic customer questions
Help customers submit service requests
Request missing information
Schedule calls
Provide estimate updates
Send contract reminders
Confirm scheduling
Send mobilization notices
Send arrival notifications
Provide insurance documentation
Provide certificates of insurance
Send licenses and certifications
Request purchase orders
Provide job-status updates
Collect customer approvals
Support change-order requests
Route complex issues to a human representative
12.2 Communication Channels
The front office assistant should communicate through:
Email
SMS
Website chat
Mobile application
Customer portal
Voice assistant, if implemented later
12.3 Human Escalation
The assistant should escalate communications involving:
Complaints
Safety issues
Legal issues
Pricing disputes
Major scope changes
Contract negotiations
Environmental incidents
Damage claims
National account issues
Sensitive customer communications
All communications should be logged in the customer record.
13. Insurance, Licensing, and Compliance Module
The platform should maintain all compliance documentation for corporate entities, franchises, operators, vehicles, and equipment.
13.1 Documents to Track
General liability insurance
Automobile liability insurance
Workers’ compensation
Umbrella coverage
Environmental liability
Pollution coverage
Equipment insurance
Certificates of insurance
Business licenses
Contractor licenses
Environmental permits
Operator licenses
Safety certifications
Customer-specific credentials
Vehicle registrations
Inspection records
13.2 Expiration Management
The system should:
Track expiration dates
Send renewal reminders
Restrict work-order access
Notify corporate compliance
Request updated documents
Automatically update qualification status
Maintain historical copies
13.3 Customer Document Delivery
When requested or contractually required, the system should automatically send customers:
Certificates of insurance
W-9 forms
Licenses
Safety records
Operator qualifications
Equipment certifications
Corporate documentation
Site-specific compliance documentation
14. Field Operations Mobile Application
Field operators should have a simple mobile workflow designed for use in active work environments.
14.1 Pre-Job Workflow
The operator should complete:
Job review
Equipment inspection
Safety checklist
Pre-trip inspection
Required documentation
Route confirmation
Crew confirmation
Customer contact confirmation
Hazard review
14.2 Mobilization Workflow
The system should record:
Time mobilization begins
Vehicle location
Estimated time of arrival
Route
Travel time
Delays
Customer notification
Arrival time
14.3 Jobsite Workflow
The operator should be able to:
Check in
Record job-start time
Upload site photographs
Complete job hazard analysis
Confirm utility markings
Record production quantities
Record water use
Record fuel use
Record disposal volumes
Capture material tickets
Track standby time
Request change orders
Document customer instructions
Report incidents
Record equipment problems
Communicate with dispatch
14.4 Completion Workflow
The operator should:
Enter job completion time
Upload completion photographs
Enter final quantities
Record disposal tickets
Complete equipment inspection
Document unresolved issues
Obtain customer signature
Submit completion report
15. GPS, Telematics, and Asset Tracking
Each SiteFleet rig and major equipment asset should have an integrated tracking device.
15.1 Location Tracking
The system should track:
Current location
Mobilization start
Route
Estimated arrival
Actual arrival
Jobsite duration
Departure
Return to yard
Unauthorized movement
Territory compliance
Customers should receive appropriate visibility into:
Mobilization status
Estimated arrival
Arrival confirmation
Work commencement
Work completion
Customer visibility should be limited to the specific work order and should not expose unrelated fleet information.
15.2 Vehicle and Equipment Diagnostics
The platform should capture available diagnostic information, including:
Engine hours
Mileage
Fuel use
Idle time
Battery voltage
Engine fault codes
Hydraulic-system status
Vacuum-system performance
Pump operating hours
Water-system performance
Tank cycles
Temperature
Pressure
PTO usage
Equipment alarms
15.3 Utilization Tracking
The system should report:
Revenue hours
Non-revenue hours
Travel hours
Idle time
Equipment utilization percentage
Revenue per asset
Revenue per operating hour
Maintenance downtime
Available capacity
16. Maintenance and Service Management
SiteFleet OS should automatically monitor fleet maintenance requirements.
16.1 Preventive Maintenance
Maintenance schedules should be based on:
Mileage
Engine hours
PTO hours
Pump hours
Calendar intervals
Manufacturer recommendations
Diagnostic alerts
Operating conditions
16.2 Maintenance Functions
The platform should support:
Preventive maintenance schedules
Service reminders
Work orders
Repair history
Parts inventory
Warranty records
Vendor management
Inspection records
Downtime tracking
Repair-cost tracking
Maintenance approval
Equipment lockout
16.3 Equipment Availability
Equipment with critical maintenance issues should automatically be removed from the dispatch pool until cleared.
17. Change Order Management
The platform should provide a formal process for managing work outside the original contract.
Change orders may be initiated by:
Customer
Operator
Franchise manager
Corporate operations
AI scope-monitoring system
The change-order process should include:
Description of changed conditions
Supporting photographs
Additional labor
Additional equipment
Additional disposal
Additional mobilization
Additional pricing
Customer approval
Electronic signature
Updated work-order value
Audit trail
Work should not proceed beyond approved limits unless emergency rules apply.
18. Job Completion and Customer Approval
Once field work is completed, the platform should create a completion package.
The package should include:
Original scope
Final scope
Work performed
Dates and times
Operator
Equipment
Production quantities
Photographs
Disposal tickets
Change orders
Safety documentation
Customer signature
Completion confirmation
The customer should be able to:
Approve the work
Report an issue
Request clarification
Dispute a line item
Rate the service
Upload additional documentation
Customer approval should move the work order into the invoicing process.
19. Back Office AI Assistant
The back office assistant should automate administrative and financial functions after job completion.
19.1 Back Office Responsibilities
The back office assistant should:
Confirm documentation completeness
Review contract terms
Review approved change orders
Validate pricing
Prepare the invoice
Attach supporting documentation
Send the invoice
Submit through customer portals
Track invoice receipt
Monitor payment terms
Send payment reminders
Escalate overdue accounts
Track disputes
Maintain collection notes
Reconcile payments
Notify franchisees of payment status
19.2 Invoice Package
The invoice package may include:
Invoice
Signed work order
Customer approval
Daily tickets
Disposal tickets
Photographs
Change orders
Purchase order
Operator reports
Equipment records
Other customer-required documents
20. Billing, Payments, and Revenue Distribution
The financial module should support multiple payment structures.
20.1 Customer Payments
The platform should support:
ACH
Credit card
Wire transfer
Check
Customer payment portal
National account terms
Deposits
Progress billing
Recurring billing
20.2 Franchise Revenue Allocation
The system should calculate:
Gross job revenue
Taxes
Payment-processing fees
Franchise royalties
Marketing fees
Technology fees
Equipment payments
Insurance deductions
Corporate service fees
Franchise net proceeds
Operator commissions
Referral commissions
20.3 Accounts Receivable
The platform should display:
Current invoices
Aging
Customer credit limits
Days sales outstanding
Collection status
Disputes
Promises to pay
Bad-debt exposure
Franchise receivables
21. Franchise Management Module
SiteFleet OS should serve as the central franchise administration system.
Features should include:
Franchise onboarding
Territory mapping
Franchise agreements
Fee tracking
Training completion
Equipment requirements
Insurance compliance
Operating standards
Marketing support
Customer ratings
Performance benchmarking
Franchise scorecards
Renewal management
Corrective-action plans
Territory expansion requests
Franchise communication center
22. Customer Relationship Management
The CRM should maintain a complete view of every customer.
The customer record should include:
Contacts
Locations
Industries
Service history
Contracts
Estimates
Work orders
Invoices
Payments
Communications
Complaints
Ratings
Insurance requirements
Pricing agreements
Sales opportunities
Account manager
Franchise relationships
National account status
The system should support:
Sales pipelines
Follow-up reminders
Proposal management
Marketing campaigns
Customer segmentation
Account planning
Cross-selling across subsidiaries
Customer-retention tracking
23. Cross-Subsidiary Lead Generation
One major competitive advantage of SiteFleet OS should be its ability to identify additional work opportunities across the SiteFleet platform.
For example:
A SiteVac customer may also need waste hauling.
A SiteFuel customer may need environmental services.
A SiteHaul customer may need water services.
A drilling customer may need hydro excavation or fluid management.
The system should analyze customer activity and recommend additional SiteFleet services.
Cross-selling tools should include:
AI-generated service recommendations
Account-manager alerts
Bundled proposals
Multi-service contracts
Customer-specific campaigns
Referral-credit tracking
Shared customer profiles across subsidiaries
24. Analytics and Business Intelligence
The platform should provide dashboards for corporate management and franchise owners.
24.1 Corporate Analytics
Corporate dashboards should include:
Total platform revenue
Revenue by subsidiary
Revenue by franchise
Revenue by territory
Revenue by service
Gross margin
Equipment utilization
Lead conversion
Work-order acceptance
Customer acquisition cost
Customer retention
Invoice aging
Safety incidents
Maintenance costs
Franchise compliance
National account performance
24.2 Franchise Analytics
Franchise dashboards should include:
Available jobs
Accepted jobs
Scheduled revenue
Completed revenue
Gross margin
Operator productivity
Equipment utilization
Customer ratings
Invoice status
Payment status
Maintenance status
Compliance status
Territory performance
24.3 Predictive Analytics
Future capabilities may include:
Demand forecasting
Territory opportunity analysis
Predictive maintenance
Customer churn prediction
Dynamic pricing
Equipment-purchase recommendations
Staffing forecasts
Route optimization
Profitability forecasting
Franchise performance risk
25. Safety and Incident Management
The platform should maintain a formal safety-management system.
Features should include:
Job hazard analysis
Toolbox talks
Pre-trip inspections
Equipment inspections
Near-miss reporting
Incident reporting
Injury reporting
Environmental-event reporting
Corrective actions
Safety training
Drug-testing records
Motor vehicle records
Safety scorecards
Customer safety requirements
OSHA documentation
Serious incidents should trigger immediate corporate notifications.
26. Document Management
SiteFleet OS should maintain a centralized document repository.
Documents may include:
Contracts
Work orders
Insurance documents
Licenses
Certifications
Customer files
Operator files
Equipment files
Inspection reports
Maintenance records
Invoices
Purchase orders
Disposal tickets
Safety documentation
Franchise agreements
Training records
The platform should provide:
Version control
Access permissions
Search
Expiration tracking
Electronic signatures
Audit trails
Secure storage
Document retention policies
27. Notifications and Alerts
The platform should generate automated notifications for:
New leads
New work orders
Available jobs
Estimate approval
Contract signature
Scheduling
Mobilization
Arrival
Delays
Change orders
Completion
Customer approval
Invoice delivery
Payment receipt
Overdue invoices
Expiring insurance
Expiring licenses
Maintenance requirements
Equipment faults
Safety incidents
Franchise compliance issues
Users should be able to configure notification methods and priorities.
28. Permissions and Security
SiteFleet OS should use role-based permissions.
Users should only access information appropriate to their role, company, territory, and customer relationship.
Security requirements should include:
Multi-factor authentication
Encryption
Secure document storage
Role-based access
Audit logs
Session controls
Password standards
Data backups
Disaster recovery
Cybersecurity monitoring
Data-retention policies
Privacy controls
Vendor-access restrictions
29. Integrations
The system should be designed to integrate with third-party platforms.
Potential integrations include:
Accounting software
Payroll software
Banking and payment systems
CRM systems
Telematics providers
GPS providers
Fuel-card systems
Maintenance systems
Insurance providers
Electronic signature providers
Mapping services
Weather services
Customer procurement portals
Franchise accounting systems
Background-check providers
Driver qualification systems
Marketing platforms
Cloud storage
ERP systems
An application programming interface should be developed so approved systems can securely exchange data with SiteFleet OS.
30. Multi-Company and Multi-Franchise Architecture
The platform must support:
Multiple subsidiaries
Multiple franchise entities
Multiple territories
Multiple service lines
Multiple pricing models
Multiple contract templates
Multiple accounting entities
Shared customers
Corporate-owned assets
Franchise-owned assets
National accounts
Territory-based permissions
Each subsidiary should have a customized customer experience while operating on the same core platform.
31. Mobile and Web Requirements
SiteFleet OS should include:
Customer web portal
Customer mobile experience
Franchise owner portal
Operator mobile application
Corporate operations dashboard
Administrative dashboard
Finance dashboard
Management analytics dashboard
The operator application should be designed for:
Simple navigation
Large buttons
Limited typing
Voice-to-text
Photo capture
Offline use
Automatic synchronization
Field durability
Low-bandwidth environments
32. Audit Trail and Legal Recordkeeping
The platform should maintain an audit trail for:
Estimate changes
Contract approvals
Work-order acceptance
Schedule changes
Operator assignments
Mobilization
Location records
Change orders
Customer approvals
Invoice changes
Payment activity
Compliance changes
User access
Document revisions
The audit trail should identify:
User
Date
Time
Action
Original information
Revised information
Approval authority
33. Recommended Development Phases
Phase 1: Core Minimum Viable Platform
The first phase should establish:
Customer intake
Service selection
Lead capture
Basic estimating
Contract generation
Electronic signatures
Work-order creation
Franchise job board
Operator qualification
Basic scheduling
Customer notifications
Mobile field workflow
Completion approval
Invoicing
Payment tracking
Corporate fleet assignment
Basic dashboards
Phase 2: Franchise and Fleet Operations
The second phase should add:
Franchise management
Advanced scheduling
GPS integration
Telematics
Maintenance management
Compliance management
Customer document delivery
Revenue-sharing calculations
Franchise scorecards
Route optimization
National account controls
Phase 3: AI and Automation
The third phase should add:
AI scope analysis
Automated estimating
Front office AI assistants
Back office AI assistants
AI document review
Automated invoice validation
Dynamic pricing
Predictive maintenance
Lead qualification
Customer cross-selling
Intelligent job matching
Phase 4: Enterprise Intelligence
The fourth phase should add:
Enterprise analytics
Predictive forecasting
Territory optimization
Franchise benchmarking
Equipment investment analysis
Customer profitability
Artificial-intelligence decision support
Advanced national account management
Automated operational recommendations
34. Initial Development Deliverables
The software development team should use this outline to create the following next-stage deliverables:
Formal product requirements document
Platform architecture diagram
User-role and permission matrix
Customer journey map
Franchise operator journey map
Field operator workflow
Work-order lifecycle diagram
Data model
Integration architecture
Security architecture
AI assistant requirements
Telematics requirements
Minimum viable product feature list
Development sprint plan
Budget and resource estimate
Testing plan
Deployment strategy
Support and maintenance plan
35. Platform Vision
SiteFleet OS is intended to become far more than a dispatch or fleet-management platform. It is designed to function as the complete operating infrastructure for the SiteFleet franchise ecosystem.
The platform will generate leads, qualify customers, estimate work, create contracts, match jobs with qualified operators, monitor fleet activity, manage compliance, automate customer service, invoice completed work, track payments, and provide franchisees with the tools necessary to operate successful businesses.
By centralizing these capabilities, SiteFleet will create a consistent customer experience across all subsidiaries and franchise territories while reducing the administrative burden placed on individual franchise operators. Franchisees will be able to focus on operating equipment, serving customers, and growing their territories while SiteFleet OS provides the technology, lead generation, administration, compliance, and operational support needed to compete at an institutional level.
The long-term objective is to create a technology-enabled franchise ecosystem that is difficult for traditional service companies or independent operators to replicate. SiteFleet OS will strengthen franchise success, improve asset utilization, enhance customer retention, standardize service quality, create recurring platform revenue, and provide SiteFleet Holdings with the operational intelligence required to scale a national infrastructure-services organization.