The constraint before the stack — workflow mapping at Golden Peak
People who work Golden Peak and East Vail already know peak-week exceptions, so automation diagnosis before anyone buys a platform is useful here when it removes that rather than when it adds another login.
The piece that removes a login — a no-build recommendation for workflow mapping
We would rather install a no-build recommendation at Golden Peak and stop than decorate a stack, and bottleneck scoring becomes a second loop only when peak-week exceptions is still true at East Vail.
What on-site actually means here — workflow mapping between Lionshead Village and Golden Peak
Lionshead Village and Golden Peak are not interchangeable desks for workflow mapping, which belongs to the people who work East Vail and is why a statewide template fails when the shoulder hits.
Workflow mapping has to be proven on a live Saturday at Golden Peak in Vail, which is what on-site means here rather than a storefront on East Vail.
Peak-week exceptions is the tell that bottleneck scoring was never designed for Golden Peak, so a sequenced automation plan is the smallest change that would matter there.
Talking through the work without a printed floor, timed to the season
Treat the first hour as diagnosis, the season gets named out loud, write instead of calling if you prefer, bring tools you already pay for.