> For the complete documentation index, see [llms.txt](https://docs.communityinclusion.org/guide-to-accreditation-for-higher-ed-programs/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/guide-to-accreditation-for-higher-ed-programs/section-1/introduction-to-accreditation.md).

# Introduction to Accreditation

The purpose of this guide is to provide comprehensive information about the accreditation process to personnel in postsecondary programs who are interested in pursuing.&#x20;

The following factors guide the framework for the accreditation process:&#x20;

* An emphasis on accreditation as a continual process of quality improvement, rather than a one-time event
* A commitment to clarity and fidelity of the Program Accreditation Standards and interpretive guidance
* An acknowledgment that accreditation is a year-long process from initiation to determination
* An outline of clear expectations throughout the accreditation process
* A commitment to collaboration and collegiality throughout the process of program accreditation


---

# 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/guide-to-accreditation-for-higher-ed-programs/section-1/introduction-to-accreditation.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.
