> For the complete documentation index, see [llms.txt](https://docs.communityinclusion.org/training-and-technical-assistance-materials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.communityinclusion.org/training-and-technical-assistance-materials/apr-data-fidelity-review/coordination-collaboration-and-state-improvement-outcomes.md).
# Coordination/Collaboration & State Improvement Outcomes
Coordination/collaboration activities are not required to be reported in the APR; however, such activities are a required activity of all Section 4 AT Act grantees. As such, when a grantee does not report at least one coordination and collaboration activity, it sends a message that they are not complying with legal requirements. Data from this section of the APR is used to populate the [CATADA Catalogue of Initiatives](https://initiatives.catada.info/), which is frequently utilized by ACL to identify grantee activities to highlight in partnership activities.
Similarly, not reporting any state improvement outcomes is permissible but can be interpreted as a lack of program focus on systemic policy work that is critical to supporting access to and acquisition of AT. These can be thought of as “systems change” initiatives that result in new, improved, or expanded policy, program, or practice outcomes that increase access to and/or acquisition of AT.
#### Red Flag: No coordination/collaboration, or state improvement outcomes are reported.
This suggests the program is not complying with the AT Act requirements and/or the program is not as robust as is could/should be.
*Last updated January 2023*
---
# 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.communityinclusion.org/training-and-technical-assistance-materials/apr-data-fidelity-review/coordination-collaboration-and-state-improvement-outcomes.md?ask=&goal=
```
`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.