Compliance & Reference Chase Module

Created by Graeme Orchard, Modified on Wed, 21 Feb 2024 at 09:53 AM by Graeme Orchard

OVERVIEW

From version 1.00.23.352 or later a new Compliance Chase module has been introduced. (We recommend that your system is updated to version 1.00.24.032 or later if you plan to use the feature)


This module allows users to setup sequences of emails that will be used to chase certain compliance items. Users can specify which items are included in the chase, how many days there will be between each chase email, and the candidate Statuses and/or Roles that will be considered for the chase. It can also be used to chase referees to return references (provided the references have been setup as compliance items).




Contents

.

TABLE OF CONTENTS





1) SYSTEM SETUP / PARAMETERS


In order to control the new module, there is a new parameter set - COMPCHASE

Details are shown below.


PARAMETERDESCRIPTION
COMPCHASE, Priority (1)Priority level needed to be able to setup a new CHASE sequence
(This can be replaced with a UAC to provide a specific list of users who should be able to create new CHASE sequences.)
COMPCHASE, Text (1)

Call Type for Compliance Chase Journals
(Default is CMPL)
COMPCHASE, Text (2)

Call Type for Reference Chase Journal
(Default is CMPL)
COMPCHASE, Flag(1)

Selection of Consultant is Mandatory
(Tick to make this mandatoy, if required)



These parameters should be set, and can be accessed from Maintenance > Setup > Parameters


Tip: If you do not have the Call Type CMPL in your system, you will want to add this (or change Compchase, text (1/2) above.)

To add a new Call Type go to Maintenance > Setup > Code Tables, select system area as C - Contact Management and choose code table Call Type [019] - then add a new CODE / Description.








 

2) CONFIGURING A NEW CHASE 


To configure who and what to chase, there is a new option found in Maintenance > Setup – Compliance Chase Configuration

(The option can also be found by going to ADMIN > [Cmpl Chase] and then clicking the [Setup] button)


Once the Compliance Chase Setup screen opens, you can click the [...] button to specify a CODE and enter a Description for your new chase sequence.

Having given the sequence a CODE/Description, there will be several [Tabs] below which you can use to configure the details for this particular chase sequence. 



 i) The [Templates] tab

The first “Templates” tab allows the user to select the templates to use for each run and the number of days to wait between each run. The templates can be selected by the dropdowns, which are based on a new “Where” type on the template of “CCH – Compliance Chase”. Pick and Edit options have also been provided as seen on Journals and Macros. 


A screenshot of a computer 
Description automatically generated

 

When designing your chase sequence use the drop-down to select the email template to send using the drop-down or click [Edit] at the right-hand end to create a new email template to be used.


{Adding/Editing templates is done in the same way as you would create any other email template. Our support article Edit or Create an Email Template  explains more. }

 

Tip: 

When designing templates for chasing a new Multiline parameter for Compliance has been added - CHASE. This will select only compliance items included on the [Compliance] tab of the chase you are creating.



This would produce an email similar to the one below. The Compliance Items listed would be any of those which were specified on the [Compliance] tab of the chase sequence that you setup.







ii) The [Compliance] tab

The [Compliance] tab details the compliance items to check. These can be whole groups (on the left) and/or individual compliance items (on the right). 

There is a tickbox to the right of each item “RptDays”. If ticked, this indicates that the system should use the reporting days on the item to determine if the item is expired or near expiry.

 

A screenshot of a computer 
Description automatically generated

 

Having selected the items you want to chase, click [Apply] to save your changes and then move on to the next tab.



ii) The [Filters] tab


 The [Filters] tab sets some of the search parameters for the chase run. Candidate status and or roles. 


A screenshot of a computer 
Description automatically generated

 

Once you have decided which candidates you want to target with this chase sequence (based on their ROLE(s) and Statuses, click [Apply] to save your changes, and move on to the next tab.




iv) The [Send Log] tab


The final [Send Log] tab shows the log of emails sent. 

Double clicking on an item in this list will open the associated Journal record.

 

A screenshot of a computer 
Description automatically generated

 

This tab is useful for seeing what has been chased and when it was chased.

Once done, click [OK] to exit this tab and close the chase sequence.




Reference Chasing [  ]  {Optional}

Putting a tick in the Reference Chase [  ]  box makes the chase into a reference chase. This will look through for “RF” (Referee) type compliance items where the referee has been set but the compliance item has not been ticked - i.e. the reference has not been received from the referee.


In the same way as compliance chasing, there are a number of templates that are used with a number of days specified for each chase. 

NOTE: The “Compliance” tab is hidden as only the “RF” type compliance items are used.


When running a chase, the emails are sent to the relevant referees and not to the candidates as would be the case with a normal compliance chase.

 

A screenshot of a computer 
Description automatically generated

 





3) SETTING THE EMAIL SEQUENCE FOR A CHASE

In order to chase the compliance items, you will want to setup various emails to send out at different stages. You might have an initial chase email, a follow-up chase, and then a Final Reminder each of which is worded differently.


Step 1: Click the [...] button and pick a chase sequence that has been setup (or click [Setup] to create a whole new sequence.)

Having done that, select the [Templates] tab and choose the 1st Template using the drop-down.

{If no templates are available, click [Edit] to open the Template Editor and design a suitable email template for chasing.}


Step 2: Specify how many days should elapse form the time the 1st template was sent until the 2nd template is sent, and set this using Days UntilThen use the drop-down to select a template to use for the 2nd email.

{Again, if no suitable template exists, you can use [Edit] to open the template editor and design a suitable template for this second chase.}


Step 3: Repeat the above, for as many chases as you want to create, specifying the number of days that must have elapsed since the previous chase, and then selecting (or creating) a suitable template.


  

 

Step 4: Decide how you want to finish the sequence; 

If you want the sequence to STOP, then you must choose *** DO NOT SEND ANY MORE EMAILS *** as the final item of your sequence.  (See below)

 

If you do not do this, then the system will continually send the final email of the sequence to the worker, until they no-longer match the group being chased (e.g. You change their status to one such as 'Archived' and do not chase these people or they send all the requested items.)




Creating the Email Template

If you need to create an email template for any of the steps above, this can be done as below.


{NOTE: Adding/Editing templates is done in the same way as you would create any other email template. Our support article Edit or Create an Email Template  explains more. }


 

STEP (i): Click the [Edit] button to open the Template Editor


STEP (ii): Give the template a Description (bottom left), and a Subject (bottom centre)

Set the Modify & Display priorities (top right) to determine which users can amend the template or see/use the template.

Also decide if the template should be personal (your use only) or shared (visible to all users - provided they are of high enough priority)


STEP (iii): Use the large white area to create the content of your template. Write the email as you want, and use the Catalogue at the left hand side of the screen to choose relevant merge fields such as Candidate Forename, etc.



See below for example email template.




 

Tip: 

When designing templates for chasing a new Multiline parameter for Compliance has been added - CHASE. This will select only compliance items included on the [Compliance] tab of the chase you are creating.



This would produce an email similar to the one below. The Compliance Items listed would be any of those which were specified on the [Compliance] tab of the chase sequence that you setup.


The email can then be sent from Outlook, just like any other email. 






Compliance Chase Merge fields

When creating your template you will want to include a list of items that you want to chase. Below are listed some useful examples of fields to include in your template: 


i) Field to list all items included in the Chase.

If you want to include a merge field to list details of all the ITEMS which are included in this chase sequence, as specified on the [Compliance] tab, use the field below:


[[MULTILINE=COMPLIANCE;CHASE]] [[RQDF_REQ_CODE$]] [[RQDF_DESC$]] [[/MULTILINE]]


Tells the system to build a list containing all the items which were specified on the [Compliance] tab of this chase, irrespective of whether they have been received or not. This is often useful for the initial email to make candidates aware of all the documents that are required for their registration.



ii) Field to list all "Non-Compliant" items included in the Chase.

If you want send a list that includes only items which are "Non-Compliant" from those included as part of the chase (e.g. have expired, have not yet been returned, or are not yet ticked for some reason) then use the field below:


[[MULTILINE=COMPLIANCE;CHASE;COMPLIANT=N]] [[RQDF_REQ_CODE$]] [[RQDF_DESC$]] [[/MULTILINE]]


This will include only items where they have not yet been received/marked as completed, {i.e. not ticked on the candidate as being compliant} or have Expired.


Considerations when Designing a Chase


When you design a chase, it is the chase sequence itself that defines WHAT gets chased, and so it is important to think about the ROLES and Compliance Items included on the chase.


For example, If you recruit both Nurses and Social Care workers then these people may have different Compliance items that are required. If that is the case, then you will want to setup a separate chase sequence for NURSES, which specifies all the items that they are required to supply as part ofn their registration, and a separate chase sequence for Social Care workers, requesting/chasing different documents.


By doing this, you can (often) use the same chase email since the merge field will only pick-up what has been specified on the chase.


For example:  The template as below

Hi [[ENID_FORENAME$]]


As part of your registration, we require the following documents from you.

Please attach by return


Documents required

[[MULTILINE=COMPLIANCE;CHASE]][[RQDF_DESC$]]

[[/MULTILINE]]



Thanks for your prompt attention


Might produce this email from a chase setup for Nurses, chasing Right to work & Mandatory Training.


Whereas using the same template email on a chase designed for Support workers might produce a different email as below (because the CHASE specifies different items as being required)



In summary, the CHASE that you setup specifies the Items that will be chased, so if different roles, require different compliance items/paperwork, then they will each need a different chase sequence created.









4) RUNNING A COMPLIANCE CHASE (How to use this)


Compliance Chasing can be found as an option under Reporting Tools as well as a button on the Admin workbench. i.e. Admin > Cmpl Chase 


Select the Chase from the dropdown. Select any additional filters that may be required (working between dates, candidate registered dates, consultant and work type tick box) and then press the [Search] button. (Bottom right)


All relevant candidates will be selected - i.e. any candidate that has at least one of the compliance items outstanding or expired or expiring for a compliance chase. The compliance items are listed in the same way as a RAG report. There is an “Incl” column that can be used to untick any listed person.


If there are any candidates listed that you do not wish to send an email to, you can click on the green ✅ in the [Inc] column and change it to a cross. ❌- there willl not be included when you send the batch of emails.




For candidates that have items outstanding, have had an initial chase email sent but are not yet due the next email, they will be initially listed, but with an   in the “Incl” column. The   can be changed to a tick   if required by simply clicking on the icon so that the next email can be sent ahead of time.


If the candidate does not have an email address, then there will be a yellow warning triangle displayed in the “Incl” column. Floating over the triangle will show the reason.


Next to the [Send] button is the signature selection button to allow the correct signature to be used.

The SMTP for bulk emailing only flag on the user is taken into account. If set, then the user will have the option to use SMTP to send the emails.




Testing the Chase Sequence

So that tests can be done, before firing off all emails, there is a Test Quantity [  ] field. The number entered here will allow the “Send” to create (but not send) the emails one at a time so that the email can be checked.

{i.e. The emails will be generated and passed to MS Outlook, but will not be automatically sent)


When running a TEST, the user is asked for each one whether or not to log the email as sent. 



Example of a Test Run

If you choose to run a TEST, you can specify the number of test emails to be passed to MS Excel.


After each email, the user will be asked if they wish to register it as SENT or not.

(If you did not send the email, you will probably want to say 'No'.)


Any emails which were makred as SENT have this indicated with the email icon. ✉️



5) HOW TO END A CHASE SEQUENCE

When setting up a chase sequence, you can determine what happens when the system reaches the last email of the sequence.


Either;

a) The system can continue to send the final email periodically and keep chasing for the required documents 

<or>

b) You can specify that once the system reaches this point, it should not send any more emails.


In the example below, you can see that the system will send Chase 3 three times, and will then stop sending that email.






6) REFERENCE CHASING

There is very little difference between Compliance and Reference Chasing. If the chase selected from the dropdown is a reference chase, then the search results show the referee name instead of the RAG (Red/Amber/Green) Compliance information and emails will be sent to the referee rather than the candidate.




Reference Chase Setup

When setting up a Reference chase, you will want to click the [Setup] button.

Within the Chase Setup Screen, you can setup Filters and Templates


