I had a 200-person wedding on a Tuesday. It felt risky, but most guests showed up and partied as if it were Saturday.
Briefly

I had a 200-person wedding on a Tuesday. It felt risky, but most guests showed up and partied as if it were Saturday.
"My fiancé and I had planned our dream summer honeymoon: We'd explore South Africa's beautiful Cape, driving along the picturesque Garden Route, before returning through the Kalahari Desert. There was just one problem, though. First, we needed to get married - and we didn't actually have a wedding date. At the time, we were living in his hometown of Johannesburg, but we were eager to return to the United States and start our new life together as a married couple."
"His October proposal, combined with the Southern Hemisphere's December to February summer, meant we needed to move quickly if we wanted to keep our honeymoon plans intact. Unsurprisingly, between vacations and friends' weddings, all of our non-holiday summer weekends were already booked. We'd either need to pivot to a longer engagement or consider holding a non-weekend wedding. Against my better judgment, we chose the latter and planned our ceremony for a Tuesday in January."
An engaged couple planned a summer honeymoon along South Africa's Garden Route and through the Kalahari, but lacked a wedding date. Living in Johannesburg and facing a short timeline due to an October proposal and the Southern Hemisphere's December–February summer, they found most non-holiday weekends already booked. They chose a Tuesday in January and worried about weekday attendance. They invited 200 people; about 90% attended. They held a cocktail-hour ceremony to save money, relied on a mostly local guest list and a lax dress code, and reported that the celebration was a success and they had a blast.
Read at Business Insider
Unable to calculate read time
[
|
]