Skip to main content

How to Get a Wedding Client Questionnaire Back Without Chasing

Get your wedding client questionnaire back on time: send it six weeks out, keep it short, save progress, and let one polite automation remind.

Published 9 min read

Illustration of a couple in profile at a small table on a sunlit balcony, filling in a wedding client questionnaire on a tablet together, coffee cups beside them

In short

A wedding client questionnaire comes back when it's short, sent about six weeks before the wedding, easy to finish on a phone in more than one sitting, and followed by one polite reminder that arrives on its own. In Gloam, couples answer from a secure link with no account, their answers save as they go when you turn on Save Progress, and an automation can wait for the submission and remind only the couples who haven't sent theirs yet.

Every wedding pro knows the shape of this problem. The wedding client questionnaire went out weeks ago. The wedding is close now, and the answers you need, the family groupings, the must play songs, the getting ready address, the vendor meal count, are still sitting in a half finished form in somebody's inbox. So you send the awkward email. Then maybe a text. Then you build the timeline around guesses and hope the day forgives you. This post is about getting that questionnaire back without the chase: send it when the answers exist, keep it short enough to finish, let couples answer in more than one sitting, and hand the reminding to a system.

The stakes are higher than tidiness. The Knot's 2026 Real Weddings Study, which captured responses from 10,474 couples married in 2025, found that couples hire around 13 vendors for their day. Your questionnaire is one of about a dozen sets of homework landing on the same two people, who also spend an average of 7 hours a week planning. And the load is rarely shared evenly: the same study found one partner carries roughly 64 percent of the planning tasks. When a questionnaire stalls, it usually isn't a couple ignoring you. It's one busy person, a long form, and a week that got away from them.

When should you send a wedding client questionnaire?

Send the final details questionnaire about six weeks before the wedding, and send a much shorter one at booking for the facts that already exist. Six weeks is late enough that the getting ready room, the family list, and the timeline are real answers instead of guesses, and early enough that you can still act on what you learn, adjust the schedule, and ask a follow up question while there's time.

HoneyBook's guidance for planners calls six to eight weeks before the wedding the standard window, late enough that most details are confirmed and early enough to follow up and build the timeline. Photographer guides land in the same place: send at six to eight weeks out, follow up at four. The reasoning explains most late returns. Sent at booking, a questionnaire asks for answers that don't exist yet. Nobody has chosen the getting ready room, the family list is still political, and the song choices aren't written, so the form waits, gets half answered with guesses, and the guesses quietly become your timeline.

DJs can run a little later for music: one DJ guide recommends asking for the must play and do not play lists two to three weeks before the date, together, from one person, with artist and title on every line. The week of the wedding is when those lists usually arrive, typed from memory on a phone, with the do not play list landing separately a few days later. Asking on time is how you avoid scoring that scramble.

How long should a wedding client questionnaire be?

Keep a wedding client questionnaire short enough to finish in one coffee, and split anything longer into two shorter sends. Form length is the strongest lever you control: Typeform analyzed 882 million form starts and found that forms with 1 to 3 questions were completed 75.68 percent of the time, while forms with 11 or more questions fell to 54.04 percent. Every question you cut buys back answers to the ones that remain.

The full Typeform picture, from 2.4 million forms between September 2025 and August 2026, is that 59.85 percent of people who started a form went on to submit it. Forms with 4 to 6 questions reached a 67.69 percent completion rate, between the short and long ends above. In Typeform's own summary, short forms are completed 40 percent more often than long ones. Those numbers cover forms of every kind, not wedding questionnaires specifically, but the direction is hard to argue with.

So cut with intent. Keep the questions only you can act on: the ones that change the timeline, the family list, the playlist, the floor plan, the meal count. Move anything that's nice to know into the final call, where a conversation handles it better anyway. Vendor guides make the same point from experience: couples skim, skip, or stop at long open ended blocks, while grouped, structured questions get finished. And let "not sure yet" be an acceptable answer where it honestly is one. A couple who can say that and move on will finish your form. A couple who has to invent an answer will close the tab.

Length isn't the only friction. Typeform found that 69.8 percent of form starts happened on mobile devices, and The Knot found that 41 percent of wedding planning is done on a mobile device. Your questionnaire will be answered on a phone, on a couch, in pieces. In Gloam, couples answer from a secure link with no account to create and nothing to install, and the questions use simple formats a phone handles well: short and long text, dropdowns, single and multiple choice, yes or no, dates, numbers, email and phone fields. Ten question types, one job each, nothing that needs a desktop and a free evening.

Illustration of a wedding DJ in profile at home selecting a vinyl record from a tall shelf, headphones around his neck, a printed song list in his other hand

What makes a couple finish a questionnaire they started?

Couples finish questionnaires that let them stop and come back. The half finished form is the normal case, not the failure case, so the winning design is progress that saves itself: a couple answers six questions on Tuesday, closes the tab, and finds every answer waiting when they return on Sunday. In Gloam, a setting called Save Progress does exactly that, and it's the single kindest thing you can turn on.

