Rankine Operating Company · AC Services
Rollout 1: going live
How we onboard technicians, train dispatch, run day one, and learn from what the system records.
Owners’ briefing · go-live Friday 6 November 2026, 9:00 am
Measured, not promised.
What goes live
Four surfaces open on day one
S1 · acservice.systems
Front door
Where everyone starts. One sign-in; the system sends each person to their own workspace.
S2 · /service-manager
The office
Accounts, contracts, leads, field devices and shift grants, purchasing and billing.
S3 · /dispatch
Dispatch console
The live board for one region: intake, assignment through the compliance gate, job state.
S5 · /technician
Technician field app
Device sign-in with a shift grant. Works offline and sends the work when the signal returns.
S4, S6, S7, S8: built; their logins are told “Your portal is not open yet.”
02 / 14
Before we go
All four gates are green
Gate
What proves it
Today
1 · Production deploy is green
A guard run on main passes both deploy jobs; the gateway answers ready
Done 2 Nov: new database, every deploy job green
2 · Photos reach storage
The gateway reports photo storage reachable before every deploy finishes
Done 2 Nov: new storage keys in place
3 · Sign-in is rate limited
The front door’s sign-in is capped at the edge: 30 a minute per visitor
Done: built into the site, ships with every deploy
4 · People can sign in
A real login for every live surface, each landing on its own workspace
Done 2 Nov: real logins on every surface
No gate, no go. Each is checked, not assumed.
03 / 14
Schedule · go-live Friday 6 Nov
Four working days to go-live
Day
Work
Done when
Mon 2
Every login tried once
Each person signs in at the front door and lands home
Tue 3
Check devices and shift grants
Each technician signs in on their own device
Wed 4
Technician session
Each tech submits a practice wrap-up offline
Thu 5 am
Dispatcher session
All six drills passed on practice jobs
Thu 5 pm
Dry run
One job from intake to complete, end to end
Fri 6
Go live, 9:00 am
Run of show, slide 10
Go-live: Friday 6 November 2026 · all four gates already green
04 / 14
Technician onboarding
Four steps from hire to first job
01
Register the device
Office, in S2 Field devices: the device ID and its kind, a browser, an Android pilot or a field tablet.
02
Open a shift grant
The grant names the technician and a time window on that device. No live grant, no sign-in.
03
Sign in at the front door
Tick “Signing in on a field device”, enter the device ID. Any miss reads “invalid credentials”.
04
Punch in, work the list
Clock in on the timesheet. Jobs the dispatcher assigned appear in the job list.
Sign-in is the first thing that can fail on day one. Every device and grant is tested on Tuesday, not on Friday morning.
The same path for employed and subcontracted crews.
05 / 14
What a technician does
One job, five states, one wrap-up
Assigned
En route
On site
In progress
Complete
The wrap-up will not submit without
  • Two photos or more
  • A customer signature, or the reason the customer was absent
  • An outcome: complete, or quote needed
  • For a quote: the full rooftop unit set, tonnage to old serial
When the signal drops
  • The device keeps the work, photos included
  • It sends everything when the connection returns
  • Sending twice is safe: nothing doubles
  • Assignments stay on the server, so no one works around the gate
Also on the device: awaiting parts, awaiting customer, parts used, checklist.
06 / 14
Technician session · Wed 4 Nov
Sixty minutes, hands on their own devices
Block
Min
Each tech leaves having
Sign in, read the job list
10
Signed in on their own device
Walk a practice job through its states
15
Moved a job to in progress
Wrap-up: photos, outcome, signature
15
Submitted a complete wrap-up
Airplane mode, then reconnect
10
Watched queued work arrive
Timesheet, and who to call
10
Punched in and out; knows the escalation contact
First group: 2 technicians · trainer: Ethan
07 / 14
Dispatcher training
The board, and the one gated door
Read the board
  • Every job in the region, its crew and its SLA timer
  • Timer health in words and marks: ok, at risk, breached
  • Intake: customer requests still waiting for a job
  • If the feed drops, the board freezes, shows how stale it is, and stops taking assignments
Assign through the gate
  • Each active crew in the region shows cleared, or refused with a reason
  • Reasons: document missing, expiring in the window, unverified, crew inactive
  • The badge is a dry run of Assign: what it shows is what happens
  • There is no override, on screen or behind it
A dispatcher on a stale board is worse than one who knows it is stale.
08 / 14
Dispatcher session · Thu 5 Nov
Six drills on practice jobs
#
Drill
Passed when
1
Open a job from intake
The request becomes a job at its site, SLA timer derived, never typed
2
Assign a cleared crew
The job shows the crew; the tech sees it on the device
3
Hit the gate
Try a refused crew; read the reason back aloud
4
Release a crew
The crew is released and the job shows its new state
5
Note, flag, message
A second visit is flagged; the note shows on the job
6
Lose the connection
The board freezes and Assign is blocked until it recovers
Dispatcher: Ivonne · backup: Ethan
09 / 14
Day one · Friday 6 Nov
Run of show
When
Who
What
8:00
Ethan
Gateway reports ready; a test sign-in lands on its workspace
8:30
Office
Shift grants open for every tech on shift
9:00
Technicians
Sign in, punch in, confirm the job list loads
9:30
Ivonne
First real job assigned through the gate
Hourly
Ethan, on call
Walk the board; log every snag with time and job number
End
Everyone
Fifteen-minute debrief; snags ranked for the fix list
Go-live 9:00 am Friday 6 Nov · on call: Ethan · dispatch: Ivonne, backup Ethan
10 / 14
The data we are after
Every job leaves a trail we can read
Signal
Recorded by
Question it answers
Time spent in each job state
S3 and S5, every change
Where do jobs stall?
Shift punches
S5 timesheet
Real labour hours per job
Photos, notes, unit measurements
S5 wrap-up
What did we find on site?
Parts used and parts waits
S5, awaiting-parts state
What should be on the truck?
SLA timers and escalations
Background sweep
Which jobs run late, and why?
Assignments and releases
S3 dispatch
How often does work change hands?
Jobs and requests opened
S2 and S3
How much work arrives, and where?
Recorded as a side effect of the work. Nobody fills in a form for us.
11 / 14
From data to product
A weekly loop, one change at a time
Record
Review weekly
Pick one change
Ship, then measure
Question 1
Where does a job wait longest, and who is it waiting on?
Question 2
Which wrap-up fields do techs skip, fight or fill in wrong?
Question 3
What does the dispatcher still do by phone or paper?
Review: every Wednesday · Dylan, Ethan and Garrett · one page a week
12 / 14
After Rollout 1
The data decides what opens next
Candidate
Holding it back today
Signal that moves it up
S4 HQ dashboard
Built and read-only; waits until regions run without it
Owners asking for rollups the weekly page lacks
S6 Customer portal
No production sign-in for customers yet
Volume of requests and calls per customer
S8 Subcontractor portal
No production sign-in for firms yet
Share of jobs run by subcontracted crews
Field tablet
The long build; S5 carries the field meanwhile
Offline sends and failures in the field
Candidates, not commitments. Opening one is a deliberate, one-line change.
13 / 14
Decisions
Every call is made
Decided
  • Go-live: Friday 6 November, 9:00 am
  • Dispatcher: Ivonne · backup: Ethan
  • On call on day one: Ethan
  • First group: two technicians, trained by Ethan
  • Response obligation: Ethan holds it
  • Data review: every Wednesday · Dylan, Ethan and Garrett
Rankine Operating Company · AC Services
14 / 14