Skip to content
Plugboard docs

Cover agreements

Admin, Cover agreements (listed under Service delivery). Requires workflow.manage.

Some schools have an insurance or repair-vendor agreement that covers device damage. Recording it here means a repair the agreement covers never asks a family to approve a charge or make a payment — the school’s own dashboard shows what it cost instead.

What a cover agreement holds

Section titled “What a cover agreement holds”

Each agreement is a card, colour-coded by whether it is in force, set up in four groups:

  • Policy — who the agreement is with and its dates.
  • Who and what it covers — which devices and, where relevant, which people.
  • Damage — a covered/excluded checklist drawn from the school’s own repair types, so “cracked screen” only appears if the school actually has a repair type for it.
  • Excess and limits — what the family still owes, if anything, and any cap on devices or claims.

A strip above the list shows agreements in force, claims made this period, devices at their limit and cost avoided.

Once an agreement has claims

Section titled “Once an agreement has claims”

An agreement that has been used offers Deactivate, never Delete — the claims already recorded against it stay in the register.

Where claims show up

Section titled “Where claims show up”

The claims register is the cover-claims report on the Reports page. What a family sees on the parent portal is templated from the rules recorded here: either “Covered by the school’s insurance, nothing to pay” or the excess amount only.

Section titled “Related”