Start a conversation

Configure Consultant Metrics (Dials)

 This guide explains how to configure the consultant DIALS on the Home Screen. This should only be done by a system administrator.

Overview

It is possible to setup the Influence database to display DIALS on the [HOME] page of the system. These dials can count various simple items, such as the number of new candidates created, or the number of Matches set to "CV Sent" Status.

Unwanted DIALS can be hidden, and certain new DIALS added (dependant upon exactly what is required)

When viewed on the HOME page the dials show WEEKLY Totals, and re-set at the end of each week. The numbers shown on the dials are for the UserID which is currently logged in. 


Defining the Dials

To add a DIAL to the [HOME] page login as a suitable high priority user (e.g. ADM) and go to Maintenance > Setup > Code Tables 

Once the option opens, select 

System Area =  C (Contact Management) 
Code Table = Analytical Code [302]    and tick the Extra Info [  ] box at the bottom of the screen. Then maximise the window to see the additional columns.


 

Dials can be shown or hidden from the [HOME] page by placing a 1/0 in the [Home Page] column (1=Shown, 0=Hidden)


The structure of the “Change Definition” column is typically:  

TYPE/Old Status /New Status 

e.g.  MAT /*  /CVS    would count MATCH records which went from the status of * (anything) to CVS (CV Sent)

The dials take their information from the Journal Status Change file, and the  TYPE specifies which status changes are counted. The values for these are

COMP = Companies
CONT = Contacts
SITE = Sites
CAND = Candidates
VAC = Vacancies

MAT = Matches
IVH = Interview History  (Uses Interview history file rather than Jnl Status Change)

Examples of Definitions

1) VAC/   /LIVE      
This tells the system to count VACANCIES which go from a status of <Blank> to <Live>

2) CAND/  /*
This counts the status change for candidate records going from <blank> to <anything>
i.e. A new candidate being added.

3) COMP/   /*      
This would count any companies going from a  status of <blank> to 'anything', i.e. 'NEW' companies added.


Other TYPES which can be used

There are also TYPES as below, although these follow a slightly different definition than those above.

JNL = Journals    (NB: This is only available for Journals v2 systems)
DOC = Document Attachments for emails

BKHD = Bookings (NB: This counts booking headers, not 'shifts') *

* A Booking header status change is created every time one (or more) days are booked. e.g. Entering a booking from 13th-17th Feb (5 Days) would result in the creation of one booking header.  Click Here to see more about the Booking Header Dial.


Additional information for JNL (Journal) TYPE dial

This TYPE is used to count the number of Journals using a dial. The definition is of the form:
JNL /CALL TYPE/CALL RESULT/JOURNAL CONTACT METHOD

e.g.   

If you wish to count any Journals made using Call Type BUSD (Business Development) then the definition should be   JNL/BUSD/*/*

