TOP OF HELP DOCUMENTATION

Last Updated 9/18/23

REPORTER Help Documentation for Compliance Admins

Setup Fields for Requirements

Requirements must be created by REPORTER Support or (if under EHPS) through your Compliance Liaison. Prior to having a requirement created, the training coordinator(s) should decide how they will manage the requirement, including how those required will be identified and maintained, how often training will be needed, and when completion is initially due.

The following fields are required:

  1. Requirement Details
  1. Prefix
  2. Requirement Name
  3. Department
  4. Requirement Description
  1. Due Date Configuration
  1. Completion Name
  2. Description
  3. Completion Type
  4. Completion Window // Completion Date
  1. Required Courses, including the following for each:
  1. ID of Course
  2. How often course needs to be retaken
  3. When should previous completions of this course count towards this requirement?        
  4. Should approved external course submissions be considered previous course completions for this requirement?        
  5. How many of the required courses must be completed (Ex. There are 2 options but only 1 needs to be completed)
  1. Unity IDs of those to be listed as Compliance Admins
  2. Communication & Contact Details
  1. Supervisors Options - Yes or No:
  1. Allow supervisors and participant liaisons to assign participants to this requirement
  2. Allow supervisors and participant liaisons to unassign participants from this requirement
  3. Allow supervisors and participant liaisons to adjust participant due dates
  1. Email Options - Yes or No:
  1. Copy supervisor on initial assignment email
  2. Copy supervisor via email when user registers for a course as part of this requirement
  1. Notify Supervisors with Out of Compliance warnings?
  2. Notify compliance contact via email if users are out of compliance
  3. Send compliance warning emails to participants?
  1. Assignment Message, included in assignment email and due date reminders, as seen here.
  2. Compliance Contact Name, Email, and Phone

Requirement Details

Identifying Information like Name, Department, Description

Identifying information about the requirement will be needed for setup, though not all information is displayed in the same way to those assigned, most can be seen by users in various areas of the system per the details below.

Field Required

About

Display

Department

What department has ‘ownership’ of maintaining this requirement; identified either by Organizational Unit Code (OUC) or name. Typically corresponds with the department offering the required courses.

Impacts the ‘Prefix’ that is included with the Name of the Requirement in emails. Ex. OIT-Data Security Training

Name of the requirement

Should identify what is being supported by tracking the required courses. In most cases, this will be the same as the course name, but it does not need to be.

Shown in every part of the system that references the requirement, including reports, participant dashboard, email notifications, and menu pages

Requirement Description

Should describe why the requirement is being tracked and who is subject to it (descriptions of the courses should be included in course setup, not in the requirement)

Only shown when a user clicks a ‘view details’ option from their dashboard, reports, or notifications (this field will not be included in any emails to users)

Due Date Configuration

Based on the time someone is assigned, what is their due date -- either a specific date or an interval

Required Courses

List the courses that correspond to the compliance requirement, and their associated enforcement details

For each selected course:

  • Course Refresher Details: Define how often the course will need to be retaken to remain in compliance. This is done for each course listed and can be either:
  • Users only need to complete the course once
  • Users need to take this course on a periodic basis (yearly, once every 4 years, etc)
  • Once - but users need to take another refresher course on a periodic basis
  • Handling previous completions: Each course will include a setting to dictate when previous completions of the course should count towards this requirement. Meaning, if you assign some as required to complete a course that they have already completed, should they be marked “In Compliance”, or is there a point at which the previous completion should not be counted?
  • The options for this setting are:
  • Always - any completion of the indicated courses satisfies the requirement
  • Only Count Completions that occur after a specific date (you select the date)
  • Only Count Completions that occur after the user is assigned
  • Only Count Completions that occur within X days of being assigned (you define the ‘X’)
  • Number Required: Identifying the courses the users will need to take and/or choose from to meet the requirements, and how many of those identified are required to be completed to remain in compliance.

Each requirement has a specific course or set of courses associated to it to identify which course completions count towards compliance. There are specific setup fields for the requirement that correspond to setting Due Dates, refresher dates, and the handling of completion credit.

Before having a requirement created, the training coordinators need to decide how they will manage the requirement, including how those required will be identified and maintained, how often will training be needed, and when is completion due by. If you have not defined these areas, please review the Compliance Requirement Maintenance Guide before submitting details for the creation of your requirement.

If training is required to be repeated on a periodic basis, a decision needs to be made regarding the maintenance of the compliance tracking. Otherwise, if training is assigned and completed once, you will only need to plan for managing those who never complete training as they will remain ‘out of compliance’ until the requirement is archived or they are unassigned.

Method 1

Create a new requirement each cycle

Method 2

Reuse the course and requirement from year to year

  • Can use the same course or a different course, but would need new instances if using the same course
  • Can use ‘from when completions count’ options to control credit for prior completions
  • Typically not recommended if a process has been established to regularly maintain the list of who is required, and the next iteration of training is always ready for those who approach their ‘refresh’ due date

  • A new instance would be created each year
  • The current year’s instance should be available at the same time as the next year’s instance
  • Requirement has Refresher settings for a yearly due date
  • Should not be used if:
  • Next cycle’s due date has not been decided
  • Next cycle’s instance is not available yet
  • Those who fail to complete training should be tracked separately from those who had a job change impacting what they are required to complete
  • Settings Guide:
  • The requirement name can be generic
  • The due date should be an interval (not a specific date)
  • The refresher will either be a specified interval (1 year) or a specific date on a yearly basis (July 15 every # year)

Once plans for long term management of the requirement have been established, the setup needs for the requirement can be confirmed based on the answers to questions included in the submission form.

There are three primary pieces of information that we are looking for:

  1. What are the required courses (Includes the fields: Required Courses, Number Required)
  2. What should the initial due date be if the person assigned has never completed the course? (Captured with Due Date Settings)
  3. How should the due date be updated based on an assigned user’s completion of the required course(s)? (Set using Refresher Settings, and From when completions count

Submission Form Fields:

Submission Form Field

Questions to consider when determining field value

Setting Details

 

What course or courses are required? (Enter Course IDs)

What courses meet this requirement?

Does everyone have to take the same course?

Are there multiple that count towards the requirement?

Do people need to take multiple courses to meet this requirement?

During setup, we can select the specific courses that should associate to the requirement. Then we can specify how many of the courses listed have to be required.

Ex. I can list OIT-User and OIT-Intro but only make 1 required, so assigned users can complete either to be in compliance.

Are the same users assigned from year-to-year?

Response Options:

  • No - users a re-identified at the start of each cycle
  • Yes - the list of assigned users is regularly maintained

How will the people who should be assigned be identified? How do you know they need to do training, and who will physically 'Assign' the person?

How do you know if someone is no longer required and if they should be unassigned? Who should identify and unassign them?

Is it something that needs to happen once and then get maintained, or do you need to repeat the identification process on a regular (annual) basis?

If training has to be completed by the same people every cycle, and the list is regularly maintained by removing those no longer required and adding anyone newly required -- then, you most likely want to use the same requirement for each training cycle.

Alternatively, if there is a specific point in the year when everyone who meets X criteria should be assigned ((or if the plans for maintenance have not been established)), you most likely should plan to have a new requirement created every year. At their point, the old requirement should be closed out and the new one created (please work with REPORTER Support to do this, reporter_support@ncsu.edu)

When is the initial assignment due? Should be a certain amount of time from the assignment (ex. 30 day after) or a specific date.

When people first get assigned training, what should their due date be? Consider whether you will count previous completions towards the requirement or not.

If someone either has never taken the course, or doesn't have a completion that counts towards the course, what due date should they get?

If this is 'one time' requirement, should people with previous completion just be marked In Compliance, with no due date?

A specific date can be set, or we can set an "interval" so that person assigned is due a certain # of units after the date they are assigned (ex. 30 days)

When should previous completions of the course(s) count towards this requirement?

Response Options:
A). Always - any completion of the indicated courses satisfies the requirement
B). Only Count Completions that occur
after a specific date
C). Only Count Completions that occur after the user is assigned
D). Only Count Completions that occurred within X days prior to being assigned
E). Multiple Courses are Required -- Will specify DIFFERENT response for each below.

When someone is assigned, does it matter if they person has already completed a course that is required?

Do we want to count all completions towards the course, or do one of the following apply?:

  • Only completions that happened after a certain date meet the requirement
  • Only prior completions that happened within a certain number of days of being assigned
  • Only completions that happen after the person is assigned

If there is more than one course required, is the answer the same for every course?

If you choose to 'disqualify' any completions, related records will be ignored when a newly assigned user's due date is determined. The value is also excluded from showing as the 'Most Recent Completion', essentially allowing the completion to be ignored for a specific requirement.

If a completion does count towards the requirement, that completion date is used along with the Refresher settings to set the due date for those assigned. More on refresher settings in the next line (below).

 

How often does this course or courses need to be completed?

Response Options:

  • Users only need to complete the course once
  • Users need to take this course on a periodic basis (yearly, once every 4 years, etc)

If users have to retake the course, how often do they need to retake which course? Include dates and/or interval value when relevant

 

How often does this course or courses need to be completed?

If someone has completed the course in the past, what should their due date be (for each course)?

The Refresher Settings for a requirement allow due date changes to automatically be applied when a course is completed. This can include changing the due date to be empty, so they have met the requirement and no further action is needed.

Regardless of whether someone is being assigned the first time or not, if they have a previous completion that counts, the "Refresher Settings" will always be used to determine the due date. If they do not get credit for any prior completions, the initial due date settings and 'Date Assigned' will be used.

Unity IDs of those to be listed as Compliance Admins

Those who have access to assign the requirement and view reports

  • Those listed will be able to assign, unassigned, and view reports
  •  In the request form, this field is labeled "List the Unity IDs of all users that should have Compliance Admin access to this requirement"
  • Never shown to participants

Communication & Contact Details

