Driver Initiated - Bad Behaviour or No Card Report

Modified on Fri, 20 Sep at 3:58 PM

Support Document for Driver Initiated - Bad Behaviour or No Card Report

Report Name:

Driver Initiated - Bad Behaviour or No Card Report

Overview:

The Driver Initiated - Bad Behaviour or No Card Report provides a comprehensive log of incidents reported by bus drivers where students either displayed bad behaviour or failed to present a valid bus card. This report is crucial for monitoring student conduct during transportation and taking appropriate disciplinary actions.

Report Type:

Incident Report

Key Information Provided:

  • Date of the incident
  • Student's first and last name
  • Student number
  • Bus involved
  • Organisation

How to Generate the Report/Filters:

Steps:

  1. Access your school's RollCall Admin Console.
  2. Select "Reports" from the navigation bar.
  3. Select "Driver Initiated - Bad Behaviour or No Card Report" from the dropdown or the report icons.
  4. Apply relevant filters such as date range and organisation.
  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. This helps in narrowing down the data to a specific period.
  • Organisation: Select the organisation or school to which the report pertains. Ensures the data is relevant to your institution.

Understanding the Report:

Columns:

  • First Name: The first name of the student involved in the incident. Example: Jane.
  • Last Name: The last name of the student involved in the incident. Example: Doe.
  • Student Number: The unique identifier for the student. Example: 123456.
  • Date: The date when the incident occurred. Example: 05/07/2024.
  • Bus: The bus number involved in the incident. Example: Bus 3.
  • Event Group: Indicates whether the event occurred in the AM or PM. Example: AM.
  • Incident Type: Specifies whether the incident was due to bad behaviour or no card. Example: Bad Behaviour.
  • Details: Additional details about the incident provided by the driver. Example: Student was disruptive during the trip.

Key Metrics:

  • Incident Frequency: Tracks the number of incidents reported. Useful for identifying trends and areas needing attention.
  • Student Involvement: Monitors which students are frequently involved in incidents. Helps in addressing recurring issues with specific students.
  • Bus and Route Impact: Evaluates which buses or routes have higher incidents. Useful for targeted interventions.

Common Use Cases:

  • Behaviour Monitoring: Ensuring that student behaviour on buses is monitored and managed effectively.
  • Disciplinary Actions: Keeping a record of incidents for potential disciplinary actions and discussions with parents or guardians.
  • Policy Enforcement: Ensuring students adhere to school policies, including carrying valid bus cards.

Tips for Interpretation:

  • Identify Patterns: Look for recurring incidents with the same students or on specific routes and buses.
  • Assess Severity: Evaluate the severity of incidents to prioritize actions.
  • Engage Stakeholders: Share findings with relevant stakeholders, such as teachers, parents, and school administrators, for comprehensive management.

Related Reports:

  • Exception Details Report: Provides detailed information on various exceptions, including behaviour-related incidents.
  • Student Behaviour Report: Tracks and monitors student behaviour across different contexts within the school environment.
  • Bus Utilisation Report: Offers insights into bus usage and occupancy, helping to correlate incidents with bus capacity.

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 Driver Initiated - Bad Behaviour or No Card 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