Sign in to MyHR

Colleague website proposition

Last reviewed on 26 July 2018

All content that goes on the colleague website must fit with this proposition.

The colleague website is for:

  • Co-op employees
  • potential Co-op employees
  • contractors who work at Co-op

It will give users easy access to information about being a Co-op colleague, at the point they need it.

All content on the site needs to meet a set of criteria:

It’s about being a Co-op colleague

All content should fit into one of these categories:

  • information that only Co-op has for all its colleagues - like pay dates or how to claim expenses
  • people policies and procedures - like paternity or disciplinary policies
  • awareness-raising issues colleagues need to know about - like a new HR system or change of leadership

The website is not for:

  • information to help people do their specific jobs - like how to do things in food stores
  • content that already exists somewhere else - like the colleague pensions website (we can signpost where this is helpful to our users)
  • advice that isn’t directly about being a Co-op colleague - like saving energy in the home or getting fit
  • information for customers and members
  • advertising
  • team pages - like telephone numbers and pictures of people

There’s a clear user need

All content must have a clear user need, which can be backed up with evidence.

As a starting point, content that gets fewer than 50 visits a month is unlikely to meet a user need.

There will be exceptions to this, which we’ll deal with on a case-by-case basis.

Example of a user need:

As a Co-op colleague who’s pregnant
I need to find out how much maternity leave I’m entitled to, and how to apply for it
So that I can arrange and plan my maternity leave.

The content owner will review and update the content

All content must be reviewed by the named content owner at least once every 12 months.

Content needs to be reviewed:

  • as part of the annual policy review cycle
  • when they get feedback about an error or problem with the content
  • when a policy or procedure changes

Public vs private content

Once we know content should go on the colleague website, a specially trained group of super editors will decide if it should be public or private, hidden behind a log-in.

Because we want to make information available at the point of need, all content should be publicly available unless there’s a reason for it not to be. Reasons to make content private include if it:

  • could damage Co-op if it got into the wrong hands - like the locations of security cameras or pictures of passes
  • is information that would be useful to Co-op’s competitors - this could include financial or corporate data
  • involves personal data that we don’t have permission to share publicly, like user research videos of colleagues sharing their opinions

We’ll work with information security to make sure we’re applying the right criteria and using them correctly.