Support Document for Revenue by Casual Traveller Report
Report Name:
Revenue by Casual Traveller Report
Overview:
The Revenue by Casual Traveller Report provides detailed information about the revenue generated by casual travellers within a specified date range. This report includes data such as the number of trips taken by each casual traveller and the total revenue generated from these trips. It is essential for understanding the contribution of casual travellers to the overall revenue and for managing transportation services effectively.
Report Type:
Financial Report
Key Information Provided:
- Traveller's first and last name
- Student number
- Number of trips taken
- Total revenue generated
How to Generate the Report/Filters:
Steps:
- Access your school's RollCall Admin Console.
- Select "Reports" from the navigation bar.
- Select "Revenue by Casual Traveller Report" from the dropdown or the report icons.
- Apply relevant filters such as date range, bus, and student.
- Click "Run Report."
- 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.
- Bus: Select "ALL" to include all buses or specify individual buses.
- Student: Select "ALL" to include all students or specify individual students.
- 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 casual traveller. Example: John.
- Last Name: The last name of the casual traveller. Example: Doe.
- Student Number: The unique identifier for the student. Example: 123456.
- Number of Trips: The total number of trips taken by the casual traveller. Example: 5.
- Total Revenue: The total revenue generated from the trips taken by the casual traveller. Example: $50.00.
Total Row:
- Total: Aggregates the total number of trips and total revenue for all casual travellers within the specified date range. Example: 0 trips, $0.0 revenue.
Key Metrics:
- Number of Trips: Tracks the total number of trips taken by casual travellers.
- Total Revenue: Monitors the total revenue generated from casual travellers.
- Average Revenue per Trip: Provides insight into the average revenue generated per trip by casual travellers.
Common Use Cases:
- Revenue Tracking: Monitoring the revenue generated by casual travellers to understand their contribution to overall revenue.
- Service Planning: Planning and adjusting transportation services based on the demand from casual travellers.
- Financial Reporting: Including casual traveller revenue in financial reports and analyses.
Tips for Interpretation:
- Identify High Revenue Travellers: Focus on casual travellers who generate the most revenue to understand their travel patterns and preferences.
- Monitor Trip Frequency: Track the frequency of trips taken by casual travellers to identify trends and make data-driven decisions.
- Analyse Revenue Trends: Use the report to analyse revenue trends from casual travellers over time and adjust services accordingly.
Related Reports:
- Overdue Balance Report: Provides detailed information on students with overdue balances.
- Revenue By Student Report: Offers insights into revenue generated by each student.
- Customer Statement Report: Summarises all financial transactions and balances for each customer.
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 Revenue by Casual Traveller 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
Feedback sent
We appreciate your effort and will try to fix the article