Hello Alex,
Thank you for your detailed feedback on AI pre-translation, post-editing tasks, and reporting.
Crowdin’s task types focus on the action performed (like “Proofreading” for reviewing content), rather than the source of the pre-translation (AI or MT). This is why post-editing tasks using AI pre-translation fall under “Proofreading” in Crowdin.
You’re correct that AI/MT pre-translated content is initially counted under “Translation,” while the human post-editing effort is under “Proofreading.” This aligns with our statuses that are used for translation exporting, API, web-hooks, etc (translated/approved):
While there isn’t a separate “Post-editing” task type currently, here are the best workarounds:
-
Use very clear task names or descriptions, e.g., “Post-editing: [Content Type],” to instruct linguists and clarify the task type for vendors.
-
Ensure your vendor agreements explicitly define MTPE tasks and their rates, even if labeled as “Proofreading” in Crowdin.
-
In Enterprise, reports or API data might help differentiate these tasks.
While don’t plan to change this logic, at least for now, I will certainly pass this important feedback to our product development team for future consideration.
Also, here are some apps you might find useful: