> For the complete documentation index, see [llms.txt](https://usecaseframework.openactive.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usecaseframework.openactive.io/framework-overview/framework-at-a-glance.md).

# Framework at a glance

The framework is broken down into five stages, which cover the identification of use case communities through to the development and evaluation of solutions that bring use cases to life within those communities. It is scalable and can be applied to both simple and complex use cases.

It is designed to be cyclical, with shared learning from use cases building an evidence library to inform the iteration of existing use cases and the development of new ones.

<figure><img src="/files/lp3Arb1VhsCc2jqFiLk4" alt="Cyclical diagram outlining the five stages of the use case framework. Stage One - Engage and convene. Identify and engage with existing communities, or build new use case communities that can identify, prioritise, fund and deliver use cases. Stage Two - Understand and plan. Identify and plan the delivery of viable OpenActive based use cases which address prioritised problem statements and demonstrate the potential impact of OpenActive. Stage Three - Develop. Develop and test OpenActive based solutions to the prioritised problem statements. Solutions could include data, technology, processes, standards or guidance. Stage Four - Learn and publish. Evaluate if the solution has delivered the expected impact and share learning through the publication of case studies and reports. Stage Five - Implement. Implement viable OpenActive based solutions."><figcaption><p>Cyclical diagram of the use case framework</p></figcaption></figure>

Use case communities can follow the whole cycle step-by-step, or pick out individual tools or activities as needed. As part of the initiative’s commitment to [open working](https://www.sportengland.org/unlocking-digital-innovation-power-open-working), use case communities are encouraged to adopt open working practices, with the following OA channels available for use:

* [Slack](https://openactive.slack.com/) - for open communication
* [Google Drive](https://drive.google.com/drive/folders/15EOMYf47kCJ7JPSKbCISkWr6RJUjM_PR) - for open sharing of resources and documentation
* [YouTube](https://www.youtube.com/@openactive) - for meeting recordings

The remainder of this document will set out each stage of the framework, describe the objective of the stage, suggest processes and activities a use case community can use and provide links to supporting tools and templates.

<table data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Engage and convene</strong></td><td>Identify and engage with existing communities, or build new use case communities, that can identify, prioritise, fund, and deliver use cases.</td><td></td><td><a href="/pages/7av3ZM5zv2cp0mxJG1E2">/pages/7av3ZM5zv2cp0mxJG1E2</a></td><td><a href="/files/sgKzPPPwGvt2WbAe261b">/files/sgKzPPPwGvt2WbAe261b</a></td></tr><tr><td><strong>Understand and plan</strong></td><td>Identify and plan the delivery of viable OpenActive based use cases which address prioritised problem statements and demonstrate the potential impact of OpenActive.</td><td></td><td><a href="/pages/03uUBzDU6vSKWzR4qcdE">/pages/03uUBzDU6vSKWzR4qcdE</a></td><td><a href="/files/uKZztq3eoh47i9YgxM7U">/files/uKZztq3eoh47i9YgxM7U</a></td></tr><tr><td><strong>Develop</strong></td><td>Develop and test OpenActive based solutions to the prioritised problem statements. Solutions could include: data, technology, processes, standards or guidance.</td><td></td><td><a href="/pages/IH5QskondtsYJHvPy0q2">/pages/IH5QskondtsYJHvPy0q2</a></td><td><a href="/files/XwlpltNP4kplbTk4Ds1u">/files/XwlpltNP4kplbTk4Ds1u</a></td></tr><tr><td><strong>Learn and publish</strong></td><td>Evaluate if the solution has delivered the expected impact and share learning through the publication of case studies and reports.</td><td></td><td><a href="/pages/6628zPNCcDdcrqVqoYt0">/pages/6628zPNCcDdcrqVqoYt0</a></td><td><a href="/files/MjPMBAdtwgn9V40Gk6U8">/files/MjPMBAdtwgn9V40Gk6U8</a></td></tr><tr><td><strong>Implement</strong></td><td>Implement viable OpenActive based solutions.</td><td></td><td><a href="/pages/UrXaN0iVTGqxum8H76z8">/pages/UrXaN0iVTGqxum8H76z8</a></td><td><a href="/files/gB1GT68DyWXGVhFXdT8C">/files/gB1GT68DyWXGVhFXdT8C</a></td></tr></tbody></table>


---

# 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://usecaseframework.openactive.io/framework-overview/framework-at-a-glance.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.