# 4.3.5 Service sheet

##

<div><figure><img src="https://content.gitbook.com/content/YOceCec3BCixhUmzyxTR/blobs/4jYoI5MkJK3BlI87Ve1m/Service%20sheet%20(1).png" alt=""><figcaption><p>Service sheet wireframe</p></figcaption></figure> <figure><img src="https://content.gitbook.com/content/YOceCec3BCixhUmzyxTR/blobs/v9C1pPdEEGn9SpVe0pHj/Service%20sheet%20-%20example.png" alt=""><figcaption><p>Service sheet example implementation</p></figcaption></figure></div>

## How it works

### **Service name**

This helps people understand what your service does and whether they need to use it.

### **Documents and any fees required**

A list of things most users need to know: for example, what your service is, what will happen, what users will get or how much it'll cost. To keep the content concise, do not include details about anything that would be obvious to users.

### **A call-to-action**

There should be a clear call to action button to start the service, usually “Start now”. You should also include a link to “sign in” or “continue journey” if the user is able to continue an existing journey.

### **Other ways to access the service**

You should provide ways for people who can’t access the service online to get support, for example, by phone or text relay. You may also include details for support channels.

## **When to use this pattern**

At the start of a service which involves the user inputting information in order to get something. For example, at the start of an application form.