A matching language is not proof of a matching document

Imagine a fictional catalogue containing two German-language service guides. One explains an earlier offer for existing customers; the other describes the current offer for new enquiries. Selecting either solely because its language is German can send the reader to the wrong information.

Identify the document family

Record the service, audience, edition, approval state and document language separately. Decide which pages refer to the document and which genuine counterparts exist. An English explanation for a different audience may be related material without being an equivalent translation.

When a shared fact changes, flag the affected versions for review. A technically generated translation should not silently replace the last approved specialist wording. The business needs an explicit policy for what remains available while review is pending.

Follow the task beyond the page

Ask a representative reader to locate the right offer, understand the document's status and prepare an enquiry. Include the form labels, errors and reply expectations. Publishing a translated introduction does not establish support in that language or a complete journey.

Exercise the fallback

Open a page with no counterpart and use the language control. The interface should explain the actual destination, whether that is an index or related English material. It should not label an unrelated page as the same article.

Keep qualified language approval separate from implementing page relationships and layout. Technical coordination is in English unless otherwise agreed. See multilingual publishing for the service scope and the dependency worksheet to identify a missing reviewer.

Worked example: the right language, the wrong offer

Use a fictional service catalogue with two German-language guides. G-41 belongs to the assessment-only offer, edition 2, for existing customers. G-57 belongs to the assessment-and-implementation offer, edition 1, for new enquiries. Both are approved, but they are not interchangeable. Their shared language tells the application nothing about which promise the customer is considering.

A customer arrives from the implementation service page. In the faulty demonstration, a document picker asks for the first approved German file and returns G-41. The result is readable and passes a superficial language check. It nevertheless describes a scope that excludes implementation. The first wrong relationship is the selection rule, before the reader opens the PDF.

The corrected planning model identifies the offer and audience first, then selects the approved edition and requested language within that family. A missing German counterpart does not permit borrowing any other German guide. The business chooses whether to show an explicitly labelled English counterpart, ask the customer to enquire or temporarily withhold the download. The application must implement that choice honestly.

Exercise the correction without changing the offer

Prepare four catalogue records: the two above, an English counterpart of G-57 and a French G-57 revision awaiting approval. Ask the reviewer to select the implementation offer in German. It should resolve to G-57, not G-41. Selecting the assessment-only offer should still resolve to its own guide, demonstrating that the correction did not merely hard-code one preferred file.

Next, withdraw the German implementation edition in the fictional fixture. The result should follow the agreed missing-counterpart treatment. It must not silently select the assessment guide or present the pending French revision as approved. Record what the customer sees and which decision the business owner must make.

Finally, change a shared prerequisite and ask the editor to find affected page and document versions. The review is successful when the editor can distinguish related material, genuine equivalents and versions awaiting approval. It does not establish professional translation quality by itself. Retain the selected offer, audience, edition and language in the acceptance evidence so a later content change can be evaluated against the same relationship.