Designing clear status messages for insurance quote journeys

People need to understand what has happened after each step in an online quote journey. A clear status message names the current state, explains what it means and gives a realistic next step. Good status design avoids implying that a quote, policy or cover exists before the responsible system or person has confirmed it.

Name states by what is known

Separate an incomplete application from one that has been submitted. Distinguish a technical acknowledgement from a completed validation, and a referral from an accepted outcome. Use terms consistently across the form, confirmation page, email and any service-team view.

Explain the next action

For each state, say whether the user should continue, correct a field, wait for a response or contact the relevant team. If no action is needed, say so plainly. Avoid vague messages such as “processing” when the user can be told what is being checked and what remains unknown.

Design for interruption and failure

• Show which step was completed and which still needs attention.
• Preserve entered information only where the product is designed and authorised to do so.
• Offer a recovery route after a temporary technical error.
• Do not tell users to repeat an action when its result is uncertain.

Test the wording against real states

Review each message with product, operations and broker owners. Test incomplete fields, delayed responses, referrals, duplicate submissions and interrupted sessions. Ask reviewers whether the message makes clear what has happened, what has not happened and who owns the next step.

This is general journey-design guidance. The meaning of insurance status, referral and completion must be defined by the accountable product and broker teams for the specific workflow. A status message alone is not evidence of cover or insurer acceptance.