- Overview
- Quickstart
- Delegate
- Trust and compliance
- Governance
- Features
- Cartographer
- Cartographer overview
- The Cartographer interface
- Getting started with Cartographer
- Working with existing automations
- AS-IS (Current Process) documentation
- Providing documents to Cartographer
- Delegating a task
- TO-BE design and PDD generation
- Refining your PDD and the quality checklist
- Generating an SDD
- Sending SDDs to Automation Hub
- Delegate for Testing
- Reference
- Troubleshooting
- Backup and restore
The Discovery and Define as-is stages in Cartographer, covering the interview structure, confirming the process map, and generating an AS-IS document.
The Discovery and Define as-is stages capture the current state of your process through a conversational interview. Cartographer describes what it is building, asks targeted follow-up questions, and confirms a locked AS-IS process map before Design to-be begins.
What happens during Discovery and Define as-is
The interview is conversational — you describe the process in your own words and Cartographer asks targeted follow-up questions. You are never handed a blank form to fill in.
| Step | Area | What Cartographer is building |
|---|---|---|
| 1 | Process framing | Process name, objective, trigger, frequency, volume, and scope boundaries |
| 2 | Roles and systems | Every team, person, and application involved, and their relationship to each step |
| 3 | Step walkthrough | A step-by-step description of the process from trigger to completion |
| 4 | Business rules and decisions | Conditions, thresholds, approvals, and exception paths |
| 5 | Gaps and ambiguities | Questions the source material cannot answer, and deferred items flagged for later |
You do not need to cover these areas in strict order. Cartographer adapts to how you naturally describe the process — if you cover rules before steps, it reorganizes automatically.
How to give useful answers
| Topic | Weak answer | Strong answer |
|---|---|---|
| Trigger | "It starts when we get an invoice." | "An invoice PDF arrives in the AP mailbox. The system checks for it every 30 minutes on business days." |
| System | "We use SAP." | "We use SAP S/4HANA. The relevant transaction is MIRO for invoice posting and ME23N for PO lookup." |
| Rule | "High-value invoices need approval." | "Invoices over $50,000 require dual approval — Finance Manager and VP of Finance — before posting." |
| Exception | "Sometimes there are errors." | "If the PO number is missing, the invoice routes to the AP Clerk for manual research. Target resolution is 48 hours." |
If you cannot answer a question, say so explicitly — for example, "I don't know, mark that as a gap." Cartographer records it and moves on. Guessing produces inaccurate documentation that is harder to fix later.
Knowing when Define as-is is complete
Review the list of captured steps, tracked in the Checklist panel's FACTS (AS-IS) group, and the proposed current-state AS-IS diagram. Correct anything that is wrong before confirming the map — once confirmed, the map is locked and used as the basis for the Architect process document. The map is never a placeholder; it is your actual confirmed flowchart, embedded in the Process Design Document (PDD).
You can change the AS-IS capture in three ways:
- Tell Cartographer to add or make a change directly, for example: "Rename Step 2 as 'Patient match to Employee Sponsor record.'"
- Provide a new file that adds information, for example: "I've attached pages from the State Regulatory agency containing business rules we must comply with. See paragraphs 5.6 to 5.8."
- Edit the underlying knowledge directly from the Knowledge section in the sidebar.
"Looks good" is not confirmation. Say explicitly: "I confirm the process map" or "the map is correct" to lock it and complete Define as-is.
Generating an AS-IS document
You do not need to generate a standalone AS-IS document to continue to Design to-be — the confirmed map carries forward automatically. Generate one when:
- You need a baseline document for compliance or audit.
- You are building a training guide for current-state operations.
- You want stakeholder sign-off on the AS-IS (Current Process) state before designing the TO-BE (Future Design) state.
- You are not yet ready to design the future state.
The PDD is the default format, typically 30–50 pages. Two other formats are also available: a Standard Operating Procedure (SOP, 15–25 pages) and a Transformation Brief (3–5 pages, for executives). Fully custom, organization-specific templates are on the roadmap — see the custom-template workaround in Generating the PDD.
Every AS-IS document contains:
- Process overview — what the process does and why it matters
- Confirmed process map — the real embedded flowchart, never a placeholder
- Step-by-step walkthrough — a detailed description of each step
- Business rules — conditions, thresholds, and approval requirements
- Roles and systems — who does what and which tools are used
- Pain points — current challenges and bottlenecks identified during the interview
- Known gaps — questions deferred for resolution
- Source attribution — which source document each fact came from
Adding benchmarks (optional): The process atlas — a built-in, curated process knowledge base — includes documented benchmarks for most processes. Prompt the agent: "Search for and include process benchmarks from the process knowledge that are relevant for this process in the AS-IS (Current Process) documentation. Annotate each benchmark with a source where available."
Next steps
Continue to Delegating a task if you need input from other team members, or continue directly to TO-BE design and PDD generation.