After the support meeting: who needs to know what?

The meeting ends; the handoff begins

Consider a fictional support meeting. A learner wants help beginning a long assignment. A teacher suggests a shorter first step. A parent can help create a quieter study period. A tutor will review the first attempt later in the week. Everyone agrees, but the phrase 'we will support them' leaves several practical questions unanswered: who acts first, what information travels with the task, and when will the group check whether it helped?

The answer is not necessarily a larger shared record. More information can also mean more confusion, more access to manage, and more material that people do not need for their role. The useful unit of coordination is often a specific action, with an owner, a boundary, and a review point. This article offers an original worksheet for that purpose. It does not replace an individualized education program, school policy, safeguarding process, or professional advice.

Two primary-source reminders

In its January 2024 assistive-technology guidance, the U.S. Department of Education distinguishes devices from the services needed to select and use them. Training and coordination may matter as well as the equipment. That guidance applies to IDEA in the United States; it is not a worldwide rule or a certification of any commercial product.

The Department's student-privacy FAQ advises teachers to check whether a classroom service is approved and to consult their institution's IT representatives. Its discussion of FERPA's school-official exception includes conditions concerning control, use, and disclosure of education-record information. A vendor's reassuring phrase is not a substitute for that local review. Other countries and settings require their own applicable assessment.

Write a handoff someone can act on

Use six fields: the learner's agreed goal; the next observable action; the person responsible; the information that person needs; the agreed communication route; and the review date. Add the learner's own description of what would be helpful wherever appropriate. If a decision belongs to a formal team or authorized professional, record that dependency rather than turning a suggestion into an instruction.

For the fictional assignment example, the goal could be 'begin the first section without needing to complete the whole project tonight.' The teacher supplies the agreed starting instruction through the school's approved channel. The family arranges the study period. The tutor checks the attempt at the next session. The review asks whether the instruction was usable and what should change—not whether the learner earned a character label such as motivated or unmotivated.

Different roles may need different views. The tutor may need the task and agreed support strategy without needing unrelated family history. An administrator may need confirmation that an action was assigned without needing the learner's private reflection. A useful test is: what decision does this person need to make, and which details are necessary for it? This is an operational design question; the institution still determines lawful access and applicable recordkeeping.

Make changes and uncertainty traceable

Give the handoff a date and a named contact for corrections. If the plan changes, make clear which version is current. A message saying 'ignore the previous instructions' is fragile when somebody was absent or a notification did not arrive. The replacement should state the new next step, who confirmed it, and when the change should be reviewed.

Leave room for 'not yet known.' Perhaps the learner has not tried the support, the family has not confirmed a time, or the institution has not approved a proposed tool. These are dependencies to resolve, not failures to hide. Do not convert lack of a reply into consent or interpret a missed task as evidence about a diagnosis, home circumstances, or intent.

Start with a fictional practice case

Before moving real information into a new workflow, have staff complete the worksheet with a fictional learner. Ask one colleague to act as the tutor, another as the family contact, and another as the authorized coordinator. Can each person identify their next step without seeing every note? Can they correct an error? Can access be removed when their role ends?

For SASHA, these are useful questions to bring to a demonstration or institutional conversation. They are not a claim that every proposed coordination feature is already available or approved for your setting. Clear handoffs are a standard to test in practice. The goal is fewer assumptions between people—and a learner who can understand what support has actually been agreed.