Student Learning & Licensure Release Notes for March 17, 2026

Updates to Rubric Extracts

This release revamps the Rubric Assessment Data Extract in Student Learning & Licensure, offering granular control over your data. Administrators can now customize extracts with smarter filters, new data columns, and a refined CSV format optimized for analysis.

• Following filters are now available, allowing users to extract data filtered by:
  • Organizations / Programs – now also includes Programs, supporting hierarchical selection for better alignment with institutional structures.
  • Course – filter by course (course code).
  • Term – limit extract to one or more terms.
  • Rubric – choose from rubrics that will result in extractable assessments.
  • Activities – filter by activity
  • Students– filter to only those students who have relevant submissions or get an assessment history for a specific student

• All filters now cascade, so each selection (e.g., Organization + Course + Term) narrows down the options in subsequent filters.
• Student, Rubric, and Activity filters now only display items that will generate records in the CSV, reducing confusion and “empty” extracts:
  • Activities without rubric assessments or outside the selected scope will not appear as selectable options.
  • Rubrics and students are similarly restricted to those that have data matching the current filter set.
• New Columns
  • Mean
  • Max Total Score
  • Score Received by Student
• Single-Row per Assessment
  • All rubric elements for a single assessment are now exported on one row per assessment per student, rather than a row for each rubric element.
  • For each rubric element, the following columns are repeated within that row:
    1. Element Description
    2. Performance Level Description
    3. Performance Level Score
    4. Performance Level Score Max
    5. Rubric Element Comments
  • Some columns in some rows may be blank, depending on the combination of rubrics, filters, and available data.
• Removed Column
  • The “Number of Elements for Evaluation” column has been removed, as its value is no longer meaningful with the new single-row, multi-element layout.
• Additional Checkboxes: Admins now have more granular control over how much context to include in each extract
  • Student Details – include additional student-level information such as demographic data.
  • Course Details – include additional course-level context.
  • Revision Assessment History – include revision/resubmission history

Ability to add Admin Components in Licensure Plans

After this release, Administrators will be able to create requirements in a Licensure Plan that are fulfilled entirely through administrator input, rather than student submissions. This makes it easier to track internal checks such as GPA verification, field experience verification, or other program‑managed milestones.

Key Features:

• New “Admin Completion” condition for Standard requirements
  • While creating a Standard requirement, admins can now choose Admin Completion as the condition.
  • This marks the requirement as one that will be completed and maintained by administrators, not by students.
• Flexible data collection methods for admin requirements
  For each requirement with Admin Completion, admins can select one or more data collection methods:
  • Document upload – upload up to 10 files for collecting supporting documentation
  • Small text field – capture concise values or notes
  • Multi‑select checkbox – track one or more options

Data Entry and Review for Admin Components

• From a student’s Licensure Plan, clicking an admin‑managed requirement opens a dedicated panel for data entry.
• Save progress, Approve, and Reject actions are available
• Admins can view and update previously saved data for all admin components:
• Safe navigation and save behavior
  • Clicking Save progress (or similar actions such as Accept/Reject where applicable) saves the data for all admin components while keeping the admin on the same page.
  • If changes have been made and the admin attempts to navigate away (Close, Done, Next Student) without saving, a discard confirmation appears to prevent accidental data loss.

Managing Admin Data Collection Methods

• Locking configuration after data exists
  • Once a data collection method has been used (i.e., data has been submitted for at least one student):
    • It can no longer be edited or deleted.
    • A banner clearly informs users that the method cannot be edited or deleted and that the only available action is to archive it.
      • Data from archived requirements are included in extracts
      • Archived requirements can later be unarchived.
  • This protects data integrity across cohorts and reporting.

History Tracking and Auditability

To support accountability, auditing, and context over time:

• Activity history for Admin and Student Completion requirements
  • Each Admin Completion (and Student Completion) requirement maintains an activity history of changes.
  • The history records:
    • Status updates (e.g., Met / Not Met).
    • Component actions, including who submitted or updated data.
    • Component labels to clarify which part of the requirement changed (e.g., <File Upload Label> submitted by <Evaluator Name>).
• Activity card and full history view
  • The most recent four changes appear in an Activity card for quick reference.
  • A “View Entire Activity History” action opens a side flyout with the full change history.

Reporting and Exports

We have extended reporting so that these admin‑managed data points can be used in downstream analysis.

• CSV exports include Admin Completion data
  • All data fields entered for Admin Completion requirements are included in CSV extracts.
  • Requirement status for Admin Completion (“Met”, “Not Met”, etc.) is also captured in these exports.
  • Files uploaded via admin document‑upload components are available in the exported zip in folders organized by student (e.g., <Student Name>_<Student PID>).
• Archived methods in exports
  • Data collection methods that have been archived are still represented in CSV exports.
  • Archived methods are clearly labeled (e.g., <Document Upload> – Archived), so programs can distinguish between active and archived requirements while still analyzing longitudinal data.

• Student visibility
  • Admin‑managed requirements set with Admin Completion won't appear in students’ Licensure Plans yet. They will be added in a future release.

Ability for students and reviewers to choose a desired frequency of time log email notifications

With this release students, time log reviewers, and instructors can choose how often they receive time log email notifications. Users can choose between receiving the regular time log notification emails OR daily or weekly summaries of the time log notification emails.

They can choose the desired setting from the My Profile area of their SL&L user account.