> For the complete documentation index, see [llms.txt](https://help.metaforms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.metaforms.ai/design-collaboration/the-programming-workspace-sp.md).

# The Programming workspace (SP)

When you hand off a version from Design, the Survey Programmer (SP) scripts the survey from it in the **Programming** module. This page shows what the SP sees, so that you know what happens after the handoff.

## The SP gets the handoff

The project members who work in Programming get a notification: **Version ready for Programming**. The notification has an **Open Programming** button.

The first time the SP opens Programming, Metaforms shows **Choose a Questionnaire to Script**. Each version that you handed off shows with a **Ready for Programming** label. The SP can select **Preview questionnaire** to read it, then selects **Start scripting with V1**.

## The workspace

![The Programming workspace: the survey script on the left and the handed-off questionnaire on the right](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FUbhoPHCsZOmkK2p6fZkj%2F27-programming-workspace-v2.png?alt=media)

* **Left**: the survey script, with the **XML**, **Quota Sheet**, and **Clarifications** tabs.
* **Right**: the Word file of the questionnaire that you handed off. Your **Client** comments are in the Word file as Word comments.
* **Top**: **Test** opens the survey, and **Sync to Decipher** sends the script to Decipher.

{% hint style="info" %}
Comments on the Design page do not show in the Programming workspace. Only the **Client** comments go to the SP, inside the Word file. If the SP must know about an internal comment, make the change in the questionnaire and hand off a new version, or tell the SP directly.
{% endhint %}

## The SP marks the version ready

When the scripting is complete, the SP selects the version control at the top, then selects **Mark ready**. The dialog **Mark Version 1 ready?** has an **Open test link** button, so that the SP can check the survey one more time. Then the SP selects **Mark ready**.

Metaforms tells the project team that the survey is scripted, and the version status changes to **Survey Scripted**. Next, you check the survey on the **Survey Link**.

Next, [review the finished survey](/design-collaboration/survey-link-and-screenshots.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.metaforms.ai/design-collaboration/the-programming-workspace-sp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.