Messages, announcements and feedback
Choose the right communication channel and understand what delivery records do not prove.
Takadar separates direct conversations, announcements, notifications, diary records, events and feedback. Choose the channel for the job instead of copying the same information into every surface.
Use the appropriate surface
| Surface | Purpose |
|---|---|
| Messages | A conversation with the permitted participants |
| Announcements | A notice published to its selected audience |
| Notifications | Updates raised by configured system and workflow events |
| Diary | A pupil-related teaching or family note |
| Events | Dated institutional activities |
| Feedback or complaints | A recorded issue for the responsible team to handle |
Writing and reading follow the user’s permissions and relationship to the record. Portal access does not make a family member a general staff-directory user.
Send with context
Confirm the intended school, participants or audience and, for child-related work, the correct child. Keep a decision in its actual workflow: a message saying “approved” does not replace approving a registration, result board or clearance record.
Use the complaint or feedback surface when an issue needs a retained status rather than an informal discussion. Staff can work the relevant saved record through the actions their permissions permit.
Understand delivery
An in-app record is not proof that every external channel delivered it. Email and SMS depend on the institution’s configured services, recipient data and applicable credit or delivery conditions. A recent diary card is not a read receipt.
For an urgent missing update, inspect the saved decision and the in-app notification or message first. Ask the institution to check contact information and delivery configuration rather than assuming another person has read the information.