> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcdemo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Review a demo before it goes live

> Test the story, access, and viewer experience from start to finish.

Previewing a draft and opening the published demo answer different questions. The draft preview helps you fix the experience; the published link confirms what the audience can actually see.

## Review the draft

Work through the experience as a first-time viewer:

1. **Story:** Does the opening make the outcome clear? Does each step contribute to it?
2. **Actions:** Follow every hotspot, branch, flow ending, and sandbox link you intend to offer. Check that the destination makes sense and that the path has an ending.
3. **Content:** Check spelling, labels, screenshots, HTML states, audio, and any customer data. See [prepare a safe capture](https://docs.arcdemo.io/guides/capture-safely.md).
4. **Presentation:** Check the guide placement and legibility on desktop and phone. Try the demo without sound; keep the important instruction available in text.
5. **Next action:** Open the destination of each CTA. Check that it is suitable for the intended audience.

Ask a teammate unfamiliar with the story to try it without coaching. Use [Feedback](https://docs.arcdemo.io/editor/comments.md) to record the step and the question behind each comment, then resolve the issues that affect the viewer's experience.

### Work through the paths systematically

Make a small test table before you begin. For each row, record the starting point, action, and expected result, then actually follow it in preview. For example:

| Start | Action | Expected result |
| - | - | - |
| Opening step | Follow the main guide | The next screen shows the promised result. |
| Audience choice | Select each option separately | Each choice opens the right path without relying on another path's context. |
| Search step | Enter the example value and a different value | The intended match advances; the other value does not unexpectedly advance. |
| Final step | Select the CTA | The destination opens and is appropriate for the audience. |

Add rows for the paths your demo actually offers. If there is a timer, try leaving before it fires and returning. If there is a sandbox, follow the intended links and a return route. If the demo is personalized, test a supplied value and its default. These checks catch different failures; reaching the final screen on the main path alone does not verify every choice.

## Publish and verify

Select **Publish** when the draft is ready. Then open the copied link in a separate browser session and test it as the intended viewer. For an embed, test the actual host page as well as ArcDemo's preview. Check access restrictions, loading, sizing, the first and last steps, and every important route.

A saved edit is not the same as a published edit. If a viewer reports an old version, check for **Unpublished changes**, publish the draft, and reload the viewer's page. See [Publish and share](https://docs.arcdemo.io/share/publish.md).

### When the published result differs from the preview

First confirm that the latest draft was published, then reopen the intended share link in a separate browser session. Verify that you copied the correct link and that its access settings and personalization values match the test. For an embed, also reload and check the actual host page; an editor preview cannot prove that the host page is using the intended embed. If the problem occurs only for a restricted link, review that link's settings before changing the demo itself.

## Keep a record of the review

Record who owns the demo, where it is shared, and when it should be checked again. When product screens change, follow [Keep a demo current](https://docs.arcdemo.io/guides/maintain-a-demo.md). If a change needs to be reversed, inspect [History](https://docs.arcdemo.io/editor/version-history.md) before restoring a draft.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.