Skip to content
plugboard.appRequest a demo

Running the desk

Reports

/reports. Needs module.reports and report.view. Three tabs: Boards (where the page opens), Operational reports and Issue insights.

Boards are the school’s own dashboards, built from widgets that each ask one question of one dataset (tickets, repairs, devices, loans, time logged, people or changes). Anyone with report access keeps personal boards; staff who also hold report.manage can share a board with everyone. A shared board shares its questions only: each viewer’s figures come from their own access and campus scope.

  • New board starts from a layout (Service desk pulse, Repairs & fleet, Termly service review or Team effort) or a blank board. Nothing is saved until Save board.
  • The board’s range (7, 30 or 90 days, or your own dates) and Board filters apply to every widget whose data has that field. Filters you change without editing say Not saved with the board.
  • While editing, Add widget builds one by hand. Describe a widget, drawn only while the school’s AI is on, proposes widgets from what you say, previewed with real figures under your own access; nothing is added until you choose Add. See Describe a widget in AI settings.
  • Figure and gauge widgets one row high that sit next to each other join into one strip of figures, a cell each; while editing they stay apart to move and resize. A comparison is said in words, such as “Up 12% on the previous 30 days” or “Same as the previous day”.
  • A widget’s title carries a tooltip saying what it counts; a note its author wrote shows on the card. Its menu has Show records and Download CSV; while editing, it has Edit, Duplicate, the moves and Remove.
  • The board’s More menu has Wall screen, Print or save as PDF, Duplicate, Schedule this board and Delete board.

The tickets dataset includes Caused by problem and Known error, so a board can count incidents by the problem behind them, Support tier, so it can count tickets by the tier they are on, and Service, the service each ticket is filed under, with No service for the rest. A ticket filed under a service your campuses do not use is counted under Services you do not have access to, never named. First contact resolution (%) and Reopen rate (%) are measures on it, with the same rules as the reports below, so a board widget or a Home widget built from report data can show either, with the usual comparison. Questions about the figures go through Search or ask.

The changes dataset holds change records, under change.view: when each was raised, when its window starts and when it was reviewed or cancelled, its status, change type, risk, outcome and campus, and Success rate (%), the share of reviewed changes with an outcome that were successful.

Termly service review is the layout for the end-of-term review with school leadership. It starts with a 90-day range and reads, in order:

  • Tickets raised, SLA met and First contact resolution, the last two as gauges against goals of 90% and 70%.
  • Reopen rate, Change success rate, Satisfaction and Repair turnaround, against goals of 5% or less, 95%, 4.5 and 5 days or less.
  • Volume by type, SLA met by type, Top problems and Changes reviewed, by outcome.
  • Tickets by service and SLA met by service, leaving out tickets filed under no service. The Service review report adds each service’s downtime, changes and problems.

Change any of it once it is your board. Scheduled for the end of each term, it covers the term that just ended. Keep the reviews themselves, and the improvements they agree, in Improvements.

ReportShowsModule
Repair volume by typeRepairs in the period grouped by repair type, with costRepairs
Repair turnaroundHow long repairs took to close, by monthRepairs
Loan utilisationThe current loan fleet, issued against availableLoans
Satisfaction (CSAT)Ratings left on repairs and tickets closed in the periodSatisfaction
Ticket volume by typeTickets raised in the period by type, with open and closed countsTickets
SLA attainmentTickets resolved in the period that met or breached their target, by priority or by service, with the attainment for each ticket typeTickets
Fleet age & warrantyFleet age, warranty runway and spares on hand, by asset typeAsset lifecycle and stocktake
Cost per device per yearRepair cost per device per year in the period, by asset typeRepairs
Damage recoveryDamage charges raised against recovered in the period, by campusRepairs
Insurance claims registerClaims made under cover agreements in the period, by cohort: claims used against the limit, and cost avoidedRepairs
Ticket effortHours logged against tickets in the period, by technician and a second groupingTime tracking
Estimate vs actualTickets raised in the period that have an estimate, with the time logged and the differenceTime tracking
First response timeMedian and 90th percentile time to first response in the period, by priorityTickets
Backlog by ageOpen tickets right now, grouped by age, with the oldest in each groupTickets
Open problemsOpen problems right now, whether each is a known error, and the incidents each one caused, open and in all, by problem or by serviceTickets
Service reviewFor each service in the period: incidents and requests, hours down and uptime, service level targets met, the changes that named it and how they went, and its open problems and known errorsTickets
Change success rateChanges reviewed in the period, by type (normal, standard, emergency): successful, rolled back, failed or not recorded, with the success rateTickets
First contact resolutionIncidents and service requests resolved in the period, and the share fixed at the first contactTickets
Reopen rateIncidents and service requests resolved in the period, and the share that came back inside the school’s reopen windowTickets

Each takes a date range, except those about right now (Loan utilisation, Fleet age & warranty, Backlog by age and Open problems). Run it on screen, export to CSV, or schedule it.

Months read as words, such as Oct 2026, in report tables, charts, board legends and report emails. CSV files keep 2026-10, which sorts and imports cleanly. Repair turnaround groups repairs by the month in the school’s own timezone.

SLA attainment measures each ticket against its service’s own target first, then the target for its own type where the school set one in service level targets, then the target for any type, in the service’s support hours where it has them. Group by shows it by Priority or by Service: tickets filed under no service are No service, and a service your campuses do not use is counted under Other services, never named.

Open problems counts only the incidents you can see. For people with service.view it has a Service column, and Group by, Service counts open problems, known errors and incidents for each service. A problem counts for the service it is filed under and for the services of the incidents it caused, so a problem behind both Printing and Wi-Fi incidents counts for each. Problems under services you cannot see are counted under Services you do not have access to, and those under none under No service. See problems and known errors and changes.

