Write the action first

State what is happening, who it concerns, the relevant date, and what the parent needs to do. If no action is needed, say so. Avoid making families search a long announcement for one deadline.

For example: ‘Class 6 A brings the signed permission form on Monday.’ Add the reason and any supporting detail after the action.

Check audience and access

Confirm whether the notice applies to the whole school, one class, or one section. Verify the student-family link when investigating a missing update. A family with multiple children needs to identify which child an update concerns.

• The intended audience is selected
• Dates and required actions are explicit
• The notice has been reviewed before publication
• Family access is prepared for the relevant student
• Any delivery channel is configured and tested

Distinguish publication from delivery

Publishing an update in a portal does not necessarily mean an email or SMS was sent. Check your configured channels and delivery workflow, and avoid promising notifications that have not been enabled.

Use a fictional family during setup to review the parent experience before inviting families to rely on it.