Skip to main content
All CollectionsForms
The Automatic Form
The Automatic Form

Use one default Application Form for job ads

Triin Elias avatar
Written by Triin Elias
Updated over 5 months ago

As introduced in the Forms Menu article, a Teamdash Form can be set to two different types by the Candidate Target Stage:

  • Automatic - inherit from landing

    • the newest option for a seamless and quick workflow

  • A specific Project Name/Project Stage (ID)

    • a legacy solution

    • effective to create a custom application form for confidential projects

This article focuses on the Teamdash Automatic Form type.

Creating an automatic form

You can create a form by navigating to the Forms menu within the Settings section.

The Edit Form view is in two columns. On the left side, you have the Builder where you can create and edit all the fields for your form. On the right side, you have the Preview to see how the form will look to the candidates.

The Builder column starts with two important fields: Title and Candidate Target Stage.​

  • Title

    • internal name in Teamdash

    • could refer to the general purpose of the Form, e.g "Basic Application Form / ENG".

  • Candidate Target Stage

    • default option "Automatic - inherit from landing"

    • keep the Automatic option to use the Form throughout different landing pages.

Using one Automatic Form for multiple job ads

When creating a landing page, you can include the Form block to offer a quick and easy way to apply. After adding a Form block, choose the preferred Automatic Form:
​

  • Add your Automatic Form inside a landing page

  • Click Publish to open the Review panel

    • The Review panel offers to choose a Project - link the landing page with the regarding project.

    • This enabled Teamdash to automatically sort candidates through landing pages into the correct projects, while using the same form.
      ​

Creating multiple Automatic Forms

The Automatic Form reliefs users from the need to create a new form for each project. But it keeps the freedom to create different Forms for various use cases:

  • Application Forms with specific screening questions and other dedicated field settings.

  • Forms to collect screening question answers at a later recruitment stage.

  • Forms for submitting home tasks.

  • Forms to gather feedback on candidate experience.

Many Form functionalities are enabled through the merge tag called form_url.

Did this answer your question?