One notice, the right audience
Publish it once against an audience built out of the register rather than out of a distribution list somebody maintains by hand, and the students it is addressed to find it on their own dashboard board and their messages page — filtered to them, urgent first, and gone when it expires.
The circular, photocopied and hoped for
A circular sent home in a bag reaches whoever the bag reaches, and a WhatsApp group has the wrong members within a term. Building the audience out of classes and sections instead makes it correct by construction — when a student changes section, the next notice follows them without anybody updating a list, because there is no list to update.
A photocopied circular sent home in school bags
A class-parent WhatsApp group with stale membership
A cork noticeboard with last term’s holiday still on it
The same announcement retyped for the board, the group and the email
Notices, screen by screen
Each of these is a screen or a service in the module rather than a heading on a roadmap.
Audience built from the register
The whole school, named classes, named sections or named students, crossed with the roles being addressed. It is a query over real records rather than a mailing list, so the audience cannot go stale between the notice being written and being read.
A name that does not match is refused
Addressing a notice by class name resolves that name against the school’s actual class list, and an unrecognised one comes back as an error naming the classes that do exist. The alternative — publishing to nobody and reporting success — is the failure mode this exists to prevent.
Categorised and prioritised
General, academic, exam, event, holiday, fee, emergency, parent-teacher meeting or circular; at normal, important or urgent. Urgent sorts to the top of the reader’s board rather than relying on capital letters.
Draft, published, expired
A draft is visible to nobody until it is published, and an expiry date is re-checked every time the notice is read — so last term’s holiday notice stops being addressed to anyone on its own rather than being flagged as old.
One document shape, every writer
Every writer goes through a single builder, so the assistant that publishes an announcement and the route that publishes a schedule change produce the same document the student surfaces read. The writer and the reader drifting apart is what used to make notices vanish.
One visibility rule, every surface
A student’s board and their messages page ask the same predicate whether a notice is addressed to them, so the two cannot disagree about what they should be seeing. Tenant isolation is enforced at the query and security-rule layer instead, because a filter running on the reader’s own machine can never be a security control.
The same row, read from somewhere else
The point of an ERP is not that it has a lot of modules. It is that a fee concession, an attendance shortfall and a report card are all reading one record. These are the places Notices touches.
Students
Classes, sections and named students come from the student register, so an audience is never a list that has to be maintained alongside the roll.
Timetable
A published schedule change writes its own notice through the same builder, so the class that has to know about it finds out on the board rather than on the wall.
Hostel & events
Event and holiday are notice categories as well as calendar entries, so a dated announcement is filed as the kind of thing it is instead of as general text.
What Notices does not do
Stated here rather than discovered in week three. If something you need is on this list, ask before you buy — it is a better conversation than the one after.
There is no notices screen for staff. A notice is published by asking the in-product assistant for it, which writes a real notice document; the composer and audience-builder components exist in the codebase but are not mounted on any route. If you want a form to fill in, this is the module to ask about before you buy.
Read receipts do not work. The data model has a row per recipient with read and acknowledgement timestamps, and screens that would display them, but nothing ever creates those rows — so the report is permanently empty and “who has read this” has no answer. Treat acknowledgement tracking as absent, not as a setting to switch on.
The only channel that reaches anyone is the in-product board. Email is configurable but not wired to notices; there is no working SMS gateway and the WhatsApp credentials are placeholders. Do not buy this expecting a text message to leave the building.
Audiences resolve for the whole school, classes, sections and named students. A transport route and a saved group are declared in the schema and are read by nothing, so a route-scoped notice is addressed to nobody — and houses, which are real in Academics, are not an audience at all.
Parent is one of the addressable roles and there is no parent portal in this build, so a notice addressed only to parents has nowhere to land. Address students and staff.
Set your institution up on Elevate
Start on the free plan for up to 250 students. Paid plans begin at ₹1499 per month, billed to the institution.