# May 15th, 2026

We're excited to introduce the following updates to survey branching, in-page translations, and response completion.

***

#### 1. Branch Survey Pages Based on Who's Taking the Survey

Surveys can now adapt to each participant. Show or hide a page based on a participant's demographic data or an earlier answer, so every participant only sees the questions that apply to them.

**What's new:** The **Conditions** panel on the Design Survey page lets you set a rule for any survey page. The rule can reference a demographic field uploaded with your participant file (department, location, union status, tenure) or an earlier survey question. When a rule is applied, a small indicator icon appears on the page so you can tell at a glance which pages are branched. Conditions combine with AND logic, and you can chain multiple conditions on the same page.

<figure><img src="/files/1HUwuKyYULg5u7aCZuj7" alt=""><figcaption></figcaption></figure>

**Why it matters:** Until now, asking different questions of different groups meant building parallel surveys or sending separate invites. Branching keeps everything in one survey, in one report, while still giving each participant a tailored experience. Reporting is fully aware of branching: response counts at the page level reflect who actually saw the page, and key driver analysis automatically respects which participants answered which questions.

**How to use it:** Open your survey, click **Design Survey**, and click the page you want to branch. In the right-hand panel, open the **Conditions** tab and click the pencil next to **Make the page visible if**. Choose a demographic field or an earlier question, pick an operator, set the value, and click **Apply**.

[Branching Based on Demographics](/knowledge-base/survey-design-and-deployment/survey-logic-and-display-conditions-quick-start/branching-based-on-demographics.md)

#### 2. Edit Translations Directly on the Design Page

Multilingual surveys no longer require an export, an offline edit, and a re-import for every fix. You can now add languages, switch between them, and edit translated content in place.

**What's new:** The **Translation** dropdown in the top-right of the Design Survey page now offers **Import**, **Export**, and **Edit**. Choose **Edit**, pick a language, and the page enters translation mode with a banner at the top. Click any element on the page (titles, descriptions, questions, answer choices, long-form HTML instructions, and comment field labels) to edit its translated version. Edits save as you type. Click **EXIT TRANSLATION MODE** to return to the normal design view.

<figure><img src="/files/yWYCTqfeluBGDCwroadJ" alt=""><figcaption></figcaption></figure>

**Why it matters:** Translation cycles used to be a serial bottleneck. A typo in a French confidentiality statement meant a file export, a translator handoff, and a re-import before the survey could go out. The in-page editor handles small fixes in seconds and works for every content type on the page, including HTML-formatted instructions that were the hardest content to edit before.

**How to use it:** Open your survey, click **Design Survey**, then click the **Translation** dropdown and select **Edit**. Choose your language and click **OK**. Click any text on the page to edit it. When finished, click **EXIT TRANSLATION MODE**.

[Editing Translations on the Suvey Design Page](/knowledge-base/survey-design-and-deployment/creating-surveys-quick-start/adding-translations-to-a-survey/editing-translations-on-the-design-survey-page.md)

#### 3. Mark a Response as Complete at the Right Moment

Capture responses to your core questions even when participants drop out before reaching the end of the survey. Set a **Completion Trigger** on any question, and any participant who answers that question is counted as complete in reports.

**What's new:** A **Completion Trigger** section on the **General** page lets you choose any question in the survey as the point at which a response is marked complete. When a participant submits an answer to that question, their response is counted in reporting, even if they close the browser or stop before the end of the survey. The survey continues after the trigger fires, so any answers given on later pages are still saved.

<figure><img src="/files/HcOB5Fq1MVyqCxsx3uCT" alt=""><figcaption></figcaption></figure>

**Why it matters:** Most engagement surveys end with optional demographic questions. Participants often answer the core engagement section, then drop off before reaching the demographic tail. Without a completion trigger, those responses are recorded as incomplete and excluded from reports. The new trigger lets you decide what "complete" means for your survey, capturing the responses that matter while still allowing optional sections at the end.

**How to use it:** Open your survey, click **General**, and scroll to the **Completion Trigger** section. Click the **Completion trigger question** dropdown, select the question that should mark a response complete, and the setting saves automatically.

[Marking a Response as Complete at a Specific Question](/knowledge-base/survey-design-and-deployment/creating-surveys-quick-start/marking-a-response-as-complete-at-a-specific-question.md)

**Also in this release:**

* A read-only view of the Design Survey page when a survey is closed, so you can review the design without reopening the survey.
* Participant data export now works for surveys that collect responses through an open link.

**Getting started.** Open any survey and look for the new **Conditions** panel on the Design Survey page, the **Translation** dropdown in the top-right, and the **Completion Trigger** section on the General page.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.talentmap.com/knowledge-base/general/product-updates/may-15th-2026.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.