> 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/aac-policy-statement/staff-timing.md).

# Staff Timing

It is necessary to consider the time required for staff to complete designated AAC related tasks including those done in training, preparation and implementation. Some educational settings we worked with found it helpful to break this down into two parts, time needed by the AAC team and time needed by all staff.

### <mark style="color:green;">Example: Staff Timing</mark>

<mark style="color:green;">Below is an example of identified needs that you may want to use within your AAC policy.</mark>

Time for the identified AAC team to complete their tasks, including:

* Receiving training related to specific areas of AAC
* Providing training to wider staff team
* Auditing current AAC equipment within school
* Building relationships with wider team around the learner and suppliers
* Assessment and feedback of AAC resources within the classroom
* Making resources

Time identified for all staff to implement AAC within the educational setting, including:

* Modelling AAC within class
* Receiving training
* Creating resources&#x20;
* Considering teaching plans and incorporating AAC within them

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

<mark style="color:blue;">What does time allocation look like for you and the team at this moment?</mark>

Talk about the changes that are needed with allocation of time to facilitate success. It is beneficial to have a member of your Senior Leadership Team on the AAC team so that time concerns can be raised directly with them. We found that the educational settings we worked with who documented and agreed time allocation within their policy felt obliged to ensure time considerations were met.


---

# 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/aac-policy-statement/staff-timing.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.