> 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/performance-measures.md).

# Performance Measures

Performance measures must be collected directly from recipients/participants without inappropriate influence. The performance measure questions (i.e., did you make a decision) and the response options should be presented to the recipient/participant so they can affirmatively select their choice. The state AT program should keep documentation of the performance measure choice made by the recipient/participant for verification of performance measure data collected/reported in the APR (e.g., a form directly completed by the recipient/participant or similar verification).

#### Red Flag: All performance measure data is always 100%.

It is highly unlikely that a program will never have a non-respondent or will never have a recipient/participant who selects “I did not make a decision” unless there are procedures in place that somehow “discourage” undesirable responses. This is especially true with very large numbers (thousands of recipients/participants). It is especially suspicious when there are non-respondents reported in consumer satisfaction but not in performance measures because those data elements are frequently collected at the same time.

*Last updated January 2023*

<figure><img src="/files/dgvWMwZGdy5yZYzNiCgf" alt="catada logo"><figcaption></figcaption></figure>


---

# 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/performance-measures.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.
