University of Bath

Creating a Case study

How to use Typecase to create a webpage showcasing a person or group from the University.

About this content type

You should use this template to tell a story of a person or group's experience of the University. You can also embed multimedia content such as audio, video, photo gallery or map to make your case study more engaging.

When to create a case study

Create a case study to:

  • tell a person’s story about their experience of an aspect of the University (a student’s experience of Freshers’ Week, a researcher’s account of their involvement in a research project)
  • showcase a collaboration between the University and a course-related partner (the work of the University’s turbo centre in collaboration with Ford, Jaguar Land Rover and Cummins Turbo Technologies)

Don’t create a case study if:

  • you want to write about a broad subject, rather than an individual experience - this would be better suited as another content type (Project, Event, Campaign)
  • you want to write about a future event or project
  • there are existing Case Studies on the same story (We do not want to duplicate content on the website as this can be confusing for users.)

Naming your Case study

The title for your Case Study should:

  • be easy to understand and avoid using fancy or technical language
  • use active language rather than passive ('The search for tomorrow's champions', not 'Tomorrow's champions discovered').
  • be informative and include enough detail to give the user a sense of what the story is about ('Research to help blind people' is not as informative as 'Research helps blind people see photos')
  • make sense when read out of context - this will help users find your content through search engines
  • be limited to 65 characters if possible so users can read it in entirety on search results

Your title should not:

  • include the phrase 'case study' (this is automatically displayed on the page)
  • be a question
  • contain commas or dashes as this will create confusing URLs - use a colon instead if you need to separate phrases ('Tuition fees and charges for all students: 2018 to 2019')

Writing a Case study summary

Use the summary to identify the person or group whose experience the case study is about, rather than just summarise the project or activity involved, for example:

Title: Bath graduates design Olympic Velodrome roof

Summary: Two graduates from the Department of Architecture & Civil Engineering worked together on the design team responsible for the Olympic Velodrome.

The summary should be no more than 160 characters.

Read the full Case Study.

Adding labels

We use labels to pin content items onto Topic pages. Only add a label if you know that your content item is going to be part of a Topic.

Labels are not typical website 'tags'. Don't add a label just because you think it might be relevant. You must know what labels the Topic uses. If you don't know, ask your Faculty Web Editor or contact the Digital team at web-support@bath.ac.uk.

To add a label to a content item, select from the drop-down list in the Labels section and click 'Add label'. You can add a maximum of 12 labels to a single content item.

Writing Case study content

Things to keep in mind when writing your Case study

Do:

  • write concisely and in plain English
  • structure your content so that the most important information is at the top
  • write first-person accounts or in the third-person with direct quotes from the person involved
  • at first mention of the individual use the full name, after that, use the first name - ‘George Parr’ at first mention, then ‘George’ after that
  • create links to any projects, courses, interests, campaigns, activities and so on where relevant

Don't:

  • create multiple case studies for the same event, project or experience unless each case study explores a different aspect of the same research or traces how a researcher’s experience has developed
  • use generic or needless headings ('Further information' or 'Introduction') - users don’t want an introduction, they want the most important information
  • use interviews in Q&A format

Try to avoid using interviews and writing in the third person. These can often including difficult language that can be confusing for the user. Paraphrasing and interlaced quotes are more use friendly.

Resources to help you write your Case study

The University's style guide will help you make sure you're using the same terminology, style and tone as the rest of the website. This is important so that website users can understand us easily through the consistency of our content.

Our formatting guide will help you create appropriate headers, links, lists and other formatting for your page. This is important because it makes the information we provide clearer to website users.

Hemingway Editor is a useful website that analyses your content and tells you whether it is easy to read or not.

Add a call to action

A call to action is the next thing you want the user to do after reading your content. The Content Publisher has special fields for entering a call to action.

Make sure your call to action:

  • is active ('Find out more about...', 'Contact the...', not 'More information is available…')
  • makes the destination of the link clear to the user
  • does not end in a full stop

Your call to action can be a link to a web page, an email address or a phone number.

If your content doesn't have a call to action, choose 'No call to action' and enter a good reason for not having one in the 'Reason for no call to action' box below.

You should always try to think of the next step for the user.

Adding responsible Organisations and Groups

After you have added all your content - including any images, media and contact details - you will be able to select an owner or associated group for your page. This allocates permissions for who in the organisation is able to maintain the content.

A guide for adding responsible Organisations and Groups is available to help you do this.