{"id":"acct-chargeback-evidence-checklist-dates","audience":"small-business","category":"finance-work","track":"finance","technique":"format","level":"beginner","title":"Turn a chargeback notice into a dated evidence checklist","free":false,"task":"You're a small business owner's bookkeeper preparing a response to a card chargeback. Write a prompt for plain text with one checklist line per evidence item in the form \"[ ] Item (owner, have or need) - due Nov 9\", followed by a last line \"[ ] Submit response (Ravi) - due Nov 12\". Gather dates are three days before the response deadline. Do not predict whether the dispute will be won. Under 100 words.","materialLabel":"Source material (attached to your prompt automatically)","material":"CHARGEBACK NOTICE - received Mon, Nov 2, 2026\n\nCustomer: Dana Whitfield. Disputed charge: $780.00 for order INV-3301, charged Oct 9. Reason given by the cardholder's bank: \"item not received.\"\nResponse deadline: 10 calendar days from the notice date.\n\nEvidence the processor asks for, and where we stand:\n1. The invoice INV-3301 - we have it (Ravi has the PDF)\n2. Carrier proof of delivery - tracking shows delivered Oct 14; Ravi has the carrier page saved\n3. Customer emails about the order - need to export from the support inbox (Kim)\n4. Refund and returns policy screenshot - need to capture from the website (Kim)\n5. Card authorization record - available in the processor dashboard (Ravi)\n\nNotes: the owner wants to know if the dispute will be won. The processor does not say; decisions are made by the bank. The owner will review the package on Nov 10. Gather dates are three days before the response deadline.","rules":[{"type":"plainText"},{"type":"maxWords","max":100}],"promptHints":[{"label":"Shows the checklist format","patterns":["\\[ \\]","owner","have or need"]},{"label":"Gives the dates","patterns":["nov(ember)? 9","nov(ember)? 12"]},{"label":"Fixes the last line","patterns":["submit response","ravi"]},{"label":"Bans predicting","patterns":["do not predict","won"]},{"label":"Caps length","patterns":["\\d+\\s*words","under \\d+"]}],"mistakes":[{"title":"Wrong due dates","why":"The AI uses the notice date or invents dates.","fix":"Say: \"Gather by Nov 9, three days before the Nov 12 deadline.\"","checks":["r0","r2"]},{"title":"Predicting the outcome","why":"The AI says the evidence makes a win likely.","fix":"Add: \"Do not predict whether the dispute will be won.\"","checks":["r2"]},{"title":"Marking have vs need wrong","why":"The AI labels everything as needed.","fix":"Add: \"Mark each item have or need from the notes.\"","checks":["r1"]},{"title":"Wrong format","why":"The AI writes a table or bullets.","fix":"Add: \"Each line like: [ ] Item (owner, have or need) - due Nov 9.\"","checks":["r0"]},{"title":"Markdown extras","why":"The AI adds bold labels, headings and a closing note.","fix":"Say: \"Plain text, no bold. Output only the lines asked for.\"","checks":["plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and runs past word limits.","fix":"Ask for fewer words than the real cap and keep each part short.","checks":["maxWords"]}],"hint":"Checklist lines come from your template. Give the exact line format, the dates, and what not to promise.","rubricLabels":["Six lines each starting \"[ ] \": five evidence items with owner, have or need, and \"due Nov 9\", then the final submit line","The items match the list: invoice (Ravi, have), proof of delivery (Ravi, have), customer emails (Kim, need), policy screenshot (Kim, need), authorization record (Ravi, have)","The last line is exactly \"[ ] Submit response (Ravi) - due Nov 12\" and nothing predicts or promises the outcome of the dispute"]}