Ansarada GRC: How to set up a Task using Predefined Tasks

Ansarada GRC: How to set up a Task using Predefined Tasks

⚠️ This is only applies in the Events and Registers modules

Are you setting up a task with a predefined task template created by your Register Owners/System Administrators?

Our system provides the feature to predefine tasks as a preset template which users can then use to set up a chosen relevant task. This will help save users time and effort and ensure consistency around the tasks being generated.

The Predefined Task will be pre-designed by your Register Owners or System administrators. The task description ie. task instructions will be predefined for the chosen task selection. All that is left for the user to do, is to edit any details of the predefined task description (if relevant) and schedule the task.

  1. In the relevant record, add a new Task in the Tasks tab.

  2. Select the relevant Predefined Task template which you want to use from the drop down list.

  3. Once a Predefined Task is chosen, the fields will populate with the details of the preset template.

  4. Update any relevant fields, if required.

  5. Then, move onto the Schedule tab to schedule the task. The scheduling will remain blank for each user to apply relevant scheduling.

  6. Select the frequency of your chosen scheduling for this task.

    1 Adhoc = one-off

    1 Weekly = weekly

    2 Weekly = fortnightly

    3 Monthly = quarterly

    12 Monthly = yearly

  7. Select the Due Date for the first (or only) task in the Next Due Date field.

    ℹ️ If the task has a recurring schedule, the Next Due Date field will update once the next period rolls over.

  8. Select the 1st and 2nd Reminder Dates for this task as # days before the Due Date.

    ℹ️ 1st Reminder Date = # days before Due Date when task actioner(s) will receive first email notification of this task assigned to them to complete. From this date onwards, the task will appear on each task actioner(s) My Summary page.

    ℹ️ 2nd Reminder Date = (smaller) # days before Due Date when task actioner(s) will receive a second email notification to remind them to complete the task assigned to them (if not already completed).

  9. Select the relevant escalation point position who will receive an email notification if the task is not completed by the due date in the Escalate To field. This can be left blank and will default to the Escalation Points of each Task assignee.

  10. Finally, select the task assignee(s)/actioner(s) in the Actioned By field.

  11. Review your Task setup and Save.

    • Related Articles

    • Ansarada GRC: How to set up a Task in the Registers module

      ✅ Applies to: Registers module Are you looking to set up a Task in the Registers module? Our system provides the capability to set up and send out tasks to automate processes involved in the management of Events or Items recorded in Registers. A task ...
    • Adding (Scheduling) the KRI Task

      Adding (Scheduling) the KRI Task The KRI’s purpose is to record each measure as required. So, unlike a Compliance Process which can have multiple Process Control tasks, the KRI only has one task, record the measurement. Hence, the Task tab only ...
    • Ansarada GRC: Turning off Obligation Tasks

      Are your users overwhelmed by the large volume of tasks being generated to review each new LexisNexis Obligation update? Our system provides the flexibility to turn off these tasks. By doing so, each Obligation (or Sub-Obligation) Owner and Notify ...
    • Drova GRC: What are Task Teams (TT)?

      Task Teams are used to allocate tasks to a group of Positions. Task Teams can be allocated to Process Controls, Risk Treatment and Event Tasks. For example, all Branch Managers could be members of the ‘Branch Managers’ Task Team and the team could be ...
    • Ansarada GRC: What is a Blind Task?

      What is a Blind Task? Blind Tasks are used to allocate Process Controls, Risk Treatments or Event Tasks to Positions that do not have Security Rights to the Parent Record (e.g. the Compliance Process, Risk, or Event). The details of a Blind Task’s ...