How do I deploy a form version to test or live mode?

Last updated: August 24, 2026

Every form has at least one version, and every version sits in one of three states: draft, published, or deployed to a mode. Deploying is what makes a version active for candidates — and you do it right from the form, on the card for the version you want.

Publishing ≠ deploying. A published version that hasn't been deployed shows as Deployable (Read-only) and candidates can't see it yet. This is the most common reason a form doesn't appear where you expect it.

Deploying affects only the mode you're currently in. Test mode is for validation before you roll out to live placements — see 📄 Understanding test mode and live mode for what else differs between the two.

Deploy a version to the mode you're in

  1. Open the form. Go to Forms and select the form. It opens on the Versions tab, with a card for every version.

  2. Confirm which mode you're in. Check the Test mode toggle in the organization selector at the top of the sidebar. It's amber when test mode is on.

  3. Find the version you want and read its badge. Draft (Editable) means it hasn't been published yet — deploying will publish it and deploy it in one action. Deployable (Read-only) means it's published but not yet deployed to this mode. Deployed (Read-only) means it's already active here, so there's no deploy button; use New Draft to make changes instead.

  4. Click Deploy (Test Mode) or Deploy (Live Mode) on that version's card. The button names whichever mode you're in.

  5. Fill in the dialog. Deploying a draft asks for Release Notes and shows which languages will publish with it. Deploying an already-published version skips straight to confirmation.

  6. Choose what happens to tasks already in flight. Under Upgrade tasks to use this version?, pick Do not upgrade any tasks, Only upgrade incomplete tasks that have not yet been opened, or Upgrade all incomplete tasks. This only touches tasks in the mode you're deploying to.

  7. Confirm. Click Deploy (test) or Deploy (live). The badge changes to Deployed (Read-only), and new tasks in that mode are created under this version.

You can also reach the same card through Version History if you're already looking at a specific version — the deploy button behaves identically there.

Test the version before it goes live

The fastest way to check a deployed version is to assign it straight to a test employee as a task. That isolates the form itself from your policy setup, so anything that looks wrong is the form.

  1. Open your test employee. Go to Employees and select the employee you use for testing, or create one.

  2. Open the Tasks tab and click Create task. The button sits to the right of the tabs.

  3. Choose the form under Form and create the task. Set a Due Date if the behavior you're testing depends on one.

  4. Walk the candidate experience. Open the task and confirm fields, conditional logic, prefills, and signatures behave the way you expect.

Test the assignment path too

Creating a task directly skips policy evaluation. When you also want to confirm the right people get this form automatically, run a placement through it.

A placement only creates tasks if a policy says so. Onboarded decides which tasks a placement needs by evaluating your policies against it — a deployed form on its own generates nothing. If the placement comes back with no tasks, confirm a policy in this mode attaches the form and that its conditions match the placement data you entered.

  1. Create a placement with test data that matches the conditions on the policy that should assign this form.

  2. Confirm the expected tasks appear. The placement should generate the tasks your policies call for, on the version you just deployed.

Deploy to live mode (when ready)

  1. Switch to live mode. Open the organization selector at the top of the sidebar and turn the Test mode toggle off.

  2. Go back to the form's Versions tab. The same version now shows Deployable (Read-only), because it hasn't been deployed to live mode yet.

  3. Click Deploy (Live Mode). Live mode adds one option test mode doesn't: Deprecate all currently published blueprint versions. Select it when this version replaces everything that came before, and leave it clear when older versions should stay available.

  4. Confirm. The badge changes to Deployed (Read-only). New placements in live mode now use this version.

Roll back or re-deploy

There's no undeploy. To back out, deploy an earlier published version over the top of it — each version tracks its deployment status independently for test and live modes.

  • Deploying an older version does not delete tasks created under the newer one. Existing tasks stay as they are.

  • New placements created after the re-deployment use the newly deployed version.

  • Rolling back in one mode does not affect the other.

Next steps

Once your form is deployed, the next step is to assign it to policies so it shows up in your onboarding flow. See 📄 How do I build a policy? for guidance.

Related articles: