# TO-BE design and PDD generation > Phase 2 TO-BE design and Phase 3 PDD generation in Cartographer, covering automation mode assignment, the future-state process map, and generating the Process Design Document. Phase 2 designs the future state of your process on top of the confirmed AS-IS map. Phase 3 combines both states into a downloadable Process Design Document (PDD). ## Prerequisites Your AS-IS process map is confirmed and locked. See [AS-IS documentation](as-is-documentation.md). ## Starting Phase 2 Phase 2 typically takes one to two hours. You can pause at any point and resume in a later session. To start, say: "Continue to Phase 2" or "Let's design the future state." ## Assigning automation modes The first task in Phase 2 is assigning an automation mode to each step in your process. **Cartographer** shows you each step and asks you to select how it will be handled after automation. | Mode | What it means | When to use it | | --- | --- | --- | | Fully Automated | Runs without human involvement — rule-based, system-to-system | Steps with clear rules where an API or RPA bot handles everything | | Assisted | Runs alongside a person who triggers or guides it | Steps where a person needs to initiate or review in real time | | Agent | AI-driven — handles variation or judgment at runtime | Steps with variable inputs, natural language, or dynamic decisions | | Human Review | Automated with a mandatory human approval step | Steps with compliance, financial, or exception sign-off requirements | | Manual | Stays fully human | Physical actions, policy judgment, or steps out of scope for now | Example assignments for a lab charge routing process: * Receive order file from LIS — Fully Automated * Validate charge codes against payer rules — Agent * Route to billing queue — Fully Automated * Approve exception charges over threshold — Human Review * Reconcile end-of-day discrepancies — Assisted :::tip If you are unsure of a mode, choose Manual as a conservative default and mark it as provisional. You can change any mode before or after the PDD is generated. ::: ## Answering design questions After the delivery model is set, **Cartographer** asks a small number of targeted questions specific to your process design. These are not a fixed checklist — only questions that are genuinely needed: * Trigger — does the process start on a schedule or when an event occurs? * Human review points — who approves exceptions and how do they receive notifications? * Error handling — what happens if a system is unavailable or data is missing? Answer what you know. If something is not yet decided, say so — it is recorded as an open item in the PDD. ## Confirming the future-state process map Once the delivery model is set, **Cartographer** generates a future-state process map, color-coded by automation mode: | Color | Mode | | --- | --- | | Blue | Fully Automated | | Teal | Assisted | | Brown | Agent | | Dark red | Human Review | | Green | Manual | :::important Confirming the future-state map is a mandatory checkpoint. **Cartographer** does not draft detailed TO-BE step documentation until you confirm the map. A change to the map shape after this point requires re-drafting affected sections, so take the time to get it right. ::: Iterate on the map until it accurately reflects your design. When you are satisfied, say: "I confirm the future-state map." ## Reviewing the drafted future-state detail With the map confirmed, **Cartographer** drafts: * Future-state steps — one entry per step with trigger, inputs, outputs, and assigned mode * Exception handling — documented only where your TO-BE handling differs from AS-IS * Benefits — a qualitative narrative covering cycle time, error reduction, capacity freed, and auditability :::note The benefits section describes qualitative outcomes only. It does not include ROI calculations, cost savings in dollars, or payback period projections. Add a quantified business case manually after download. ::: Review the drafted detail and request corrections before confirming Phase 2 is complete. Once you confirm, say "Phase 2 is complete" or "ready to generate the PDD" to move to Phase 3. ## Generating the PDD ### Document metadata Before generating the PDD, **Cartographer** asks for four values in a single prompt: | Field | Default | Notes | | --- | --- | --- | | Process name | The process you documented | Use the official name as it appears on document covers | | Organization name | None, required | For example, "HealthCo — Revenue Cycle" | | Author | None | Name or names to appear on the cover and header | | Document version | 1.0 | Increment to 0.x during review cycles, and promote to 1.0 at final sign-off | :::tip Use a 0.x version number during stakeholder review. Promote to 1.0 only when the document has received final sign-off. This avoids confusion when you share draft versions. ::: ### Choosing a document format At Phase 3 entry, you can choose a document format. If you skip this step, **Cartographer** generates a standard PDD. | Format | Best for | Typical length | | --- | --- | --- | | PDD | Full automation design documentation for developers, architects, and Centers of Excellence | 30–50 pages | | Standard Operating Procedure (SOP) (coming soon) | Future-state how-to guide for operations teams and training | 15–25 pages | | Transformation Brief (coming soon) | Executive summary of current-to-future change | 3–5 pages | | Custom template (coming soon) | Your organization's own format | Variable | ### What every PDD contains **AS-IS content, from Phase 1:** * Current-state process overview and narrative * Current-state process map — real embedded flowchart * Step-by-step current workflow * Entities, roles, and systems used today * Business rules and decision points * Pain points and current-state gaps **TO-BE content, from Phase 2:** * Future-state process overview * Future-state process map, color-coded by automation mode * Step-by-step future workflow with mode per step * Delivery model table — step, current mode, future mode * Exception handling changes * Qualitative benefits narrative **Supporting sections, auto-generated:** * Source attribution (coming soon) — where each fact came from * Open gaps and deferred items from the Phase 1 gap register * Roles and responsibilities * Referenced documentation ### Reviewing and downloading After generation, which typically takes two to five minutes, the PDD appears in the **Delegate** document panel with: * A live preview of all sections * "Refine section" links at the bottom of each section for targeted updates * Screenshot placeholders where system screenshots would appear, filled from any screen recordings you attached in Phase 1 **Result:** When you are satisfied with the content, select **Download** to save a `.docx` file. The downloaded file always reflects your most recent draft, including any refinements you made in the panel. ## Next steps Continue to [Refining your PDD and the quality checklist](refining-and-quality-checklist.md).