Match signup errors to the correct recovery
Match each signup error to the actual account state and a supported recovery action. Keep valid input, associate the message with its field and avoid counting uncertain creation as success. The sandbox inventory should include existing-account, expired-verification and timeout cases because retrying can otherwise create a misleading or duplicated state.
Worked example — illustrative data.
| Error state | Copy specimen | Recovery/acceptance |
|---|---|---|
| Invalid email format | Enter an email address in the shown format | Associate message with field; keep other input |
| Existing account | Use sign-in or the supported recovery route | Avoid creating a duplicate |
| Verification expired | Request a new verification link | Use current supported flow |
| Service failure | We could not confirm account creation | Safe retry or help route |
| Password requirement | Explain the actual unmet requirement | Do not invent rules |
Ask the product owner for actual error codes and account states before writing final messages. Group technical failures only when the same customer action resolves them. Make errors discoverable without relying on color alone and test keyboard recovery. Use synthetic data and provider-supported sandbox methods. Follow each request to the receiver so a slow response is not mistaken for a safe duplicate attempt. Keep sensitive account details out of logs and analytics.
Decision: Accept the form when normal, invalid and uncertain states lead to the right next action and the receiver agrees with the screen. Improved error copy alone does not establish an uplift in activation.
A timed-out response may still leave a created account: An account can be created despite a timed-out browser response. A retry route must reconcile the existing state instead of silently creating another account or confirming failure without evidence.
Continue with Guides for stores, software teams and local businesses, SaaS website design and development and Connect a SaaS signup page to onboarding.
For error identification and accessible recovery, see the W3C WCAG quick reference.