Record yourself performing a task, then turn the recording into a routine, a knowledge skill, AS-IS documentation, or a business task.

A recording captures one manual task so Delegate or Cartographer can turn it into something reusable afterward: a replayable routine, a generalized skill, Cartographer AS-IS documentation, or a business task. This guide covers the full lifecycle — preparing the task, recording it, and choosing what to build from it.

Record one clear, linear task rather than an entire business process. Good examples include:

If the process has several unrelated outcomes, record each one separately — smaller recordings are easier to review and reuse.

Before starting:

Do not deliberately record passwords, API keys, access tokens, one-time passwords, or personal or confidential data your organization hasn't approved for recording. Recording currently has no way to pause and resume — if sensitive information appears accidentally, stop the recording, and start a clean one rather than continuing.

You can start a recording from several entry points — the Create a recording option in the chat, or from Settings - Recordings - New recording.

Once started, a recording indicator shows it's in progress. Recording supports a microphone on/off toggle if you want to narrate while you work; there's no separate pause control yet.

Keep recordings under 1 GB — a shorter, focused recording also converts faster and is easier to review.

Complete the task from beginning to end, using the real sequence you want Delegate to understand:

Avoid exploratory clicks or detours you don't want repeated. If you're narrating, explain why you made a choice or what indicates the task succeeded — this helps later, whether you convert the recording into a routine or a skill.

Select Stop recording when the task is done. A review dialog opens with the recording named Untitled - date and time by default, a video preview, and the steps captured, total time, and number of apps used. Below that, an optional field lets you add up to 250 characters of context.

The recording is saved under %APPDATA%\UiPath\Delegate\Recordings\ — select Show in Explorer from the dialog to find it directly.

Check that:

If the recording is incomplete or contains sensitive information, make a new clean recording rather than relying on an unsafe capture.

The review dialog offers Build routine directly, plus a More menu with Build skill, Document AS-IS, and Add to business task:

If the recording was made to answer a task someone delegated to you, you can also use it directly as your answer to that request.

Select Build routine from the review dialog, or ask for it directly in chat, for example: "Convert my recording into a reusable routine with the customer name and date range as inputs."

Conversion typically takes around 5-20 minutes, depending on recording length, and runs in the background — you can keep using Delegate while it works. It analyzes the video and action trace to identify the steps, screenshots to clarify ambiguous UI, then generates the routine and lets you review inputs, paths, and accounts before it's ready to use.

During review, decide whether each recorded value should be a fixed constant, a user-provided input, or a value looked up from another source. Don't assume a customer name, date, or filename should stay hardcoded just because that's what appeared in the recording.

Select Build skill from the review dialog's More menu, or ask for it directly in chat, for example: "Create a knowledge skill from this recording that explains the decision rules."

Unlike a routine, a knowledge skill is written in prose rather than generated as a strict replay: it describes the goal, the applications involved, the decisions and business rules demonstrated, and named inputs rather than the exact values used. It normally doesn't embed per-step screenshots — it captures the method so Delegate can adapt when values or screens change.

Before using a routine or knowledge skill operationally: