When you create a new Workforce Compliance Requirement, they will default to our standard "Training" form - example below:



And the standard "Approval" form should a Requirement require approval:



However, you are able to add your own bespoke forms and have specific workflow steps assigned, in a similar way to how Radar Events are set. 


This is currently something that only we can do here at Radar, so please contact us if you would like to change the above form or have different options, and we can action this for you.


In order to add your own forms to a requirement, follow the steps below:


1. First you need to create your form(s) using the Form Editor tool. We recommend that new forms are created in your Staging site so that you can fully test them in a safe environment prior to them going into your Live system. (You can find Form Editor help here).


2. Next, you need to create the Compliance Requirement (Requirement Type) that you would like the form(s) to link to. (Please find Workforce Compliance help here).


3. Finally, raise a support ticket with us here at Radar via either your support portal or by emailing support@radarsoftware.co.uk and provide us with the following information:

  1. Name of the requirement(s)
  2. Name of the form(s) that you want to be linked to the requirement
  3. Who will be completing the form(s)? If you have multiple forms (workflow steps) in a requirement, each form can be assigned to a different role if required. Please find the options below: 
    • Self - This is the user to whom the requirement will be assigned. I.e. All user's will complete their own requirement.
    • Line Manager - This is the Manager in Radar for the users to whom the requirement will be assigned. 
    • A Radar role - E.g. "HR Manager"
  4. Would you like the requirement's workflow to follow a different path based on answers in a form? E.g. If you have a form with an assessment in it, you can ask for a different path to be followed based on if the user passes or fails the assessment. For example, you may wish something similar to the below to happen:
    • If the user achieves a mark of 80% or higher, mark requirement as complete
    • If the user achieves a mark below 80%, give them a second attempt (this would re-assign the same form/workflow step to the user to complete in full again) 
    • If the user fails achieves a mark below 80% on second attempt, assign form "Reset attempts" to the user's Line Manager
  5. Is the requirement recurring? If so how would you like the recurrence to work? Please find the three options below:
    • Calculating from a "Completed" date in a form - If the form has a date field such as "Date training completed", we can set the recurrence to calculate the next due date based on the date entered here and the settings in the requirement itself. For example, if the requirement is scheduled to recur annually (you set the recurrence in the Requirement Type - help available here), and the "Date training completed" is entered as 1st March 2020, the next due date would be 1st March 2021.
    • Calculating from an "Expiry" date in a form - If the form has a date field such as "Expiry date", we can set the recurrence to be based on the date entered in this field. For example, if the requirement is "DBS Check" and the "Expiry date" entered is 1st January 2021, then the next due date would be 1st January 2021.
    • Calculating from the date a requirement was physically completed in Radar - Alternatively, the next due date can simply calculate based on the date the previous requirement was completed in Radar and the settings in the requirement itself. For example, if I go in to Radar and complete a requirement on the 1st August 2020, and the requirement has an annual recurrence set (set in the Requirement Type), then the next due date would calculate to 1st August 2021. If you do not have a date field in your form, this is how a recurring requirement will calculate.


Once we have the above information, we will link the form(s) and the requirement(s) together for you.