What to do when a scheduled install can't run — and where each piece lives.
You do it
Happens on its own / Cowork does it
1
It's bumped
Weather, crew ran long, material didn't land. The job isn't happening.
YOU
2
Mark it — same row, same week
M = reason · N = today's date.
Do not delete the row. It stays in the week it was rolled from.
WIP SHEET
3
Cowork pulls it off the Y&J calendar
Event deleted, so the
install calendar clears itself — it's a live embed.
Subs stop seeing a job that isn't happening. No redeploy.
COWORK → CALENDAR
4
You email the customer
Template A if you have no new date. Template B if you do.
Fill the reason line with the real reason. That's what makes it land.
JOB NIMBUS
5
It ages until you deal with it
Every sync, Cowork scans all week tabs for un-cleared bumps and lists them oldest first.
"Sara Rader — bumped 12 days ago — weather." It cannot quietly disappear.
COWORK
6
You re-place it
Move the row into a new week tab. Clear M + N. Set Confirmed = x.
Cowork re-adds the Y&J event on the next sync. It drops off the aging list.
WIP SHEET → COWORK
Step 2 is the whole system. If M and N are set, everything
downstream works. If you delete the row or move it early, it falls off the cliff and Cowork can't see it.
Job Nimbus stays where it is — customer comms and billing. It doesn't talk to the sheet.
The sheet drives the crews; Job Nimbus drives the customer. Two audiences, deliberately not wired together.