Project Transitions
Last updated: October 30, 2026
During your engagement with a project, you may be transitioned to another project due to factors such as client requirements, project completion, or temporary pauses. Project extensions are not guaranteed and depend on client needs and project availability.
What to Expect (Turing-Initiated Transitions)
To ensure full alignment, we will proactively communicate this with you.
Developer-Initiated Transitions
If you want to transition to a different project while currently active on another project, you have two options:
Discuss with your Project Manager first — Talk to your current PM to explore internal transition possibilities.
Resign from your current project — This will make your profile available to apply for other opportunities.
Important: Resigning from a current project does not guarantee placement on a new project.
You will receive a new Statement of Work (SOW) to accept to confirm your agreement with the terms and requirements of the new project.
Project transitions are handled through an internal transfer workflow that moves you directly from one project to another—no separate offboarding from your previous project is required.
Your credentials and access will remain active during this transition, ensuring a smooth and uninterrupted workflow. Once you complete initial onboarding, your ID verification, KYC, and banking information remain active and do not need to be redone when switching between projects. However, you will need to complete the required assessments again for each new project, even if you have previously completed assessments in the same language.
Need Help?
If you have any questions or concerns about project transitions, please contact our Team.