Student Code History Report

Modified on Fri, 20 Sep at 4:00 PM

Support Document for Student Code History Report

Report Name:

Student Code History Report

Overview:

The Student Code History Report provides a comprehensive record of changes in student codes over a specified date range. This report includes details such as the student's name, student number, old student code, and new student code. It is essential for tracking changes in student identifiers and ensuring accurate and up-to-date student records.

Report Type:

Student Information Report

Key Information Provided:

  • Date of the code change
  • Student's name
  • Student number
  • Old student code
  • New student code

How to Generate the Report/Filters:

Steps:

  1. Access your school's RollCall Admin Console.
  2. Select "Reports" from the navigation bar.
  3. Select "Student Code History Report" from the dropdown or the report icons.
  4. Apply relevant filters such as date range, student name, and student number.
  5. Click "Run Report."
  6. Use the on-screen report tool or export the report to PDF or Excel.

Filter Information:

  • From Date/To Date: Specify the date range for which you need the report. For this report, the date range is from 05/07/2024 to 05/07/2024.
  • Student Name: Select "ALL" to include all students or specify individual student names.
  • Student Number: Select "ALL" to include all student numbers or specify individual student numbers.
  • Organisation: Select the organisation or school to which the report pertains. Ensures the data is relevant to your institution.

Understanding the Report:

Columns:

  • Date: The date when the student code change occurred. Example: 05/07/2024.
  • Name: The name of the student. Example: John Doe.
  • Student Number: The unique identifier for the student. Example: 123456.
  • Old Student Code: The previous student code. Example: STU001.
  • New Student Code: The updated student code. Example: STU002.

Key Metrics:

  • Code Changes: Tracks the number of student code changes within the specified date range.
  • Student Identification: Ensures accurate and up-to-date student identifiers are maintained.

Common Use Cases:

  • Record Keeping: Maintaining accurate records of student code changes for administrative purposes.
  • Audit Trail: Providing an audit trail of changes to student identifiers for compliance and verification.
  • Data Integrity: Ensuring the integrity of student data by tracking and verifying code changes.

Tips for Interpretation:

  • Verify Code Changes: Ensure that all code changes are accurately recorded and reflect the correct student information.
  • Monitor Frequency: Track the frequency of code changes to identify any unusual patterns or potential issues.
  • Analyse Impact: Assess the impact of code changes on other systems and processes to ensure seamless updates.

Related Reports:

  • Student Report: Provides comprehensive information about each student within a specified date range.
  • Parent Report: Offers detailed information about parents or guardians associated with students.
  • Customer Statement Report: Summarises all financial transactions and balances for each customer (parent/guardian).

Troubleshooting:

  • Missing Data: Ensure that the report is generated for the correct date range and filters are applied properly.
  • Incorrect Filters: Double-check the filters to ensure they align with your reporting needs.
  • Data Discrepancies: Verify data entries in the RollCall system for accuracy if discrepancies are found in the report.

Additional Resources:

(To be filled in by the support team)

This support document should help you understand and effectively utilise the Student Code History Report in your RollCall system. If you encounter any issues or have further questions, please contact our support team.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article