Repairs
/repairs, and /repairs/<id> for one. Needs module.repairs.
A repair is somebody’s device that needs work. It carries the device, the
fault, the person, its status and what it cost, and it is numbered R-1, R-2
and so on. In the API, the events and the audit log a repair is called a
submission (submission.created).
Fitted to how devices are provided
Section titled “Fitted to how devices are provided”The Setup wizard asks How are student devices provided? under Repairs. The answer decides how much of the repair module the desk uses. Lodging, loaners and each device’s repair history are the same for every answer.
| Answer | Cover agreements and damage charges | Vendor booking | Statuses |
|---|---|---|---|
| School-owned 1:1, including levy or fee programs | On | On | All ten |
| Families buy a set device through a vendor portal | Off | On | Four |
| Families bring any device that meets a spec | Off | Off | Four |
| Shared school devices only | Off | Off | Four |
| Mixed or not sure | On | On | All ten |
The answer is applied once, when it is first given or changed. Each part stays a switch in Settings, Statuses & fields, so a school can turn any of it on or off later. A desk that never answered keeps every option and all ten statuses. For the two answers where families bring a device or devices are shared, the shared My day layout on Home counts Loans issued in place of Ready for collection.
Switching an option off is enforced, not only hidden: the charge, cover agreement and vendor booking routes refuse while their option is off, the same way a switched-off module does.
The light desk
Section titled “The light desk”With four statuses the desk works in Open, With vendor, Ready and Closed. These are four of the ten statuses, switched on under those names; the other six are switched off. On a repair the four statuses are the steps across the top, and choosing one moves the repair there. An open repair’s next step is Mark ready for collection, because there is no bench stage in between.
The queue
Section titled “The queue”Repairs opens on Open, which is every status but Closed. The tabs are Open, Pending, With vendor, Ready and Closed, each with its count. A light desk has no Pending tab, because Open is its first status.
Above the list:
- Search by person, serial or repair number.
- Priority and Assigned to (Anyone, Me, Someone, Nobody yet), when the school uses priorities and assigns technicians.
- Coverage.
- Filter, which holds Describe a filter while the school’s AI is on and you may use Ask. Type a sentence such as “unassigned repairs” and it becomes the list’s own filters, removed the usual way.
- Display groups the queue by status, technician, repair type or coverage, opens a repair beside the list instead of on its own page, and prints labels for the page.
Each row shows the device and its warranty, the client, the fault with where it stands, priority, technician and when it was lodged, with the repair’s next step as a button. Right-click a row for Open in new tab, Copy link, Print label, the next step and Assign to me.
On a wide screen a column beside the list shows Open repairs by stage and Needs a look: Past their SLA, No technician, With a loan out and the oldest open repair. Every line there is a filter on the queue.
The queue arrives fifty at a time, newest first, with the total above the list. Open is worked out by the server, so the count is your whole open queue rather than the rows on screen.
Where repairs come from
Section titled “Where repairs come from”| Source | How |
|---|---|
| The kiosk and the student portal | A student or staff member books it themselves, with an optional photo of the damage |
| The desk | New repair on the queue, or on a device’s page |
| Ask | “Create a damaged display repair for Riley Brooks with a loan” |
| The API | Your own integration |
A repair booked at the kiosk or in the portal arrives with a sticky toast, so it is not missed.
New repair takes the person, repair type, serial, priority, a loan device and an intake photo, with the reason as notes, and the police report number and budget code where the school uses them. Once the person and type are chosen it shows the likely outcome.
The lifecycle
Section titled “The lifecycle”A repair moves through statuses and carries a priority. The status set is fixed, but each status’s name, colour and order are yours to define, as are the priorities. With the default names:
- Pending. Newly lodged, waiting to be picked up.
- Booked in, then In progress. Booked in, then a technician is working on it.
- At vendor, Awaiting parts, Parts received, Awaiting approval or Awaiting payment. Waiting on something outside the bench.
- Ready for collection. Fixed and waiting for collection.
- Closed. Handed back.
The progress strip
Section titled “The progress strip”On a desk with all ten statuses, a strip across the top of every repair folds them into six stages that read the same on every repair:
| Stage | Statuses it covers, by their default names |
|---|---|
| Received | Pending |
| Booked | Booked in |
| In repair | In progress, At vendor, Awaiting parts, Parts received |
| Awaiting client | Awaiting approval, Awaiting payment |
| Ready | Ready for collection |
| Collected | Closed |
The current stage shows the exact status where it says more than the stage, and how long the repair has been in that stage. Dates come only from recorded status changes: a stage nobody recorded entering shows no date rather than a guess. Awaiting client is only needed for some repairs, so a repair that went straight past it shows it as skipped.
Working one
Section titled “Working one”The repair’s title is the first line of its reason. In the header:
- Print label, for people who can print labels.
- Move to…, on a desk with all ten statuses: every status under the stage it belongs to, and Close repair. A light desk moves through its four steps instead.
- More actions: Replace device, Edit details (serial, reason, priority, police report number, budget code), Copy tracking link and Delete repair. Deleting says first what it takes with it, and is refused while a damage charge that is not waived stands against the repair.
The column down the side holds the facts: technician, priority, fault, coverage (with the device’s warranty, AppleCare+ and insurance dates, and any cover agreement that excluded the repair or whose claim limit is reached), the linked ticket, police report and budget code. Below them sit the client, with a link to their person page, Supplier, In this repair (the device and any loaner lent meanwhile) and the client’s other repairs.
Supplier shows the supplier the repair is with: the vendor of the cover agreement it is claimed under, the repair vendor it was lodged with, or the device’s own supplier, in that order, and says which. It gives a contact, their hours, the response and resolve times they promise and the school’s account number with them. It is left out when no supplier is known.
The main column reads in order:
- The next step, in its own words with the button that takes it: Start the repair with Start work, Waiting for parts with Parts received, Review the vendor update, Collect the temporary loan with Open the loan and Close repair, or, on a closed repair, Record outcome when it has none. A closed repair also offers Re-open here.
- Likely outcome, when the school’s history supports it.
- Notes and history: status changes, vendor updates and the rest, newest first, back to when it was lodged.
- Replacement, when the device is being replaced rather than repaired.
- Outcome and parts.
- Damage charge, where the school charges families.
- Vendor and communications, where a vendor has a part in the repair.
- Attachments, when the repair has any files.
- Device at lodgement, the MDM facts captured when it was lodged.
- Flows, when a flow offered something on this repair or ran about it.
Assign
Section titled “Assign”Assign to me is on the queue row’s right-click menu, for people with
repair.update. A flow can assign a technician when a
repair is lodged.
If your desk does not work this way, turn Assign technicians off on Statuses & fields.
Change status and priority
Section titled “Change status and priority”As the work progresses. Each change is recorded in the history. Priority is in Edit details.
Marking a repair Ready for collection tells the client it is ready to collect. A school can change that notice through the built-in flow When a repair is ready for collection on Flows. A status a vendor connector worked out moves the repair but sends nothing, because nobody has seen the device. While a repair is ready, Vendor and communications also offers Send collection email and, for a student, Email tutor.
Issue a loan
Section titled “Issue a loan”In this repair offers Assign a loan (needs repair.update and
loan.view): pick an available device to lend to the client while theirs is
away. A loaner already lent can be swapped (Swap loaner) or unassigned
(Unassign, with Undo). Plugboard can pick an available device from the right
loan group automatically when somebody books a
repair and asks for a loaner.
The loan and the repair stay linked, so when the repair closes you know which loaner to collect back. The loan number also appears on the person’s tracking page and in the parent portal.
Likely outcome
Section titled “Likely outcome”What the school’s own closed repairs like this one came to: the share of each result, the median time, the usual cost, the parts most often replaced and who pays. Every number is statistics over the school’s closed repairs with a recorded outcome, matched by device model, repair type and coverage. The only AI on the card is the repair type read from the fault description and a sentence written from the numbers, each marked Suggested and each dismissable.
On a repair, the card shows only when it comes from at least eight similar closed repairs at the school. In New repair the card is there from the start, labelled General estimate until the school has eight similar repairs, and it can suggest a loaner and a vendor job to start with the repair.
Record an outcome and cost
Section titled “Record an outcome and cost”Choose Record outcome on the repair. The same form is used everywhere an outcome is asked for, and it takes:
| Field | |
|---|---|
| Result | Optional. Repaired, Replaced, No fault found or Beyond repair. Choose it again to clear it |
| Parts replaced or repaired | From your own parts catalogue |
| Repair cost | Adds itself up from the parts; you can type over it |
| Covered by | The coverage the repair falls under |
| Notes |
A summary line at the foot of the form says what you are about to save. The result then shows beside Outcome and parts on the repair, with Edit outcome and Reset outcome.
Type over the total when the job cost something else. A part sourced in a hurry, or supplied free under warranty, means the sum is wrong. What you type wins, and the parts keep the prices they were saved with, so last term’s numbers do not move when you update a supplier price.
Costs feed cost analytics.
Outcomes for several closed repairs
Section titled “Outcomes for several closed repairs”A repair closed without an outcome leaves billing incomplete. While Repairs and
Costs are both on, a banner at the top of Repairs and of
Home says how many, such as 3 closed repairs need an
outcome. The banner needs repair.view; Add outcomes on it needs
repair.update and opens the same form for all of them: the repairs waiting
are listed on the left and the form is on the right. Save and next records
one and moves to the next, and Skip leaves one for later. On a phone you
step through them without the list. The banner goes once the last outcome is in.
Book a vendor repair
Section titled “Book a vendor repair”Book vendor repair, in Vendor and communications, raises the job with the school’s repair vendor through its connector, CompNow or Edunet. The confirm says what the vendor gets: the serial, the fault and the client’s contact details, with the policy number when the repair is claimed under a cover agreement. Only the vendor can cancel the job. A lost or stolen device is not sent to the vendor; the same button requests a replacement instead.
Once booked, the vendor’s reference and status show on the repair, and you can send the vendor a note or a file.
It is offered only while Vendor repair is on in Statuses & fields and a repair-vendor connector is enabled.
Attachments and the lodgement photo
Section titled “Attachments and the lodgement photo”Attachments lists the repair’s files, with the photo from the lodgement first, as a thumbnail. The photo is there when the school asks for one at lodging (Photo of the damage) and the student added it.
Every file can be downloaded. People with repair.update can delete a file,
which is recorded in the repair’s history and the audit log
(submission.attachmentDelete), and, once the repair is booked with a vendor,
Send to the repair company, one file at a time. Attachments are read only
through the repair, by people with repair.view: never in the tracking link,
the student or parent portal, or emails, and never by an AI feature.
Close repair (needs repair.close) when the device is returned. Closing
returns any loaner still linked to the repair, and invites a satisfaction
rating on the tracking page.
Coverage
Section titled “Coverage”Each repair type carries a coverage: warranty, insurance or chargeable, or whatever you have defined in Statuses & fields.
The person booking a repair at the kiosk or in the portal sees the fault in plain words, such as Cracked or damaged screen, and does not choose a coverage; Plugboard works it out from the type. On the repair, the coverage is in the facts down the side. It is also how cost analytics breaks spending down.
Where the school holds insurance with its repair vendor, a cover agreement decides whether a family pays anything. Where a family is being asked to pay, see damage charges: one person proposes the charge and a second approves it.
Notifications and tracking
Section titled “Notifications and tracking”When a repair is lodged, the person gets a tracking link and email updates as it moves on. They can follow progress at any time on the tracking page, without an account and without asking.
Automation
Section titled “Automation”A flow that starts when a repair is lodged can assign a cracked screen to a particular technician, set its priority, or notify the desk. See flows.
Realtime
Section titled “Realtime”The desk gets live updates. When a colleague changes a repair, lists and detail pages refresh and a toast appears, so two technicians do not both start the same job.
Permissions
Section titled “Permissions”| Permission | Allows |
|---|---|
repair.view | See the queue, open a repair and read its attachments |
repair.create | Lodge one |
repair.update | Change status and priority, assign, record the outcome and cost, book the vendor, manage attachments and the loan on a repair |
repair.close | Close or delete a repair |
Repairs and tickets
Section titled “Repairs and tickets”Repairs are about a device. Tickets are about everything else. Both are independent modules and either can be switched off.