A growing library of vetted, control-aware prompts for the work you actually do - interpreting instructions, drafting, building checklists, reviewing, and briefing leadership. Copy, paste, adapt.
Three rules before you use these. 1) Company policy - not the tool - decides what data you can put in; use public or approved data only. 2) Treat every answer as a draft and verify it against the primary-source instructions. 3) AI assists; it doesn't sign the workpaper. You still do.
Interpret instructions
Instruction interpreter
You are an expert in [report - e.g., the FFIEC Call Report]. Using ONLY the official instructions I paste below, explain in plain English what [schedule / line item] requires: what is included, what is excluded, and the common misreadings. For every point, quote the exact instruction language you relied on. If the instructions are ambiguous or silent, say so explicitly - do not fill the gap with assumptions.
Instructions:
[paste the relevant public instructions]
Guardrail: paste only public/approved instruction text. Check each quoted citation back to the source.
"Where does this map?" helper
Using only the instructions below, tell me where [product / transaction type] should be reported on [report]. Give the candidate line item(s), the inclusion/exclusion language that supports each, and any line items it is commonly confused with. If the instructions don't clearly resolve it, list the open questions I'd need a specialist to confirm - don't guess.
Instructions:
[paste]
Guardrail: a starting point for research, not a determination. Confirm mappings with your own review.
Draft & summarize
Executive summary from bullets
Turn the bullet points below into a concise executive summary for senior leadership (max 150 words). Lead with the result, then the drivers, then anything that needs attention. Neutral, factual tone. Do not add any number, conclusion, or speculation that isn't in the bullets.
Bullets:
[paste your approved talking points]
Guardrail: approved data only. You own the final numbers and framing.
Process narrative for internal audit
Draft a clear process narrative for [process], suitable for internal audit, from the steps below. Include inputs, the key controls, the review/approval points, and outputs. Where a step has no obvious control, flag it as "control not evident" rather than inventing one. Keep it factual and concise.
Steps:
[paste]
Guardrail: the flagged gaps are prompts for your judgment, not conclusions.
Checklists & prep
Reporting prep checklist
From the instructions and process notes below, build a step-by-step preparation checklist for [schedule]. Group it by phase: Gather → Prepare → Review → Submit. Mark every step that involves a control or a required reconciliation with "[control]". Keep each step short and actionable.
Source:
[paste instructions / process notes]
Guardrail: your future self at 9pm during close will thank you - but still review the checklist against the live instructions.
Tie-out & cross-check list
Based on the instructions below, list the cross-checks and tie-outs I should perform for [schedule] - internal consistency checks and common reconciliations to other reports or schedules. For each, state what should equal what, and why. If a check depends on data I haven't provided, note the assumption.
Instructions:
[paste]
Guardrail: verify each tie-out actually holds in your data before relying on it.
Review & QC
Common-errors pre-review
Act as a skeptical reviewer of [schedule]. List the most common errors and red flags, and for each, the specific check I should run before submission. Be concrete. If you're not certain something is an error, label it "verify" rather than asserting it. Order from highest to lowest risk.
Guardrail: a second set of eyes that never tires - not a replacement for yours.
Variance explainer (draft)
Given the current-vs-prior values below, draft neutral, factual variance explanations a reviewer would accept. For any variance you cannot explain from the data provided, write "needs explanation" - do not invent a cause. Keep each explanation to one or two sentences.
Data:
[paste approved figures]
Guardrail: approved data only; every "needs explanation" is yours to resolve.
Leadership & communication
Leadership talking points
From the results and notes below (approved data only), draft 5 crisp talking points for a leadership update: what happened, why, what's on track, what needs attention, and the ask. Plain, confident, no filler.
Notes:
[paste]
Guardrail: approved data only; sanity-check every claim before you present it.
Clear email to the team
Draft a short, clear email to my reporting team about [topic], using the notes below. Professional and direct, no fluff. Put the action or deadline up top. End with what I need from them and by when.
Notes:
[paste]
Guardrail: you know the team and the tone - adjust before sending.
No prompts match that search.
New control-aware prompts every week.
Subscribe free and get the latest prompts, worked examples, and the guardrails - straight to your inbox.