Skip to main content

Try on a Student

Updated this week

Overview

The Try on a Student feature lets you test draft audits against real student enrollment data before publishing. This validation step ensures your audit requirements function correctly with actual student records.

Some of the benefits of using this feature include:

  • Confirms requirements correctly identify intended courses

  • Reveals unexpected behaviors before publishing

  • Verifies audit flexibility across different student scenarios

  • Identifies issues early in development, saving significant time

  • Builds confidence in audit accuracy before publishing

Note: Try on a student is only available for students you have permission to view.

Finding and Trying on Students

  1. Navigate to your institution's Stellic login page and sign in.

  2. Select the Programs tab from the left menu.

  3. Locate the program containing the audit version you want to test.

  4. Open the Audit version dropdown menu and select your audit version.

  5. Click Try on a student to open a small student search bar.

  6. Enter a student name and click Test.

  7. Review how your audit evaluates the student's actual enrollment data.

Understanding the Results

The feature applies the student's actual enrollment history to your draft audit, showing how their enrollments will match the audit requirements.

Important Note: Try on a Student validates your audit requirements against the student’s course data. Using Try on a Student is an important validation step prior to publishing audits. After publishing audits, you should expect to do full testing of student audit progress against the entire student record.

Best Practices

  • Use Try on a Student with 3-5 students representing different academic scenarios

  • Specifically check:

    • Requirements that should be capturing courses but aren't

    • Requirements picking up unexpected courses

    • Edge cases specific to your program requirements, such as students with transfer courses

  • Document unexpected behaviors for troubleshooting

  • Make iterative improvements based on results

  • Use this feature throughout the audit development cycle

Did this answer your question?