We’ve got three permit sets due in six weeks across two jurisdictions, and I’m tightening buffers to keep evenings untouched without risking milestones. I’m running MS Project with 15-minute dailies and a Friday risk review — what buffer rules or communication cadence have kept your teams on time and calm?
I’ve had better luck with a single project buffer (Critical Chain) instead of per‑task padding, plus a visible buffer burn chart — think of it as a surge protector for chaos — and swap the ‘15-minute dailies’ for an async check‑in before lunch and a 20‑min Thursday AHJ touchpoint to pull forward surprises. Caveat: anything that burns >50% of remaining buffer triggers a same‑day replan, not overtime; does that match your jurisdictions’ response times?
One tweak that’s worked for me is pulling the Friday risk review to Wednesday at 1pm and adding a 30‑min ‘unblock’ call, plus a 24‑hour freeze before each jurisdiction handoff; in MS Project I mark those as zero-duration ‘Freeze Gate’ milestones with a 0.5d feeding buffer so evenings stay untouched. Small caveat: the 15‑minute dailies can sprawl — cap updates to blockers only and push everything else to the Wednesday unblock. Would shifting that review mid‑week help, @OP?
Quick example: I use a “green by noon” rule — each discipline lead posts a two-sentence status by 12:00, and anything amber triggers a same‑day replan/resource swap so evenings stay untouched. It works well but only if someone’s empowered to cut scope or slip a micro‑milestone by a day. Would that fit alongside your Friday review?
, what’s kept us sane on two‑jurisdiction pushes is a strict “T‑48 lock” on each permit package: at 48 hours out we freeze scope and run a 20‑min checklist against AHJ notes, and any churn after that needs sponsor approval — way less thrash than a rolling “Friday risk review.” Small caveat: you need a visible owner board in MS Project (I just use a custom Flag and a filter) so everyone sees what’s inside the lock. Would you try T‑36 first to fit the six‑week runway?