Straight into the service manual page
WrenchQuarry
More

3 safety check intervals a dispatcher sets for crews

WrenchQuarry Editorial Team · Published · 11 min read · How these guides are written

The three recurring safety check intervals a dispatcher sets are every trip, weekly, and monthly to annual.

  • Every trip — the driver files a post-trip report after every run, even when no defects are found.
  • Weekly — the dispatcher drafts, gathers driver input, and files a project safety review report under the safety category of project records.
  • Ownership — each check gets one name and a back-up, with the dispatcher watching every due date and chasing missing reports.
  • One board — daily, weekly, monthly, and annual items live on a single calendar so the monthly checks do not vanish behind the daily noise.

What the three intervals are

You run a small field crew. Your calendar already fills with job start times, drive windows and customer callbacks. Safety checks sit on top of that. Three recurring intervals cover most of what your crews touch on a job site and in a truck.

The first is every trip. The driver reports defects before and after each trip. The second is weekly. A project safety review report gets completed and filed each week. The third is monthly to annual.

These three cadences do different jobs. The trip check catches a broken tie-down before the truck leaves the yard. The weekly review catches a pattern — the same unsafe condition showing up on the same job for three weeks straight. The monthly and annual cycle catches the slow stuff: a fire extinguisher losing its charge, a training certificate lapsing.

Set the three on one calendar. Assign one name to each. Then your crews know what gets checked, when it gets checked and who answers when it does not.

Why a dispatcher owns these dates

The dispatcher holds the live picture. You see which truck is rolling, which crew is on site and which job just changed. That makes you the person who can enforce a recurring check without slowing the crew down.

The weekly report is a real deliverable. The California Department of Transportation construction manual says a project safety review report must be completed every week and filed under the safety category of the project records. Someone has to own that filing date. On a small crew, that someone is the dispatcher.

The trip report works the same way. The FMCSA Safety Planner says a report must be submitted after every trip, even when no defects are found. That rule removes judgment from the driver. It is not "report if something broke." It is report, always. The dispatcher watches for the missing report, not the broken part.

Training dates live on your board too. The heat illness prevention training runs annually for all field staff. The hazard communication training runs every two years. Both are mandatory under that manual. If you let one slip, the crew shows up to a hot job site without the refresher, and the paperwork trail shows the gap.

The point of dispatcher ownership is simple. The crew is busy doing the work. You are the one watching the clock.

Interval one: every trip

Every trip means every trip. A truck leaves the yard, a report gets filed when it comes back. The report covers pre-trip and post-trip checks. It records defects the driver found and defects anyone else reported to the driver during the run.

The FMCSA requirement is blunt: submit the report after every trip, even if no defects are found by or reported to the driver. The empty report is the point. It proves someone looked.

What goes in a trip report on a small crew:

  • Pre-trip walk-around — tires, lights, mirrors, tie-downs, load securement.
  • Cab check — gauges, brakes, wipers, horn.
  • Defects noted — anything the driver saw, heard or felt.
  • Other reports — a customer or a spotter flagged something during the run.
  • Signature — the driver confirms the report is complete.

Dispatch workflow for the trip check:

  1. Truck rolls. You log the departure.
  2. Truck returns. You confirm the report was filed.
  3. No report within your window, you call the driver.
  4. Defect found, the truck stays parked until it is fixed.

The dispatcher's job is not to inspect the truck. It is to confirm the report exists. A driver who skips the empty report will skip the defect report too. The pattern starts with the easy one.

On a two-truck crew this feels like overhead. Run it for a month and it pays back the first time a driver catches a cracked tie-down before the highway instead of after.

Interval two: weekly

Weekly is your pattern check. One report, filed every week, covering the whole project or job site. The Caltrans construction manual requires a project safety review report every week, filed in the safety category of project records. The filing location matters as much as the report. If it lands in the wrong folder, the next person looking for it will not find it.

The weekly report is where unsafe conditions get named. The manual's instruction is to identify unsafe conditions and the specific contract provisions or regulations involved. Naming the regulation turns a complaint into a finding. "Guards missing on the saw" is a note. "Guards missing on the saw, contract provision on machine guarding applies" is a record.

What the weekly review covers:

  • Incidents and near misses — anything that happened, plus anything that almost happened.
  • Repeating conditions — the same hazard showing up week after week.
  • Corrective actions — what was fixed, what is still open.
  • Training status — who is current, who is coming due.
  • Sign-off — one name confirms the report is complete and filed.

The dispatcher's weekly rhythm:

  • Monday — pull last week's open items.
  • Midweek — walk the yard, confirm corrections landed.
  • Friday — draft the report, gather driver input, file it.
  • Close out — mark the week's report filed, open next week's log.

One report a week sounds light. Do it for a quarter and you get a timeline you can hand to anyone: what broke, what got fixed, what kept coming back. That timeline is the cheapest proof that your crew runs a real safety program and not a stack of forgotten forms.

Here is how the three intervals compare:

IntervalWhat gets checkedWho files it
Every tripVehicle defects, found or not foundDriver
WeeklySite conditions, incidents, corrective actionsDispatcher
Monthly to annualEquipment condition, training currencyDispatcher

Interval three: monthly to annual

This interval holds the slower checks. Equipment condition runs monthly. Training runs annually or every two years. The dispatcher puts them on a wall calendar and watches them come due.

Monthly inspection of portable fire extinguishers sits in this bucket. The CCOHS fire extinguisher guidance raises the question of what items may be included in a monthly inspection, and the supplied guidance does not answer it — confirm the item list with your safety officer or local fire authority. Nothing on that list needs a specialist. A crew member with two minutes and a checklist can do it.

