Wedding dates to avoid in 2019

Don't book your wedding day in over these dates!

We all know the drama that the World Cup caused when it fell on some people’s wedding days, so we’re here to help you prepare in advance. Here are the main dates to avoid next year when it comes to your nuptials.

14th February

Valentine’s Day may sound like the most romantic time to say your ‘I do’s, however, the trouble is, so do so many other couples – meaning that venue prices sky rocket. Stick to a dine in for two meal deal and throw your wedding on a different day.

 15th March

This day in the middle of March is bad luck according to ancient superstition and “beware the ides of March” is even quoted in Shakespeare. When it doubt, leave it out…

 17th March

St Patrick’ Day might be an Irish celebration, but that won’t stop the English party-goers. Unless you want drunken revellers wearing garish green outfits to photobomb your photos outside your cute country pub venue, we’d suggest a change of plan.

YOUR WEDDING DAY TIMETABLE, SORTED

Be happy with your chosen date
Be happy with your chosen date

13th September

This is the first Friday of the year to fall on the thirteenth day – making it unlucky for some. If you’re superstitious and want to prevent disaster, then avoid this day.

20th September–2nd November 

The Rugby World Cup will be on over these dates. To steer clear of the football World Cup issues, we’d highly recommend dodging these dates.

WE REVEAL EXACTLY HOW MANY GLASSES OF CHAMPAGNE ARE IN A BOTTLE

13th December

Another Friday the 13th to avoid if you’re feeling paranoid. However, we think you may bag a wedding venue bargain if you do pluck up the courage. 

It’s also worth noting that you should probably avoid any family birthdays too! We’d also suggest, finding out about any plans for the local area around your wedding date – just in case there’s an annual fair or a full-on carnival planned for that day. 

Comments

Oops – nothing in this comment!

Sorry, we couldn't post your comment right now. Can you try again later?