Fleet, Inventory & Safety

A field technician's workplace is mostly a vehicle and other people's property. The truck carries the products, the equipment, the spare parts and the person, and it spends more of the day moving than parked. That makes the fleet three things at once: the business's biggest physical cost after labor, a regulated workplace with its own federal and state rules, and a source of data (where every truck is, how it's driven, how long it idles) that the rest of the platform can use.

Field-service software often leaves the fleet to a separate telematics vendor and a spreadsheet. It works until a truck with a brake defect is assigned to a route, a technician runs out of product halfway through the day, or an injury needs reporting within hours and nobody knows whose job that is. This chapter covers what the platform should know about vehicles, the materials they carry and the people in them.

When a Truck Is a Commercial Motor Vehicle#

The Federal Motor Carrier Safety Regulations apply to commercial motor vehicles (CMVs). In the federal definition, a vehicle used on a highway in interstate commerce to carry property is a CMV when its gross vehicle weight rating, gross combination weight rating, or actual weight is 10,001 pounds or more, whichever is greater. Vehicles carrying more than 8 passengers for compensation, more than 15 without compensation, or hazardous materials in quantities that require placards are CMVs regardless of weight.

A compact pickup with a spray tank usually sits under the line. A heavy-duty pickup towing an equipment trailer, a box truck, or a service body on a one-ton chassis can cross it, and the combination rating counts. Two caveats make this a per-vehicle question, not a per-company one:

• Intrastate rules can differ. The federal definition turns on interstate commerce. States set their own rules for vehicles operating only within the state, and their thresholds and exceptions don't always match the federal ones. Check the rules where the trucks run.
• The rating is what counts, not the load today. Record each vehicle's GVWR and the GCWR of any combination it pulls, so the system can tell which vehicles bring which obligations.

When a vehicle is a CMV, a set of obligations follows for the vehicle and its driver:

Obligation	What it requires
Medical certification	Drivers examined and certified as physically qualified, generally at least every 24 months, more often for some conditions
Daily inspection report	A written report at the end of each day's work on each vehicle, when a defect is found or reported
Annual inspection	Every vehicle inspected at least once in the preceding 12 months, with documentation carried on the vehicle
Hours of service	Limits on driving and on-duty time, with a short-haul exception for drivers who stay local
Texting	Drivers may not text while driving, and carriers may not require or allow it

The short-haul exception matters most for route businesses. A driver who stays within a 150 air-mile radius of their normal reporting location, and returns and is released within 14 consecutive hours, is exempt from the standard record-of-duty-status rule. Property-carrying drivers still need 10 consecutive hours off between on-duty periods, and the carrier must keep time records for six months showing when the driver reported, total on-duty hours, and when they were released. A field app that already records clock-in and clock-out (The Technician App) is most of the way to those records; the platform needs to keep them for the required period and be able to produce them per driver.

Inspections#

Inspections exist to keep an unsafe vehicle off the road, and the system's job is to make sure the defect a driver reports actually stops the vehicle.

For CMVs, the daily inspection report has to cover at least service brakes (including trailer brake connections), parking brake, steering, lights and reflectors, tires, horn, wipers, mirrors, coupling devices, wheels and rims, and emergency equipment. Drivers don't have to prepare a report when no defect was found or reported to them. Reports, with the repair certification and the next driver's review, are kept for three months.

Even for vehicles under the CMV line, the same checklist is good practice, and it costs little to run every truck through it. Build it into the app as part of clock-in or clock-out, with photos for anything flagged, and connect it to assignment:

• A safety defect takes the vehicle out of service until a repair is certified. Route assignment checks the vehicle's state, the same way it checks a technician's skills and licenses (Dispatch & the Day of Service).
• The next driver reviews the repair before driving. The record shows the defect, the repair and the review, in that order.
• Annual inspections and registrations are dates with owners. Track each vehicle's inspection, registration and insurance expiry the way you track technicians' licenses, with reminders well before they lapse.

Telematics#

A telematics device in each vehicle reports where it is, how it's driven and how the engine is doing. Vendors such as Motive, Samsara and Geotab sell the hardware and an API; the platform's job is to connect the vehicle's data to the person and the work. Typical data:

• Location and trips: GPS points, trip start and stop, stops at addresses, miles driven.
• Driver behavior: accelerometer events such as harsh acceleration, braking and turning, speeding and crashes; AI dash cameras add events such as rolling stops, following distance and distracted driving.
• Engine and vehicle: odometer, fuel, idle time, diagnostic trouble codes, depending on the device and vehicle.

The integration that makes it useful is who drove which vehicle when. Assignments change (a truck in the shop, a technician covering another route), so record the vehicle on each shift, from the driver's selection at clock-in, a scan of a code in the cab, or the telematics vendor's own driver login. Then the data answers questions the platform cares about:

