> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/data-library/change-management.md).

# Change Management

Track, manage, and monitor change management processes by integrating code repositories and ticketing systems within Sprinto’s Data Library.

The **Change Management** section in Sprinto’s Data Library enables you to collect evidence and maintain compliance by tracking changes to codebases and operational workflows. This is achieved by integrating your existing **code repositories** (such as Bitbucket, Azure DevOps, GitLab) and **ticketing systems** (such as Jira, Trello, Asana) directly into Sprinto.

With these integrations, Sprinto can automatically capture and assess relevant change records, ensuring your organisation meets audit requirements and maintains operational transparency. You can also add **workflow checks** to collect targeted evidence and demonstrate adherence to your internal change management policies.

### Key Capabilities

* **Centralised Change Tracking** – Monitor all tracked code repositories and ticketing systems from a single dashboard.
* **Automated Evidence Collection** – Capture and store change-related data for compliance reporting.
* **Workflow Checks** – Create and manage checks to validate adherence to change processes.
* **Customisable Monitoring** – Filter, explore, and select checks relevant to your compliance framework.
* **Provider Flexibility** – Connect multiple systems, including popular developer tools and project management platforms.
* **Audit-Ready Reporting** – Ensure that your change management processes meet auditor expectations with clearly mapped responsibilities and evidence.

### Use Cases

<table><thead><tr><th width="194.61328125">Use Case</th><th>Description</th></tr></thead><tbody><tr><td><strong>Audit Compliance</strong></td><td>Automatically capture and present evidence for code and workflow changes to meet SOC 2, ISO 27001, or other compliance frameworks.</td></tr><tr><td><strong>Operational Oversight</strong></td><td>Track the lifecycle of changes, from request to implementation, across multiple systems.</td></tr><tr><td><strong>Policy Enforcement</strong></td><td>Validate that every change request follows approved change management protocols.</td></tr><tr><td><strong>Risk Reduction</strong></td><td>Identify untracked or unauthorised changes before they cause security or compliance issues.</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sprinto.com/data-library/change-management.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.
