Home / Use cases / School office: every teacher hears it once

School office: every teacher hears it once

A school office inbox fanned out to teachers and staff. Parent emails and admin notices land in each teacher's own inbox.

School office: every teacher hears it once

The setup

The school secretary fans office@ out to year leads and specialists: y1@, y2@, y3@, y4@, y5@, y6@ plus music@, pe@ and sendco@.

How the mail flows

  1. A parent emails about a pickup change at 2:10pm.
  2. The class teacher and the office both hold the identical message minutes later.
  3. Admin notices go the same way: one message in, nine staff inboxes updated.
  4. office@ remains the single archive governors can audit.

Why Sinka fits here

  • No mailing lists to update every September when staff changes.
  • Supply teachers get a real inbox copy the day they start, revoked the day they leave.
  • Read/unread is personal: the office's read state never hides mail from teachers.

Watch out for

  • Safeguarding mail needs named humans, not copies — keep your DSL procedure on top of the inbox flow.
  • Parents replying to all nine copies would be chaos; replies go to the teacher who answers, which is the point.

Last updated: 29 October 2026 · Browse all use cases

Try this setup yourself. Sinka is free and open source — one inbox in, every teammate covered.
Get Sinka on GitHub
?
This site sets no cookies, runs no analytics and loads nothing from third parties.