• Planned versus actual. Compare the optimizer's planned drive times and sequence to the actual trips. Systematic gaps mean the road network data or the service durations are wrong (Route Optimization).
• Proof of visit. A stop at the property's coordinates during the visit window corroborates the check-in (Proof of Service).
• Costs. Miles and idle time per route, per branch, per technician. Idling is fuel spent going nowhere, and in hot or cold climates it's how technicians stay comfortable between stops, so measure it before trying to eliminate it.
• Safety coaching. Events with video, reviewed and coached, with a safety score per driver over time.
• Maintenance. Service schedules from odometer readings; fault codes as early warnings.

Telematics is also data about people. Decide what's collected, who can see it, how long it's kept, and whether it's tied to a person off the clock, and tell drivers. Involve counsel before using it for discipline.

Hazardous Materials on Board#

A pest control or lawn care truck carries concentrated products that are hazardous materials in transport, and federal hazmat rules apply even though the truck isn't a hazmat carrier. The usual route through them is the materials of trade exception: hazardous materials carried by a business in the course of its work, in limited quantities, are exempt from most of the hazmat regulations if a short list of conditions is met.

• Quantity per package. For most classes a field truck carries, up to 30 kilograms (66 pounds) or 30 liters (8 gallons) per package for packing groups II and III, and much less for the most dangerous packing group I.
• Quantity per vehicle. The total gross weight of all materials of trade on a vehicle can't exceed 200 kilograms (440 pounds), with separate limits for batteries.
• Packaging. Leak-tight for liquids, sift-proof for solids, securely closed, secured against shifting and protected from damage, in the manufacturer's original packaging or packaging at least as strong.
• Marking. A common name or proper shipping name on each package.
• The driver knows. The operator must be informed that the hazardous material is on board and of the exception's requirements.

States add storage rules for pesticides on service vehicles. Arizona requires pesticides on an unattended service vehicle to be in a locked storage space unless the responsible applicator keeps them in view, and requires containers to be secured in a locked space during transport. Utah requires containers to be secured during transport, and products with "danger" or "poison" signal words to be locked away from children, unauthorized people and animals. Check each state's rules; the pattern is consistent enough to design for:

• Know what's on each truck, by product and quantity, from inventory (Truck Stock and Inventory), so the per-vehicle limit can be checked and an inspector or emergency responder can be told.
• Carry the safety data sheets for everything on board, available offline on the device (Safety Data Sheets in the Field).
• Equip and record spill kits, and make a spill a reportable incident in the app.

Truck Stock and Inventory#

Products, bait stations, traps, filters and parts move from a supplier to a branch warehouse, from the warehouse to a truck, and from the truck to a customer's property. Each step is a point where stock can be wrong, and a technician who discovers mid-route that the truck is out of the product a visit requires has just lost that visit.

Model inventory as locations (supplier, warehouse, truck) and movements between them:

• Receiving puts stock into a warehouse, with lot numbers and expiry dates where products have them.
• Loading moves stock from the warehouse to a truck, usually at the start of the day or the week.
• Consumption moves stock from a truck to a property. For regulated products, derive it from the material records the technician already completes (Proof of Service) instead of asking for a separate count.
• Restock requests come from the truck: requested, approved or denied, and fulfilled, so a supervisor can see what each truck is asking for and whether it got it.
• Counts reconcile the system with reality. Cycle-count trucks on a schedule; a large gap between expected and counted stock is a training problem, a recording problem, or theft.

Then use it for planning. The route for tomorrow knows which services are scheduled and which products each typically needs, so the system can warn the night before that a truck won't have enough termite bait for its three inspections. For regulated products, the lot and expiry on the truck also matter for the record: an expired product shouldn't be offered in the app's product list.

Protective Equipment#

Under OSHA's general PPE standard, an employer must assess the workplace for hazards that call for protective equipment, select equipment that fits each affected employee, and certify the assessment in writing with the workplace, the person certifying and the date. Each employee who must use PPE is trained on when it's needed, what it is, how to put it on, adjust and remove it, its limits, and its care, and must show they understand before doing the work. The employer pays for required PPE, with narrow exceptions such as ordinary safety-toe footwear.

For applicators, the product label adds its own requirements: the label specifies the gloves, eyewear, respirator or coveralls for that product and application method (Regulated Materials). A system can help:

• Show the PPE a product requires on the material record screen, from the label data in the catalog.
• Record issuance and training per technician: what was issued, when, fit tests for respirators, and training dates.
• Run a PPE check as part of the vehicle inspection or clock-in: present, in good condition, replacements requested.

Safety Data Sheets in the Field#

