HELP US MAKE DOTSUPER MORE USEFUL

Can we learn from your visit?

Privacy notice

LTRLS Learning Through Real-Life Scenarios

The two documents do not agree

Reconcile quantities, numerals, dates and revisions across six fictional document decisions. Learn when to correct extraction, clarify instructions or release an order.

6 fictional cases20–30 minutes solo; 45–60 with a team (estimates)Arabic–English business documents; no rule of legal language precedence context
Start experience

No account needed. Work alone or discuss with a team.

Source documents are reconciled before a downstream release.
dotSuper. Original illustration for this learning experience.. Original dotSuper material. Contact dotSuper for reuse permissions. Third-party sources retain their own terms.

What you will practise

Make the trade-off visible.

Trace important fields to the approved source and resolve material disagreement before commitment. Correct transcription, document authority and business approval are separate checks.

  • Distinguish extraction, unit conversion, source conflict and authorisation.
  • Identify critical fields and test whole-document usability.
  • Resolve exceptions without unnecessarily stopping unrelated work.

Built for the people making the call

Order coordinatorsProcurement teamsDocument-AI project ownersArabic–English operations teams

Original fictional educational cases. All companies, prices, volumes and outcomes are illustrative. Sources support the stated principles, not claimed customer results. Completion is a learning record, not a professional assessment.

From the exercise to the business

What a better decision could change.

What you will learn

Explain why a field is reliable and what must happen when sources disagree.

Potential business value

Reduce avoidable ordering and fulfilment errors while directing review to material uncertainty.

How the value could happen

Source traceability → correct field interpretation → authorised resolution → accurate downstream action.

Measures to examine

  • Critical-field errors per document
  • Documents requiring material correction
  • Time to resolve document exceptions
  • Errors discovered after order release

Keep these limits in view

  • A language or timestamp does not establish authority by itself.
  • High field accuracy can hide unusable documents.
  • Review effort must be measured alongside extraction speed.

A useful next step: Define the critical fields and authorised source for one document workflow before evaluating automation.

Explore the companion method
  1. 01

    Read the situation

    Identify the purpose, people and consequences.

  2. 02

    Make your choice

    Confirm a response before opening the reasoning.

  3. 03

    Question the control

    Discuss what would need to change in a real workflow.

  4. 04

    Leave with a card

    Record an owner, evidence, approval conditions and a stop point.

LTRLS / Practise before the real decision

A situation. A choice. A better question.

A neat summary can still contain an unsafe order. Compare short synthetic documents, using the supplied English glosses, and decide what can proceed.

6 fictional cases20–30 minutes solo; 45–60 with a team (estimates)No account, no countdown

Progress and notes stay in this page’s memory. Refreshing, leaving or closing the page loses them. Use anonymous examples and roles.

Running this with a team?
  • Supply the English gloss beside every Arabic excerpt. Do not score Arabic language fluency.
  • Ask learners to classify the problem before proposing a correction.
  • A source-language difference should never become a cultural stereotype or an assumed authority rule.

Prefer to read?

The complete case notes.

The same situations and reasoning, without the interactive flow.

Open all 6 cases

Case 01

Different units, the same quantity

The English request specifies 120 pieces. The Arabic order states: «الكمية: ١٢ علبة. تحتوي كل علبة على ١٠ قطع.» The supplied gloss is: “Quantity: 12 boxes. Each box contains 10 pieces.” Product identity and pack size are confirmed. An assistant flags a 120-versus-12 mismatch.

What should the coordinator do with the quantity field?

  • Use 120 because English should always take precedence.
  • Record 12 boxes × 10 pieces = 120 pieces and clear this quantity exception.
  • Enter 12 pieces because the Arabic document is the order.
  • Hold the order until both documents display an identical number.

Recommended response for this scenario

Record 12 boxes × 10 pieces = 120 pieces and clear this quantity exception.

Both sources specify 120 pieces once the unit is normalised. Preserve the box count and pack conversion in the record. Clearing this quantity exception does not validate the rest of the order. Each material field retains its own evidence.

Why each choice matters

Use 120 because English should always take precedence.
The quantity is supported by unit conversion, not language precedence.
Record 12 boxes × 10 pieces = 120 pieces and clear this quantity exception.
The documents express an equivalent quantity. Other fields still require their own checks.
Enter 12 pieces because the Arabic document is the order.
This drops the packaging unit and understates quantity tenfold.
Hold the order until both documents display an identical number.
Equivalent units can be reconciled without rewriting both documents when the conversion is confirmed.

Practical control: Store the original quantity, original unit, conversion evidence and normalised quantity.

Discuss: What would change if pack size were not confirmed?

Case 02

One missing numeral changes the order

