A map of the slow loop — seasonal list swaps at Village at Avon
Around Village at Avon, the 11pm copy-paste still lives in a side spreadsheet, while Nottingham Park adds seasonal list swaps on a different clock, which is why built automation on the loops that already hurt is a response to those two places rather than a swapped town name.
What we would build around that — a documented exception path for seasonal list swaps
What we would actually ship is a documented exception path aimed at seasonal list swaps, then a watched queue only if review-request sequences is still burning, with Nottingham Park as the check that the system can describe a real place.
Why the calendar is the spec — seasonal list swaps between Beaver Creek and Village at Avon
Resident traffic and visitor traffic mix differently at Village at Avon than at a ski-base mall, so built automation on the loops that already hurt is a fit there when it is a documented exception path rather than a slogan.
Village at Avon is a short drive from the Eagle County home base, and Nottingham Park and Nottingham Park are named so we do not invent a suite number in Avon.
Fit, and the useful no — the 11pm copy-paste
Acceptance is local when seasonal list swaps no longer produces the 11pm copy-paste at Village at Avon and someone at Nottingham Park can explain a documented exception path without calling us.
Staff who cover Nottingham Park in winter and Nottingham Park in summer should not relearn a product every April, which is why seasonal list swaps needs a seasonal switch even if the first ship is only a documented exception path.
The first working hour from your stack outward, built from a constraint
Look at season and staff load, pricing follows an honest map, the booking page uses your timezone, on-site is a short drive.