Skip to content
plugboard.appRequest a demo

Running the desk

Improvements and service reviews

/reports/improvements, under Knowledge & reports. Needs the Reports module and report.view; adding and moving records needs report.manage.

Improvements keeps two lists on two tabs:

  • Register: the ideas that would make the desk better, each with an owner, a date to review it by and the benefit it should bring. The tab’s count is the ideas still open.
  • Service reviews: the reviews held with the principal, the business manager or whoever the desk answers to, with who attended, what was discussed and the actions agreed.

Both link to the problems, tickets and changes behind them, so a review can say what was agreed and the register shows what came of it.

The open ideas are one list, the furthest along first and then by the date to review them by:

ColumnWhat it shows
ImprovementThe title, with the first line of its expected benefit under it
OwnerWho is carrying it
Review byThe date to look at it again. Past that date it reads Overdue, in red
StatusProposed, Approved or In progress

Ideas that are Done or marked Not doing fold away under Done and not doing.

Add an improvement asks for:

Field
ImprovementA few words, such as Spare chargers in every computer lab
OwnerWho carries it, or nobody yet
Review byWhen to look at it again
CampusShown when the school has more than one campus. Leave it as Whole school otherwise
Expected benefitWhat gets better, and how you will know
DetailsAnything else

The idea starts as Proposed and opens on its own page.

The button at the top of an improvement is its next step; More has the others.

FromNext steps
ProposedApprove, or Not doing
ApprovedStart, Back to proposed, or Not doing
In progressMark done, or Not doing

An idea needs its Expected benefit before it is approved, and its Result before it is marked done. While either is missing the button says what to add and opens the field. An idea in progress stays editable, so its result can be written as the work goes. Done and Not doing close it.

Approving an improvement is a step in the register, made by somebody with report.manage. It does not ask for an approval request the way a change does.

Record a review, on the Service reviews tab, asks for:

Field
ReviewIts name, such as Term 4 service review
Led byWho led it, or Not set
Held onThe date it is planned for or was held, which is required
CampusShown when the school has more than one campus
AttendedNames and roles, such as the principal and the business manager
PurposeWhat the review is for

The tab lists the reviews, the most recent first, with who attended under each name.

A review starts as Planned, and its page shows the date as Planned for. Mark held needs who attended and the date, and is offered from the review’s day, not before. A review held early offers Move to today in its place: it moves the date to today, and Mark held follows. Once held, the date reads Held on. On the review’s page, write what was Discussed and the Actions agreed. A review stays editable once held, so its actions can be followed up. Cancel review…, under More, closes one that did not happen.

The Termly service review board is the pack to take to the review, and a scheduled email can send it on the last day of each term.

An improvement or a review opens on its own page, with its status, its owner or who led it, its date and its campus in the column beside it. Its campus reads Whole school when it has none. Editing it, from More, offers the campus when the school has more than one.

Connected records links the problems, tickets and changes behind it. A service review can also link the improvements it agreed. It lists both ways, so an improvement shows the reviews and changes that link to it as well as what it links to. Each linked record follows your own access, so one you cannot open is not shown to you.

These records have no bookings, approvals, effort or cost. They are never listed in School operations or its work widget on Home.

Adding, editing and moving an improvement or a service review is recorded in the audit log, named as an improvement or a service review.

PermissionAllows
report.viewSee the register and the service reviews
report.manageAdd and edit improvements and service reviews, move them between statuses, and link records to them

Linking a ticket also needs ticket.view, and linking a change change.view. See permissions.