Skip to main content

Your browser is out of date, and unable to use many of the features of this website

Please upgrade your browser.


This website requires cookies. Your browser currently has cookies disabled.

Content types

This is a list of the different content types that you may be asked to write for.

Content type Format Description
Code of practice HTML and PDF

Codes of practice set out what the law requires and what standards we expect of those we regulate when complying with the law. Codes are more definitive than guidance with the distinction and clear implication being that if we find schemes are not meeting these standards we will take action.

  • Use the code of practice template when writing modules. It is comprised of module details / navigation and links / drafting principles / review table.
  • Do not add content as footnotes (unless it is a legal reference). Either include it in the main text or remove it if it’s not important enough to include.
  • Use ‘Legal references’ as the title for footnotes. Only use these for references to legislation.
  • See our house style and tips on using plain English

Where possible avoid using active titles for single code modules so that we can use those for guidance eg ‘Conflicts of interest’ for the code module and ‘Managing conflicts of interest’ for the guidance.

Using legal language in codes of practice:

  • ‘Must’ is used for legal requirements.
  • ‘Should’ is used for our expectations.

Only expectations that are underpinned by legislation can be included in codes of practice.

Any ‘best practice’ that is not underpinned by legislation can only appear in guidance.

See more detail in legal and technical content.

Code of practice examples

Detailed guidance HTML

Provides detailed, practical guidance about how to meet the standards in our codes or achieve an acceptable level of compliance on a ‘comply or explain’ basis.

Also provides guidance for pension experts involved in automatic enrolment.

Always add the published date at the top of the guidance.

Detailed guidance examples

Note: detailed guidance can be one or more pages.

Basic duties guide HTML

Short, focused content that answers a need our audiences have of TPR and helps them to complete a task, or a series of steps or sub-tasks. May be one or more pages.

Note: If the guide has more than one page the first should contain the most important information that most people need to read. Subsequent pages should provide more detail.

Basic duties guide examples

List page HTML

Lists content, products or publications.

List page example

Statement HTML

Sets out TPR’s view or position at a point in time. Does not contain guidance. Not usually updated after being published.

Statement examples

Corporate publication PDF or HTML

Provides information about TPR, how we regulate and insight we have gathered. Not usually updated after being published.

Corporate publication examples

Enforcement publication HTML or PDF

Sets out details of our regulatory and enforcement activity to demonstrate the actions we are taking when schemes do not comply.

Enforcement publication examples

Checklist PDF, DOC

A short, task-focused product consisting of questions or actions with a box to complete for each. May include brief supporting information for each question or action.

Checklist example

Example or template PDF, DOC A completed example or blank template for a policy, process or letter – such as a sample risk register, conflicts of interest policy or AE letter to staff. Enables the user to download or print and then complete.

Enables users to submit information to us as part of an online transaction (or by downloading a file and emailing or posting it to us).

Note: Try to avoid guidance or user manuals by creating user-friendly forms that have been tested with users.

See: how to write good questions for forms

Interactive tool or calculator HTML Question-based content in an interactive format. Examples include decision tree tools, calculators and educational quizzes. May be logic-based, ie the sequence of questions and the results depend on the user’s answers.
Case study HTML, video

Examples that help the user understand how to complete a task or process.

Note: To be of value they need to apply to a significant number of users, add something important to guidance and be useful over the long term.

Press release HTML

News content produced by TPR’s press team and sent to the media.

Press release examples

Biography HTML

Describes someone who is responsible for running TPR and using our regulatory powers.

Biography example

Blog post HTML

Provides thought leadership and opinion.

Blog examples

Job advert HTML Informs users of a vacancy or work opportunity.
Freedom of information (FOI) response HTML

Information that we publish in response to FOI requests.

FOI examples

Event HTML Provides details about webinars, workshops and other TPR events.
How-to video Video

Provides short, practical guidance in a visual format.

How to video example

Video transcript HTML

Sets out the full text of videos.

Video transcript example

Campaign page HTML

A standalone page that acts as a destination point for a campaign.

Note: Where possible, drive traffic straight to existing content rather than via a separate campaign page.

Speech HTML

The full text of public speeches made by TPR staff.

Speech examples

Infographic HTML Provides information or data in a pictorial format. May not be suitable for smaller screens.

Content in a question and answer format. Usually ineffective as people struggle to find what they are looking for and tends to lead to duplication.

We follow the GOV.UK approach and are phasing out this type of content.

Elearning / toolkit LMS Content that helps the user to gain deeper learning, change their behaviour, improve their skills and develop their expertise.