Training runs on a longer clock. The Caltrans construction manual sets the floor at four hours of safety training for each employee each year, included in the district's annual training plan. The same manual requires heat illness prevention training annually for all field staff, and hazard communication training offered every two years. Three separate training obligations, two different clocks, one planner.

Monthly to annual checklist for the dispatcher:

  • Monthly — fire extinguisher walk, tag signed, gauge readable.
  • Monthly — first aid kit stock and eyewash station checked on your own schedule.
  • Annually — heat illness prevention refresher for every field employee.
  • Annually — four hours of safety training logged for each employee.
  • Every two years — hazard communication training offered and recorded.
  • On hire — new employee gets the full set of training.

The calendar entry that saves you is the one set a month early. Heat illness training that pops up the week of a heat wave is training nobody has time to run. Load it in the shoulder season.

Ask your safety officer or your local fire authority which items you must sign off on, then build the checklist from that answer.

Building one calendar that holds all three

Three intervals, one board. Put them where the dispatcher and the crew both see them.

A simple setup that works:

  • Daily log — trip reports, sorted by truck.
  • Weekly log — safety review report, one row per week, filed Friday.
  • Monthly row — equipment inspection, due on a fixed date.
  • Weekly row — training status, who is current, who is coming due.
  • Annual row — heat illness refresher, four-hour training total.

The daily and weekly items run off live jobs. The monthly and annual items run off the calendar date. Keeping them on the same board stops the monthly check from vanishing behind the daily noise.

Color coding earns its keep here. Red for anything past due. Yellow for anything due this week. Green for done and filed. You can read the whole safety program off one screen in the morning without opening a single document.

When a job changes the picture — a new site, a new hazard, a new driver — you move the relevant check forward. A hot job site pulls the heat illness refresher closer. A new driver pulls the full training set forward to onboarding. The calendar is a living thing, not a printout.

Who does what on the crew

Clear names beat clear rules. Every recurring check gets one owner, with a back-up you name alongside.

  • Driver — files the trip report every run.
  • Crew lead — walks equipment, checks extinguishers, signs the tag.
  • Dispatcher — watches every due date, chases missing reports, files the weekly review.
  • Safety officer — sets the training plan, approves the checklist, answers regulation questions.
  • Owner — reads the weekly report, funds the fixes.

The dispatcher is the hinge. Drivers and crew leads produce the evidence. The safety officer sets the standard. The owner sees the pattern. Without the dispatcher watching the dates, the reports pile up unfiled and the training lapses quietly.

Back-ups matter. If your only dispatcher takes a week off and nobody else watches the due dates, the whole system runs on memory. Give the back-up the same board access and a standing reminder.

What a missing check looks like

Missed checks do not announce themselves. They show up as small frictions that stack.

  • No trip report filed — you find out when an insurer or auditor asks for last month's records.
  • Weekly report skipped for two weeks — you cannot reconstruct what happened or what got fixed.
  • Extinguisher tag stale — you find out during a walkthrough, not during the fire.
  • Heat illness training late — you find out during the first heat wave of the year.
  • Hazard communication training past due — a new chemical enters the yard and nobody on the crew has the refresher.

Each of those gaps starts as a date nobody owned. The fix is not a new policy. It is putting the date on the board with a name next to it.

Running the board week by week

A week on the dispatcher's board looks like this:

  • Monday morning — open the log, list last week's open corrective actions, check any trip reports still missing from Friday.
  • Tuesday — confirm the crew lead started the monthly equipment walk if this week carries it.
  • Wednesday — midweek check on open items from the weekly review.
  • Thursday — pull training status. Flag anyone coming due within the next month.
  • Friday — draft the weekly safety review report, gather driver input, file it under safety records, close the week.
  • Month end — confirm the extinguisher tags are signed, confirm the gauge readings, record the monthly walk.

Fifteen minutes a day keeps the board honest. The alternative is a Friday afternoon scramble to reconstruct a week you no longer remember.

What the owner should ask for

Owners should not run the board. They should read it.

Ask for three things each month:

  • The weekly report stack — every week filed, nothing missing.
  • The open corrective action list — what is still broken and how old it is.
  • The training status — who is current, who is coming due.

If the stack is complete and the open list is short, the program is working. If the stack has holes, the dispatcher needs help, not criticism. Holes in the stack usually mean the dispatcher is carrying too many live jobs to sit down and file.

The four-hour annual training floor belongs in the annual plan. Check that plan once a quarter, not once a year. A plan that slips in March does not recover by December.

Putting the three intervals to work this week

Start small. Three intervals, one board, one name each.

  1. Confirm every driver files a trip report on every run, including clean runs.
  2. Put the weekly safety review report on a fixed day and file it under safety records.
  3. Set the monthly equipment walk on a fixed date with a named crew lead.
  4. Put heat illness prevention training, the annual four-hour training total, and the two-year hazard communication training on the calendar with lead-time reminders.
  5. Give the dispatcher the board, a back-up, and fifteen minutes each morning to read it.

The three intervals are not paperwork for paperwork's sake. The trip report keeps a defective truck off the highway. The weekly review turns a recurring hazard into a named finding. The monthly and annual cycle keeps the slow equipment and training obligations from lapsing unnoticed.

Run all three and your safety program stops being a folder of forgotten forms. It becomes a live record your crew, your insurer and your regulator can all read the same way.

General information, not legal or tax advice.

Sources

More field guides