Fleet age & warranty counts the fleet: every device except those retired, lost or on order. Spares are in it, with a Spare column and total for the spares on hand when the school has any. Devices On order are counted beside the fleet, not in its figures. Cost per device per year leaves devices on order out too. See spare and on order.

Service review is the end-of-term review for each of the school’s services: one row for each service you can see, the busiest first.

ColumnWhat it counts
Incidents, RequestsIncidents and service requests raised in the period and filed under the service
Hours down, UptimeFrom the monitors that count towards its status: down while every one of them with a result is down, over the time they were checked. Blank when no monitor counts or none had a result
Targets metOf its tickets resolved in the period with a target, how many were resolved inside it, on the service’s own targets and support hours, such as 100% of 3
Change successOf the changes that named it in the period and have been reviewed, how many were successful, such as 50% of 2
Open problems, Known errorsRight now, counted as Open problems counts them

The figures above the table add them up across the services, with problems counted once however many services they touch. With two or more services that have tickets, the chart compares their incidents and requests.

Service review in a service’s side column opens the report for that service alone, titled such as Wi-Fi service review, with its downtime and uptime among the figures. All services goes back to every service.

It is worked out from what you can see: tickets and changes inside your campuses and departments, and only the services your campuses use. It needs service.view as well as report.view, and the report list leaves it out without it.

Scheduled, it is worked out for each person it is sent to in the same way, so a recipient on one campus gets that campus’s review. The schedule’s owner and everyone it names need service.view: a schedule naming somebody without it is refused, a recipient who loses it is left off the next send, and a schedule whose owner loses it pauses. Schedule it for the end of each term to cover the term just ended.

Ask cannot run it, and nothing in it is sent to an AI model.

Both measure incidents and service requests resolved in the period. Problems and changes are the desk’s own records, so they are left out.

First contact resolution is the share fixed at the first contact: no more than one reply from the desk, never reopened and not raised again. A ticket logged during a phone call or at the counter and resolved there counts, as does one fixed with a single reply by email, Teams or the portal. Internal notes are not replies.

Reopen rate is the share that came back inside the school’s reopen window, 14 days unless the school set another. Its summary names the window. A ticket comes back when it is reopened, when its requester replies on the portal, or when a flow or a technician moves it out of resolved or closed. Returns on older tickets are taken from the audit log, which records every return but not whether it was inside the window.

Each report’s Group by shows the figure by Month (the default), Queue, Record type or Campus, with the tickets resolved, how many were fixed at first contact or reopened, and the rate. By month it charts as a line, and otherwise as bars. The same two measures are on the tickets dataset for report boards and Home widgets.

The staff Experience report (/reports/experience) is a separate page in the same navigation group, without a date range, export or schedule. Its frustration figures count staff tickets only. See sentiment and staff experience.

A report whose module is switched off shows as unavailable, and the server refuses to run it, so a scheduled email or a question in Ask cannot send data from a module your school has turned off.

A report you run shows its summary as one strip 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 name each series with its figure, and switch it on and off. Series are drawn in shades of one ink, with the series a chart singles out, such as late work, in the accent colour. A second line is dashed, so no series is told by colour alone.
  • 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.

The Issue insights tab looks at issues over a range you choose, or the last 7, 30 or 90 days. Its figures are one strip, each with the change on the previous period in words, such as “Up 12% on the previous 30 days”, “Up 4” from zero, or “Same”. Under them are 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.

For people with service.view, Issues by service lists each service’s issues in the period against the period before, how many are still open, and its open problems and known errors, so the termly review can say that Printing had 41 issues, with 2 open problems and 1 known error. Each service opens its page. A service with no issues in either period and no open problem is left out, and issues under services you cannot see are counted in a line under the table, never named.

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.

Repair volume by type is your budget report. It says what is breaking and what it costs.

Repair turnaround is your service report. If the average is climbing, either volume is up or something is stuck. Cross-check against overdue work.

Loan utilisation tells you whether the pool is the right size. A pool permanently at ninety percent issued is too small.

Satisfaction is only meaningful with enough responses. See CSAT.

Schedule a report to be emailed on a recurring basis: a weekly summary to the ICT manager, a termly one to the business manager. Scheduled emails, under the operational reports, lists them; a board is scheduled from its More menu with Schedule this board. Both need report.manage.

How often offers Every day, Weekdays, Every week and Every month, at a time in the school’s own timezone, and End of each term when the school has term dates. Nothing is emailed more than once a day. A fixed report covers the days you set under Covers the last; a board uses its own range.

End of each term sends on the last day of each term in the school’s term dates, at the time you choose. The editor says when the next one is, such as Next on 18 Dec 2026, or that no more term dates are set. It covers the term, from its first day:

  • a fixed report runs over the term, in place of a number of days;
  • a board’s widgets use the term in place of the board’s own range, and a widget with its own range keeps it.

Send me a test now covers the term so far. A schedule for the end of each term needs term dates to be saved, and one that comes due with none set is skipped and says why in its Delivery history. Pair it with the Termly service review board, sent to the principal or the business manager, and the Service review report beside it.

Delivery uses your email connector and runs in the background. The report.scheduled message carries it, and its wording is editable.

Every report exports to CSV. Column headers match the on-screen ones.

UseWhen
HomeWhat is happening right now
AskA question somebody just asked
ReportsA recurring review, or something finance needs
PermissionAllows
report.viewRun a report and export it, keep personal boards, and read the improvement register
report.manageCreate and manage schedules, share boards with everyone, and keep the improvement register and service reviews

The changes dataset also needs change.view. The Service review, the Service column and grouping by service in Open problems, and Issues by service also need service.view.