Phase banner

The phase banner shows users that a service is still in development and encourages them to provide feedback.

The main website phase banner is used at the top of every page. A service page banner can be used under the page header, above the service’s main content area.

Use phase banners when you want users to understand they’re using an evolving service and their feedback will help improve it.

Site-wide phase banner

Use across all pages until your platform meets full operational standards, when:

• proposed work outlined in the website discovery report is completed
• full compliance with the GOV.UK Service Standard is achieved
• the service is sustainably run with appropriate support and governance

Service-specific phase banner

Use for individual services hosted on the Government Project Delivery website that are in development.

New services with limited audiences should have an alpha banner.

When services are being used by real users but work and user journeys to comply with the service standard should have a beta banner.

Phase banners can be removed, or show as live, when full compliance with the GOV.UK Service Standard is achieved and the service is sustainably run.

Don’t use phase banners when other approaches better communicate status. They should only be used for services, not products.

Use tags instead when:

• you’re marking individual pages or content items rather than entire services
• content is under consultation or review
• you need to show status of documents or guidance

Structure phase banner content to set clear expectations and encourage useful feedback.

Use standard phase names that users recognize from government services:

• use ‘Alpha’ for early testing phases
• use ‘Beta’ for pre-launch development phases
• keep labels simple and avoid technical jargon

Design feedback mechanisms that don’t disrupt user journeys:

• include a clear “feedback” link that explains how users can help
• link to email, dedicated feedback forms, or feedback pages
• ensure users can return to their original location after giving feedback
• consider opening feedback forms in new tabs to preserve user progress

Remember to set help users understand what to expect from services in development by:

• explaining on service start pages what phase means and what kind of feedback helps
  be clear about limitations or known issues
• linking to information about the development process where helpful