Statuses & fields
Settings, Statuses & fields (/admin/workflow), gated by the
workflow.manage permission. Open repairs in the header goes to the
repair queue.
None of these are hard-coded. Statuses, priorities, coverages, repair types, borrower groups and the parts catalogue are all your school’s own data. So is whether several repair features exist at all.
The page is in tabs: Repair lifecycle, Coverage & types, Parts catalogue, Borrower groups, Fields, Ticket mappings and Sorting criteria.
Changes to the lists (names, colours, order, Available, and rows you add) wait in a bar at the foot of the page until you choose Save statuses & fields, and a tab holding changes that are not saved yet is marked with a dot. The switches under Fields, the parts and the school fields save on their own.
Do this before anyone lodges a real repair. The answer the school gave in setup to How are student devices provided? has already set some of it (see fitted to how devices are provided).
Repair lifecycle
Section titled “Repair lifecycle”Repair statuses
Section titled “Repair statuses”The ten stages a repair moves through. The set is fixed: you cannot add or delete a status, but each one’s name, colour and place in the list are yours, and unticking Available takes a status out of the desk’s choices. Drag a row to reorder it, or use the up and down arrow keys.
With the default names: Pending, Booked in, In progress, At vendor, Awaiting parts, Parts received, Awaiting approval, Awaiting payment, Ready for collection and Closed. A light desk, set up for devices families own or devices the school shares, offers four of them under the names Open, With vendor, Ready and Closed.
On a light desk the list shows only the four statuses in use, here and under Ticket mappings, the same as the repair pages. Show the 6 not in use lists the others, to offer one again; Hide the 6 not in use folds them away. Reordering the rows on show leaves the hidden ones where they are. A desk with all ten statuses lists them all.
Rename them to whatever your desk already says out loud. If your team says “on the bench”, call it that.
Priorities
Section titled “Priorities”The urgency levels. Each has a name, a colour and a place in the list, which sets the order they appear in. Add one with Add priority.
Service level targets are set per priority, so if you want response and resolution clocks, define priorities first and set targets second.
Coverage & types
Section titled “Coverage & types”Coverages
Section titled “Coverages”Who pays, listed as Coverage categories. The shipped set is warranty and insurance; add Chargeable or whatever else your school uses.
Coverage is how cost analytics splits spending, which is the number your business manager asks for. It is not shown to a student booking a repair: they choose the fault in plain words, and Plugboard works the coverage out from the repair type.
Repair types
Section titled “Repair types”What kind of repair it is, and which coverage it carries: a cracked screen under insurance, a battery under warranty. Each type can also name a ticket category.
At the kiosk and in the student portal the default types appear in a student’s words, such as Cracked or damaged screen or Water or a drink got on it. A type you add appears under the name you give it, so word it the way a fifteen-year-old would recognise. “Damaged display” rather than “LCD assembly failure”.
Parts and prices
Section titled “Parts and prices”Parts catalogue is what technicians pick from when they record a repair outcome, with what each part usually costs and how many are on hand.
Kept per kind of device, because an iPad screen and a laptop screen are not the same part and pretending otherwise makes the numbers useless: laptops, Chromebooks, desktops, iPads, tablets, iPhones, other mobile devices, printers and other. A part’s device kind is fixed once it exists.
You start with a list priced for a school Mac fleet rather than an empty one. Every row is yours to rename, re-price, hide or delete.
Each part has a name, a device kind, a usual price, Stock on hand and
Reorder at. A part at or below its reorder level is marked Needs reorder
and raises a sticky notice (part.reorder); a level of zero turns the flag off.
Search the catalogue, or show only the parts that need reordering or the hidden
ones.
How pricing behaves
Section titled “How pricing behaves”- Ticking the parts that were replaced adds their prices up into the repair’s cost.
- Typing over the total wins. A part sourced in a hurry, or supplied free under warranty, means the sum is wrong and what you type is right.
- A price change only affects repairs recorded from then on. Repairs keep the parts and costs they recorded, so last term’s numbers do not move when you update a supplier price.
- Hiding a part keeps it on the repairs that used it but takes it off the picker. Untick Available for new repairs when a part is discontinued: the history stays intact and nobody selects it again.
Borrower groups
Section titled “Borrower groups”Categories a loan pool serves, such as Students, Staff or Senior School. A loan group names the borrower groups that can borrow from it; a group with none chosen lends to anyone.
Fields
Section titled “Fields”Repair fields
Section titled “Repair fields”The switches that turn individual repair features on and off. Off means the field or control does not appear anywhere, rather than appearing and being ignored. Each switch saves as soon as you change it.
| Switch | What it controls |
|---|---|
| Priorities | Whether staff can set a priority on repairs |
| Assign technicians | Whether a technician can be assigned to a repair |
| Staff loans | Whether loans show the staff and student distinction |
| Police report number | Capture a police report number on insurance jobs |
| Budget code | Capture a budget or cost code on repairs |
| Vendor repair | Whether a repair can be booked out to an external repairer. Offered on a repair only while a repair-vendor connector (CompNow or Edunet) is enabled |
| Cover agreements | Claim repairs under the school’s insurance with its repair vendor. See cover agreements |
| Damage charges | Propose and approve charges to families for damage. See damage charges |
A small primary school with two technicians usually turns off priorities and assignment, because both add a click to every job and neither changes what happens. A large school with a bench and a queue wants both.
Cover agreements and Damage charges off are enforced, not only hidden. Their routes answer as a switched-off module does, a repair’s cover is worked out without any agreement, and Charge approvals and Cover agreements leave the menu.
Photo of the damage
Section titled “Photo of the damage”When a repair is lodged at a kiosk or in the student
portal: Off (the default) or Optional: students may add one photo. With
it on, booking a repair offers Add a photo. Only people who can see the
repair see the photo; families never do. It saves as soon as you choose, and
each change is recorded in the audit log (submission.photoSettingUpdate). See
attachments and the lodgement photo.
School fields
Section titled “School fields”Your school’s own fields on devices, people and loans: text, long text, number, date, yes or no, choice, several choices, or a staff member. Each has a name, help shown under it in forms, whether staff must fill it in, who can see it (everyone who can see the record, or managers only) and whether it is shared with the school’s AI, which is off until you turn it on. Up to 30 fields in use and 60 in all for each kind of record. Fields are archived, never deleted, and their values come back with them. Student records take no free text.
Ticket mappings
Section titled “Ticket mappings”Ticket statuses are the ticket’s own status list: their names, colours and order are yours, as for repairs. With the default names they are Open, In progress, Waiting on requester, Waiting on supplier, Resolved and Closed. The service level clock follows their meanings rather than the words you use: Waiting on requester and Waiting on supplier stop it, and resolved and closed end it. The portal shows those two to the person who asked as Waiting for your reply and Waiting on a supplier.
Repair statuses in a ticket system pairs each repair status with one of the ticket statuses.
Sorting criteria
Section titled “Sorting criteria”For each option in a list (categories, subcategories, priorities, departments, repair types and catalogue items) write a sentence saying when it fits, and up to five example phrases. These are what the school’s AI reads when it sorts new work; see AI settings. Try a sample runs a sample sentence against the description and examples on screen, saved or not, as one metered AI call, and changes nothing. The tab is there whether AI is on or off, and Edit priority criteria and Edit repair type criteria on the first two tabs open it at that list.
Where these changes show up
Section titled “Where these changes show up”Everything on this page flows through to:
- The kiosk and student portal, where repair types appear when somebody books a repair.
- The repair queue, where statuses and priorities are the tabs and filters.
- Cost analytics, which groups by type and coverage.
- Service level targets, which are set per priority.
- Flows, whose conditions match on type, priority, coverage and the rest of a record’s fields.
- Reports.
Changing things later
Section titled “Changing things later”Renaming is safe. A label change updates everywhere, and history keeps its meaning because records reference the key instead of the words.
Deleting is refused for anything a record still uses: a priority on a repair, a coverage on a repair type, a repair type on a repair, a borrower group on a loan. Untick Available instead. It stops appearing in pickers but keeps working on the records that already use it. Statuses cannot be deleted at all.