Turn Save Progress on for a questionnaire and a couple's answers save automatically as they type, then restore themselves when the couple returns on the same link. A started questionnaire becomes saved work instead of a lost tab. If a couple has answered one of your questionnaires before, their earlier answers can also prefill the next one, so nobody retypes the basics.

One more piece of design helps: ask the couple to fill it in together. Guides for photographers make this point about family information in particular. A form answered by one partner at midnight tends to miss the other partner's family entirely: the step parent nobody mentioned, the grandparents who need a chair and a shorter walk, the two relatives who should never be grouped in one photo. Those answers also come more honestly in writing than across a phone call, which is exactly why the questionnaire exists. It's the same reason the companion post on how to follow up with wedding leads treats written answers as gold: people write down what they won't say out loud.

And give the form a real date. Not a threat, a date: the Friday your timeline draft is due, named in the email that carries the link. Couples finish forms with dates attached and drift on forms that say "whenever you get a chance." In Gloam the questionnaire itself doesn't carry a built in due date, so the date lives where it belongs anyway, in your message and in the reminder timing you set below. What Gloam does track is status: each couple's questionnaires appear in their client portal, marked completed with the submission date once they're in, so a couple can see for themselves what's still open.

How do you remind a couple without chasing them?

You build the reminder once, and you let it fire only for couples who still owe you answers. A manual chase treats every couple like a late couple, including the ones who replied the same day. A wait based reminder knows the difference: the automation sends the questionnaire, waits for it to come back, and only emails the couples who haven't answered, once, kindly, with a reason attached.

In Gloam the flow looks like this. An automation sends the email that carries the questionnaire link. Then a wait step watches for the questionnaire to be submitted, with a time limit you choose. Couples who submit move on and hear nothing more about it. When the time runs out for a couple who hasn't answered, the automation sends one friendly reminder email, written by you, in your voice, naming what the answers make possible: the timeline draft, the family photo list, the playlist. Delays can skip weekends, so the reminder lands on a weekday like a person sent it. There's even a starting pattern built in for exactly this: wait for questionnaire completion, then follow up. One honest limit, stated plainly: Gloam reminders are email based. There's no text message step for questionnaires, so keep the email kind, short, and easy to act on from a phone.

For context, other tools split this differently. HoneyBook includes forms and questionnaires on every plan, with prices checked on its pricing page on November 18, 2026: Starter is 29 dollars a month billed yearly, and automations and text message reminders start on Essentials at 49 dollars a month billed yearly, with Premium at 109 dollars. If text reminders matter most to you, that's a fair reason to look there. Gloam's answer is the wait step: the reminder goes only to couples who haven't finished, it's included with the visual automation builder on the free plan, and the free plan includes 5 questionnaires. Pro, at 25 dollars a month or 240 dollars a year, makes questionnaires unlimited.

If a questionnaire still doesn't come back after the reminder, change the channel, not the volume. Vendor guides converge on the same fallback: one friendly note, then a short call. Put the unanswered questions on the agenda for the final consultation and ask them live, writing the answers down yourself, the same way the post on how to get wedding contracts signed faster treats a stalled signature as a friction problem, not a character flaw. The call isn't a defeat. Some answers, the delicate family ones especially, were always going to arrive better by voice. The system simply makes sure the call is the exception, for one or two couples a season, instead of the routine for all of them.

What does a calm questionnaire rhythm look like?

A calm rhythm looks like this: a short questionnaire at booking captures what exists, the final details questionnaire goes out six weeks before the wedding, progress saves itself along the way, one polite reminder reaches only the couples who still need it, and a short call catches the rest. Nobody gets chased, nobody gets guessed about, and your timeline rests on answers the couple actually gave you.

That's the experience Gloam is built to give: less admin for you, and a planning process that feels considerate from the couple's side of the screen. If your questionnaires currently live in a form tool, a spreadsheet, or a thread you have to search the night before a wedding, try Gloam free and send your next one the calm way. The free plan never expires, and your first questionnaire can be the one that simply comes back.

Frequently asked questions

About six weeks before the wedding works for most pros. HoneyBook's planner guidance calls six to eight weeks before the wedding the standard window, and photographer guides give the same range: earlier, and the couple is guessing at details that don't exist yet; later, and there's no time to act on the answers. Song lists for a DJ can go a little later, two to three weeks out.

What should a CRM for wedding DJs actually do? A wedding DJ in profile setting up a speaker on a stand in an empty reception hall, string lights overhead and gear cases at his feet

16 min read

What Should a CRM for Wedding DJs Actually Do?

A CRM for wedding DJs should catch every inquiry, chase the retainer without awkwardness, collect the song list on time, and run the night from one timeline.

  • Client Experience
  • Choosing a CRM
What should a CRM for wedding venues actually do? A venue coordinator on a stone terrace at dusk, holding a floor plan sheet while staff set tables under string lights in the garden below

15 min read

What Should a CRM for Wedding Venues Actually Do?

A CRM for wedding venues should catch every inquiry, book tours without phone tag, and turn a signed contract into a paid date, keeping couples calm.

  • Client Experience
  • Choosing a CRM

Join the waitlist today

Start for free and upgrade as your business grows. Simplify bookings, contracts, invoicing, and client communication today.