# Create a journey (/docs/guides/create-journey)



A journey should describe one outcome a customer expects from an agent.

<DocImage src="/images/product/journeys.jpg" alt="Journeys list with test-case counts, readiness status, Run controls, and View controls" caption="Journeys show whether a saved task is ready to run and how many test cases cover it." />

## Write the description [#write-the-description]

Open **Journeys**, select **Create journey**, and write the task in ordinary customer language. Include:

* Who is asking
* What they want to accomplish
* The final state they should see
* Any confirmation that must occur
* Any duplicate, unauthorized, or harmful state that must not occur
* What a safe failure response should say or do

```text title="Good journey description"
A signed-in customer asks to cancel an order that has not shipped.
Confirm the order number before cancellation. Verify that the order is canceled
and that no second cancellation record exists. If the order has shipped, do not
cancel it and explain the next available option.
```

## Review the plan [#review-the-plan]

<Steps>
  <Step>
    ### Check the intent [#check-the-intent]

    Confirm that the plan describes the same customer task and does not add unrelated work.
  </Step>

  <Step>
    ### Check success [#check-success]

    The final state must be observable. Replace phrases such as "the agent handled it" with a product state that can be checked.
  </Step>

  <Step>
    ### Check protected behavior [#check-protected-behavior]

    Add forbidden actions or states, required confirmation, authorization boundaries, and duplicate-effect protection.
  </Step>

  <Step>
    ### Check the failure response [#check-the-failure-response]

    Define safe recovery, escalation, or noncompletion. The agent should not claim success when the state is unknown.
  </Step>

  <Step>
    ### Check coverage [#check-coverage]

    Review normal, edge, failure, uncertainty, and recovery cases. Keep cases that change the decision or exercise a meaningful risk.
  </Step>
</Steps>

<DocImage src="/images/product/journey-detail.jpg" alt="Journey detail with success, protected behavior, failure response, and coverage sections" caption="Edit the plan until each section matches the real customer task." />

## Approval and updates [#approval-and-updates]

Submit a journey for review when your workspace requires approval. Later edits create a new version. Existing results continue to reference the version they used.

If an update changes required actions or success criteria, review coverage and run the journey again.

Continue with [Run an assessment](/docs/guides/run-an-assessment).