Freight Fleet SOP Questions: Process Street or SweetProcess

The specific list, application, license verification, medical certificate, road test, drug and alcohol testing records, is a compliance standard that does not change per driver, so it belongs documented once in SweetProcess.

What changes per driver is status: which documents are collected and which are still outstanding, which is exactly what a Process Street checklist tracks, one instance per new hire, with a blocked go-driving step until every required document is on file.

A fleet running a mix of company drivers and owner-operators often applies this inconsistently, treating the file as optional paperwork for an owner-operator hauling under their own authority. Regardless of employment status, the file needs to be complete before that driver is dispatched under your operation.

A driver qualification file checklist should confirm each of these is on file:

• The driver's application and license verification are both collected and recorded, with outstanding documents visible for that driver.
• The medical certificate is on file and current before the driver is cleared to drive.
• The road test result is recorded and attached to the driver's file before the driver is assigned a load.
• Drug and alcohol testing records are collected and filed as part of the same qualification record.
• One checklist instance exists per new hire, and the go-driving step stays blocked until every document is complete.

A checklist alone will not fix that; it needs an owner who actually reviews the completed inspection, not just confirms one was submitted, and a documented standard for what a defect report should trigger, does the truck get pulled from dispatch, or does it run with a flagged repair.

Process Street can require the inspection record before a load gets assigned; SweetProcess documents what dispatch is supposed to do when a defect shows up, so the answer does not depend on who is working that shift.

The pattern worth watching for is a driver who submits the same defect-free inspection report regardless of the truck's actual condition. Spot-checking a sample of reports against the vehicle's maintenance history is a cheap way to catch that before it becomes a roadside violation.

Most fleets already have electronic logging device data doing the real-time tracking; the SOP gap is usually what happens next, who reviews violations, how a driver gets coached, and when a pattern triggers something more than a conversation.

Document that escalation standard once in SweetProcess, and run the weekly review as a recurring Process Street task assigned to whoever owns safety, even if that is currently the owner-operator themselves.

A single repeated violation from the same driver is a different situation than a first-time edge case caused by a weather delay, and your documented standard should say clearly which response applies to which, rather than leaving that judgment call to whoever happens to review the log that week.

Fast, complete documentation matters for insurance and liability, which makes this a case where a checklist genuinely helps: a Process Street task triggered the moment an incident is reported, walking whoever is on call through photos, driver statement, and notifying insurance, in order, so nothing gets missed in the moment.

What counts as a reportable incident, and who has authority to speak to insurance, is a standard written once in SweetProcess so it does not depend on which dispatcher is on shift.

A minor incident that seems too small to log at the time is often the one that resurfaces weeks later as a claim, which is exactly why the reporting threshold needs to be documented rather than judged case by case.

Claims processing, cargo damage, freight loss, is downstream of incident reporting and belongs on its own checklist with its own deadlines, since insurers and shippers both have response windows that do not wait for your fleet to catch up.

It is also where back-office work, paying out settlements, tracking recovered costs, tends to bottleneck; a platform like Every is built for that financial administration side once claims volume is more than the owner can track in a spreadsheet.

Olivia, MeetMyCOO's AI COO, can help you work out where the handoff between dispatch, safety, and claims should happen on your own checklist, since that handoff is usually where a claim quietly stalls.