OSHA's hazard communication standard requires safety data sheets to be readily accessible to employees during each shift when they're in their work areas, and electronic access is acceptable if it creates no barriers to immediate access. For employees who travel between workplaces during a shift, the sheets may be kept at the primary workplace facility, provided employees can get the information immediately in an emergency.

For a field operation, the device is the natural place. Ship the safety data sheet and label for every product in the catalog with the app's offline data, and link them from the product, the material record and the truck's inventory. A technician with a splash in the eyes in a basement with no signal shouldn't depend on a download.

Incidents and Injuries#

Things go wrong in the field: an injury, a vehicle accident, a spill, a dog bite, damage to a customer's property. Each needs a report, fast, and some carry legal deadlines:

• Fatalities must be reported to OSHA within 8 hours, and in-patient hospitalization, amputation or loss of an eye within 24 hours.
• Motor vehicle accidents on a public road (outside a construction work zone) don't have to be reported to OSHA under that rule, but must still be recorded in the injury and illness records if the employer keeps them.
• Injury and illness records (the OSHA 300 log, the annual summary and incident reports) are kept for five years after the end of the year they cover.

Give the app an incident report that works offline: what happened, when, where, who was involved, photos, the vehicle, and any product. Route it immediately to a named person per branch, with the clock on any reporting deadline visible. Link incidents to the vehicle, the technician, the visit and the customer, so a property damage claim, an injury record and a vehicle repair can be traced back to the same event.

Certifications and Training#

Fleet and safety records are mostly dates that expire:

Record	Belongs to	Blocks when it lapses
Driver's license	Technician	Driving any vehicle
Medical certificate (CMV drivers)	Technician	Driving a CMV
Applicator license	Technician	Applying regulated products where it's required
PPE training, respirator fit test	Technician	Work requiring that equipment
Annual inspection	Vehicle	Assignment of that vehicle
Registration, insurance	Vehicle	Assignment of that vehicle

Treat them the same way: an expiry date, an owner, reminders on a schedule before it lapses, and a rule that the scheduler and dispatcher check before assigning the person or vehicle. Licenses & Permits covers the model for licenses in depth; vehicle and safety records fit the same shape.

What This Means for the System You Build#

• Each vehicle with its weight ratings, so the system knows which ones are commercial motor vehicles and which obligations follow.
• Time records kept per driver for the short-haul exception, from the app's clock-in and clock-out.
• Inspections in the app, with defects taking the vehicle out of service until a repair is certified and reviewed, and assignment checking vehicle state.
• The vehicle recorded on every shift, linking telematics trips and events to the technician and the visit.
• Telematics used for planned versus actual, proof of visit, costs, coaching and maintenance, with a stated policy for driver data.
• Inventory as locations and movements, consumption derived from material records, restock requests with states, and counts.
• Per-vehicle hazardous material quantities, state storage rules met, and SDS and labels available offline.
• PPE requirements shown from label data, with issuance and training recorded per technician.
• An offline incident report routed to a named owner with reporting deadlines visible.
• Expiring records for people and vehicles in one model, checked before assignment.

References#

Specifications

• 49 CFR 390.5: Definitions, commercial motor vehicle at 10,001 pounds or more, and the passenger and placarded hazmat prongs
• 49 CFR 391.45: Persons who must be medically examined and certified, certification within the preceding 24 months, and shorter intervals for some conditions
• 49 CFR 395.1: Scope of rules in this part, the 150 air-mile, 14-hour short-haul exception and six months of time records
• 49 CFR 396.11: Driver vehicle inspection reports, parts covered, no report when no defect, and three-month retention
• 49 CFR 396.17: Periodic inspection, each vehicle inspected within the preceding 12 months
• 49 CFR 392.80: Prohibition against texting, drivers and carriers
• 49 CFR 173.6: Materials of trade exceptions, per-package and 200-kilogram vehicle limits, packaging, marking and informing the operator
• 29 CFR 1910.132: Personal protective equipment, general requirements, hazard assessment and written certification, training, and employer payment
• 29 CFR 1910.1200: Hazard communication, safety data sheets accessible each shift, electronic access, and employees who travel
• 29 CFR 1904.39: Reporting fatalities, hospitalizations, amputations and losses of an eye, 8- and 24-hour deadlines and the public road exception
• 29 CFR 1904.33: Retention and updating, five years of injury and illness records
• Ariz. Admin. Code R3-8-302: Storing and disposing of pesticides and devices, locked storage on unattended service vehicles and in transport
• Utah Admin. Code R68-7-19: Storage, transportation and disposal, securing containers in transport and locking "danger/poison" products

In practice

• Samsara: Driver behavior guide, accelerometer and dash camera safety events, and driver and vehicle safety scores