A Consent-Aware Handoff from K–8 to High School Support

Start with the student’s priorities

A move to high school changes more than a student’s schedule. New adults, routines, and expectations can make familiar supports harder to access. Before preparing a handoff, ask the student what they want to continue, change, or leave behind. Treat their answers as essential planning information, not an optional courtesy.

A useful opening conversation is specific: “Which routines help you get started?” “What would you like a new teacher to understand about how you ask for help?” “Is there anything from middle school you do not want shared?” Give the student time to think, and offer more than one way to respond, such as speaking, writing, or discussing options with a trusted adult.

Record the student’s own wording where practical, and distinguish it from adult observations. For example, “I want a quiet reminder before group work” is different from an adult’s interpretation that the student “does not participate.” That distinction helps the receiving team begin with the student’s perspective rather than a fixed label.

Separate useful context from a full record transfer

A transition meeting does not require every prior document to be passed along. Decide what the receiving team needs for a defined purpose: perhaps to prepare a first-week check-in, understand a successful classroom routine, or know whom the student trusts. Leave unrelated history out of the handoff.

Use ONWARDology and Onward180 as concepts to guide this planning, not as a reason to assume that information moves automatically between products. The Onward Suite connects Ready Set Onward, Onward Families, Onward180, ONWARDology, Onward Nexus, OnwardSync, Onward Signal, and Onward Playbook; that description alone does not establish a shared login, shared records, or a live integration. Confirm the process and permissions for any tool or document your setting uses.

A practical handoff might include three items: the student’s preferred way to ask for help, one support that has worked in a specific setting, and a named adult responsible for the first follow-up. It might exclude old notes that do not inform those decisions. For an overview of the product landscape, see the [Onward ecosystem](/ecosystem) and [solutions](/solutions) pages; use them to understand the suite, not to infer how a particular school’s records are handled.

Make permission specific and understandable

Consent is not simply a signature collected at the end of a busy meeting. Explain what information is proposed for sharing, who would receive it, why it may help, and how it will be shared. Invite questions before asking the student and, where appropriate, their family to decide. Follow your organization’s established consent and privacy procedures; this article is not legal guidance.

Avoid vague requests such as “May we share the file?” Instead, name the material and purpose: “May we share your preferred check-in routine and the name of your middle-school contact with the ninth-grade support team so they can plan your first two weeks?” Make clear that the student can raise concerns, ask to revise the proposed summary, or identify information they do not want included. Be honest about the limits of choice under your organization’s procedures.

Write down the decision, the agreed scope, and who will carry out the handoff. If permission is not given, do not treat silence as approval. Ask what, if anything, the student is comfortable sharing, and plan a low-pressure way for them to introduce their needs after the move.

Assign people, timing, and a fallback

A handoff is more dependable when one person owns each next step. Before the school year ends, identify the receiving contact, the person who will share the approved summary, and the student’s first check-in point. Set a date to confirm that the contact was reached; sending information is not the same as knowing someone can act on it.

Use a short checklist:

- Ask the student what should continue, change, or stay private. - Select only information tied to a clear transition purpose. - Explain recipients and sharing method; document the decision under local procedures. - Name the sending and receiving contacts and agree on a follow-up date. - If a handoff cannot happen as planned, identify a student-chosen adult to help bridge the gap.

If you are considering a product as part of the workflow, verify the actual process with your organization rather than assuming that a product name signals a particular data path. The [Onward Nexus](/products/onward-nexus) and [OnwardSync](/products/onwardsync) pages can help teams review those products, but confirm any intended use, access, or connection directly before relying on it.

Close the loop with the student

After the move, check whether the agreed support is present and feels useful. Ask a focused question: “Did the new adult understand the routine you wanted to share?” If not, work with the student to adjust the explanation or identify another contact. Avoid making the student responsible for repairing a handoff that adults own.

The next action is straightforward: schedule a brief transition conversation, draft a one-page summary from the student’s priorities, and review its exact contents and recipients with the student before sharing. That small sequence turns a product-aware transition into a human one: purposeful information, explicit permission, and a clear person ready to follow through.

Common questions

### Should the high school receive the student’s entire K–8 record?

Not automatically as part of a planning conversation. Identify the purpose of the handoff, select information relevant to it, and follow your organization’s established procedures for records and permission.

### Does mentioning ONWARDology and Onward180 mean information transfers between them?

No. The product names and their place in the Onward Suite do not establish shared login, data interoperability, or a live integration. Confirm any specific workflow or connection before relying on it.