> 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/learn-and-publish/stage-outline.md).

# Stage outline

## Objective

Evaluate if the solution has delivered the expected impact and share learning through the publication of case studies and reports.

## Process

<figure><img src="/files/JxuQLVGcOk8ZL7JCWQzH" alt="Process map outlining the process for the learn and publish stage of the framework. The first row starts with two inputs, KPIs and milestone reporting. Moving from left to right, these inform an activity to evaluate MEL against defined objectives. This leads to an output of learning and insights. From there the process map moves to the second row, with a further input - MEL evaluation and learning. This informs the second activity of the stage, sharing insights with the OA community. With the second output being published case studies and reports."><figcaption><p>Learn and publish process map</p></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://usecaseframework.openactive.io/learn-and-publish/stage-outline.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.