Information included in automatic emails associated with assigning. Includes settings for when to copy or notify supervisors and admins. There are a number of Yes/No settings in requirement setup that correspond with either what level of access Supervisors should have for the requirement or the sending of automated email

Supervisor-Related Settings

Through their 'My Team' page in REPORTER, Supervisors have access to interact with employees that report to them, including access to Assign training, Unassign Training, and Update Due Dates for assigned training. All of these options can be enabled or disabled on a per-requirement basis.

Setting / Option

Description

Notes

Allow supervisors and participant liaisons to assign participants to this requirement

By assigning the training, they are identifying the employee is required to complete the related courses. If disabled, only Compliance Admins will be able to assign the requirement.

Recommendation is to enable this option if Supervisors have authority to identify who needs training.

Allow supervisors and participant liaisons to unassign participants from this requirement

By unassigning the requirement, they are removing the previously identified person from the list of those required to complete the related courses. If disabled, only Compliance Admins can remove training assignments.

Recommendation is to disable this option if those required is determined by the training owners.

Allow supervisors and participant liaisons to adjust participant due dates

This allows the due date the employee has been given for training to be changed. This would typically only be done if extenuating circumstances merit an extension

Recommendation is to disable this option if the due date is designated by the training owners.

SUPERVISOR MESSAGE SUGGESTIONS:

If unassign is allowed:

  • If an employee is no longer required to complete this training, you can unassign them using these instructions or reach out to the training contact included above to request they be unassigned.

If unassign is not allowed:

  • If an assigned employee is no longer required to complete this training, please reach out to the training contact included above to request they be unassigned.

If unassign is managed on a periodic basis:

Separated and Inactive Employees are removed within 2 weeks of their termination date.

Template for Weekly Message to Supervisors:

Employees listed as reporting to you are Out of Compliance for the following training requirement:

{%requirementName%}

Training Contact:  {%complianceContactName%}, {%complianceContactEmail%} {%complianceContactPhone%}

To see which employees need to complete training, please login to REPORTER and review the Compliance Warnings for your Employees (see instructions at go.ncsu.edu/supervisorhelp).

  • If the employee list on your ‘My Team’ tab is incorrect, please refresh your list as demonstrated here.
  • If this does not resolve the issue, please contact your departmental HR representative to have the related employee record(s) corrected in the Peoplesoft HR system. Once the record is corrected in HR, REPORTER will update within 24 hours.

{%supervisorMessage%}


Additional resources for Supervisors using REPORTER are available on the
 support.reporter.ncsu.edu page "Supervisor and HR Reps (NCSU)".


Training owners may continue to send you this weekly notice as the NC State Supervisors of an Out of Compliance employee.  Supervisors are identified using the 'Reports to' field of job records from the PeopleSoft HR system and cannot be changed in REPORTER manually.

Communication Options

Setting / Option

Description

Notes

Do you want to copy participant's supervisors on the initial assignment email?

When assigned, users are sent an email with their due date and information about the required training. If this setting is enabled, if a person assigned has a Supervisor, that Supervisor will be CC'd on the assignment email to the user.

Depending on how the user is assigned, the email template used will either be the "Assignment Email" or the "Assign and Register Email", as seen at https://support.reporter.ncsu.edu/home/get-help/help-docs/compliance-admins/compliance-emails/

Notify supervisor via email when user registers for a course as part of this requirement?

If someone is assigned as required to complete training and they have a Supervisor, when they register for any instance of the course(s) that meet the requirement, this option will copy (CC) the registrant's Supervisor on the registration confirmation email.

The registration email does not specifically reference required training, so if it needs to, those details should be entered in the instance setup field 'registration confirmation email notes'.

Send compliance warning to participants?

If enabled, Compliance warnings are emailed to users as they approach their due date, and if they have passed their due date. These are sent daily to users if they are within 30 days of, 14 days of, 1 day of, or passed their due date.

These emails are sent on a specific schedule and details of the emails can be seen at: https://support.reporter.ncsu.edu/home/get-help/help-docs/compliance-admins/compliance-emails/#warnings

Notify Supervisors with Out of Compliance warnings?

If enabled, an email is sent once a week to the Supervisors of those who are out of compliance to prompt them to check their reports in REPORTER. This is a general email that only identifies which requirement the Supervisor has out of compliance employee(s) under.

Notify compliance contact via email if users are out of compliance

If enabled, an email is sent once a week to whatever email address is listed as the primary compliance contact so long as anyone assigned is Out of Compliance

Contact Details

Compliance Contact

Typically a generic name and email account is used but a specific person can also be indicated if appropriate.

This information will be provided in all compliance emails sent to assigned users. Questions about the Requirement that are received by REPORTER Support will also be directed to this contact.

Assignment Message

Should be a short message to clarify to users why they are being assigned/are required to complete training. In the request form, this field is labeled "Please enter the assignment message that will be included in the assignment email and out compliance warnings:"

Included in the email sent when someone is assigned a requirement. Also included if compliance warnings emails are enabled -- see email template details here.