← Back to the guide

Type into the blank cells, then print or use your browser’s “Save as PDF”. Typed changes are not saved when you close this page. The filled example follows your blank copy.

Use this with AxiomBlue

Apply this decision process through AxiomBlue’s schedule controls, with a human review of customer commitments.

  1. Check job duration, address and weather sensitivity alongside the current forecast. Review existing bookings and, on Professional, crew skills and approved leave.
  2. Preview the proposed schedule change in Auto Schedule. Check travel, warnings, unplaced jobs and fixed appointments before applying it; then inspect the changed job records.
  3. Confirm changed arrangements with the affected customers and crew. If you configure a rescheduling notification automation on Professional, test its recipient mapping and channel first; a schedule edit alone is not proof of delivery.

Product instructions: Scheduling jobs on the Crew Calendar · Auto-Scheduler & Schedule Health · Automation Overview

AXIOM BLUE / PRACTICAL RESOURCES

Rain-day and bad-day playbook

Your working copy

Decide these before the bad day, so the morning of it is a checklist, not a meeting. Fill in the example column with your own rules. It is a planning worksheet; check the forecast source and any contract commitments you have with customers.

What to recordYour notes
Who makes the call, and by when
What counts as a washout
Which jobs move
Where they go
Preview check before applying
Who tells the customers
Who tells the crew
What the stood-down crew does instead
If the weather clears by 9:00 am
A call-out on a bad day
A job running over
Review at the end of the week

AXIOM BLUE / PRACTICAL RESOURCES

Rain-day and bad-day playbook

Filled example — illustrative records

Decide these before the bad day, so the morning of it is a checklist, not a meeting. Fill in the example column with your own rules. It is a planning worksheet; check the forecast source and any contract commitments you have with customers.

What to recordExample
Who makes the call, and by whenOwner or scheduler, by 6:00 am, from the 5:30 am forecast
What counts as a washoutMore than 70% chance of 5 mm or more before midday, or lightning forecast
Which jobs moveOnly jobs marked weather-sensitive (roofing, external painting, lawns); indoor work stays
Where they goThe next available day, weekends excluded; same crews where possible
Preview check before applyingNo job left without a slot; no fixed customer appointment pushed past its deadline
Who tells the customersOffice confirms changed arrangements; an explicitly configured and tested notification can assist
Who tells the crewMoves show in the app; crew leader texts the team by 6:15 am
What the stood-down crew does insteadIndoor jobs brought forward, van restock, quotes, training
If the weather clears by 9:00 amReview and apply a revised plan if appropriate; confirm the agreed time with each affected customer
A call-out on a bad dayDispatch Map: the crew it adds least driving to; tell any customer whose job moved
A job running overExtend it on the calendar; move the next job and let its customer know
Review at the end of the weekJobs moved, customers who complained, calls the office took, what to change in the rules