About project types

When a user creates a project based on a project type, the project automatically inherits certain settings from it, such as translation memories, terminology databases, available locales, or processing settings.

These settings refer to:
  • The source locale from which users can translate.
  • The due dates of the tasks in the project.
  • The workgroup responsible for the project.
  • The default workflow that the project will use (the same for all locales or a different one for certain locales).
  • The default file type configuration that the project will use (the same for all locales or a different one for certain locales).
  • The default cost model that the project will use (the same for all locales or a different one for certain locales).
  • The Studio QA Checker profile.
  • The translation memory that the project will use—whether it uses the one that the client uses (if configured) or a specific one (the same for all locales or a different one for certain locales).
  • The terminology database that the project will use—whether it uses the terminology database that the client uses (if configured) or a specific one (the same for all locales or a different one for certain locales).
  • Any custom AIS properties or project attributes that the user who creates the project needs to provide.
  • The default machine translation configuration that the project will use (the same for all locales or a different one for certain locales).
  • The default quality model (the same for all locales or a different one for certain locales).

When you create a quote, you can also select a project type, to give the language service provider (LSP) more information such as the workflow, the workgroup, the cost model, or the file type configuration. However, the LSP may use a different project type to provide the quote.

Term validation projects do not use project types.