Skip to main content
Continuous project type

Sometimes a project doesn't have an end date

Triin Elias avatar
Written by Triin Elias
Updated over a week ago

In addition to a classic recruitment project that ends with a new hire, you can create continuous projects in Teamdash.

Common use cases for using the Continuous project type:

  • continuously open positions

    • the position has a high turnover

    • the same position is active in multiple locations

  • to gather unsolicited applicants

    • this is a great option to collect applicants who apply via your career site and add them to your talent pool without any designated project for the moment.

How to create a continuous project?

You can start as usual by creating a new project. In the Project Edit view, you find a toggle to switch on the Continuous project (always accepting candidates) option.

By switching the project type to Continuous, the project Deadline field is replaced with the option to set a GDPR consent length for project candidates.

This is necessary because without having a project-based timeline, the software cannot trace if the consent is valid by the project status. Therefore, you can set the GDPR consent length in advance and it applies to all incoming profiles.

If a profile is added to your Continuous project, its GDPR status will remain valid for the set period. After that, the GDPR status will automatically change and the profile should be included in your set database management, whether it is managed by you or automatically by Teamdash GDPR automation.
​
​How will the Continuous type project show on the dashboard?

You will see a yellow "continuous" icon on the project preview. In addition, to keep your time-to-hire statistics correct, continuous projects are not measured by active days.
​

What happens if a candidate who is in the Continuous project applies again?


The profile will automatically move back to the Submissions stage, and they can move through your recruitment funnel to get the best candidate experience once again.

Did this answer your question?