If you wish to count only telephone journals of this type, then the * at the end needs to be an uppercase “P”   i.e.  JNL/BUSD/*/P


Additional information for DOC (Document Attachment) TYPE dial

This TYPE is used to count the number of times a particular document has been attached. It is most commonly used to count the number of times the "Safe CV" document of a candidate has been attached/sent out. The definition is of the form:

DOC/RECORD TYPE/DOCUMENT PREFIX /

e.g.   

If you wish to count the number of times the 'Job Spec' of a vacancy has been sent out then the definition should be   DOC/ENIV/JOB /

If you wish to count the number of times the 'Safe CV' document from a candidate has been sent out, then the definition is  DOC/ENID/SCV /

Valid values for RECORD TYPE are:

ENID = Candidate
ENIV = Vacancy

The values for DOCUMENT PREFIX can be found from within Parameters by looking at:
ENIGMACND, ENIGMAVAC or ENIGMACLI parameter sets and viewing the TEXT tab.


Special features for "SCV" Docs

If using the TYPE of DOC with SCV to count numbers of Safe CV's sent out there are some extra features for the dial.

DOC/ENID/SCV /  - This will count any time that the SCV (Safe CV) document is sent out.

DOC/ENID/SCV> /  - This will count any time that the SCV (Safe CV) document is sent out via an On-Spec Match or just 'Ad Hoc' attached

DOC/ENID/SCV< /  - This will count any time that the SCV (Safe CV) document is sent out via a Vacancy Match

i.e. If a user had sent out a candidate Safe CV 3 times, once using the [CV Snt] stage of a Match where the candidate is linked to a Vacancy, once using [CV Snt] for on OnSpec match where the candidate is linked directly to a contact, and once via an Ad-Hoc email where they had simply attached the CV using the Attach[ ] option from the [Docs] tab of the candidate the dials would read as below.

DOC/ENID/SCV /  -  3  (since the CV has been sent out 3 times
DOC/ENID/SCV> /  -  2  (since the CV has been sent out once via an OnSpec Match and also Ad-Hoc attached to an email.)
DOC/ENID/SCV< /  -  1  (since the CV has been sent out once via an Vacancy Match)



Additional Information for the Booking Header (BKHD) TYPE Dial

It is possible to have a dial labelled 'Bookings'' which will count booking headers. This means that if a single booking were taken for 3 Days (Mon/Tue/Wed) and entered as such, then the system would count one booking rather than 3 (Shifts).


An example of the definition for this dial is shown below:

NOTE: What the dial actually counts is entries in the Jnl Status Change file, created on a specified day by that user.

e.g.  If UserID "MAJO" created 3 different bookings on 10th Feb  (Booking dates 15th-17th Feb, 10th-15th Feb and one for 16th Feb) then this would result in 3 records being created in the Status Change file, and the bookings dial would report 3 Bookings for UserID MAJO on 10th Feb



Accumulating Multiple items in a Single Dial

The Offset column is usually set to be a unique number for the separate target types and represents an internal 'register' where the counts are accumulated. To accumulate multiple definitions into a single dial, ensure that the Offset number is set to the same value for each definitions you wish to accumulate.

e.g. To have a single dial that shows the total number of Vacancies which were set to WITHDRAWN or LOST, you might create two dial definitions;

Definition            Offset          HomePage

VAC/*  /WITH        12                  1
VAC/*   /LOST       12                  0

The first definition counts vacancies set to the status "WITH" and shows the dial on the HOME page.
The second definition counts vacancies set to the status of LOST but is not displayed as a dial on the home page, but it adds those figures to the total of the first dial because it has the same offset.


 

 Exporting Consultant Metrics (Dials) as a Table.

1)      From the workbench select Maintenance> Reporting Tools > Export Consultant Metrics  and wait for the screen to appear.

2)      Use the filters at the top of the screen to select a date range, etc. then press [Go] to display the chosen information.

 


Main Team: If you have linked user IDs to a team (Dept) then you can filter to display info for only member of that team.

Branch: filters the results to a single branch (if users have been assigned to a branch when setup within User Profiles)

User:  Display figures for a single user.

The [Excel] button will allow you to export the displayed information into an MS Excel spreadsheet.

NB: From version 1.00.19.284 (or later) it is possible to control which UserID's appear in the export using a tick-box on the User record "Include in Metrics Export". All users will appear until you set the flag for one user - at which point only ticked users will then appear.


Setting Consultant Targets (for Dials)

This document explains how to set the targets that are used on the meters seen on the Home Page for each consultant.

For a guide in how to configure the specific data the targets use please click HERE

From the workbench choose Maintenance > Reporting Tools > Consultant Targets. 


[Image 1]


Once the performance targets screen appears, you can begin setting up targets.

Type:                     
You can choose to set targets for A – Agency Default, T – Team or C- Consultant. When showing target meters, the system will show targets from the lowest level.

Year:                     
You can set targets for a specific year, or for ‘Any year’.

[Create]               
If the screen is grey/full of dots, then you need to hit [Create] to create blank set of targets for the chosen selections. (Year/Consultant)

Columns:               
The columns shown represent the meters you will see on the HOME Page. Click on any column heading to select that meter.

Value:                    
Once you have chosen a column (see above) you can use this to set a value for all rows of the chosen column by clicking the [Set All] button.
 

Example

The example demonstrates how to set target for a specific consultant. (DS – Dave Sargeant), with the targets applying to *any year*.

You can easily set targets for each week of the year by selecting a column heading, Entering the target value into the Value [       ] field, and then clicking [Set All]

This means that DS has a target of adding 12 new clients per week, every week of *any year*.


[Image 2]



Notes:

Agency (A)  or Team (T) targets are useful if you want the same targets for everyone in your company, or all members of a particular TEAM, since you only need to set them up ONCE.
e.g. If I wanted all consultants to have a target of sending 20 CVs, and adding 10 New Contacts, it would be easier to set an AGENCY target for this. Each consultant would then be individually expected to achieve 20CVs sent, 10 Contacts added, etc.

If one consultant was part-time, and has a different set of targets (8 CVs and 4 New Contacts) then I could create a set of Consultant (C) targets for that one individual


 






 Keywords: Setup, Consultant, Targets, Metrics, Table


Choose files or drag and drop files
Helpful?
Yes
No
  1. Martin Parkinson

  2. Posted
  3. Updated

Comments