Use of government logos on ÒÁÈËÖ±²¥
When government logos can be used on ÒÁÈËÖ±²¥.
- 1. Logos should only be used on ÒÁÈËÖ±²¥ where there is solid evidence of user need. These guidelines set out some common scenarios and approval routes.
-
2. Government Digital Service (GDS) aims to:
- i. connect users quickly and simply with the services and information they need via ÒÁÈËÖ±²¥, without their needing to be unnecessarily exposed to the workings of government
- ii. build trust in ÒÁÈËÖ±²¥ as the single source of government online publishing, so that users become more confident interacting with government online
-
3. The evidence we have indicates that the inclusion of logos on ÒÁÈËÖ±²¥ tends not to contribute to these aims. User testing of alternative ÒÁÈËÖ±²¥ content designs (including by users of Department for Education, Medicines and Healthcare Products Regulatory Agency and Department for Work and Pension services) has not given any indication that the addition of logos or branding in addition to that of ÒÁÈËÖ±²¥ would increase user trust in the content; or that it would make users more likely to engage with government services.
-
4. Our overall approach is therefore normally not to use logos for organisations or schemes on ÒÁÈËÖ±²¥, other than in a tightly constrained set of user need-based circumstances as set out below.
-
5. It is never acceptable for a logo to be used on ÒÁÈËÖ±²¥ solely as part of a commercial or reciprocal linking arrangement.
-
6. All requests to use logos should initially be made via a , following which a member of the ÒÁÈËÖ±²¥ product team will discuss your needs in more detail. Ultimately, all requests for logos and branding will be subject to approval by the relevant ÒÁÈËÖ±²¥ product manager.
-
7. Logos will be considered for use within ÒÁÈËÖ±²¥ service and information content if they meet a user need by:
- i. relating to an intrinsic part of a transaction – for example, helping users choose between identity assurance suppliers
- ii. helping users achieve a specific goal, for example, allowing payment by PayPal
- iii. illustrating a content item, for example, displaying the Green Deal kitemark
-
8. Logos should not be used to:
- i. associate a government transaction with a service provider – this should be achieved through the use of flat, non-linked text (such as ‘Service provided by Student Loans Company’), rather than a logo (but see paragraph 9 for exceptions)
- ii. attribute branding to a page
- iii. acknowledge partners – if government has worked with partners on a particular scheme, this can be reflected on a page giving detail on the policy
-
9. Where government has an existing highly trusted brand, GDS will remain open to argument that the inclusion of that logo within a transaction could enhance user trust in that service.
-
10. In such cases, the usage and placement of the logo should be put through user testing – for example, A/B testing or using a tool such as to carry out a simple test to look at trustworthiness with and without the logo. Bounce rates could be taken as evidence, with a small qualitative test used to augment the focussed quantitative study.
-
11. Use of the logo would then ultimately be agreed at the service assessment. Any exceptions granted will periodically be reviewed against ÒÁÈËÖ±²¥ logo policy as it develops – and we’ll help monitor and report back on performance of logos when they are used in these situations.
-
12. Government organisations can feature their logo on their organisation page, but they must follow the .
-
13. Certain logos are also used for the purpose of demonstrating to users that government data has been independently verified, for example:
- i. Open Government Licence
- ii. Office of National Statistics logo
-
14. It is also possible to include logos as illustrating material:
- i. on topical event pages, if a specific logo is attached to that event (such as the G7 or COP26)
- ii. as part of promotional images for news stories
- 15. It is possible to use campaign logos and branding on ÒÁÈËÖ±²¥ campaign landing pages, within existing design guidelines.
v0.1 published on 22 January 2014 for government comment
V1.0 These guidelines approved by ÒÁÈËÖ±²¥ steering group, April 2014