Frontend templates

Completed transaction

The completed transaction frontend template is what an end-user interacts with once they have completed all the necessary tasks/actions within an individual government service

How it works

Any service starting on GOV.UK should have a feedback page, it doesn’t need to have a start page.

After an end-user completes a transaction on an online service they are directed to the completed transaction frontend template where they relay their experience using a service. The results are in Feedex. Satisfaction scores used to be on the performance platform, where you could compare scores across different services.

Also, there is an option for a promotional banner to appear within the interface. Examples include but not limited to:

• Organ donation
• Reminder to bring id in order to vote
• MOT reminders
• Electric vehicles

The domain for every completed transaction must have a /done prefix.

Live examples

• Give feedback on Tax your vehicle
• You've completed your transaction
• Give feedback on Check if a vehicle is taxed

Complete list of examples available and page data on Content Data.

How it's built

These are the underlying technologies that make-up the completed transaction front template.

Content schema

completed_transaction

What is a content schema?

A GOV.UK content schema is a JSON schema that defines the data structure of a piece of content. It determines what content and metadata attributes the page has.

Content type

completed_transaction

What is a content type?

Content type describes the types of pages that exist on GOV.UK. It’s stored in the content item (JSON) as document_type. It powers search filters in all finders and changes the content type label users see on GOV.UK pages.

Publishing app

mainstream-publisher

What is a publishing app?

Publishing apps are used by publishers across government departments to publish content to GOV.UK.

Rendering app

feedback

What is a rendering app?

Rendering apps render content to GOV.UK end-users.

Components

The components used within the completed transaction frontend template

Component	Source	Publishing app input field(s)
Layout super navigation header	Autogenerated in frontend template
Breadcrumbs	Autogenerated in frontend template	Tagging > Breadcrumbs
Page title	Customized by publisher	Title (required)
Generated on page via custom styling, without using any pre-existing components	Customized by publisher	Promotions
Heading	Customized by publisher	Parts > Part[i] > Title
Form radio button	Autogenerated in frontend template
Form character count	Autogenerated in frontend template
Button	Autogenerated in frontend template
Related navigation when displayed within contextual footer	Customized by publisher	Mainstream browse
Related navigation when displayed within contextual sidebar	Customized by publisher	Related content items
Feedback	Autogenerated in frontend template
Layout footer	Autogenerated in frontend template

Help improve this frontend template

To help make sure that this page is useful, relevant and up to date, instructions on how to contribute can be found on the GitHub repository (opens in a new tab).