To estimate and count the translation cost, keep track of the most active members, view the project status along with existing issues, and view historical data of the previously generated reports, open your project and go to the Reports tab.
You can analyze your project data with the following reports:
This report allows you to analyze the translation progress and see what method was used for translation (translated by a person, MT, or TM). You can also check if there are any issues with Quality Assurance (QA) checks and strings.
By hovering over the progress line, you’ll see the details on translated and approved words.
QA check issues are defined by QA checks parameters configured in the project’s Settings > Quality assurance. QA issues can be checked and resolved by proofreaders in the Editor.
The Unresolved issues section allows you to analyze the following parameters:
You can find all unresolved issues in Editor using the With Unresolved Issues filter option.
You can find the total number of texts in the project under the Project Size. You can also see the numbers of such texts:
This report might be generated based on the following parameters: words, strings, characters, and characters with spaces.
This section helps to analyze the overall project progress. You can check translation, proofreading, and source strings activities for different periods.
There are four time periods available: day, week, 30 days, and a year. The graphs are generated based on the parameter you choose for the Project Size.
Hover over the dots on the graphs to check more details:
Hover over the bars on the Source strings activity chart to see how many texts in source strings were added, deleted, and updated.
Click on the parameter title to hide a section from the graph and to bring it back when needed.
Use this option to analyze just specific parameters on the graph.
You can also highlight a specific section on the graph by hovering over the parameter title.
Use this report to plan your budget and count the approximate cost of translations. Set the translation and approval rates to see the cost for untranslated and not approved strings in the project.
You can generate a Cost Estimate report based on the following filters:
To generate the Cost Estimate report, follow these steps:
You can set the prices for Base rates (full translation, proofread) and configure Net Rate Schemes (percentage of the full translation rate paid for translation using TM suggestions).
In the Base Rates section, you can set rates for the following types of work:
In the Net Rate Schemes section, in addition to the base rates, you can set the percentage of the full translation rate to be paid for translations made using TM suggestions of various TM Match types. By default, you can configure the percentage of the full translation rate for the following TM Match types:
101 (perfect) – for translations made using Perfect match TM suggestions (source strings are identical to TM suggestion by text and context).
100 – for translations made using 100% match TM suggestions (source strings are identical to TM suggestion only by text).
You can also add your own TM match types, specifying the preferred percentage of text similarity and the percentage of the full translation rate to be paid for such a translation.
To add your own TM match types, follow these steps:
In addition to base rates that are applied to all languages by default, you can add individual rates for specific languages. To add individual rates, click Add individual rates.
To select the language or languages for individual rates, click the drop-down menu, and select the ones you need. You can create as many individual rates as you need.
If you plan to work with multiple rate configurations, save them as templates by clicking Save as > New rates template, then specify the template name and click Save.
When saving a new template you can choose the template visibility using the following options:
Share with all project members – makes the template visible to all translators within the project. Regardless of the number of translators or their different rates, they all will have access to the template. It can include both general rates and individual rates for specific languages and translators, along with a net rate scheme. This transparency promotes clarity in pricing, allowing translators to review rates, generate reports on their translations, and calculate cost estimates. The key benefit is that translators understand the net rate scheme and can apply their base rate, even if it’s not included in the template.
Share with managers within the organization – makes the template global, visible only to managers across all projects of the organization. This option streamlines rate consistency across various projects.
If neither of the options is selected, the template remains visible only to managers within the current project, limiting access to a select group of project members. These options provide flexibility in controlling who can view and use the rate template to accommodate different organizational preferences.
Saved templates allows you to quickly switch between different configurations for report generation.
Click Templates to view and manage your saved rate templates.
Select Include pre-translated strings if you want to include pre-translated strings in a Cost Estimate report. By default, this option is selected.
For example, you have an untranslated string Validate your username
in your project. You generate a Cost Estimate report with the Include pre-translated strings option selected. This string will be included in the Cost Estimate. Then you pre-translate this string via TM or MT engine and once again generate a Cost Estimate report with the Include pre-translated strings option selected. This time, the pre-translated string Validate your username
won’t be included in the Cost Estimate report.
On the other hand, with the Include pre-translated strings option cleared, the string Validate your username
will be included in the Cost Estimate report both times, when untranslated and when pre-translated via TM or MT engine.
Internal Fuzzy Matches – Fuzzy TM matches found among the untranslated strings that potentially can be added to TM. For example, if the first string in the file is Validate your username
, and the last one is Validate your username again
, there will be an internal fuzzy match.
To get a more deliberate report that includes a prediction of internal fuzzy matches, select Calculate Internal Fuzzy Matches.
This way, all the internal matches would be counted to see how many strings can be added to TM if the strings are translated one by one as listed. Keep in mind that calculations are approximate because strings might be translated in a different order.
When the report is generated, you will see the following amounts:
To download the Cost Estimate report, click Export and select the preferred export format (CSV, XLSX, or JSON).
Use this report to calculate the actual translation cost based on the completed job.
You can generate a Translation Cost report based on the following filters:
To generate the Translation Cost report, follow these steps:
You can set the prices for Base rates (full translation, proofread) and configure Net Rate Schemes (percentage of the full translation rate paid for translation using TM suggestions, MT suggestions, and existing translations).
In the Base Rates section, you can set rates for the following types of work:
In the Net Rate Schemes section, in addition to the base rates, you can set the percentage of the full translation rate to be paid for translations made using TM suggestions, MT suggestions, and other translations of various Match types.
By default, you can configure the percentage of the full translation rate for the following match types categories:
TM Match types:
101 (perfect) – for translations made using Perfect match TM suggestions (source strings are identical to TM suggestion by text and context).
100 – for translations made using 100% match TM suggestions (source strings are identical to TM suggestion only by text).
MT Match types:
100 – for translations made using 100% match MT suggestions (new suggested translations are identical to MT suggestion).
Other translations types:
100 – for translations made using existing translations (new suggested translations are identical to the existing translations).
If a string has a combination of TM and MT suggestions and existing translations, the new translation is counted at the lowest Net Rate Scheme value. For example, if a string has a 101% (perfect) TM match suggestion (10% of the full translation rate) and a 100% MT match suggestion (5% of the full translation rate), the new translation added to this string will be counted at a 5% of the full translation rate.
You can also add your own TM, MT, and Other translations match types, specifying the preferred percentage of text similarity and the percentage of the full translation rate to be paid for such a translation.
To add your own match types, follow these steps:
In addition to base rates that are applied to all languages and users by default, you can add individual rates for specific languages and users. To add individual rates, click Add individual rates.
To select the languages and members for individual rates, click the drop-down menus, and select the ones you need. You can create as many individual rates as you need.
When the report is generated, you will see the following amounts:
To download the Translation Cost report, click Export report and select the preferred export format (CSV, XLSX, or JSON).
In addition to the Translation Cost report, which is based on the Contribution Raw Data and grouped by languages, you can retrieve this detailed contribution raw data using the Generate Report (Contribution Raw Data schema) or via the Raw Report Data app available on the Crowdin Store. This allows you to generate your own custom report according to your specific requirements.
The Contribution Raw Data report provides various columns depending on the selected mode (translations, approvals, or votes). Each column offers specific insights, for example source string text hash
, which is useful for identifying changes in source strings despite having the same stringId
. It’s important to note that multiple records can exist for the same stringId
if the source hash or plural form varies.
For repeated translations by the same user on the same source string, into the same target language, the same plural form, and if the source text has not changed, only the translationId
, targetUnits
, and updatedAt
columns will update in the report statistics. Deleted translations are also included in the count. Understanding these columns can help you better interpret the raw data and optimize your localization process.
View the available report columns and their mode applicability (i.e., translations, approvals, and votes) in the following table:
Name | Available in Report Mode | Description |
---|---|---|
userId | Translations, Approvals, Votes | Type: Numeric identifier of a user who added a translation. |
languageId | Translations, Approvals, Votes | Type: Target language identifier (Crowdin language code (e.g., uk)). |
stringId | Translations, Approvals, Votes | Type: Numeric string identifier in Crowdin project. |
translationId | Translations, Approvals, Votes | Type: Numeric identifier of the translation in Crowdin project. |
fileId | Translations, Approvals, Votes | Type: Numeric file identifier in Crowdin project where the source string is stored. |
filePath | Translations, Approvals, Votes | Type: Path to the file that contains the source string (e.g., /main/docs/index.md). |
pluralForm | Translations, Approvals, Votes | Type: Translation plural form (each plural form is displayed as a separate record in the report). |
sourceStringTextHash | Translations, Approvals, Votes | Type: Hash of the source string. |
mtEngine | Translations, Approvals, Votes | Type: MT engine name from which a translation was provided. |
mtId | Translations, Approvals, Votes | Type: Numeric MT engine identifier. |
tmName | Translations, Approvals, Votes | Type: Translation memory name from which a translation was provided. |
tmId | Translations, Approvals, Votes | Type: Numeric translation memory identifier. |
preTranslated | Translations, Approvals, Votes | Type: Specifies if a translation was applied via pre-translation. |
tmMatch | Translations | Type: The highest match value of the translation with other TM suggestions, if any. |
mtMatch | Translations | Type: The highest match value of the translation with other MT suggestions, if any. |
suggestionMatch | Translations | Type: The highest match value of the translation with suggestions from other translators, if any. |
sourceUnits | Translations, Approvals, Votes | Type: Specifies the number of words in the source text (available only if |
targetUnits | Translations, Approvals, Votes | Type: Specifies the number of words in the translation (available only if |
createdAt | Translations, Approvals, Votes | Type: Specifies the date when the string was initially translated. |
updatedAt | Translations, Approvals, Votes | Type: Specifies the date when the last translation was added. |
mark | Votes | Type: A vote mark that indicates how the translation rating has changed (e.g., if a translation has been voted up or down, or if the vote has been canceled). |
Report that allows you to check all the project members and see who contributed the most.
Default parameters:
Re-sort the members by clicking on the needed parameter. For example, if you want to analyze members by their proofreading activity, click on the Approved parameter to redo sorting.
To generate a custom list of top members, choose the text unit (words, strings, characters, or characters with spaces) and set a date range for which you want to see the activity.
To view the information about a specific member, enter their name or username in the Search field.
Top Members list has the following columns:
To show or hide some columns, click on the upper-right side of the table and select the preferred ones.
To download the report, use the Export button in the upper-right corner.
The Archive section allows you to access the records of previously generated Cost estimate and Translation cost reports, providing a convenient way to review historical data.
This section also eliminates the need to wait for a report generation to complete. You can initiate a report generation and return to it later at your convenience. Within the Archive, you can review the report summary and, if necessary, download it in various supported file formats.
Each project within an organization has its own independent archive section with previously generated reports available only to project members with manager permissions (or higher).
Reports generated by translators based on their contributions are not added to the archives.
To view the summary of the previously generated reports (i.e., archive records), follow these steps:
To export the previously generated reports, follow these steps:
To delete the previously generated reports, follow these steps:
Besides UI, reports Archive can also be managed using the API methods from the Reports sections: