[Internal] Reports: Understanding Them

[Internal] Reports: Understanding Them

Introduction

This document provides information about understanding Reports.

Understanding Reports

The Reports page:

Key points to understanding Reports:
  1. The count in the Usage Report equals the sum of the count in the Completion Report and the count from the Non-Completion Report .
  2. The Usage and Non-Completion Reports are based of the user's last login.
  3. The Completion Report is based off the final test pass date.
  4. "Last ## Days" does not include today's date.
  5. Custom time frame can be set up to include today's date.
  6. Because Reports are pulled using different date ranges, it is possible for a user to show up on one report and not the other. For example, suppose a user completed the orientation last week, but logged back in the same day a report was being pulled to review the orientation information. If a Report was pulled for the last 30 days, this user would show up on the Completion Report but not the Usage Report . The reason this is so is because the Usage Report is based off the last login date. So, if the user logged in the same day the report was generated by “Last ## Days”, they would not appear on this report. However, if the Usage Report was pulled using a Custom time frame which included today’s date, then the user would be listed.


    • Related Articles

    • [Internal] Support Guide Index

      Introduction This index provides an easy way to jump to any internal support guide without having to navigate to find it . Admin Intake Screen: Setting up a Pre-filled Email Address Organizational Unit: Create a New One Reports: Understanding Them ...

    • [Internal] Child Handles: Naming Best Practices

      Introduction This document provides best practices for naming child handles (sub org units). The term child handles is for internal use only. When speaking with clients, refer to them as sub org units. When creating a child handle, use the following ...

    • [Internal] Working Desk Tickets: Best Practices

      Introduction This document provides best practices for working desk tickets. Desk tickets are automatically assigned to the Client’s Customer Care Representative. Working a Ticket Each rep should read through their tickets periodically throughout ...

    • [Internal] Turnaround Times: Best Practices for Setting Expectations

      Introduction This document provides best practices for setting client expectations by communicating turnaround times. It is crucial, when working an issue or project for a client, to provide them with a turnaround time. This sets their expectation ...

    • [Internal] Decision PathFork: Resizing

      Introduction Decision PathForks expand the width of the page, sometimes under the placeholder image. When this happens, a client may want all of the PathFork options to be the same width. This guide provides step-by-step instructions for resizing a ...