> For the complete documentation index, see [llms.txt](https://docs.changeup.com/app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.changeup.com/app/changeup-dms/implementation-overview.md).

# Implementation Overview

Implementing ChangeUp is straightforward. Follow this outline to be on the right track. Breaking down the project into three phases: **Planning**, **Integration**, and **Test & QA** historically work well.

## Checklist

### Planning

The planning phase is critical to get all stakeholders on the same page, set expectations, and uncover any risks as early as possible:

* [ ] **Define Teams** - With enterprise partners, this typically involves CSR, Product, UX/UI, Engineering, Accounting, and Legal.
* [ ] **Scoping Questions** - Decide on topics that ChangeUp will provide before integration starts.
* [ ] **Project Timeline** - Refine the project timeline based on discovery during scoping questions.

### Integration

This is where the hands-on work really starts. As long as planning has been completed, integration will go smoothly.

* [ ] Finalize UX/UI Design
* [ ] Plan for Downstream System 
* [ ] [Technical Implementation](#technical-implementation)

### Test & QA

ChangeUp widget(s) have been tested in the partner sandbox environment, and the flow of donations in internal partner systems is configured.

* [ ] Switch to [Live Environment](/app/changeup-dms/widget-setup/test-and-live-environments.md)
* [ ] Confirm Data Transfer from [Post Transaction](/app/changeup-dms/widget-setup/implement-the-post-checkout-webhook.md)
* [ ] QA and Launch 🚀

## Technical Implementation

Following the framework above, the steps to going live in your application are:

1. [Create a widget](/app/changeup-dms/widget-setup/create-a-widget.md)
2. [Configure the widget](/app/changeup-dms/widget-setup/configure-donate-at-checkout.md) with charities, donation type, and other settings
3. Copy [Installation](/app/changeup-dms/widget-setup/install-widget.md) code
4. Copy into your app
5. Test & QA
6. Go live


---

# 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.changeup.com/app/changeup-dms/implementation-overview.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.