Translation Brief and Target Text · Lesson 4

Keep a Message Consistent Across Card, Button and Confirmation

4 min read

Lesson objectives

  • Match promise, action and condition across three points in a user journey.
  • Identify the point that needs content-owner clarification before release.
  • Deliver a decision matrix linking each source to its target and conflict risk.
Reading tools

Translate the Whole Journey, Not an Isolated Line

A fictional registration journey has three messages: a card invites an application before Friday, a button submits it, and a later message says the application was received for eligibility review. Each line can look sound alone. Replacing the button with ‘Confirm your place’, however, contradicts both the card and receipt. Read the messages as a sequence. For each one, record the established fact, requested action and promise the evidence cannot support. The reader experiences a path rather than separate translation files. A successful form submission does not establish acceptance when eligibility review still follows.

Build a three-row matrix: source, target and what the user expects after the action. On the card, ‘Apply’ sends details for review. On the button, ‘Submit application’ retains that act. On the receipt, ‘We received your application’ confirms transmission only. If a draft says ‘Registration successful’, determine whether successful refers to data transfer or eligibility approval. Hold wording that can promise approval when the source has not settled that distinction. Consistency does not require identical words at every point; it requires stable scope of fact and action.

Separate content conflict from style difference. The card may say ‘Send a visit request’ and the button ‘Submit request’; the expressions differ but the action does not. ‘Book now’ implies a settled place unsupported by the brief. If the button file and email file disagree, do not silently edit the email to match the button. Trace each string to its source version and ask the content owner a narrow question. If an approved update establishes immediate place confirmation, review all three rows together; changing only the button would leave the journey inconsistent.

Lesson summary

Compare the same promise across card, button and confirmation, and mark any result unseen in the matching build.