Appearance
Signing an SLA, and what is kept
An SLA is an agreement about money, so what matters as much as the current one is the record of what a school actually agreed to, and when.
Where to find it: SLA History on a school, and Mark Signed on SLA Management
The signed copy is the SLA as it was shown
When an SLA is signed — by the school on the Portal, or by you with Mark Signed — the lines the school was looking at are saved as they stood.
This is the whole point of a signed copy
The agreement is built from the school's own activities, so it changes as their activities change. A copy worked out afresh afterwards would tell you what the SLA would say today, which is no use at all when the question is what somebody signed in September.
So the copy is the lines themselves, kept as displayed. It replaces any earlier copy for that signing, and SLA History reads older copies too, so agreements signed before this went in still show.
A copy that cannot be saved does not stop the signing
Signing is the thing that matters, so it always goes through. Where the copy could not be written, the SLA shows as signed and its lines are worked out again when you look — which is the old behaviour, and the reason to check a signed SLA's history looks right rather than assuming it.
Revoking does not unsign
Revoking a signed SLA leaves it signed and archives it, with its copy, and a new pending SLA takes its place — exactly as a change of cost does.
Why that is the right way round
A signed agreement is a fact about the past. Unsigning it would remove it from SLA History and let the next signing overwrite its copy, which would quietly lose the record of what the school had agreed to.
So the history grows: each signed version archived with what it said, and one pending agreement in front of it.
See also
- Schools — SLA Management, and what an SLA is built from
- SLAs, for a school — the school's side: reading one, signing it, asking for changes
- A school's SLA is not what you expect
