Tour In-country reviews for software localisation, with UI context
Rigi by XTM helps you run in-country reviews against the real interface, so local teams can validate wording, tone, and fit before release. This tour shows how reviewers comment, approve, and keep decisions tied to the right screen.
Trusted by teams at world’s leading organizations
Take the in-country review tour
Rigi helps you run in-country reviews against the real interface, so local teams can validate wording, tone, and fit before release. This tour shows how reviewers comment, approve, and keep decisions tied to the right screen.
Get local sign-off without long email threads
In-country reviews often fail when reviewers only see strings in a list. In this tour, you’ll see how Rigi lets reviewers check translations on screen, leave clear feedback, and approve changes with a visible audit of what was accepted.
In-country review steps inside Rigi
A walkthrough of how teams run in-country reviews using a visual software localisation tool.
You’ll see how to:
-
Invite in-country reviewers to the right content
-
Review translations on screen for clarity and fit
-
Comment on specific strings with clear context
-
Resolve feedback and keep changes traceable
-
Approve or request updates by screen or section
-
Export outcomes so delivery is clear to all teams
Try an in-country review on one key flow
Pick a high-visibility screen or feature and we’ll show how Rigi supports reviewer feedback and approval in context.
What teams achieve with in-country reviews in Rigi
Teams shorten review cycles, reduce unclear feedback, and catch UI wording issues earlier because reviewers see the interface, not just the strings. Decisions are easier to track, and approvals are clearer for release planning.
Faster localization cycles
with automated workflowsCountries trusted
by Teams in WorldwideMore consistent
Localization DeploymentsFAQ's
What is an in-country review in software localisation?
An in-country review is a validation step where local market reviewers check translated UI text to confirm it reads naturally and matches local expectations. In Rigi, in-country reviews happen with screen context so reviewers can see where each string appears.
Who should take part in an in-country review?
Common reviewers include regional marketing, local product owners, in-country support leads, and country managers. The right reviewers depend on the product and the risk of incorrect UI wording in that market.
What should reviewers check during in-country reviews?
Reviewers typically check meaning, tone, terminology, and whether the translation fits the UI. They also confirm that local requirements are met, such as preferred product naming or formal vs informal language.
How does Rigi support in-country reviews?
Rigi links strings to screen context so reviewers can validate translations against the UI. Reviewers can add comments and approvals tied to the relevant screen, helping teams act on feedback faster.
What is the difference between in-country review and linguistic QA?
Linguistic QA focuses on language quality and accuracy, usually handled by linguists. In-country review focuses on local suitability and acceptance, typically done by market stakeholders who represent the local audience and business context.
How is reviewer feedback managed in Rigi?
Feedback is captured against the relevant string or screen so it stays contextual. Teams can track what has been addressed and what still needs action, which helps prevent repeated questions and conflicting edits.
Can in-country reviews be used for frequent releases?
Yes, especially when you focus review on high-visibility areas or key flows. A targeted in-country review step helps teams validate changes without reviewing every string in every release.
Tour our platform and features
Book a demo and run an in-country review in context
See how local reviewers can approve UI translations with screen context, clear feedback, and tracked outcomes.
