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

# Task Forms

> Collect customer information on project tasks and review each submission.

Attach a form to a project task to collect onboarding details, implementation requirements, or other information your team needs. Each task can have one form. Forms belong to ordinary tasks in active customer projects, rather than milestones.

## Add a form

Open the task, go to **Form**, and select **Add form**. Start with a blank form or choose **Start from templates** to use a starter or a published [form template](/product/form-templates).

Give the form a title and optional instructions, then add the questions your customer should answer.

| Question type | Use it for |
| - | - |
| Short text | A name or brief answer |
| Long text | Requirements or other detailed answers |
| Email | An email address |
| Number | A quantity or numeric value |
| Date | A date |
| Multiple choice | One answer from a list |
| Checkboxes | More than one answer from a list |

Mark questions as required where needed, add help text, and provide at least two populated options for choice questions.

## Show questions conditionally

Select **Add condition** on a question to show it only when an earlier answer matches. For example, ask about the customer's existing system only when they select a migration option.

Each question can have one condition referring to an earlier question. Available comparisons depend on the answer type.

Review the impact prompts when changing a question's type or position, or deleting a question or option. Those changes can require removing conditions that depend on it.

## Choose how customers respond

Under **Customer responses**, choose the policy that fits the request:

* **One response:** accept one submission for the attached form, across all recipients. Publishing a later version does not reset this allowance.
* **Allow updated responses:** let customers submit updates while preserving earlier responses. This is the default for a blank form.

## Save and publish

<Steps>
  <Step title="Review the draft">
    Check the questions, options, conditions, and response policy. If you use the form assistant, review its suggestions before **Accept & Apply**. Applying a suggestion changes the editor; it does not publish the form.
  </Step>

  <Step title="Save as draft">
    Save the current changes. Resolve any missing labels, incomplete options, or invalid conditions before continuing.
  </Step>

  <Step title="Publish">
    Select **Publish** once the saved form has at least one question. Unsaved changes must be saved first. After publication, return to the task and check the form's status.
  </Step>
</Steps>

Editing a published form creates a new draft version. Customers continue to see the published version until you publish the changes.

Publishing does not invite anyone or make the task visible. Customers also need access to the shared project and task; follow [Customer Portal](/product/customer-portal) to configure that access.

## Preview the published form

<Warning>
  **Preview as customer** opens the live published form. Submitting it creates a real response and can use the form's one-response allowance. It can also trigger the normal submission notifications.
</Warning>

Open **Preview as customer** to inspect the published questions and layout. Unsaved draft edits are not shown there. Avoid submitting sample answers to a form intended for a customer's only response.

## Review responses

Select **View responses** on the task. Choose a submission to read its answers, response number, form version, and submission date. Download a PDF when that option is available.

A submission completes the information request. It does not automatically complete the task's internal status. Review the answers and update the task as appropriate.

## Remove a form

Open the form's menu, select **Remove form**, and confirm. Removal stops access to the form and removes its response history from the task screen. Review or download the responses you need before removing it.

## FAQ

<AccordionGroup>
  <Accordion title="Why can't I publish?">
    Save the draft first. Check that it has at least one question, every question has a label, choice questions have enough options, and conditions have valid values. If publishing reports an error, keep the draft and retry once the issue is resolved.
  </Accordion>

  <Accordion title="Can I reuse these questions on another task?">
    Create a [form template](/product/form-templates) for a reusable question set. Each task receives an independent copy, which you publish separately.
  </Accordion>

  <Accordion title="Can a project template include forms?">
    Yes. Add forms to tasks while editing a [project template](/product/project-templates#include-forms). Check the copied forms' publication status when creating a customer project.
  </Accordion>
</AccordionGroup>


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