Schedule it once, and it’s on everyone’s calendar.
Most scheduling failures aren’t calendar failures — they’re relay failures. RSP eliminates the breakdown: schedule a job once, and the same date lands on every crew calendar, on the office’s board, and — if you choose — on the customer’s own job page.
The board
The schedule is one board with a lane per technician, at four zoom levels — Day, Work Week, Week and Month — with an agenda list one tap away, which is how a schedule reads best on a phone. Beside the grid sits the bench: everything won but not yet booked, in plain sight, grouped by what it is, until somebody gives it a date. That is the entire system for not forgetting work, and it works because it is boring. Installs, service calls, site visits and inspections all live on the same grid — a schedule that shows two thirds of the work is a schedule everybody quietly keeps a second copy of.
Drag to schedule, drag to reschedule
Pull a job from the bench onto a technician and a day, confirm the times and the crew — a lead tech plus any helpers — and it’s booked. Rescheduling is the same drag in reverse. Multi-day installs land on every assigned tech’s lane across every day they run, and when plans change they reconcile rather than rebuild: extend the range, shorten it, or swap crew partway through, and the days sort themselves out. Days already worked keep their history.
Real calendar invitations
Scheduling a job sends each booked technician a real calendar invitation — one per person per day, landing in Outlook, Apple Calendar or Google Calendar alike, with nothing to install or connect on their end. Move the job and the invitation updates the same event instead of stacking a duplicate; take someone off the crew and theirs cancels. Invitations go to your team, never to a customer.
RSVPs, visible back
The answers come back to the board. The office sees who accepted, who declined, and who hasn’t answered, right on the grid — an acceptance is a quiet tick, a decline is a flag the dispatcher can’t miss. Nobody schedules a Thursday around a tech who said no on Monday.
And for teams on Google Workspace, the board also shows where a tech is already committed elsewhere — a plain busy block, without reading what their calendar says.
Site visits, before there’s an estimate
Not everything schedulable is a job yet. A walk-through books straight from the lead — a date, a technician, a window — and you can share it to the customer’s page if you choose, so “somebody is coming Thursday at ten” exists in writing on both sides.
From accepted to a date, on a Tuesday afternoon
What stops a job from being forgotten?
Work that has been accepted but not yet scheduled sits on a visible bench next to the calendar, grouped by type, until somebody gives it a date. It is not in a folder, an email or somebody’s head. The AI assistant’s brief raises it too, so an unscheduled job that has been sitting a while comes and finds you.
Does this land on my technicians’ real calendars?
Yes. Scheduling a job sends each booked technician a standard calendar invitation that lands in Google Calendar, Apple Calendar or Outlook and blocks the slot — nothing to install or connect on their end. Reschedule and it updates the same event rather than stacking a duplicate; unschedule and it cancels. Customers never receive one — invitations are for your team only.
Can I see every crew’s week in one view?
That is what the board is — one lane per technician, at four zoom levels from a single day to a month, with everything the company has on: installs, service calls, site visits and inspections together. An agenda list sits one tap away for when you’re reading it on a phone rather than a monitor.
What about jobs that need two people, or more than a day?
Booking takes a lead technician plus any helpers, so a job that needs a second set of hands is scheduled as one job rather than two. Multi-day installs land on every assigned technician’s lane across every day they run, and extending, shortening or re-crewing partway through reconciles the remaining days instead of rebuilding them.
Does my customer find out when I schedule them?
Only if you want them to. Scheduling can post the date and the assigned technician to the customer’s own private job page, and that is a decision per job rather than something that happens automatically. Nothing about your internal scheduling — who else is booked, or what else is on — is ever visible to them.