School approval workflows for anything that matters

Most school systems record decisions. They do not govern them

Almost every school management system will store the fact that a waiver was granted. Very few will stop it being granted by somebody who should not have granted it, or make sure the director saw it first, or tell you three weeks later who approved it and when.

So the controls live outside the software. A signature in a book. A WhatsApp message saying go ahead. An understanding that certain things get checked with the principal. These work while everybody is present and honest, and they fail exactly when you need them, which is during a dispute or an audit.

For schools with boards, sponsors or more than one campus, this is increasingly the question being asked. Not what did you spend, but who authorised it, and can you show me.

How Enaton handles it

You describe your own chain. What needs approving, how many levels, who sits at each one, and what happens if somebody does not respond. Enaton then applies it consistently, every time, whether or not the people involved remember.

A decision, once made, is part of the record. It cannot be edited to say something else afterwards. That is what turns an approval into evidence rather than a formality.

Chains you define

• As many levels as the decision warrants, from one signature to several
• Different chains for different things, so a small consumables order does not follow the same path as a capital purchase
• The right approver identified by the rules rather than by whoever happens to have access
• Escalation when somebody sits on a request, so nothing quietly stalls for a fortnight

What passes through it

• Fee structures, before they can bill anybody
• Waivers and bursaries above whatever threshold you set
• Extra charges applied to a group of learners
• Purchase requisitions, orders and payment vouchers
• Changes to a learner’s financial record

For the approver

• A single queue of what is waiting on them
• Enough context to decide without opening four other screens
• Approve or reject in bulk where the volume justifies it
• Requests they raised themselves, tracked, so they are not chasing by phone

When something goes wrong

If a part of the school needs to be paused while something is fixed, it can be, deliberately and visibly, with a reason that is shown to the people affected rather than leaving them staring at an error. Turning something off never quietly means letting everything through.

Who this is for

Directors and boards get governance that actually holds. Principals stop being the bottleneck for every small decision. Bursars have cover, because the authority for what they did is recorded. Auditors get a trail rather than a folder of signatures.