Traffic is not evenly distributed. Mutual societies, insurers, education hubs, and hospitality portals in Thailand often see sharp loads around Songkran, New Year, and school calendar turns. A rebuild sequence that ignores those peaks invites avoidable outages.
Put peaks on the wall
During roadmap workshops we ask sponsors to mark non-negotiable quiet periods and non-negotiable peak periods on a shared calendar before debating phases. The exercise is simple and frequently overdue. Once peaks are visible, arguments about “shipping in April” become concrete risk discussions.
Freeze windows are not laziness
A planned freeze before a known peak is a professional control, not a lack of ambition. Document what remains mutable (content fixes, urgent security patches) and what is locked (schema changes, identity provider swaps). Operators need that distinction in writing.
After the peak
Schedule a short review within two weeks of a major peak: what broke, what was manually reconciled, what the risk register missed. Those notes feed the next rebuild phase better than generic post-mortems copied from other industries.
Portal Riverpoint keeps Thai calendar constraints in every Bangkok engagement because portals do not pause for public holidays — they often work hardest then.