A realistic wedding website timeline

Your wedding website does not need to be finished the moment you get engaged. It needs to become useful at the right moments: first when guests begin reserving the date, then when they need to make travel decisions, and finally when you need firm RSVPs.

For a celebration in the Philippines with relatives arriving from other countries—or an international wedding with family travelling from the Philippines—the useful timeline often begins earlier than a local-only checklist suggests. Flights, leave requests, visa appointments, school calendars, and holiday traffic all affect when guests need reliable information.

Think of the website as a living guest guide, not one large launch.

12 to 15 months before: secure the foundations

Once your date and general location are confirmed, reserve your website address and decide what information will be private. You can begin with only:

• your names;
• wedding date;
• city and country;
• a short welcome; and
• a note that more details will follow.

This is also the right time to build the first version of your guest list by household. Record full names, preferred names, email addresses or mobile numbers, and which guests may bring a partner or children. If both families maintain separate spreadsheets, combine them before invitations are designed. Duplicate households and unclear plus-ones become much harder to untangle after codes have been sent.

You do not need menu choices, a final schedule, or an enormous gallery yet. Publishing uncertain details creates more work than leaving them out.

9 to 12 months before: make the site useful for travel

Share a save-the-date and the website when guests need to plan. For overseas guests, a year ahead is reasonable; for mostly local guests, six to nine months may be enough. Earlier is helpful around Christmas, Holy Week, school breaks, or other periods when flights and hotels fill quickly.

At this stage, add:

• the confirmed city, date, and ceremony time if available;
• the nearest practical airports;
• a realistic note on travel time, not just map distance;
• recommended areas or confirmed hotel blocks;
• passport or visa reminders framed as guidance, not legal advice; and
• a contact method for genuine travel questions.

For Metro Manila, Tagaytay, Batangas, or destination venues reached by road, explain the transport reality. A venue may appear close on a map but take much longer on a Friday afternoon. Guests planning from abroad will not know that unless you tell them.

Keep the save-the-date separate from the RSVP. A guest saying “Can’t wait!” on Messenger is not a confirmed response, and asking for a firm answer before travel costs are clear tends to produce guesses.

6 to 8 months before: shape the complete guest experience

By now, your visual direction and core plans should be settled enough to build the fuller website. Add the story and photographs you actually want to share, but prioritise practical details:

• ceremony and reception venues;
• event schedule and who is invited to each event;
• attire guidance with useful examples;
• transport or parking arrangements;
• accommodation information;
• gift preferences, if you choose to include them; and
• a concise FAQ based on questions guests are already asking.

If you have several events—perhaps a welcome dinner, ceremony, reception, and next-day gathering—make eligibility clear per guest. The website should not make someone decline an event to which they were never invited.

This is a good review point for parents and coordinators. Ask them to flag missing information, but nominate one person to approve final wording. A website edited by committee can quickly contradict itself.

3 to 5 months before: open online RSVPs

Open RSVPs when the formal invitations are sent and the information guests need to decide is stable. For many weddings, three to four months before the date is comfortable. Allow more time when travel, visas, or several days of events are involved.

Before opening the form, confirm:

• every invited household appears under the correct code;
• named partners and children are assigned correctly;
• each guest sees only their relevant events;
• meal options match the caterer’s wording;
• dietary and accessibility questions are included;
• the deadline is visible on both invitation and website; and
• confirmation messages explain whether responses can still be edited.

Run the flow yourself on a mobile phone, then ask two people outside the planning team to test it. Include one person who is comfortable online and one who may need more guidance. Fix the points where either person hesitates.

Set the public deadline at least one to two weeks before your venue or caterer requires final numbers. You need time for polite follow-ups, reconciliations, and unexpected changes.

6 to 8 weeks before: follow up and clarify

As the deadline approaches, contact households that have not replied. A personal message is kinder and more effective than a vague public reminder:

Hi, Ana—we’re finalising plans for the wedding and noticed we haven’t received your RSVP yet. When you have a moment, could you reply at weddinghome.co/our-wedding by Sunday? Please let us know if you have any trouble with the form.

Update the FAQ with recurring, genuinely useful questions. If several guests ask about shuttle timing or whether a barong is appropriate, others are probably wondering too.

Avoid changing established facts silently. When a time, entrance, or transport plan changes, update the website and send a direct update to affected guests. The site is the source of truth, but guests still need to know that the truth changed.

2 to 4 weeks before: publish the final practical details

Your website now becomes the day-of reference. Confirm exact start times, maps, parking instructions, shuttle pickup points, attire notes, contact information, and the final order of events. Add an “updated on” date if details have changed.

Send one calm reminder with the website link. Guests should not need to search months of chat history or find the printed invitation while packing. For travellers, include weather expectations and any venue-specific realities—outdoor paths, limited mobile signal, cash-only transport, or a long transfer from the airport.

Do not publish private room assignments, personal phone numbers, or guest travel itineraries on an unrestricted page. Use protected guest views or direct messages where appropriate.

After the wedding: close with care

Leave the practical information available for a short period, especially if guests are still travelling. Then replace the urgent reminders with a thank-you note. If you plan to share photographs, say when and how rather than promising an immediate gallery.

Export and keep your RSVP and guest records before retiring the site. You may want the final attendance list for thank-you notes, supplier reconciliation, or simply as part of your wedding archive.

The best timeline is not the one that publishes everything earliest. It is the one that gives guests dependable information when they need it and gives you clean decisions when planning depends on them.