Skip to content

Inductions

/inductions. Needs module.inductions.

The start-of-year device handout, run in an organised way. Import a roster, work through it, record what each student was issued.

Because handout week does not look like the rest of the year. Two hundred students, a queue down the corridor, four staff, and a spreadsheet somebody is editing while somebody else is reading from it.

Inductions exist to make that survivable, and specifically to answer “has this student already been through” without anyone shouting across a room.

Import a roster of students who need a device, grouped into a program. A program is usually a year level or a cohort: Year 7 2026, or Staff refresh.

Rosters come from a spreadsheet, which is what schools already use for this. See the Google Sheets connector for reading one directly, or import a file.

Track progress per student: not started, in progress, completed.

Record the device issued, and any device returned. Both are worth capturing: the returned device is how you find out what came back and what did not.

Students check their own status at the induction kiosk by tapping their card, which removes a large amount of “am I on the list” traffic from the staff running it.

From schools that do this every January:

  • One station running the induction kiosk at the front of the queue. Students tap, find out whether they are on the list and where they stand, and are sent to the right place.
  • Staff stations running the inductions page, recording issued devices.
  • The serial autocomplete on. Typing a serial from a sticker gets it wrong; picking it from your MDM does not.

The record of who received what is the thing you will want in March, when a device turns up with no owner or a family says they never got one.

It also feeds device records, so an issued device is assigned to its student from day one rather than the first time it breaks.

PermissionAllows
induction.manageRun inductions, import rosters, record issued devices