# Two-language request review card

Original fictional example for Overskill. This is a copy and task review, not a saved request or a translation service. Use it alongside the rendered example and the message-map CSV.

## Filled card: Bridge Repair

**Reader:** A customer requesting a wooden-chair repair in English or Spanish.

**Task:** Choose the item category, describe the problem, correct a missing description, review the request and understand the received-request message.

**Business boundary:** Receiving the request does not book an appointment. The sample reply-time wording is fictional business policy.

**Fixed identifiers:** `DEMO-R042` and category ID `chair` remain unchanged. The example supplies the item description in both languages; it does not translate customer-entered text.

| Variant | Aligned keys | Missing | Wrong meaning | Stale | Spanish values present | Decision |
| --- | ---: | ---: | ---: | ---: | ---: | --- |
| Diagnostic, source revision 1 | 10 | 1 | 1 | 0 | 11 of 12 | Hold: fix K07 and K10 |
| Corrected, source revision 1 | 12 | 0 | 0 | 0 | 12 of 12 | Author-proposed correction; check meaning and the rendered task |
| K12 source changed | 11 | 0 | 0 | 1 | 12 of 12 | Hold K12 for the new source meaning |

These counts classify twelve customer-message keys, not every word on the teaching page. A populated value is not evidence of a correct translation or completed customer task.

### K07 — missing required-field message

- Source: “Describe the item before continuing.”
- Diagnostic Spanish: empty.
- The example visibly labels an English fallback. The fallback does not complete the Spanish task.
- Proposed Spanish: “Describe el objeto antes de continuar.”
- Check: can the customer tell what must be corrected and continue after correcting it?

### K10 — wrong confirmation

- Source: “Request received”.
- Diagnostic Spanish: “Cita confirmada” (a confirmed appointment).
- Proposed Spanish: “Solicitud recibida”.
- Preserve K11: “Esto no es una cita confirmada.”
- Check: both languages must describe receipt of a request, not an appointment or a promise of a slot.

### K12 — a changed source

- Source revision 1: “We will reply within two working days.”
- Spanish tied to revision 1: “Te responderemos en un plazo de dos días laborables.”
- Source revision 2: “We will reply within three working days.”
- Keep the revision-1 Spanish visible as stale. Do not silently label it current because it is nonempty.
- Proposed revision-2 Spanish: “Te responderemos en un plazo de tres días laborables.”
- The other eleven keys still refer to their unchanged source revision 1.

**Real Overskill build, saved request, booking and language persistence:** Not tested.

**Actual reader observation:** Not tested. The supplied example is fixed, contains no submission or storage, and makes no request to a business.

## Blank card

- Business and one customer task: ______
- Intended languages and regional wording: ______
- Starting screen and ending meaning: ______
- What the confirmation must **not** imply: ______
- Current source version/date: ______
- Fixed record/category IDs that must not be translated: ______
- Who supplies or reviews translated wording: ______
- How customer-entered text is handled (preserved, separately translated, or unresolved): ______

| Message key / screen | Exact source / source revision | Translation / reviewed source revision | Missing, wrong, stale or aligned? | Proposed change | Actual task observation |
| --- | --- | --- | --- | --- | --- |
| ______ | ______ | ______ | ______ | ______ | Not tested |
| ______ | ______ | ______ | ______ | ______ | Not tested |
| ______ | ______ | ______ | ______ | ______ | Not tested |

- Required-field and failure messages included: ______
- Confirmation and next action included: ______
- Explicit fallback behavior and whether it blocks this language: ______
- Device/browser, keyboard path and exact observed result: ______
- Language/meaning reviewer and remaining questions: ______
- Next source change: keys affected ______; unchanged keys ______

## Carry one change into Overskill

For an existing app, name the screen and message keys, state what the customer must understand, supply the corrected copy and ask to preserve the remaining behavior. Then repeat the whole task in the resulting app.

If a separate build is appropriate, open [the app brief builder](https://www.overskill.com/learn#brief-builder), edit its inputs and review the generated brief before choosing **Start build**. Copy is secondary. The link imports no message map or example; supply the relevant materials separately. Account access, credits and actual app behavior remain separate checks.