- What happens during the Analysis step
-
What you can do in the Analysis step
1) Review the analysis summary
5) Remove content items from the project
The Analysis step is the first stage of every Dynamic Project. At this stage, Localization Hub analyzes your content to detect changes, creates jobs for updated items, and allows you to review the results before sending anything to translation.
Dynamic Projects remain in the Analysis step until you confirm that the detected changes are correct and choose to proceed.
What happens during the Analysis step
When a Dynamic Project is created, Localization Hub automatically performs Content Analysis, comparing the current content in your CMS with the version last translated through Localization Hub.
Based on this comparison, the system identifies:
New or updated content → jobs are created
Unchanged content → no jobs are created
Untranslated items → jobs are created for missing languages
The Analysis step shows you everything the system detected and gives you full control before the project moves forward.
What you can do in the Analysis step
The Analysis step contains multiple tools and actions to help you validate results and manage the content before translation begins.
1. Review the analysis summary
how many items and fields contain changes
how many words were updated
a breakdown by criteria categories such as New properties, Outdated properties, Untranslated pages or blocks
the date and time when Content Analysis was last run
how many jobs were generated during the last run
📖 Read more about Content Analysis.
2. Update analysis results
To refresh analysis results, click Rerun Analysis in the Content Analysis summary box. This reruns analysis for all content in the project. Depending on the project size, the process may take some time, and progress will be displayed in the summary box.
If you know exactly which content has changed, you can rerun analysis for a smaller scope. Select specific content items in the Analysis tab or specific jobs in the Jobs tab, then click Rerun Analysis from the action bar above the table. Only the selected items will be reanalyzed. This option becomes available after the initial full analysis has completed.
You can monitor analysis progress in the Content Analysis summary box and temporarily pause the analysis if needed.
While jobs are being updated, you’ll see an update indicator next to the affected jobs. During this time, job details—such as requested due date, localized fields, and briefing—cannot be modified. However, the jobs remain available for viewing.
3. Adjust analysis parameters
Some analysis parameters can be updated. What you can change depends on whether the project was created with Analyze all content or Select specific content.
If the project uses "Analyze all content", you can update:
- Analysis Criteria
- Target Languages
- Services for Content Analysis
Updating Target Languages or Services affects only newly ordered content that matches the updated settings.
Existing jobs and analyzed content will remain in the project, even if they no longer match the current selection. If you manually remove content items from the project, they will not reappear in this project unless their target languages and services are still included in the project scope.
If the project uses "Select specific content", you can update only:
- Analysis Criteria
The content scope, target languages, and services cannot be changed after creation.
To make changes, click (the pencil icon) to edit the criteria, target languages, or services.
Click (the save icon) icon to apply your changes.
💡To apply the new settings, rerun Content Analysis. Existing jobs remain, but if a job no longer meets any of the selected criteria, its Analysis Match will switch to "Unchanged".
4. Change the Project Mode
You can switch between:
One-time — analysis runs only once unless you trigger it manually
Continuous — analysis runs automatically on a set schedule using the saved parameters
You can change the project mode at any time while the project remains Analysis status.
When you create a Dynamic project using Continuous mode for the first time, the automated action is created which you can adjust to your schedule in Automations.
To adjust the schedule, click the automation name to open it in Workspace Settings → Automations, then update the Schedule for field and save your changes.
5. Remove content items from the project
From the Analysis Status tab, you can remove content items from the analysis scope if they no longer need to be monitored or translated.
Select one or more content items using the checkboxes. Click Remove in the action bar above the table.
When you select one or more content items, you can choose to Remove from table or Remove from workspace:
Remove from table
Removes the selected items from the Selected content table for this project.
The items may reappear after you rerun Content Analysis if changes are still detected and the items match the project’s scope.
Existing jobs created for these items remain in the project.
💡 Use this option to temporarily clean up the table by removing items you’ve already reviewed or don’t need to act on right now, without changing the project scope or affecting workspace-wide tracking. The removed items can reappear in future analysis runs if changes are still detected.
Remove from workspace
Removes the selected items from the analysis scope across all Dynamic Projects in the workspace that are in New or Analysis status.
The items will no longer be analyzed or trigger job creation in any Dynamic Project in this workspace.
Projects that already have jobs In Progress or beyond are not affected.
The items can be added back to analysis only if they are ordered for translation again and match the project’s analysis settings.
💡Use this option when the content should no longer be tracked or translated through Dynamic Projects at the workspace level.
6. Remove jobs from a project
From the Jobs tab, you can remove one or more jobs from a project if they are no longer needed.
Select one or more content items using the checkboxes. Click Remove in the action bar above the table.
What happens when you remove jobs
The job is removed from the project.
Any edits made within the job (such as requested due date, localized fields, or briefing changes) are permanently lost.
The underlying content item is not removed from the project’s analysis scope.
Important to know
If you rerun Content Analysis and the content item still matches the project’s analysis settings, the same job may be created again automatically.
Newly created jobs will be treated as new jobs — previous edits will not be restored.
Removing a job does not prevent the content from being analyzed or included in future analysis runs.
💡If you want to prevent a content item from being analyzed or recreated as a job in the future, remove the content item from the project (or from the workspace) using the Analysis Status tab instead of removing the job.
7. Review and manage jobs
You can open individual jobs to review detected changes, adjust job settings, and control which content is sent for translation.
Open a job and review differences
To open a job, click the Job ID in the Jobs tab. This opens the job detail view, where you can review changes detected by Content Analysis.
In the job view, you can compare:
the current source version retrieved from the CMS
the source version that was last translated
The comparison can be viewed using different modes, depending on your needs:
Split View – shows the current and previously translated versions side by side
Show Changes – highlights only the modified parts of the content
HTML mode – displays the raw structured or rich-text markup
Source mode – shows a technical field-level representation of the content
Each field includes visual indicators that help you quickly understand its status:
Outdated badge for fields that have changed
Unchanged badge for fields without changes
Field-level word count
Side-by-side comparison of current and last translated content
This view helps you clearly understand what has changed and what requires translation.
Localize or unlocalize fields
Within the job view, you can control whether individual fields are included in the translation job.
For each field, you can toggle:
Localize: Yes – the field will be included when the job is exported to the translation tool
Localize: No – the field will be excluded from translation
This is useful for fields that should not be translated, such as IDs, placeholders, system values, or image URLs.
Edit job details
From the job detail view, you can also update key job parameters:
Requested due date
Sets or updates the expected delivery date. Translators can see this date in Localization Hub and, if supported, in the connected translation tool.Job briefing (instructions)
Add or edit instructions for translators. The briefing is visible in the job and is sent to the translation tool or CAT tool (depending on your integration).
Save changes
After reviewing differences, adjusting localized fields, or editing job details, you can choose how broadly your changes should be applied.
⚠️ Important: The selected save option applies to all changes made on the page. This includes field localization settings, briefing updates, and other editable job parameters. Changes will be applied according to the save option you choose.
Three save options are available:
Save for job
Applies the changes only to the job you are currently editing.
💡When to use: Choose this option when you want to update instructions or settings for a single job only and do not want the changes to affect other jobs.
Save for all languages
Applies the changes to all jobs for the same content item across different target languages within the same project.
💡When to use: Use this option when you want to add the same instructions or settings for all language versions of the same content without opening each job individually.
Save for content type
Applies the changes to all jobs whose parent items belong to the same content type as the currently opened job.
💡When to use: Select this option when you want to apply consistent instructions or settings to all jobs related to the same content type, across languages and items.
8. Move the project forward
Once you finish reviewing and adjusting the Analysis results, you can move the project to the next workflow step.
Click Proceed to Step in the top-right corner.
This opens the Transition To view, where you configure how the project moves forward.
Configure the transition
In the transition view, you can:
Choose the target workflow step
Select the step you want to move the project to (for example, In Progress).
Select the service to order
Choose the translation service that will be used for the next step.
Set the requested due date
This date will be applied only to the project. Individual job due dates will not be affected.
Assign users
These settings help with project ownership and internal tracking.
Set the project name
The project number stays the same during transition. For a user-friendly title, you can provide a name.
Choose the project type
Personal Project — visible only to you and users with permission to access all projects
Shared Project — visible to other users in the workspace
Select the export scope
💡If you prefer not to export jobs at this stage, keep the default export settings and adjust them later when you export the jobs.
Only changed content — exports only content detected as changed by Content Analysis
Exports only content that Content Analysis identified as changed, based on the selected export mode:
Entire pages (all content and blocks)
Exports the full page, including all blocks and fields, if at least one field on the page has changed.
Best when translators need full page context.
Full parent item or child block
Exports the complete parent item or the specific child block that contains changed fields.
Balances context with reduced content volume.
Only changed fields
Exports only the fields that were modified since the last translation.
Most efficient option with the lowest word count, but minimal context.
💡 These options affect what is sent to the translation tool, not which jobs exist in the project. Jobs are created based on Content Analysis results.
All content — exports all content included in the project, regardless of changes
Select Cost Center
Select a cost center from the dropdown. If no options are available, it means no cost center is linked to the Service or in case you selected the existing project.
Export behavior
If Export jobs immediately is enabled, jobs will be sent to the translation tool as soon as the project transitions to the next step.
You can also configure grouping options to control how jobs are combined in the translation tool and define the name of the resulting grouped job.
Complete the transition
Click Proceed confirm the transition.
Comments
0 comments
Please sign in to leave a comment.