# Getting started with Cartographer

> Prepare for a Cartographer session, configure the recommended model and execution mode settings, and start a business process analysis project.

## Before your first session

| What to have ready | Why it matters |
| --- | --- |
| A clear process name and one-sentence objective | Anchors the entire interview and prevents scope drift |
| Existing SOPs, process diagrams, or training materials | Upload during Phase 1 to accelerate documentation. See [Providing documents to Cartographer](providing-documents-to-cartographer.md). |
| Names of the systems and applications used | Required for the Systems section and the automation mode assessment |
| Any known decision points or business rules | Gives **Cartographer** a head start and reduces clarification questions. Business rules can be listed explicitly, such as a list, or implied, such as a decision point in an existing process diagram. |
| Current and target process metrics | Gives **Cartographer** an understanding of your business goals |
| Your organization's Process Design Document (PDD) template, if applicable | Upload at the start or end of a session to generate a custom-formatted output using template-creation skills |

:::tip
**Delegate** sessions persist, so you do not need to finish in one sitting. Pin your session in the sidebar immediately after you start it so you can resume later without losing context.
:::

## Model and LLM configuration

| Setting | Recommended value |
| --- | --- |
| Model (see [Choosing the LLM model](choosing-the-llm-model.md)) | GPT 5.4 |
| Approval mode (see [Local security configuration](local-security-configuration.md#approval-mode)) | Balanced — **Delegate** confirms before high-impact actions |
| [Screen context](local-security-configuration.md#screen-context) | Optional. Enable it if you want **Delegate** to see your attached apps directly, rather than relying only on the documents and screenshots you upload. |
| Communication style (**Settings > Behavior**) | Balanced or Detailed |

:::note
Model and approval mode are independent settings. The model controls which AI engine runs. Approval mode controls how much **Delegate** asks for confirmation before acting. Set both independently.

The model you select persists after you set it, so you do not need to reset it each session. Check it at the start of a new engagement to confirm it is still selected.
:::

:::important
Settings not currently exposed to end users include temperature, system prompt overrides, context window limits, token budgets, and bring-your-own-model. These are not available in the current **Delegate** interface. For organization-level LLM governance, such as model pinning, data residency, or model routing per skill, contact your UiPath administrator.
:::

## Starting a project

1. Open **Delegate**.
2. Select **New Business Process** (select **Business Process** in the sidebar, then select **+**). This tells **Delegate** you are going to use the **Cartographer** skills and features.
3. Provide project details such as name, description, and context, and add context project files if you have them.
4. Optional: review the skills enabled for the project. By default, only **Business Analyst** and **Knowledge Base** are enabled. Both must remain enabled.
5. Select **Create** to launch the project.

**Result:** A project begins with no tasks. Input files, skills, and project settings remain editable — find it under **Business Processes** in the sidebar, then select the options menu (⋮) next to its name:

![Sidebar showing the Business Processes list with Project options open next to a project name](https://dev-assets.cms.uipath.com/assets/images/delegate/business-processes-sidebar-584a64b3.webp)

## Starting a task

1. Approve or reject requests as they appear. Generally, approve requests to read and write within the project space. Review requests to read outside the project space more carefully, and consider write requests outside the project space with particular care — rejecting or denying access only guides the agent to work within a smaller boundary.

**Result:** **Cartographer** begins executing the skill, which includes setting up a wiki for the PDD project and reading the files you provided for context. As it consumes those documents, it checks its Process-Skills database for a match to apply UiPath proprietary process context, and shows you when a match was found, as a **Process Knowledge** tool card:

![Process Knowledge tool card showing the matched process context, its retrieval operation, and response](https://dev-assets.cms.uipath.com/assets/images/delegate/process-knowledge-tool-card-d4ea2873.webp)

:::note
It is normal for **Cartographer** to spend around 5 minutes extracting information. Stronger models run slower than smaller, faster ones — see [Choosing the LLM model](choosing-the-llm-model.md) for the available options.
:::

**Result:** **Cartographer** asks clarification questions to resolve ambiguities. You can respond by selecting one of the offered options, answering the question directly, or providing a document that answers the question — for example, an Excel table listing the business rules that apply at a step.

## Session and task persistence

Session-specific context, such as files opened or data extracted in the current conversation, does not persist unless the session is pinned. Always pin a **Cartographer** task before closing **Delegate**.

## Next steps

Continue to [AS-IS documentation](as-is-documentation.md) to begin Phase 1.