Skip to content
plugboard.appRequest a demo

Service quality

Plugboard and ITIL 4

Plugboard’s service desk is aligned with ITIL® 4 practices for incidents, service requests, problems and changes, with priority set from impact and urgency, service level targets on your school’s working calendar and per service, a knowledge base and asset register, supplier records, the school’s services with what each depends on, security incidents kept to a Security department, and an improvement register with the service reviews held with school leadership.

ITIL is guidance for organisations, not a test a product passes, so no tool is “ITIL compliant”. This page shows what Plugboard does for each practice, and what it leaves out.

The wording we use

“Aligned with ITIL 4 practices”

It means the desk’s records and rules follow those practices. It is our own description: PeopleCert has not assessed Plugboard, and we make no other ITIL claim.

The four an ITIL-trained team checks first

  • Incident management
  • Service request management
  • Problem management
  • Change enablement

What Plugboard does for each practice, in plain words, with the page that explains it.

ITIL 4 practiceIn Plugboard
Incident managementFaults are tickets of kind Incident, with priority set from impact and urgency. A fault reported again stays an incident, marked as possibly recurring so you can link it to a problem. An outage many people report becomes a major incident: one ticket owns it, the reports hang under it, and the school sees one notice. Escalate moves a ticket through the school’s support tiers, first line to third line or its own names, with a reason, and Waiting on supplier pauses the clock while a vendor has the next move. See tickets and major incidents.
Service request managementRequests such as software, access and shared mailboxes are tickets of kind Service request, from the portal, kiosks, email or Microsoft Teams, with service level targets of their own when you set them. See self-service portals.
Problem managementProblem records hold the root cause, the workaround and the known-error state. Incidents link to them with Was caused by, and each linked incident shows the workaround. Resolving a problem offers to resolve its open incidents. See problems and known errors.
Change enablementChange records are normal, standard or emergency, with a risk, impact, implementation and rollback plans, a change window, approval, freeze periods and a review that records the outcome. A change in a freeze waits until a change approver records why it cannot wait, and the change calendar shows windows and freezes by month. Nobody approves their own change unless your school allows it, and then the approval reads Self-approved. Changes name the services they affect, with each service’s owner and support hours and whether the window falls inside them, and the service reads Planned work while the change is under way. A major incident, a monitor that goes down or a service lists the changes made in the 72 hours before it. See changes.
Service deskOne queue for the portal, kiosks, email, Microsoft Teams, phone calls and walk-ups. See finding your way around.
Service level managementResponse and resolution targets by priority and by record type, and targets per service, on your working calendar and term dates. A service sets its own targets where it needs them and its support hours run the clock for its tickets; the desk’s apply where it sets none. Every ticket with a target reads On track, Due soon, Overdue, Clock paused or Met. See service levels and a service’s service levels.
Service catalogue managementBusiness and supporting services, such as Wi-Fi, Compass and RADIUS, each with an owner, support hours, campuses and a status in plain words, watched by the school’s monitors. A service lists the monitors, network devices, devices, printers and other services it depends on and the contracts and suppliers that support it, each shown only to staff who may open that record. A person can set a service’s status with a message for up to 24 hours; otherwise the monitors that count decide it. A ticket is filed under the one service it names, or by a person, and reports count tickets by service. Services the school marks public are on its status page, and each service has a review date. See services.
Knowledge managementKnowledge base articles on your public help centre, and the desk’s own runbooks, bound to the devices and categories they are about. See knowledge base.
IT asset managementA device register kept current from your device management, with owners, loans, repairs, stocktake and disposals, beside a register of software contracts. See devices.
Monitoring and event managementUptime monitors on the services the school relies on, raising alerts by severity, and network devices matched to the tickets about them. A monitor that goes down names the changes that touch it, and the services that depend on it under Used by. See monitors.
Measurement and reportingBuilt-in reports, report boards and Home widgets, including service level attainment by record type or by service, first contact resolution, reopen rate, open problems with the incidents each caused, and change success rate. The Termly service review board puts them in one pack, and the Service review reports each service’s tickets, downtime, targets met, changes and problems. See reports.
Continual improvementAn improvement register: each idea with an owner, a review date, its expected benefit and its result, from Proposed to Done or Not doing, linked to the problems, tickets and changes behind it. See improvements and service reviews.
Supplier managementSupplier records with contacts, support hours and the supplier’s own response and resolve targets, linked from the devices, software contracts, repairs and tickets they hold or are waiting on. Beside them, software contracts and their renewals, cover agreements with insurers and repair vendors, and repairs booked out to a vendor. See suppliers.
Information security managementSecurity incident is a built-in category, and words such as “phishing”, “hacked” or “ransomware” choose it. From Ticket settings a school creates a Security department, or chooses one it has, and security incidents then go there: only its members and administrators see them. A technician outside Security who raises or recategorises one hands it over and does not see it again. Every hand-off is in the audit log, and the Security desk shows how many tickets were handed to it in the last 30 days. The desk’s own controls are an MFA policy, the audit log, privileged elevation and department scoping that denies by default. See security incidents and the security model.
Relationship managementPartly Service reviews with school leadership, recorded with who attended and the actions agreed, and the Termly service review emailed on the last day of each term. Satisfaction ratings when a repair closes, and a staff experience report. Stakeholder maps and engagement plans are not modelled. See improvements and service reviews and satisfaction ratings.
Service configuration managementPartly An asset register with record linking: devices, people, tickets, loans and repairs are connected, and a service lists the records it depends on directly, each showing the service under Used by. Relationships between other records are not modelled. See devices and services.

The wifi in the science block keeps dropping. The report stays an incident with its own service level clock, the desk records the cause as a problem, and the fix goes through a change that somebody else approves.

Sam raised the problem from incident #4. Rachel approved the change: by default, nobody approves their own.

Plugboard does not model these. If your school runs them, they stay in the tools and documents you keep them in.

  • Relationships between other records
  • Information security beyond incidents
  • Timing suppliers against their targets
  • Release management
  • Deployment management
  • Service continuity management
  • Capacity and performance management
  • Service financial management
  • Availability management

Service configuration. Devices, network devices and printers are an asset register with record linking, and a service lists the records it depends on directly or by a fleet rule. There are no relationships between other records, such as a switch and the access points behind it, or a virtual machine and its host, so the impact of a failure is shown one step away, under Used by.

Information security beyond incidents. There is no security risk register or control testing. A self-hosted school without the restricted database role cannot have private departments, so its security incidents stay on the ICT desk.

Supplier targets are shown, not timed. A supplier’s response and resolution targets appear on the supplier and on the tickets that wait on it, but no clock measures the supplier against them, and nothing reports a supplier’s attainment.

Plugboard records changes, backs itself up and reports costs, but it does not offer release, deployment, service continuity, capacity and performance, service financial or availability management to a school.

ITIL® is a registered trademark of the PeopleCert group.