Name the exact comparison problem
For W-8, the dispatch says 120 kilograms while the receipt says six bags. Those records cannot be compared until the bag weight and meaning are known. Six bags might represent the full amount, a partial receipt or a different packing basis.
Record both values as submitted. Ask for the documented conversion and confirmation of what the receiving team counted. Do not assume twenty kilograms per bag merely because it makes the totals agree.
For services, the same problem appears when “completed” means work performed to the partner but accepted to the client. The issue may be a definition mismatch rather than failed delivery.
Keep the suggested finding attached to evidence
A useful exception describes the affected work order, source records, expected rule, observed difference and next question. It should not label a partner unreliable based on one ambiguous record.
If configured AI reads documents or notes, check whether it has taken a subtotal for a total, confused dates or omitted a qualification. Give reviewers access to the relevant passage or table rather than only a summarized discrepancy.
Distinguish reported issue, confirmed issue and resolved issue. An internally closed ticket may mean an administrator finished processing it, not that the receiving site accepted the work. Define the status needed for your operation.
Use the exception to improve the next handoff
Assign the clarification to the source owner who can answer it. Record the reply, reviewer and resulting change. Where no answer is available, keep the limitation visible rather than silently selecting a preferred source.
If many receipts use bags without a weight basis, change the collection request or acceptance procedure. Repeated cleanup is often a sign that the source process needs a clearer definition.
Review patterns at the appropriate level. Several exceptions at one site could reflect a local reporting problem, a genuine operational issue or both. Investigate before using the count to rank partners.
Work through the Relay example
This is a fictional teaching example. Adapt the fields and rules to the question your own workflow needs to answer.
| Step | W-8 example | Decision |
|---|---|---|
| Observe | 120 kg versus six bags | Units are not yet comparable |
| Clarify | Request the documented bag basis | Keep original entries |
| Review | Check receiving evidence and conversion | Confirm or retain the discrepancy |
| Improve | Add explicit unit context | Reduce repeated ambiguity |
Build this part of your plan in more detail
These lessons address the next practical questions in this module. Choose the detail your workflow needs, then return to complete the exercise.
- How to Analyze Documents as Evidence: Sources, Context and Review
Keep document findings attached to the relevant passage and reporting period.
Add this part to your plan
On workbook page 3, write the W-8 exception and the evidence required to resolve it. Include who owns the clarification.
Download workbook (fillable PDF)Compare with a suggested answer
The team records an unresolved unit comparison, asks for the documented basis and receiving confirmation, and approves a resolution only after review. It does not invent the missing conversion.
Self-check: Could another reviewer repeat your reasoning from the recorded evidence?
Questions you may have
Should every discrepancy block operations?
Define escalation and acceptance rules for the actual risk and workflow. A reporting mismatch and a critical operational issue may need different handling.
Does AI detection prove the partner made an error?
No. It identifies a potential issue for review against the source and agreed definitions.
Apply the method to your work
Use the five-part plan to assess the sources, analysis and permissions your team needs. The solution page shows where a connected platform can support that workflow.
Explore the partners & suppliers solution →