FILTERSYou can specify the Candidates Statuses & Roles that are applicable to this chase.
TEMPLATESYou can create the emails that will be sent to the Referee asking them to send back a reference for the candidate.


IMPORTANTWhen designing the Reference chase template, if you want to add the referee name, you need to use the 'Contact' field, but it must be adjusted to contact 2


i.e. [[CMC_FORENAME$]]  would need to become [[CMC2_FORENAME$]] to display the Referee Forename.




EXAMPLE COMPLIANCE CHASE EMAIL

Below is an example of an email for chasing Referees

Dear [[CMC2_FORENAME$]],


I emailed you a few days ago, requesting a reference for [[ENID_FORENAME$]] [[ENID_SURNAME$]] who provided your name as a referee.


I know that you are probably very busy, but I would be most grateful if you could spare a couple of minutes to send in a reference for [[ENID_FORENAME$]].


I am looking forward to hearing from you shortly.


Thank you.



This will produce output something like below




7) USEFUL COMPLIANCE CHASE EMAIL MERGE FIELDS

When designing emails to chase Referees and asking them to send back completed references, the following merge fields may be useful.


DescriptionMerge Field
Referee Forename[[CMC2_FORENAME$]]
Referee Surname[[CMC2_SURNAME$]]
Referee Email[[CMC2_EMAIL$]]
Referee Mobile[[CMC2_MOBILE$]]
Referee Telephone[[CMC2_PHONE$]]



TIP: When designing your chase template email you can select these fields from the Contact Management Contacts section of the Catalogue, double-click to inset them intoi the template and then just edit [[CMC_.....]] and change it to [[CMC2_.....]]




APPENDIX: Example Chase Emails (Templates)

Below are some example templates that can be used for chasing compliance items. If you wish to use these simply copy/paste the text from below into the 'Chase' email on your system, You can then modify the wording to suit.


Compliance Chase 1: 

Chase 'New Applicants' for all items specified in the chase sequence.


Hi [[ENID_FORENAME$]]


Thank you for registering with us. As part of your registration we need the following items.


Items required

[[MULTILINE=COMPLIANCE;CHASE]][[RQDF_DESC$]]

[[/MULTILINE]]


Please send at your earliest convenience



Compliance Chase 2: 

Chase 'New Applicants' for any items specified in the chase sequence that have not yet been returned/marked as 'complete'


Hi [[ENID_FORENAME$]]


We recently asked for some items as part of your registration. We are still awaiting the following items.


Items not yet received

[[MULTILINE=COMPLIANCE;CHASE;COMPLIANT=N]][[RQDF_DESC$]]

[[/MULTILINE]]


Please can you send these at your earliest convenience.



Compliance Chase 3: 

'Final' chase for 'New Applicants' for any items specified in the chase sequence that have still not yet been returned/marked as 'complete'


Hi [[ENID_FORENAME$]]


We urgently need the following compliance documents to complete your registration. Until we receive these we are unable to offer you work


Items Urgently Required

[[MULTILINE=COMPLIANCE;CHASE;COMPLIANT=N]][[RQDF_DESC$]]

[[/MULTILINE]]


Please send at your earliest convenience; If you have any queries please contact us.



Reference Chase 1: 

This email can be used to contact a Referee, and ask them to send back the completed reference form on behalf of a candidate.



Hi [[CMC2_FORENAME$]],


We have been asked to contact you by [[ENID_FORENAME$]] [[ENID_SURNAME$]] who is in the process of apply for work through us.


Please can you complete the attached Reference Request form, and return it to us at your earliest convenience.


Many thanks



NB: Don't forget to amend the template and attach the empty 'Reference Request' form that you wish to be completed.




Reference Chase 2: 

This chase can be used to chase a Referee again, and ask them to send back the completed reference form on behalfl of a candidate.



Hi [[CMC2_FORENAME$]],


A little while ago we contacted you asking for a reference for [[ENID_FORENAME$]] [[ENID_SURNAME$]].


We still have not received this.

Please could you get this back to us at your earliest convenience, as we will be unable to complete the registration for [[ENID_FORENAME$]] until we receive this.


Many thanks



NB: Remember to attach the relevant Reference Request form to the template if you want to re-send the form to the referee..









Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article