> For the complete documentation index, see [llms.txt](https://connected-places-catapult.gitbook.io/trial-design-guidebook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://connected-places-catapult.gitbook.io/trial-design-guidebook/foreword.md). # Foreword Trial design toolkit This guidebook presents guidance, resources and activities to help SMEs develop a detailed and refined trial proposal. The guidebook has been developed by [Connected Places Catapult](https://cp.catapult.org.uk/), the UK’s innovation accelerator for cities, transport, and place leadership. This guidebook consolidates previous Catapult knowledge and insights on trial design, development, and deployment. The consolidated guidebook is being trialled within the [Innovate UK](https://www.ukri.org/councils/innovate-uk/) funded rail milestone programme, with the objective to be rolled out across all Catapult trialling and testing projects. We welcome any feedback on the template and the guidebook to progress our approach and the support we provide. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://connected-places-catapult.gitbook.io/trial-design-guidebook/foreword.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.