Write ambiguous values explicitly
A date such as 04/05 can mean different days to different readers. Spell out the month when the audience spans regions. Name the currency next to an amount and state whether a duration means calendar days or working days. When quoting a time, include the relevant timezone. Preserve the original order identifier instead of reformatting it as a number.
Compare meaning, not matching typography
Arabic and English may display digits and punctuation differently while preserving the same fact. Review the underlying quantity and the condition attached to it. 'Three days after dispatch' is not equivalent to 'three days after purchase.' For US and Saudi readers, avoid inserting a conversion rate, tax treatment or delivery promise that the approved source does not provide.
Fictional worked example
Fictional source: 'Dispatch by October 6; delivery usually takes 2–3 working days after dispatch.' A translation fails if it promises arrival on October 6 or drops 'working.' Build a review row with dispatch date, duration, day type and starting event, then compare both replies against it. This checks operational accuracy even when the wording differs.
Action checklist
- Spell out ambiguous dates and identify the timezone.
- Label amounts with their currency and preserve identifiers.
- Check the event that starts each duration.
- Review Arabic and English against the same structured fact row.