Reporting
To support the transition to CERCLE, a dedicated reporting subproject team assembled to evaluate the reports used by CERC staff and clients and recommended a future reporting platform. The team reviewed existing reports and data fields with the goal to reduce redundancy and consolidate information into more comprehensive, streamlined reports. As events transition to CERCLE, the way you access reports, the tools you use, and the available data will change. Events in CERCLE will follow updated reporting processes, while those remaining in Momentus will continue using the existing reporting structure for now.
CERCLE Events Short-Term Reporting Solution
As we prepare for the July 1 launch, the project team has adopted a short-term reporting solution to support go-live while continuing to develop a long-term reporting platform. This interim approach, expected to be in place through approximately September, relies on CSIS (Continuing Studies Information System) and CERCLE to deliver the most commonly used data fields. In the short term, the following report areas will be available:
-
Event Reporting
-
Roster Reporting
-
Promo Code Reporting
Continuing Studies Information System (CSIS)
While many program staff already have access to CSIS and are familiar with its navigation, some may be new to the system. If you are new to CSIS and need some help navigating reports, we recommend visiting this helpful CSIS Reports KB article (graciously created by Paul Miller, Interpro). You will find instructions and screenshots to guide you through accessing the CSIS reports listed below.
Need CSIS access?
If you don’t yet have a CSIS user account, please contact your program manager to begin the process. This CSIS Directory KB article has instructions for authorized CSIS users to add new users to CSIS. If you are not sure who to contact in your department, you can consult the Lifelong Learning (L3) Department Contact list as a starting point.
Short-Term Reporting Details
EVENT REPORTING
-
Primary Tool: Course Summary FY report in CSIS
-
Purpose: Provides registration and service revenue, program category, enrollment, and cost information at the individual instance level.
-
Included Fields:
-
Curriculum (program unique identifier, shared across instances)
-
Instance (program unique identifier, unique across instances)
-
Program Name
-
Status (Approved, Cancelled, etc)
-
Category (Highest level category, e.g., “Languages”)
-
Subcategory (Subcategory, e.g., “Spanish”)
-
Instance Type (Public, Private)
-
Delivery Type 1 (Modality)
-
Delivery Type 2
-
Start Date / End Date
-
Registration Revenue (Total revenue received from registrations)
-
Service Revenue (Total revenue received from service orders)
-
Paid (Total amount paid for a given event)
-
Unpaid (Total amount outstanding for a given event)
-
Subtotal (Total amount expected for a given event, pre-tax)
-
Total (Total amount expected for a given event, post-tax)
-
Direct Costs (Amount of costs attributed to the program, e.g., instructor fees, development, special marketing, etc)
-
Net Revenue (Gross-direct costs)
-
Enrollment (Number of active learners)
-
New Instance (First-time or a repeat offering)
-
Developer
-
Fiscal Year (FY)
-
Evaluation Overall Rating
-
-
Fields not Available:
-
Capacity (Currently available on the Enrollment Revenue report in CSIS)
-
Waitlist (The number of people on the waitlist for an event)
-
ROSTER REPORTING
Participant Data Report
-
Primary Tool: Participant Data in CSIS
-
Purpose: The Participant Data report is an aggregated report listing registrants across multiple events, fiscal years, and other groupings. It is best for broader insights and not day-to-day operational use.
-
Included Fields:
-
Individual ID (Learner unique identifier in CSIS)
-
First Name
-
Last Name
-
Email Address
-
Title
-
Organization Name (Learner place of employment)
-
Organization Parent
-
City
-
State/Province
-
Postal Code
-
Curriculum Number (Program unique identifier, shared across instances)
-
Instance Name
-
Instance Number (Program unique identifier, unique across instances)
-
Start Date
-
Fiscal Year
-
Developer
-
-
Fields not Available:
-
Address 1 (Registrant street address provided at registration)
-
Address 2 (Registrant street address provided at registration, e.g., unit numbers)
-
Country (Registrant country provided at registration)
-
Order Number (Unique identifying order number, multiple registrations could be on a single order)
-
Order Date (Registration submission date)
-
Credentials (Learner credentials)
-
End Date (Date the program ends)
-
Ordered Total (Amount due for registration, prior to any discounts)
-
Individual Instance Roster Report
-
Primary Tool: Individual Instance Roster in CSIS
-
Purpose: The Individual Instance Roster includes detailed registrant contact information for a specific course instance, found at the bottom of the actual course instance page.
-
Included Fields:
-
First Name / Last Name
-
Organization Name (Learner place of employment)
-
Degree (Learner credentials)
-
Address 1
-
Address 2
-
City
-
State
-
Postal Code
-
Country
-
Email
-
Phone Number
-
Instance Number
-
Start Date / End Date
-
Credit Hours
-
-
Fields not Available:
-
Order Date (expected addition mid-July)
-
Special Accommodations (expected addition mid-July)
-
Title
-
Custom Event Questions
-
PROMO CODE REPORTING
-
Primary Tool: CERCLE
-
Purpose: This report is designed to show which registrants used a promo code, the program they registered for, the discount amount applied, and the final amount paid.
-
Delivery: The CERCLE team can access and export this report to share with clients as needed. This interim solution will be used sparingly until the long-term reporting solution is in place.
REGISTRATION FORM RESPONSES
-
Primary Tool: CERCLE
-
Purpose: Captures responses to custom registration questions and accommodation requests.
-
Delivery: The CERCLE team can access and export this report to share with clients as needed. This interim solution will be used sparingly until the long-term reporting solution is in place.
Long-Term Reporting Solution
The Reporting Team evaluated multiple platform options to identify a widely accessible, sustainable, and user-friendly reporting system for noncredit registration. A formal proposal prioritizing key reporting needs and outlining two long-term platform options has been submitted to leadership. The executive team has reviewed the proposal and is currently engaged in negotiations with the preferred vendor. Once approved, the Reporting Team looks forward to beginning implementation and expanding the reporting resources available to staff and clients.