A renovation is a relay. Each trade hands off to the next, so a single slip early in the job pushes everything behind it. Here's how we keep the whole supplier group on one timeline — automatically — when a project moves forward or falls back.
Today, when a job slips, the update travels by phone tag. The coordinator calls the cabinet installer, forgets the countertop shop, texts the electrician, and the appliance delivery shows up on the original date to a kitchen that isn't ready. Someone always misses the memo — and a missed memo means a wasted truck roll, an idle crew, or a install done out of order.
The schedule lives in a dozen places at once: our project plan, the GC's notebook, each supplier's own calendar. The moment one of them changes, the others are wrong.
The project timeline already lives in one place — the client's Project Plan. It's the single source of truth, and it already knows how to cascade: move one phase and every phase after it slides by the same amount, each keeping its own length.
Instead of every supplier keeping their own copy of the dates, every supplier subscribes to the one schedule. When the coordinator moves a date, the change ripples down the trades and lands in each supplier's own calendar — without a single phone call.
Every supplier reads from the one schedule at the centre — so when it moves, they all move.
Each trade depends on the one before it being finished. That dependency is exactly why a single delay ripples forward — and exactly what lets us shift everyone correctly with one move.
Say the flooring crew hits a supply delay and finishes one week later than planned. The cabinet installers can't start on bare subfloor, so their week moves too — and countertops (templated off the cabinets), then fixtures, lighting and appliances, all shift by the same week. One move, applied once, updates the whole back half of the job.
Flooring stretches by a week — and cabinets, countertops, fixtures, lighting and appliances each slide a week to the right, keeping their own length and the gaps between them. The coordinator makes one change; every supplier sees their new date.
The magic isn't a new date — it's that the new date reaches everyone the same minute it changes. Three simple pieces make that happen:
Each supplier subscribes to the project once — a single calendar link in their phone or Outlook. Unlike a one-time "add to calendar," a subscription refreshes on its own, so their dates are always the current dates.
The instant a date they're on moves, they get a note: "Your cabinet install moved from Mar 10 to Mar 17." No chasing, no group texts — only the suppliers actually affected are told, and only about their part.
The supplier taps Confirm to lock the new date — or flags a conflict. The coordinator sees at a glance who's locked in, so the new plan is real, not assumed.
Only one person moves a date — the project coordinator — so the schedule never forks. Suppliers don't edit the timeline; they flag and confirm. That keeps a single, trustworthy version for the whole group.
Appliances don't arrive to an unfinished kitchen; crews don't show up to a job that isn't ready for them.
When a date opens up because the job moved forward, the next trade can pull in early instead of waiting.
Every supplier knows the dates they're looking at are the real, current dates — not last week's.
Slack gets squeezed out of the schedule because changes propagate in minutes, not days of phone calls.
The hard part — the cascade math — already lives in the plan's adjustable timeline: move one phase and the rest follow. To turn that into a shared feed, we add three things: a live per-project calendar link each supplier can subscribe to, a small notification step when dates change, and a confirm tap. That live feed needs a lightweight hosted service behind it — the one piece a static page can't do on its own.
One living timeline, one hand moving it, and every supplier reading from the same page.