everly.
Guest List & RSVP

What Goes on a Wedding Address Collection Form

What an address collection form should ask for, why a link beats a paper card, and what happens to the data after a guest hits submit.

Everly Team·3 min read·
A single form panel seen at an angle, its rows of empty boxes ruled across the page and an abstract square grid resting at one corner

An address collection form only needs five fields, but most couples build one from scratch in a Google Form and end up with either too few fields (no apartment number, and now packages bounce) or too many (a phone number nobody asked for). Everly's version is a form for exactly this, already wired to your guest list.

Here's what belongs on it, and what happens to the data once someone submits it.

The fields that actually belong

Street address, apartment or unit number as its own field (not folded into street — it gets lost), city, state, and zip. That's it. A name field to identify who's submitting, since the form needs to know which guest this address belongs to. Skip anything else — a phone number or dietary note doesn't belong on an address form; that's what your RSVP form is for.

A physical response card with a blank for the address works, but every blank has to be manually typed into your guest list afterward, and handwriting is its own error source. A form guests fill in directly writes clean, typed data with no transcription step. A QR code on a printed card gets you the best of both — something to hand out physically that still opens a digital form.

What happens after submit

This is the part most address forms get wrong: they dump the response into a spreadsheet row with no connection to your actual guest list, so you're back to manually matching names. Everly's standalone address form instead holds each submission in a review queue and suggests a match against your existing guests by name and email. From there you apply it to the matching guest, create a new guest if it's someone new, or dismiss it if it's a duplicate or mistake. The address never overwrites a guest record on its own — you approve every match.

Once approved, the fields aren't stuck in a form response — they're guest columns like any other, which means they show up in your guest list and in your guest CSV export without a separate download.

Building your own vs. using one that's already connected

If you only need a handful of addresses, a plain form works fine — you'll match the names by hand. Past a few dozen guests, the matching is the part that eats time, which is the whole reason to use a form that's already tied to your guest list instead of a standalone one.

Continue Reading