Appearance
Calendar
The shape of your year, and the things that depend on it.
Academic Year — your years and the terms within them. Nothing can be taught until these exist, so this is the first thing to set up.
Learning Duration — how long a pupil has been learning a subject, offered on an application so they can say.
Register Keys — what a teacher marks against a pupil for a lesson: present, absent, and the rest. Each has a colour, so a register can be read at a glance.
Task Results — whether a lesson happened and, if not, why. A task result decides three things: whether the teacher is paid, whether the pupil is charged, and whether the lesson needs making up.
Teaching Groups — a grouping recorded against individual lessons, so a set of lessons can be identified as belonging together without making them a Group with members and fees of its own.
Academic Year
Two things on this screen are worth reading before you touch them: the non-working dates, and what Diarise does. Every field on it is listed in the field reference.
Non Working Dates
The days the whole service does not teach — INSET days, a closure, a training day. Open an academic year and the list sits under the terms. Press Edit to change them: Add non-working dates sits beneath the list, and Change and Remove are on each row. Like the terms, they are saved with the year when you press Save, and Cancel throws the changes away.
Each entry is a stretch of time rather than a single day. From takes a date and either Morning or Afternoon; To takes a date and either Mid Day or End Of Day. A single afternoon and a fortnight's closure are both one row. The description is what shows in the list afterwards, so "INSET" or "Christmas closure" is worth typing.
Saving a date does not move the lessons
The plan engine reads non-working dates as it lays sessions. It does not go back over sessions already in the schedules. Add a date after the year has been diarised and every lesson already sitting on that day stays exactly where it is.
This is the most reported thing in this part of Xperios, and it is the same for bank holidays and for a school's or teacher's own non-working time. The answer is always: get the dates in, then diarise the year again.
The list on the academic year is the whole service's non-working time. Three other levels exist, kept elsewhere, and the engine reads all four:
| Whose non-working time | Where it is kept |
|---|---|
| The whole service | Here, on the academic year |
| One school or centre | That contact's School or Centre tab, under Dates |
| One teacher | That contact's Teacher tab, under Dates — and only once the entry is approved |
| One service type | The service type's own non-working time |
A school's closure days do not appear in a teacher's diary, and are not meant to: a teacher looks at their own diary, which would otherwise carry every school's dates.
Diarise
Diarise lays the year's sessions again. What else it does depends on whether the year is open for scheduling:
| What Diarise does | |
|---|---|
| Open Schedule ticked | Creates this year's schedules from last year's — for the service types that progress schedules, along with the year's charges and the schools' SLAs — and then lays every plan's sessions |
| Open Schedule not ticked | Lays the schedules that already exist, keeping sessions off term breaks, bank holidays and non-working dates. It creates nothing |
Ticking Open Schedule does nothing on its own. It is pressing Diarise that progresses and lays.
How many sessions it lays for each plan is a choice on the plan's service type: each term's sessions exactly, as many as each term has room for, or as many as a yearly maximum allows. See How many sessions get diarised — it also explains the per-term warning you may now see when a term comes up short.
When it finishes it reports what it did — schedules created, schedules laid, sessions added, moved and removed, and how many were already as they should be. Read those numbers: sessions can be removed as well as added, because a term that no longer has room for its full count loses the sessions that no longer fit.
Then it lists anything it could not lay, with the reason for each. Usually that is a schedule where the change would touch lessons that are already marked, confirmed or credited — the batch leaves those alone rather than overwriting somebody's register. Open each one it names and make the change from its Schedule tab, where it is previewed and you agree to it. A lesson already paid to a teacher is never moved at all.
Every date in first, then Diarise once
Diarise is a whole-year job. There is nothing to gain from running it after each date — put all the non-working dates in, then press it once.
Where the Diarise button is
On the toolbar, beside Add, Edit and Delete, whenever you are looking at a year rather than editing it. It is there on every year, open for scheduling or not, for anybody whose User Group may change academic years. The newest year is at the top of the list.
It asks before it runs, and the question says which of the two jobs above it is about to do — so you can tell before you agree whether this run will create schedules or only lay sessions. What it did appears just above the record afterwards.
Saving the year with changed Non Working Dates offers Diarise under the list, which saves going back to the toolbar for the commonest reason to run it.
Why a term can end up one session short
Each term lays the number of sessions set on the schedule — its Term sessions — and no more than will fit between the term's dates. Enter more than the term has room for and you get what fits, not what you asked for.
A non-teaching day does not simply vanish from the run: the lessons after it each move on a week, and if the term has no spare week on that weekday the last one falls past the end of term and is dropped. The term is one session short, and nothing carries it into the next term by itself.
An example: a term with exactly eleven Mondays, one of them an INSET day, leaves every Monday schedule with ten sessions.
To make that session up in a later term, raise that term's Term sessions by one on the schedule. That charges for it as well — which is normally right, as the pupil is having the lesson.
Leave
Leave Types and Leave Reasons are not two halves of one thing
They sit next to each other and sound related, but they are about different people. Leave Types are a teacher being away. Leave Reasons are a pupil leaving something they were signed up for.
Leave Types
The kinds of absence a teacher can book — sickness, annual leave, training.
Each type carries four things that decide how it behaves:
| Colour and Icon | How it is drawn, so a calendar can be read at a glance |
| Take From Allowance | Whether this absence is deducted from the teacher's entitlement |
| Needs Approval | Whether somebody has to agree to it before it stands |
Those last two are what make the list worth setting up deliberately. Training that does not come off the annual leave allowance, and sickness that needs no approval, are both expressed by the type rather than by anything the teacher does.
A booking records the teacher, the dates, the academic year and, optionally, a single service type — so leave can be limited to one part of what somebody teaches rather than taking them out altogether.
Leave Requests
The absences waiting on a decision, because their type needs approval.
A request keeps the date it was made, the decision, when it was answered and by whom, so the trail survives the answer.
Leave Reasons
Why somebody left something they were signed up for.
A reason applies to as many of the seven services as you choose: tuition, group memberships, hires, events, auditions, exams and studies. Only reasons marked for a service are offered when leaving that service, which keeps each list short and sensible — "instrument returned" has no business appearing when a pupil leaves a choir.
The reason chosen is kept on the record that ended, alongside a free-text note for anything the list cannot express. Both stay readable afterwards: a past membership keeps why it ended.
One reason can cover several services
A reason such as "moved out of the area" applies to all seven. Tick each service it belongs to rather than creating the same reason once per service.