An approved source field reads «الكمية: ١٥٠ قطعة». The supplied gloss is “Quantity: 150 pieces.” The extracted summary says 15 pieces and reports high confidence. The source and its approval status are clear.

Which correction is justified by the available evidence?

  • Keep 15 because the confidence is high.
  • Use an intermediate quantity until someone confirms the number.
  • Ask the customer to issue a new order before correcting the transcription.
  • Correct the extraction to 150, log the error and check any downstream draft that used 15.

Recommended response for this scenario

Correct the extraction to 150, log the error and check any downstream draft that used 15.

The source supports 150 pieces. Correct the extracted field, retain the source reference and identify affected downstream drafts. A confidence value does not override clear evidence. Record this failure for the workflow’s evaluation set.

Why each choice matters

Keep 15 because the confidence is high.
Confidence is not independent evidence that the transcription matches the source.
Use an intermediate quantity until someone confirms the number.
An invented compromise quantity has no documentary basis.
Ask the customer to issue a new order before correcting the transcription.
The approved source is clear; this is an extraction error rather than conflicting instructions.
Correct the extraction to 150, log the error and check any downstream draft that used 15.
This fixes the derived value while preserving the approved source and its traceability.

Practical control: Link each critical extracted field to its source and propagate reviewed corrections to dependent drafts.

Discuss: What would you inspect if a purchase order had already been created from the summary?

Case 03

Both dates were read correctly

The English quotation says delivery on 3 October 2026. The Arabic order says «موعد التسليم: ٥ أكتوبر ٢٠٢٦», glossed as “Delivery date: 5 October 2026.” Both were transcribed correctly. Neither record establishes that the parties agreed to the changed date.

What is the best next action?

  • Ask the authorised commercial owner to resolve the date disagreement and record the agreement.
  • Use whichever file has the latest modification timestamp.
  • Use the earlier date because it is safer for the customer.
  • Run another translation and accept its preferred date.

Recommended response for this scenario

Ask the authorised commercial owner to resolve the date disagreement and record the agreement.

Correct reading has exposed a real conflict. Resolve it with the authorised parties before promising delivery. Keep both sources and the resolution record. Do not assign precedence because of language or choose a date that merely seems convenient.

Why each choice matters

Ask the authorised commercial owner to resolve the date disagreement and record the agreement.
The uncertainty concerns the instruction, not the transcription.
Use whichever file has the latest modification timestamp.
A timestamp does not establish mutual agreement or change authority.
Use the earlier date because it is safer for the customer.
The supplier may not have committed to that date.
Run another translation and accept its preferred date.
Translation cannot decide which commercial instruction was authorised.

Practical control: Classify source conflicts separately from extraction errors and route them to an owner who can resolve the business instruction.

Discuss: Which record would establish that the supplier accepted the revised date?

Case 04

The newest attachment is not approved

The approved order is revision two for 120 pieces. A later email attaches revision three for 180 pieces and labels it “draft for discussion.” The assistant chooses revision three because it is newer. No authorised quantity change is recorded.

Which source should govern the current order?

  • Revision three because a later timestamp supersedes earlier content.
  • Combine revision three’s quantity with revision two’s price.
  • Keep revision two as the approved basis and route revision three as a proposed change.
  • Delete revision three so it cannot affect any later decision.

Recommended response for this scenario

Keep revision two as the approved basis and route revision three as a proposed change.

Revision two remains the approved basis. Record revision three as a pending proposal and obtain the required change decision. Preserve the relationship between versions. If the customer has withdrawn the current order, that fact also requires a recorded decision.

Why each choice matters

Revision three because a later timestamp supersedes earlier content.
This confuses recency with approval.
Combine revision three’s quantity with revision two’s price.
The resulting order is a new combination that nobody approved.
Keep revision two as the approved basis and route revision three as a proposed change.
This preserves the current authority while allowing a legitimate revision to be considered.
Delete revision three so it cannot affect any later decision.
The draft is useful evidence of a proposed change and should retain its status.

Practical control: Track revision, approval status, authoriser, effective scope and superseded records separately.

Discuss: What evidence would make revision three the correct basis for release?

Case 05

Field accuracy hides document failures

A test has 100 documents with ten checked fields each. Twenty field errors occur in twenty different documents. Three errors affect critical quantities. The proposed release policy permits no unresolved critical-field error. The vendor reports 98% field accuracy and requests automatic posting.

What does the test support?

  • Automatic posting because 98% field accuracy exceeds a common benchmark.
  • Report 98% field accuracy, 80 fully correct documents and the critical errors; resolve release controls before expansion.
  • Treat only two documents as affected because the field error rate is 2%.
  • Reject all document automation permanently.

