Build a verification checklist for a vendor bank-change request

About this exercise

A vendor emailed new bank details and asked you to use them for the next payment. Write a prompt for a checklist of exactly 5 lines, each starting "- [ ]", from the policy and the email. End with a sixth line starting "Status:" that says HOLD. Plain text, under 110 words. Don't tell anyone to ignore or report the email as fraud; the checklist only verifies.

Common mistakes when you ask AI for this

• Calling the number in the email. The AI suggests replying to the email or calling the number it lists. Try: Say: "Callback uses the number in the vendor master, not the email."
• Missing the domain mismatch. The AI doesn't notice the sender's domain differs. Try: Add: "Note that the sender's email domain differs from the domain on file."
• Declaring fraud. The AI says this is a scam and tells staff to delete it. Try: Add: "The checklist only verifies. Don't call it fraud."
• Markdown extras. The AI adds bold labels, headings and a closing note. Try: Say: "Plain text, no bold. Output only the lines asked for."
• Trusting the AI to count words. AI is bad at counting and runs past word limits. Try: Ask for fewer words than the real cap and keep each line short.

What a strong prompt includes

• Gives the checklist shape
• Covers callback and form
• Mentions the domain
• Ends with status
• Bans fraud conclusion

Practice this now ↑

Related exercises

• Accrue goods received but not invoiced at PO price (Finance AI · Accountants)
• Age open requisitions as of today and flag the old ones (Finance AI · FP&A and financial analysts)
• Age reconciling items and escalate those over 60 days (Finance AI · Accountants)
• Alert sales to a competitor's price change, facts only (Research & AI Search · Product managers)
• Allocate shared rent by headcount using the right roster (Finance AI · Accountants)