Thanks for your interest, Doug!
We haven't (yet) gone to the lengths of creating a unique schedule per project and switching "on" the go-live weekend.
What we have been doing up until now is setting the project with the standard schedule for that country/state, and then for the go-live weekend, setting those tasks with a 'Fixed Dates' contraint. This allows us to force the planned start and completion dates/times on the weekend, and set the correct planned hours, and Workfront just sets a duration of 0.
However, I have recently noticed that this causes an issue with Workfront's 'User Utilization' reporting. Any tasks with a 0 duration are missing from the utilization report results. E.g. if a user works Monday to Thursday, then takes the day off on a Friday and instead works on the go-live Saturday, the planned and actual hours go missing from the reporting. The user then looks like they were only 80% utilised for that week. I have submitted a ticket to Support on this, which they are looking at.
In terms of resolving the above issue, whilst your idea of creating a project-unique schedule would be an OK workaround at the project level, it wouldn't work for applying to the resource as they work on many projects, so therefore wouldn't really work for us because the resource's schedule overrides the project's schedule once they're assigned to a task.
So, depending on what Support come back with, we either need to accept that the Utilization reporting will have some inaccuracies, or we need to move to your "wide open" schedule and maintain the non-working times via task bookings (which is another kettle of fish I'd rather not get into if possible!).
I am interesed to hear if any of Workfront's product team have thoughts on the idea of allowing ad-hoc working day overrides as per my feature request as I think this would be the most elegant solution and avoid some hefty workarounds.
Regards, David