> 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/setting-owned-technology.md).

# Setting-owned Technology

Our partnership settings identified a requirement to have their own assessment and loan bank. This allowed the AAC team to work alongside the local speech and language therapist and explore alternative AAC options with individual learners. This raised a need to consider who owns the equipment and funding provision for learners who require their own AAC. Effective provision of AAC goes beyond the school day. It is important that you promote the use of AAC at home and beyond, this is explored in the [Funding Options](/aac-policy/funding-options.md) section later on in this document.


---

# 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/setting-owned-technology.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.
