Who is this article for?

Users who want to view Scorecards for their organisation.

No elevated access or permissions are required.

Scorecards let you map Actions, Performance Indicators, and Risks onto a card that gives you at-a-glance information about how your organisation is performing against the set objectives. They can only be created and managed in Classic but can be viewed in Browser. This article will show you how to do the former.

In this article:

1. Scorecards view
2. Scorecard notebook
3. Tree of Contents
4. Creating Scorecards
5. Managing Scorecards
   • Adding items
   • Adding notes
6. Linking Scorecards
7. Creating Smart OU Objects
8. Setting up performance ratings
   • Panic status
   • Weighting
   • Thresholds
9. Further reading

1. Scorecards view

To access Scorecards:

1. Open the Classic application.
2. Click 'Views'.
3. Select 'Scorecards'.

You will be taken to a list of all Scorecards:

2. Scorecard notebook

To open a Scorecard notebook, click on the item in the list.

3. Tree of Contents

Clicking the '+' symbol displays all the items within the Scorecard in a hierarchy view, with each top-level item displaying its children below it.

4. Creating Scorecards

To create a Scorecard:

1. Go to the Scorecards view.
2. Click 'New Scorecard'.
   This will create a blank top-level object for you.
3. Fill in the requested information.
4. Click 'Save'.

Want to customise your Scorecards?
Hierarchy objects can be customised with a code, icon, name, and allowed depth within the tree. To set these up, please contact the Support Team. 

5. Managing Scorecards

Adding items

To add an item:

1. Go to the Scorecards view.
2. Highlight the element you want to be a parent.
3. Click 'Add/Remove...'.
   This will open a list of available items.
4. Select the item type from the list.
   You will see a pop-up modal where you can add (>/>>) and remove (</<<) items.
5. Click 'OK'.

Items can be added to multiple areas of the Scorecard hierarchy, allowing for a comprehensive overview.

Adding notes

To record a note:

1. Go to the Scorecards view.
2. Open an object in the hierarchy.
3. Click 'Add' (under 'Notes & History').
4. Enter your note.
5. Click 'OK'.

You will be able to see your note once the object refreshes:

Notes can be recorded against each hierarchy object, separate to the individual items. Any notes added to Actions, PIs, and Risks from this view will also be added to the items themselves. 

6. Linking Scorecards

To link Scorecards:

1. Go to the Scorecards view.
2. Highlight the element you want to be a parent.
3. Click 'Add/Remove...'.
   This will open a list of available items.
4. Select 'Linked Scorecard'.
   You will see a pop-up modal where you can add (>/>>) and remove (</<<) Scorecards. Note that you will only see Scorecards you can edit in this view.
5. Click 'OK'.

Ownerships for Scorecards are inherited down the tree structure, so a User added at the top-level will also own the children objects. This does not extend to the linked Scorecard. You will need to define the Ownership within the linked Scorecards to make them visible to the required Users.

Linking multiple Scorecards?
Reciprocal links are not available, so the linking process is one way only. You can still link multiple Scorecards together using this feature - make sure you link them in an order that makes sense!

7. Creating Smart OU Objects

Smart OU hierarchy objects are automatically propagated based on User or Roles ownerships. To be able to set up a Smart OU Scorecard, it must not contain any Actions, PIs, or Risks within its hierarchy already.

To set up a Smart OU Scorecard:

1. Go to the Scorecards view.
2. Highlight the Scorecard you want use.
3. Click 'Add/Remove...'.
   This will open a list of available items.
4. Select 'Organisational Units'.
   You will see a pop-up modal where you can add (>/>>) and remove (</<<) Users and Roles.
5. Click 'OK'.

Once created:

1. Select the OU object from the list.
   You will be taken to its notebook.
2. Check the 'Maintain Automatically' option.
   You will be presented with a list of Ownerships.
3. Tick the required options.

Items with the ticked Ownerships assigned to the selected Users and Roles will be automatically added to the Scorecard. This also applies to all new items.

8. Setting up performance ratings

Once an item, such as an Action, PI, or Risk has been linked to a Scorecard hierarchy, the combined performance of these objects can be used to create a performance rating. Any updates to these items will influence this performance rating.

Panic Status

Panic Status replaces the object icons with performance icons using the RAG status mapping.

This is set on a User basis.

To toggle this view, select the 'Panic' button in the toolbar.

With 'Panic?' disabled, the object icons will be shown. When enabled, these status icons will be shown:

The status for each level of the hierarchy is calculated according to the rules created in the 'Weighting' and 'Threshold' settings.

Weighting

Scorecard objects can be weighted to account for various levels of importance within the current hierarchy level. This weighting allows to statuses of all the sub-items in a hierarchy level to be combined to calculate the overall status. 

By default, each object weighting is set to 1, i.e. they all contribute the same when aggregating up. To specify that a specific element is more important than another in calculating the status of hierarchy objects above it, you can assign it a higher weight.

Thresholds

Scorecard objects can have different thresholds, which are used to calculate how statuses are aggregated. By default, thresholds are calculated on a worst child basis, with amber and red thresholds set to 1. This means:

• If there are any reds on any of the elements below, then the hierarchy object status is red.
• If there are no reds, but ambers, then the hierarchy object status is amber.
• If there are no reds or ambers, then the hierarchy object status is green.

These standard rules can be altered to create your own scoring rules. For example, setting your red threshold to 3 would mean that there would need to be 3 or more objects with a red status for the hierarchy to be set to red. 

You can also set your thresholds using % variances, and this functions in the same way as the scoring rules using whole number thresholds.

Sometimes, you may find that the Scorecard shows a green status with a red rider icon. This means that there are some objects within the Scorecards that are below the threshold, but the overall rating meets the green threshold.

If there are not enough items in the hierarchy to meet the thresholds, the status icon will be displayed as a blue question mark icon.

9. Further reading

• Using the Scorecards module in Browser
• Reporting on Scorecards in Classic