Reports
/reports. Needs module.reports.
Operational reporting with CSV export and scheduled email delivery.
The reports
Section titled “The reports”| Report | Shows | Module |
|---|---|---|
| Repair volume by type | Submissions in the period grouped by repair type, with cost | Submissions |
| Repair turnaround | How long repairs took to close, by month | Submissions |
| Loan utilisation | The current loan fleet, issued against available | Loans |
| Satisfaction (CSAT) | Ratings left on repairs and tickets closed in the period | Satisfaction |
| Ticket volume by type | Tickets raised in the period by type, with open and closed counts | Tickets |
| SLA attainment | Tickets resolved in the period that met or breached their target, by priority | Tickets |
| Fleet age & warranty | The active fleet’s age and warranty runway, by asset type | Asset lifecycle |
| Cost per device per year | Repair cost per device per year in the period, by asset type | Submissions |
| Damage recovery | Damage charges raised against recovered in the period, by site | Submissions |
| Ticket effort | Hours logged against tickets in the period, by technician and a second grouping | Time tracking |
| Estimate vs actual | Tickets raised in the period that have an estimate, with the time logged and the difference | Time tracking |
| First response time | Median and 90th percentile time to first response in the period, by priority | Tickets |
| Backlog by age | Open tickets right now, grouped by age, with the oldest in each group | Tickets |
Each takes a date range. Run it on screen, export to CSV, or schedule it.
A report whose module is switched off shows as unavailable. From 0.17.1 the server also refuses to run it, for every report, so a scheduled email or an assistant request cannot send data from a module your school has turned off.
Charts
Section titled “Charts”From 0.18.1, a report you run shows its summary as a row of figures, then a chart suited to its rows, then the table. Most reports chart as bars; Repair turnaround is a line by month, Loan utilisation a donut by status, and Backlog by age a column per age group. A report with more than twelve rows charts the twelve largest and says so; the table lists every row.
- Hover a bar, point or slice for its exact values. Or focus the chart and use the arrow keys, Home and End; Escape hides the values again. Screen readers hear the same values.
- Legend keys switch a series on and off.
- Table headers sort, numbers as numbers. Sorting is for reading only: the CSV export keeps the order the server returned.
The charts read only what the report returns, so a chart never shows a figure the table does not.
Issue insights
Section titled “Issue insights”The Issue insights tab looks at issues over a range you choose, or the last 7, 30 or 90 days. It shows the period’s figures against the previous period, a daily line with the previous period dashed behind it, the most common issues, and devices with repeat issues. The tables carry inline bars so the largest rows stand out.
Time reports
Section titled “Time reports”Ticket effort and Estimate vs actual read the time logged on tickets, and appear only while time tracking is on. Quick time without a ticket is not included.
Ticket effort shows technician, a second column, entries and hours. Its Group by list sets the second column: Technician & category (the default), Work type, Campus, Department or Requester. The CSV export uses the same grouping.
Estimate vs actual lists unmerged tickets raised in the period that have an estimate, either their own or their category’s default. For each it shows the estimate, the time logged whenever it was logged, and the variance in hours and as a percentage.
Both apply the school’s report rounding (none, 6 or 15 minutes, set in ticket settings). Each entry is rounded up before it is added, so ten 2-minute entries at 15-minute rounding count as two and a half hours. When rounding is on, Ticket effort’s summary says so. The stored minutes are never changed.
Which one answers which question
Section titled “Which one answers which question”Repair volume by type is your budget report. It says what is breaking and what it costs, which is the input to next year’s device decision as much as to this year’s spending.
Repair turnaround is your service report. If the average is climbing, either volume is up or something is stuck. Cross-check against SLA breaches.
Loan utilisation tells you whether the pool is the right size. A pool permanently at ninety percent issued is too small. You notice as a student standing there without a device, not as a number on a screen.
Satisfaction is only meaningful with enough responses. See CSAT.
Scheduling
Section titled “Scheduling”Schedule a report to be emailed on a recurring basis: a weekly summary to the ICT manager, a termly one to the business manager.
Delivery uses your email connector and runs in the
background. The report.scheduled message carries it, and its wording is
editable.
Scheduling is the feature worth using. A report somebody has to remember to run gets run for about two months. One that arrives on a Monday is one that gets read.
CSV export
Section titled “CSV export”Every report exports to CSV, which is what finance will ask for. Column headers match the on-screen ones.
Reports against the dashboard and the assistant
Section titled “Reports against the dashboard and the assistant”Three ways to look at the same data, for three different situations.
| Use | When |
|---|---|
| Dashboard | Right now, at a glance |
| Assistant | A question somebody just asked |
| Reports | A recurring review, or something finance needs |
Permissions
Section titled “Permissions”| Permission | Allows |
|---|---|
report.view |
Run a report and export it |
report.manage |
Create and manage schedules |
Related
Section titled “Related”- Costs for interactive cost exploration with charts.
- Service levels for the targets turnaround is measured against.