Skip to content
plugboard.appRequest a demo

Running the desk

Changes

/changes, and /changes/<id> for one. Needs change.view, with the Tickets module or the School operations module on.

A change record is scheduled work that could break something if it goes wrong: replacing the core switch, pushing an operating system update to a year group, moving the library system to another server. It holds the plan, the window it runs in, who approved it and how it went.

A ticket of type Change is somebody asking for a change. The change record is how the desk carries it out. School operations lists the same records among its work, so a school with both modules sees each change in both places.

Changes under Service desk has two tabs, List and Month. The header holds Change rules, for the people who set them, and Plan a change.

List shows the changes that are still open, by window:

  • Under way: in progress or implemented, waiting for review.
  • A section for each day a window opens, in date order. A day inside a freeze period names the freeze beside its heading.
  • No window yet.
  • Freeze periods: each freeze still to come, with its dates and how many open changes fall in it.

Each row shows the change, its type and risk, its window and its status. A row whose window falls in a freeze says which one:

The row readsMeaning
In the HSC exams freeze, flaggedA normal or standard change waiting for a change approver to record why it cannot wait
Emergency change in the HSC exams freeze, flaggedAn emergency change, which goes ahead in a freeze
Reason recorded for the HSC exams freezeA change approver has recorded why it cannot wait

Reviewed and cancelled folds away underneath.

Month is the change calendar: a month at a time, Monday first, with each day’s change windows and the freeze periods it falls in. A freeze’s days are shaded, and it is named on the day it starts and again on the Monday of each week it runs through. Each change shows its start time on its first day and links to the change. Changes implemented or reviewed are drawn quieter, and cancelled ones are left off. The arrows move a month at a time, and This month comes back.

On a phone the month reads as a list of the days with a window, and the days a freeze starts or carries into the next week. The address keeps the tab, so a link to /changes?view=month opens the calendar.

Plan a change (needs change.manage) asks for a title, a description, an owner, a campus and the change window. Edit change, under More on the change, offers the same, campus included. The change opens as a Draft, and its Change plan is filled in on the change itself:

TypeNormal, Standard or Emergency (below)
RiskLow, Medium or High
ImpactWho and what is affected, and for how long
Implementation planThe steps
Rollback planHow to put it back
Implementation checkHow you confirmed it worked, written once it is done
Post-change reviewWhat happened, written at the end
OutcomeSuccessful, Rolled back or Failed, chosen at the end

The type, risk, impact, implementation plan, rollback plan and a change window are all needed before a change is requested, approved or started. An approval is for the plan as it stood: change the plan afterwards and the approval no longer counts, so it is asked for again. Once a change is in progress its plan is fixed; the implementation check, the review, the outcome and the actual effort and cost can still be recorded.

A change moves through Draft, Requested, Approved, In progress, Implemented and Reviewed, or ends as Cancelled. The button at the top of the change is the next step; More has the others, Edit change and Cancel work….

  1. Request approval. Under Approvals, choose who approves it, in order or together, and request approval. Then move the change to Requested.
  2. Approve. An approver records the decision on the change or under My approvals. Declining needs a note saying why, so the requester knows what to change. Moving a change to Approved needs change.approve.
  3. Start the change. Only while its window is open.
  4. Mark implemented, with the Implementation check written.
  5. Mark reviewed, with the Post-change review written and an Outcome chosen.

Work the change depends on has to finish before it can be approved or started. A window in a freeze period needs a reason recorded first.

Normal is the path above: approval of the plan before it starts.

Standard is routine work approved once, in advance, as a standard change in Change rules. Choose the standard change on the change and its plan and risk are copied in. Schedule the change then takes it from Draft to Approved without a fresh approval. It still needs a window, an implementation check and a review. If its plan is edited away from the standard change, it is refused until it is made a normal change and approved.

Emergency is work that cannot wait for approval. Start now, approve after starts it from Draft or Requested. It still has to be approved, and reviewed, before it can be marked reviewed.

A freeze period is a named run of days with no changes, such as exam weeks or the first and last weeks of term. Its first and last days are included. Freezes are set in Change rules.

A normal or standard change whose window touches a freeze does not move to Approved or In progress until a change approver records why it cannot wait. That covers Schedule the change on a standard change too. The change says so above its plan: This window falls in the HSC exams freeze, with the freeze’s dates.

To record the reason:

  1. Open the change. For a change approver, the button at the top reads Record why it cannot wait. Anybody else sees Waiting for a change approver.
  2. Write why it cannot wait, such as The exam room projector failed and the HSC trial starts Monday.
  3. Choose Save reason.

The change then reads Going ahead in the HSC exams freeze, with the reason, who recorded it and when. Approval and starting go on as usual.

  • Only somebody with change.approve records the reason, on the change itself. Saving or editing the change cannot write it.
  • The owner of a change cannot record the reason for their own change, unless the school lets staff approve their own work.
  • The reason is for that window and that freeze. Moving the window clears it, and a window in a different freeze needs a reason of its own.

An emergency change goes ahead in a freeze. It is not held, and it is flagged instead: Emergency change in the HSC exams freeze on the list and on the change, and the freeze is named on its line in the audit log.

Recording a reason is in the audit log as well, with the reason and the freeze.

An approval for a change, or a purchase, cannot name the person who asked for it or the change’s owner as an approver, and neither of them can record the decision. The owner counts because the owner carries the change out. The people offered as approvers leave them out.

