Top of page

Insurance · Fictional file F-018

Before asking the customer, check the file.

A case note asks for two things: a repair estimate and proof of purchase. The estimate is already there. What does the handler actually need to request?

The evidence

F-018 lists estimate RE-04 in the attachment index. The estimate names this case and item ITEM-047. No proof-of-purchase receipt appears in the supplied baseline file.

Draft for the handler: “We have the repair estimate. Please send the proof of purchase for item ITEM-047 so we can complete the file.”

Reviewer’s decision: Check the wording or look in another authorised source before contacting the customer. Nothing has been sent. The example does not decide cover, liability or entitlement.

Plain text path

Compare ITEM-047 in the case with ITEM-047 or ITEM-074 on receipt PO-09. A document that exists in the attachment list can still be the wrong document.

Change one fact · Fixture F-018

Inspect the attachment list before contacting the customer

Case item: ITEM-047 · Receipt slot: Absent

F-018/B contains RE-04; RE-04 matches ITEM-047. No proof of purchase is in the supplied register.

They already sent the estimate.

Unsent draft request

Only proof of purchase is missing from this file.

Unsent draft message for handler review

“We have the repair estimate. Please send the proof of purchase for item ITEM-047 so we can complete the file.”

Plain HTML comparison of all 3 file F-018 attachment states
Receipt absent (F018-BASE)

They already sent the estimate. — Only proof of purchase is missing from this file.

Matching receipt arrives (F018-RECEIVED)

No repeat request needed. — The two documents requested at intake are in this file. The handler still decides whether they are sufficient.

Receipt names another item (F018-OTHERITEM)

Hold. The item codes differ. — Having a receipt in the file does not establish that it belongs to this item.

Top