A Google Form can look ready while the email path is still fragile. Before you publish the link, run a preflight that verifies recipients, respondent email source, template fields, test-send behavior, and the latest send result you expect operators to rely on later.
Most notification failures are configuration failures, not form-submission failures. The form collects responses, but the right people still do not get the right email.
Recipient drift
A copied form still points at an old owner inbox or misses one of the current team recipients.
Email source mismatch
The form no longer collects email the same way the confirmation template expects.
Template gaps
Merge fields may be stale after questions were renamed or reordered.
No visible proof
Operators need a recent send result they can inspect after testing and after the first live submission.
Recommended preflight sequence
Open the form in edit mode and launch FormNotifier from Extensions.
Confirm whether you need owner alerts, respondent confirmations, or both.
Review every recipient address, including extra team recipients and shared inboxes.
Verify the respondent email source is either collected email or the correct email question.
Trim the subject and body down to the fields that matter in the inbox.
Run Preflight and resolve warnings before saving.
Use Send test and verify the message arrives in the expected inbox.
Submit one real test through the public form link and check the recent send result afterward.
The strongest launch signal is not only that a test email can be sent, but that one real public submission also behaves exactly as expected.
What to inspect in the email itself
Subject clarity
The inbox should reveal what happened without opening the message first.
Correct merge values
Check that names, dates, or request types render cleanly instead of showing blank placeholders.
Useful next step
Respondent confirmations should say what happens next and who to contact if needed.
Operator readability
Owner alerts should surface only the fields a human needs to triage quickly.
Boundary: preflight helps validate setup, but it is not a full deliverability guarantee or a replacement for a dedicated CRM or support platform.