One of the first key steps for many major events is the save the date message. From emails and simple cards to more flashy or elaborate invitation-style options, save the dates are the key to letting your guestlist know about an upcoming event and to block off their calendar accordingly.
While the function of a save the date is fairly standard, the goal of any save the date is to maximize the amount of guests who will actually attend your event. For casual or milestone events, like a wedding, this is important if you want as many friends or family there as possible.
More importantly though, if you are planning a fundraiser, gala, reunion, corporate event, or any event where ticket sales or revenue will be a consideration, the question of when to send save the dates to your guests is critical.
While different event types have drastically different planning timelines, there are some common planning elements that make determining when to send save the dates easier. Here are the key things to keep in mind while determining your event timeline:
Often the biggest expense for any type of event, working with your venue rep to figure out when a hard head count will be needed is one of the first determining elements for when to send save the dates. Some venues may offer multiple rooms/plans that offer your more flexibility to finalize your guestlist later in the planning stages. However, some venues may require a non-refundable deposit or refuse changes after a certain deadline (sometimes months in advance for more popular venues). The earlier you need a final headcount, the earlier you will need to send your save the dates in order to begin collecting RSVPs and formalize your guestlist.
Are you relying on ticket sales or donations to fund various elements of your event? Do you need to justify the ROI of the event to stakeholders in order to actually hold it? Earlier save the dates allow for you to move on to the steps of soliciting donations or opening ticket sales, and to start collecting event revenue to measure performance against your expected budget.
This is probably the most event type-specific consideration on this list, because there is a vast difference between inviting family and friends to a milestone event (like a wedding or anniversary) and inviting clients to a corporate gala, for example. For family and milestone events, your guests often have a personal reason for keeping the event high in their future planning. However, for corporate and nonprofit events, you want to time your save the dates to be early enough to occupy a spot on your guests’ calendars, but not to fall out of their mind if months go by before future correspondence.
For a general rule of thumb, you should work backwards from other event timeline milestones to determine your save the dates. For example, as you plan your event, start by working your way back from the actual event date to the first deadlines (vendor final payments, venue head count deadlines, etc). Then, work your way back two months to establish when you’ll want to send out formal invitations. Finally, move back a month or two to set a date for when to send save the dates. Here’s a helpful tool for considering how long you should expect guests to RSVP to give you an idea of the kind of windows you’ll need between each of these.
© 2023 All Rights Reserved
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
csrftoken | past | This cookie is associated with Django web development platform for python. Used to help protect the website against Cross-Site Request Forgery attacks |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
laravel_session | 5 days | laravel uses laravel_session to identify a session instance for a user, this can be changed |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
XSRF-TOKEN | 1 month | This cookie is set by Wix and is used for security purposes. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
Cookie | Duration | Description |
---|---|---|
_gat | 1 minute | This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites. |
_uetsid | 1 day | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
_uetvid | 1 year 24 days | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_ga_5XLFPG0W9S | 2 years | This cookie is installed by Google Analytics. |
_gat_gtag_UA_11703970_6 | 1 minute | Set by Google to distinguish users. |
_gat_gtag_UA_11703970_9 | 1 minute | Set by Google to distinguish users. |
_gat_UA-11703970-6 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
Cookie | Duration | Description |
---|---|---|
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
MUID | 1 year 24 days | Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
Lf6OyVqEU0nVTJQeFIeIpSQjqWYSbIW7umu3OHBy | 1 month | No description |
MUa7b6LkjpVOL8iFskJjTasRS5pBCQiV4Zd6SxpG | 1 month | No description |
rsvpify_session | 1 month | No description |