Recommended response for this scenario

Report 98% field accuracy, 80 fully correct documents and the critical errors; resolve release controls before expansion.

There are 1,000 checked fields and 980 are correct. Only 80 documents have no checked-field error. Three critical quantity errors breach the proposed release condition. Test correction and review controls on representative documents before expanding automatic posting.

Why each choice matters

Automatic posting because 98% field accuracy exceeds a common benchmark.
No universal benchmark was established, and the stated release policy is not met.
Report 98% field accuracy, 80 fully correct documents and the critical errors; resolve release controls before expansion.
This keeps the denominator and business consequence visible.
Treat only two documents as affected because the field error rate is 2%.
The scenario explicitly places errors in twenty different documents.
Reject all document automation permanently.
The evidence identifies limits and a need for correction or controlled review, not a universal prohibition.

Practical control: Report field, document and critical-error measures separately, with sample composition and the intended downstream action.

Discuss: How would the finding change if all twenty errors were harmless layout differences?

Case 06

Clear the resolved order and learn from it

All critical fields now match the approved sources. The order has the required approvals. A decorative heading wraps differently in the Arabic document, but no content is missing. The customer deadline is today. A reviewer proposes holding for a complete visual match.

Which decision best balances reliability and useful work?

  • Release under the agreed checks and record the non-material layout difference for improvement.
  • Hold until the documents are visually identical.
  • Release and disable all future document review.
  • Replace the approved Arabic source with an automatically translated English version.

Recommended response for this scenario

Release under the agreed checks and record the non-material layout difference for improvement.

The remaining issue is a decorative line wrap. Proceed under the completed material checks and retain the approved sources. Log the layout issue without blocking this order. Use recurring exceptions to improve the workflow’s data and review process.

Why each choice matters

Release under the agreed checks and record the non-material layout difference for improvement.
The material release conditions are satisfied. The remaining difference has no stated operational consequence.
Hold until the documents are visually identical.
That introduces delay without addressing a material uncertainty in this scenario.
Release and disable all future document review.
A successfully resolved case does not validate every future document.
Replace the approved Arabic source with an automatically translated English version.
A derived translation should not silently replace the approved record.

Practical control: Define material release criteria and a separate route for cosmetic improvements. Preserve the source and resolution history.

Discuss: Who decides whether a document difference is material to this workflow?

Worked example / Fictional teaching context

Document reconciliation and exception card

Illustrative assumptions, not a customer result, forecast or professional assessment. Keep the conditions beside the numbers.

Document A
English request: 120 pieces
Document B
Arabic order: 12 boxes, 10 pieces per box; English gloss supplied
Normalised quantity
12 × 10 = 120 pieces
Quantity finding
Equivalent quantities, provided the pack-size evidence and product identity are confirmed
Separate issue
Delivery dates differ across documents; do not infer authority from language
Decision
Record the quantity conversion, clarify the material date conflict with the authorised owner
Value evidence
Resolution time and downstream order errors, measured together

Try the idea in a different situation

A supplier spreadsheet and an email agree on quantity but use different product revisions. Write a release decision with evidence and authority.

Prompts for your discussion
  • Does not mistake agreement on one field for agreement on the whole order.
  • Identifies the approved specification revision and its owner.
  • Records a resolved exception or a clear hold condition.

Use these prompts to examine the reasoning, not to award a score or certify readiness.

Sources and limits

Keep the context with the decision.

Original fictional educational cases. All companies, prices, volumes and outcomes are illustrative. Sources support the stated principles, not claimed customer results. Completion is a learning record, not a professional assessment.

Editorial source review: 2026-09-17. Not legal approval or a verified readiness assessment.

  • All scenario facts and numerical examples are fictional. They are not verified customer results or estimates of a particular business’s performance.
  • The stated durations are planning estimates. Learning outcomes and commercial impact have not been validated with intended readers.
  • Source guidance is used for the stated principles. It does not establish legal applicability, certification or professional approval.
  • Changed-fact prompts support discussion. This is a fixed case sequence, not a branching simulation.
  • English glosses accompany the synthetic Arabic excerpts. The exercise practises document reconciliation and does not determine legal language precedence.

/ CITE OR SHARE THIS GUIDE

Make the evidence easy to verify.

When you reference this guide, link to its canonical URL. That gives readers one stable place for the evidence, limitations and future updates.

Suggested citation

dotSuper Research Desk. (September 17, 2026). The two documents do not agree. dotSuper. https://dotsuper.net/feeds/applied-systems/bilingual-document-decision-lab

Share on LinkedIn

Move from practice to your operating context

Put the decision into practice

Define the critical fields and authorised source for one document workflow before evaluating automation.

Talk with dotSuper