CursusOS / Platform / Automation and Google Workspace

Automate the consequence, not the form.

Two hundred specified trigger points absorb the chasing, the re-keying, the assembling and the remembering.
Not one of them is a decision.

Book a demo See full functionality

cursusos.com/automation

Automation

200 trigger points · one notification queue · full audit

ChainsNotificationsConsentAudit

200

Trigger points

Notification queue

100%

Attributed writes

Leave approved → absence → cover → notifyAutomated

Bus delay → attendance flags → parentsAutomated

Document expiring → re-request → reminderAutomated

Safeguarding concern → routed, never decidedHuman

200 trigger points

Identified across every department, each with its actor, its downstream writes and its exceptions.

One notification queue

WhatsApp, email and push, with per-channel consent, language preference and urgency tiers.

Workspace is the login

Group membership is the permission model. There is no second directory to maintain.

Proposes, then confirms

Anything involving judgement is generated as a proposal for a person to accept. Attention is spent where attention is the point.

The chain

Automate the consequence, not the form.

Most school software automates the paperwork and leaves a person to perform everything the paperwork implies. Here an approved leave request writes the attendance record, which triggers cover, which builds the cover sheet from the absent teacher's own lesson plan, which notifies the cover teacher, the head of department and the affected classes. One action, one chain, no chasing.

cursusos.com/automation

Trigger chain

Leave approved · 07:02 · 6 downstream actions

ChainAuditNotificationsExceptions

Staff absence written to attendanceComplete

Cover requirement raised for 4 periodsComplete

Cover sheet generated from lesson plansComplete

Department head notifiedComplete

Affected classes and parents updatedComplete

No free specialist for P6 ArabicNeeds a human

Google Workspace

Workspace is the login, not an integration.

Staff, students and parents sign in with their school Google account. Workspace Group membership is the permission model, so there is no second directory to maintain and no separate password to forget. Classroom stays Classroom, Drive stays Drive, and CursusOS supplies the structure underneath both, then reads the outcomes back for reporting and intervention.

Google Workspace for Education

Identity

Single sign-on for every audience. Adding someone to a Group grants access, removing them revokes it.

Classroom

Classes, rosters and assignments stay where teachers already work. Outcomes read back for reporting.

Drive

Lesson plans, policies, examination papers and staff files live in Drive, under the school's own retention rules.

Calendar

Term dates, events and the timetable publish to the calendars people already look at.

Admin console

The school's existing audit, retention and security controls continue to apply to the documents.

Automation

Full functionality

Every workflow below is specified with its trigger, its actor, the screen it happens on, the step sequence, the permissions and the edge cases.

Ask about any of it

01How a trigger is specified

Two hundred notification and automation points are identified across the platform. Each one is written before it is built.

The event that fires it, in the language of the school rather than the database.
The actor, if there is one, and what they were doing at the time.
Every downstream write, in order, with the permission each one runs under.
The exceptions, including what happens when the chain cannot complete and who is told.

02The notification queue

WhatsApp, email and push delivered through one queue rather than three systems.
Per-channel consent held per person, and respected without a marketing exception.
Language preference per recipient, not per school.
Quiet hours and urgency tiers, so an evacuation message is never queued behind a newsletter.
Delivery, failure and read state written back to the record that sent it.

03Identity and permissions from Workspace

Workspace Groups map to capabilities inside the product, controlled from a screen a head teacher can operate.
Access is granted to a Group, never to an individual, so a new teacher inherits the right access on day one.
Leaving the Group revokes access immediately, across the platform and every scoped portal.
No second directory, no shadow user list, no orphaned accounts after a resignation.

04Classroom, Drive and Calendar

Classes and rosters provisioned from the timetable, so Classroom matches the actual teaching structure.
Assignment outcomes read back for reporting, intervention and workload analysis.
Documents stored in Drive under the school's own retention and audit policy rather than in a vendor silo.
Term dates, events and timetable changes published to the calendars staff and families already use.

05Audit and reversibility

Every automated write is attributed to the trigger that caused it, not to a service account nobody can explain.
A chain that fails halfway is visible, with the completed steps listed and the incomplete ones named.
Any automated action a human could take, a human can also reverse, with the reversal logged.
Automation proposes and a person confirms wherever judgement is involved. Curriculum differentiation and house sorting follow the same shape deliberately.

06What is deliberately not automated

Two hundred trigger points absorb the chasing, the re-keying, the assembling and the remembering. Not one of them is a decision.

Safeguarding judgements are never automated, only routed and recorded.
Exclusions, offers, appointments and progression are always confirmed by a named person.
Generated content, from differentiation to cover sheets, is a proposal until somebody accepts it.
Where the system is uncertain, it says so and stops rather than guessing quietly.

Continue