COMMUNICATIONS
The right conversation.
The right next step.
Make institutional messages relevant to the recipient, the record and the next action.
State what the recipient needs to know or do. Separate urgent incidents, routine updates and individual requests.
START WITH THE QUESTION
Is the message connected to the work it asks someone to do?
A general announcement, a missing-document request and a sensitive student follow-up need different audiences and different approval paths. Bring the purpose, context and next action together before choosing the delivery channel.
WHAT MAKES IT USEFUL
Give every message a recipient, reason, and next action.
Audience follows context
Start with a class, intake, campus or verified relationship. Review exclusions and recipients before a message is approved, especially when membership has recently changed.
A message has an owner
Give replies and follow-up tasks a responsible team. Decide how absence cover, escalation and unresolved questions will work before opening a communication channel.
Delivery is part of the plan
Agree preferred channels, contact verification and delivery-provider requirements during scoping. A message prepared in a workflow is different from confirmed delivery to a recipient.
FROM DISCUSSION TO DAILY WORK
Plan the route from event to response.
- 1
Choose the purpose
State what the recipient needs to know or do. Separate urgent incidents, routine updates and individual requests.
- 2
Review the audience
Check membership, guardian permissions, language preferences and any disclosure restrictions.
- 3
Close the loop
Name the reply owner, follow-up period and way to handle a failed delivery or unanswered request.
Connected communicationsChoose the purpose → Close the loopSEE HOW THE WORK CONNECTS
Connected communications
Is the message connected to the work it asks someone to do?
- 01
Choose the purpose
State what the recipient needs to know or do. Separate urgent incidents, routine updates and individual requests.
- 02
Review the audience
Check membership, guardian permissions, language preferences and any disclosure restrictions.
- 03
Close the loop
Name the reply owner, follow-up period and way to handle a failed delivery or unanswered request.
Illustrative workflow · Shape the details around your institution.
CONFIGURE WITH INTENTION
Agree channels, audiences, and escalation.
- Audience groups and relationship-based recipient rules
- Sender identity, templates and approval requirements
- Preferred channels and provider connection requirements
- Reply ownership, retention and escalation windows
QUESTIONS TO RESOLVE
Questions about connected communications.
Use these questions to make the evaluation specific to your institution.
Which delivery channels can we use?
Channel selection is part of requirements scoping. Bring your email, SMS or messaging-provider needs, local availability and sender requirements; the proposed integration and delivery responsibilities should be confirmed explicitly.
Can communications use class or campus groups?
Class, campus and relationship context are useful starting points for audience rules. Validate how changes in enrollment and guardian permissions update membership before relying on a live recipient list.
How should emergency communications differ?
Emergency communication requires an institution-approved procedure, responsible responders and appropriate fallback channels. Review that procedure separately from routine messaging; a general announcement workflow is not a substitute for an emergency plan.
YOUR INSTITUTION. YOUR CONTEXT.
Start with a conversation that needs a clearer outcome.
Start with a real workflow, the people involved and the outcome you need.