Know who does the work
The personas involved and the stages the work moves through.

UiPath Cartographer turns scattered process knowledge into the Map of Work, the definition your documents and automations come from.
UiPath Cartographer turns scattered process knowledge into the Map of Work, the definition your documents and automations come from.
UiPath Cartographer turns scattered process knowledge into the Map of Work—a versioned, readable definition of how your business runs.
A structured account of the objects, rules, exceptions, and judgment behind a process, rather than prose buried in a document.
One definition the whole organization works from. Every change is owned, versioned, and traceable, so what was decided and who signed off stays answerable.
Runtime decisions feed back into the Map of Work, and every process mapped seeds the next, so understanding compounds instead of going stale.
How a scattered set of procedures and recordings becomes one approved definition of the work.
Teams spend weeks interviewing and writing documentation before anything ships, and you often cannot say how work needs to transform until a first attempt exposes the gaps.
Discovery becomes a guided conversation instead of weeks of interviews, so projects reach the build sooner and the backlog stops growing.
The exceptions, the workarounds, and the reasons a process works the way it does get written down and owned, rather than carried in a few people's heads.
One governed definition with a named owner, full version history, and a record of real decisions, so what is true and who approved it stays answerable.
The design documents and the build are generated from the same definition, so developers and coding agents stop re-specifying edge cases by hand.
The Map of Work is a living, readable, versioned definition of how a process runs, held in Open Knowledge Format (OKF) and owned by your organization.
Permissions on publish, plain-language diffs between versions, rollback, a named owner and approver, and provenance on every statement.
The personas involved and the stages the work moves through.
The applications involved and the data objects the process creates, reads, and changes.
The business rules and compliance obligations the process has to follow.
The paths the work takes when something does not go the usual way.
The reasoning behind decisions, including the calls experienced people rarely record.
The outcomes and key performance indicators the process is measured on.

Drop in the procedures, recordings, and policies you already have. UiPath Cartographer reconciles them, flags where they disagree, and asks only what it cannot work out.

UiPath Cartographer names the business objects, captures the rules and exceptions, and builds the Map of Work. You review and approve every fact before anything moves downstream.

Drop in the procedures, recordings, and policies you already have. UiPath Cartographer reconciles them, flags where they disagree, and asks only what it cannot work out.

UiPath Cartographer names the business objects, captures the rules and exceptions, and builds the Map of Work. You review and approve every fact before anything moves downstream.

Exporting a mapped process produces the process design document (PDD) for sign-off and the solution design document (SDD) for the builder. Change the Map of Work and regenerate.

The Decision Ledger records the decisions people make at runtime and feeds that judgment back, so an exception approval becomes part of the next revision.

Exporting a mapped process produces the process design document (PDD) for sign-off and the solution design document (SDD) for the builder. Change the Map of Work and regenerate.

The Decision Ledger records the decisions people make at runtime and feeds that judgment back, so an exception approval becomes part of the next revision.
Discovery is not a solo job. Here is where each role picks it up.
BUSINESS ANALYSTS
UiPath Cartographer asks the missing questions and drafts the Map of Work. You review, approve, and design how a process should look like instead of authoring documents by hand, and the deliverables you used to write are generated automatically.
BUSINESS PROCESS OWNERS
A faithful, living definition of how your process actually runs, including the judgment your team applies, kept in step with the system that runs it.
DEVELOPERS AND BUILDERS
Coding agents and Maestro build from the same Map of Work the business approved, so the handoff carries less ambiguity and fewer edge cases get re-specified by hand.
UiPath Cartographer defines the work. These are the products that build it, run it, and assist alongside it.
ORCHESTRATION
Runs the processes UiPath Cartographer defines, coordinating agents, robots, and people across long-running work.
Maestro artifacts are generated from the same Map of Work, so what runs matches what the business approved.
BUILD
Where developers and coding agents turn an approved Map of Work into working automations, without re-specifying the edge cases by hand.
The generated solution design document is the input, so the build starts from what the business already signed off.
ASSISTANCE
The general-purpose assistant UiPath Cartographer is built on, sharing the same identity, audit, and control plane.
Route a question to the person who knows the answer and it opens in their own Delegate with the context already there.
CODE-FIRST
Point a coding agent at an approved Map of Work and it generates the working artifacts, including the Case Plan that Maestro runs.
UiPath Cartographer turns scattered process knowledge into one governed Map of Work: a sourced, versioned definition of how a process runs today and how it should run next. From that Map, Cartographer generates the PDD and build-ready SDD that coding agents use to implement the solution on UiPath Maestro.
No. Process mining is a complementary approach. UiPath Process Mining shows what happened in your event logs. UiPath Cartographer captures the intent, rules, exceptions, and human judgment behind the work and produces a definition you can build and audit from. Use Process Mining for visibility and Cartographer for defining what a process should look like.
No. The process design document and solution design document are outputs of the Map of Work, never the source of truth. Because both are generated from one definition, they cannot drift apart. Change a business rule in the Map of Work and regenerate, rather than editing two documents by hand.
No. It changes what the job involves. Analysts become the cartographers who own and maintain the Map of Work. UiPath Cartographer runs the discovery conversation and drafts the structure, but it assists and never approves. Every decision about what is true stays with a person.
The Map of Work is a first-class governed artifact. It carries permissions on publish, plain-language diffs between versions, rollback, a named owner and a named approver, and role-based access control. Every statement keeps its provenance, so where a rule came from and who signed off is always answerable.
UiPath Cartographer is available, get started now.