> 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/ongoing-training-and-development/whole-staff-training.md).

# Whole Staff Training

When there is an identified need for whole staff training, consider content and delivery. Decide whether an off the shelf training package is suitable or if something bespoke is needed. Also consider whether to enlist the help of external training providers or if members of the team have the experience required to deliver the content themselves. 

### <mark style="color:green;">Example: Training Delivery</mark>

<mark style="color:green;">Below are examples of how some of our Partnership settings decided to deliver training to their whole staff team.</mark>&#x20;

For example one setting we worked with used an external training provider to deliver content from Project Core while another was able to facilitate Makaton training as they had a certified tutor in house.

In some instances, the need for whole school training led to content being developed internally based on the need for skill development in topics such as modelling, AAC within routines, and alternative access to paper-based AAC. In order to make the content feel relevant and to boost confidence, examples and videos of the setting's learners and staff were used as illustrations of good practice.&#x20;

The content developed allowed staff involved with early AAC implementation to see videos of learners who had moved on to other classrooms. They were able to see how those learners had developed, which instilled pride in their learner’s achievements and the impact their support made.&#x20;

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

<mark style="color:blue;">AAC does not stop when learners step outside the classroom. Take the time to consider the entire community at your educational setting who communicate with your learners. Make sure to include members from the office, kitchen, grounds and health teams.</mark>&#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.acecentre.org.uk/aac-policy/ongoing-training-and-development/whole-staff-training.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.