Counts show all available guides. Filters combine to narrow your results.
Build a workflowGuide
Check several partial deliveries against one order
Count each authorized delivery event once and show shortages and over-deliveries by order line.
Illustrative resourceNot tool-testedAdults working with non-sensitive partial deliveries information
What you’re working towards
A line-by-line received, outstanding and over-delivered ledger, with duplicate delivery references held before totals. This is an authored practice example; no consumer AI run has been recorded.
Your choice also saves this guide’s current worked-example checkmarks. Only this browser; no account or sync. View saved guides
Saving needs JavaScript. Reading and downloading this guide does not save it.
Make a start
One step at a time.
3 steps
Start with the synthetic worked example or other non-sensitive inputs. Run one prompt at a time in your chosen AI tool. Replace any bracketed placeholders with the requested material, check each reply, and supply the source or earlier outputs that step needs. Paste them again if the tool lacks that context.
Start with the synthetic example, then adapt each prompt to your task.
01
Try the complete example
Open a new chat in a text AI assistant you already have permission to use. Paste all of Input from this guide, then the prompt below, in one message. Do not paste Output: that is the illustrative answer for comparison. Expect a written result that will count each authorized delivery event once and show shortages and over-deliveries by order line. Different wording is fine; the source facts and rules must agree.
Your starting prompt
Audit delivery event IDs before totaling. Follow the explicit duplicate-copy rule, keeping every source row traceable. Sum counted events by exact order ID, then return ordered, received-per-notes, outstanding and over-delivered quantities with formulas and control totals. Keep physical verification and commercial decisions separate.
Use only the complete synthetic input pasted above. Return the finished written result. Keep missing facts unknown. Do not send, publish, order or change another service.
02
Trace the answer back to the source
Compare the answer with Input yourself. R4 is logged but excluded; D1–D4 are each counted once. O1 receives 20 with no gap; O2 receives 12 against 10 ordered, giving 2 over and 0 outstanding. Raw 39 minus duplicate 7 equals counted 32; the two order-line totals also sum to 32. Documentary received quantities do not become claims that real parcels were inspected. If a check fails, paste: “This part is wrong: [quote it]. My source says: [quote the exact line]. Return the complete corrected result and explain the change.” Recheck before saving; if the source itself is incomplete, keep that part unresolved.
Your starting prompt
Audit the result against the source pasted in this chat. Check these specific points:
- R4 is logged but excluded; D1–D4 are each counted once.
- O1 receives 20 with no gap; O2 receives 12 against 10 ordered, giving 2 over and 0 outstanding.
- Raw 39 minus duplicate 7 equals counted 32; the two order-line totals also sum to 32.
- Documentary received quantities do not become claims that real parcels were inspected.
Show each mismatch and return a complete corrected replacement. Distinguish your text audit from checks that only a person or the actual application can perform.
03
Use your own input
For your own version, open a new chat. Paste the prompt below after replacing every bracketed field. Replace related IDs, quantities, dates, rules and limits together; none of the practice facts carries over. Expect the same named deliverable using your source. Review it yourself: count each unique delivery reference once, then add quantities by order line and independently verify shortages and overages. If a check fails, paste: “This part is wrong: [quote it]. My source says: [quote the exact line]. Return the complete corrected result and explain the change.” Recheck before saving; if the source itself is incomplete, keep that part unresolved.
Your starting prompt
Reconcile my order lines with all partial delivery rows using the exact matching and duplicate rules I supply. Audit event IDs first; preserve excluded duplicates and hold conflicting event records. For each order line calculate received-per-records, outstanding and over-delivered amounts separately, with source IDs and control totals. Flag unmatched orders, returns or unclear quantities; do not infer refund rights or physical receipt.
MY INPUT
Order lines with IDs and quantities: [replace with your own complete non-sensitive details, or state unknown]
Delivery rows with unique references: [replace with your own complete non-sensitive details, or state unknown]
Exact item matching keys: [replace with your own complete non-sensitive details, or state unknown]
Duplicate handling rule: [replace with your own complete non-sensitive details, or state unknown]
No refund/entitlement assumptions: [replace with your own complete non-sensitive details, or state unknown]
Use only MY INPUT for facts and constraints. Ask for an essential missing fact or conflicting rule before deciding; do not import practice-example names or numbers. Return the complete result plus unresolved questions and a source-based check list. Do not send, publish, buy, schedule or change another service.
Optional: improve the result
Test a conflicting repeated event
Separate an approved duplicate copy from an unresolved conflicting record. This optional extension uses only the synthetic example. Return to the sample chat, or paste its full Input into a new chat first. Do not transfer the changed sample values to your own input.
Advanced prompt
For a separate variant of the synthetic input, replace R4’s quantity 7 with 9 and remove the owner’s statement that R4 is a repeated copy. Keep the rest. Explain why D3 is now unresolved, list both conflicting rows, and report only the unaffected confirmed subtotal for O2 without pretending the final O2 receipt total is known.
Show, then try
See the shape of the result.
This input is synthetic. The output is a written illustration of the intended result, not a verified AI-tool run.
01 / The starting point
Synthetic input
Synthetic practice input. All names, products, records and policies below are invented.
Synthetic order ledger; all quantities count folders.
Order O1: blue folders, ordered 20.
Order O2: green folders, ordered 10.
Complete delivery-note rows:
R1: delivery D1, order O1, quantity 12.
R2: delivery D2, order O1, quantity 8.
R3: delivery D3, order O2, quantity 7.
R4: delivery D3, order O2, quantity 7.
R5: delivery D4, order O2, quantity 5.
Owner confirmation: R4 is a repeated copy of R3, not another parcel; preserve it in an excluded-duplicate log and count D3 once. Delivery IDs are unique event keys in this fixture and order IDs are the exact matching keys. No returns, cancellations or other deliveries. These are documentary quantities; physical contents have not been inspected. No refund, payment or acceptance decision is requested.
Copies text only. For image or file tasks, use the source files named in the steps too.
Illustrative answer authored for this guide; not a recorded AI response.
Delivery-row audit
R1 / D1 → include 12 for O1.
R2 / D2 → include 8 for O1.
R3 / D3 → include 7 for O2.
R4 / D3 → exclude from totals as the owner-confirmed repeated copy of R3; retain in duplicate log.
R5 / D4 → include 5 for O2.
Five input rows represent four counted events plus one excluded duplicate copy.
Order-line reconciliation
O1, blue folders: ordered 20; received per notes D1 12 + D2 8 = 20; outstanding 0; over-delivered 0.
O2, green folders: ordered 10; received per notes D3 7 + D4 5 = 12; outstanding 0; over-delivered 2.
Outstanding is max(ordered − received, 0); over-delivered is max(received − ordered, 0). A negative shortage is not used.
Control totals
Ordered: 20 + 10 = 30 folders.
Raw note rows total: 12 + 8 + 7 + 7 + 5 = 39.
Excluded repeated quantity: 7.
Counted delivery quantity: 39 − 7 = 32, also 20 + 12 = 32 by order line.
Net excess across these lines: 2, entirely on O2. No line is outstanding.
Review note
Confirm actual parcel contents separately if needed. The extra 2 green folders create a discrepancy to resolve with the appropriate owner; this ledger does not establish a refund, entitlement, purchase acceptance or instruction to return them.
These checks use the worked example and its particular facts. With your own material, check your actual names, numbers, sources and rules; do not reuse the sample’s values as the answer.
Unsaved checks stay in this tab and reset when you reload. If you choose Save guide, its current example checkmarks are kept in this browser when storage is available.
!
A few things to watch for.
Similar quantities are not enough to prove a duplicate. Use an event key and the owner’s explicit duplicate handling rule.
Conflicting rows with the same event ID need a hold and clarification, not “keep first” by default.
Do not offset a shortage in one product with an excess of a different product when checking individual order lines.