> For the complete documentation index, see [llms.txt](https://knowledge.adsgroup.org.uk/8RnoQ2Y1ZgHQnhYYpqoO/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.adsgroup.org.uk/8RnoQ2Y1ZgHQnhYYpqoO/sc21/continuous-sustainable-improvement-plan-csip/accessing-the-csip.md).

# Accessing the CSIP

Continuous Sustainable Improvement Plan (CSIP

All SC21 companies require a CSIP and it is the only mandatory part of the Programme. This plan should align your improvement to your business strategy remembering that how you prioritise your improvement activities and when, is for you to decide.

Your plan should not resemble a Gantt chart with an obvious ‘end point’ as improvement is continuous. It is, in effect, a conveyor belt of improvement activity.

A CSIP template is attached below. If you may already have a similar document (that you might call it something else) you do not need to change to the recognised SC21 format, but your plan should cover the same ground.

{% file src="/files/KnHufTvjxqOS2IJXPr6V" %}

Further Advice on how to complete a CSIP, led by Melody Little from Thales, can be found [here  ](https://adsgroup.vids.io/videos/7991d5b51f1ae7c4f0/sc21-csip-masterclass)


---

# 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://knowledge.adsgroup.org.uk/8RnoQ2Y1ZgHQnhYYpqoO/sc21/continuous-sustainable-improvement-plan-csip/accessing-the-csip.md?ask=<question>&goal=<user_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.