A desk of one can turn this off: Let staff approve their own changes and purchases, and record their own reason to go ahead in a freeze, in Change rules, Approving your own work. Changing it needs role.manage, because whoever holds that can already make anybody an approver. With it on, every approval somebody gives their own work reads Self-approved, on the approval and in the audit log.

Settings, Change rules (/admin/changes), also reached from Change rules on the Changes page. It needs change.view, with change.approve or role.manage.

SectionWhat it setsNeeds
Freeze periodsA name, a first day and a last day for eachchange.approve
Standard changesA title, risk, impact, implementation plan and rollback plan for eachchange.approve
Approving your own workWhether staff may approve their own changes and purchases, and record their own reason to go ahead in a freezerole.manage

Add a freeze adds a row. Add term starts and ends is offered when the school has term dates still to come: it adds a freeze for the first school week of each term not yet started and the last week of each term not yet over, named like Term 4 2026 start and Term 4 2026 end. Point at the button to see the dates first. A freeze already named that way, or already covering those days, is left out.

Freeze periods and standard changes wait for Save in the bar at the foot of the page, with Discard beside it. The self-approval box saves as you tick it. Every save is recorded in the audit log. Flows never change these rules: they are the rules approvals are judged by.

Services it affects, above the change plan, names the services the change touches. Each shows its status, its owner and its support hours, and whether the window falls inside them: This window is inside its support hours or Outside its support hours. A change to the Wi-Fi controller in the middle of a school day can then be moved before anybody approves it. A service with no hours of its own is checked against the desk’s. A service the change names that you cannot see is counted, never named.

People with change.manage and service.view keep the list:

  • Add a service it affects finds a service by its name or one of its other names.
  • When the change links a monitor, network device or device under Connected records, the services that depend on it, or whose fleet takes it in, are offered, such as Add Wi-Fi, which depends on AP-HALL-01, with Add. Nothing is added by itself.
  • Remove takes a service off.

While the change is In progress inside its window, each service it names reads Planned work on Services, on its page, on Home and on the public status page, and goes back to its monitors when the window ends or the change moves on. See planned work. Only a change names services; other work in School operations does not.

Naming a service is recorded in the audit log, such as said a change affects Wi-Fi. The section needs service.view.

When something goes down, the first question is what changed. Plugboard answers it from the records, by rules, with no AI.

Changed in the last 72 hours lists the changes in progress, or implemented with a window in the 72 hours before the outage, that touch the same thing:

Shown onWhen
A major incident’s ticketWhile it is a major incident
An incident ticket that names a monitored serviceWhen that service went down in the three days before the ticket was raised, or is still down
A monitor’s detail on MonitorsWhile the monitor is down
A service’s pageAlways: the 72 hours before the service went down or started having problems, or the last 72 hours while it is working

A change touches an outage when it links the device, the network device or the monitored service involved, or when it is at the same campus. A change with no campus is the whole school’s, and an outage with no campus could be anywhere, so either way the change is listed. A change at another campus is listed only through a record it links. Each change says why, such as Linked to the monitor that is down, the campus name or Whole school, with its status and window. The most specific come first.

On a service the campus alone is not enough: a change is listed when it names the service, or links something the service depends on or a device in its fleet, such as Linked to AP-B12, which Wi-Fi depends on.

The list needs change.view, with ticket.view on a ticket, monitor.view on a monitor or service.view on a service. It says nothing when no change is near.

The monitor’s alert says the same in a line of its own, to people who can see changes: Library system is down. Changed in the last 72 hours: and the first three changes.

The other way round, a change lists the incidents raised during its window or in the 72 hours after it that:

  • are about a device the change linked (Same device);
  • name a monitored service or a network device the change linked, read the way a ticket’s services panel reads them (Names a linked service); or
  • are major incidents at the change’s campus, or anywhere when either has no campus (Major incident).

Incidents since this change shows under the plan when there are any, with each incident’s number, when it was raised and its status. It needs ticket.view as well, and lists only incidents you can see.

Link the monitors, devices and network devices a change touches under Connected records, below, so both lists can find it. Naming a service under Services it affects puts the change on that service’s own list.

Connected records on a change links tickets, devices, documents, software contracts, network equipment and monitored services. Each linked record keeps its own access checks, so a record you cannot open is not shown to you.

A ticket or a device with changes linked to it shows them in a Changes panel. On a ticket of type Change with no change record, the panel offers Create change record: a draft normal change, filled in from the ticket’s subject, details and campus, with you as its owner, linked back to the ticket and opened for you. That needs change.manage.

The Change success rate report counts the changes reviewed in a period, by type: successful, rolled back or failed. The Changes data in the report builder holds every change, with its type, risk, status, outcome and campus and a success rate, for report boards and Home widgets. See reports.

PermissionAllows
change.viewSee changes on the Changes page and its calendar, in School operations, on tickets and devices, and near an outage
change.managePlan, edit, link and move changes, and create one from a ticket of type Change. With service.view, name the services a change affects
change.approveApprove changes, record why a change cannot wait for a freeze period, and set freeze periods and standard changes
role.manageLet staff approve their own changes and purchases

On a fresh desk only the Owner role holds the change permissions. Add them to the roles that plan and approve changes under Settings, Roles. See permissions.