> For the complete documentation index, see [llms.txt](https://docs.acecentre.org.uk/aac-policy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acecentre.org.uk/aac-policy/transition.md).

# Transition

Inevitably, all educational journeys are filled with transition. Either transition to another class, another setting, or on completion of education; adult services.

During transition there may be a risk of device/ AAC abandonment. Research suggests there are a variety of reasons why this may happen, including a lack of professional expertise, lack of professional support, difficulties with accessing the device and lack of implementation (Murphy et al. 1996, Hodge 2007, Baxter et al. 2012). With this is mind, it is imperative that we consider a learners AAC system when considering transition.

We know that planning head for transition is key to success. It is the same for considering AAC within transition. Consider how from day 1 of transition AAC can be considered as central.

### <mark style="color:blue;">Discussion point! Transition</mark>

<mark style="color:blue;">What currently happens with students and their AAC at transition points? How do you share information with staff?</mark>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.acecentre.org.uk/aac-policy/transition.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.