Prompt Engineering for Bankers & Loan Officers

You've used dozens of prompts across this course. This lesson pulls back to teach the craft itself — the techniques that consistently turn AI from a hit-or-miss assistant into a reliable one. Prompt engineering sounds technical, but for a banker it's really about clear thinking: telling the AI exactly what you need, the way you'd brief a sharp new analyst. Master a handful of patterns and every task in your day gets faster.

What You'll Learn

• Five prompt patterns that work for nearly any lending task
• How to control output structure, length, and tone precisely
• How to reduce hallucinations on numbers and regulations
• How to build and save your own prompt library

Pattern 1: Role + Task + Context + Format

The foundation from Module 1, worth internalizing. State who the AI is, what to do, the situation, and the output shape. A complete example:

ROLE: You are a seasoned commercial lender.
TASK: Draft talking points for a borrower meeting.
CONTEXT: Established restaurant seeking a $200K equipment loan;
DSCR is adequate but seasonal revenue swings concern me. Borrower is
experienced but new to bank financing.
FORMAT: 5 bullet talking points + 2 questions to probe seasonality.
Plain, conversational language.

The more precisely you fill each slot, the less the AI has to guess.

Pattern 2: Give an Example (Few-Shot Prompting)

Show the AI what "good" looks like and it will match the pattern. This is the single fastest way to get house-style output:

Here is an example of how we write stipulation requests:
"To keep your file moving, please send: (1) your 2023 business tax
return — all schedules and the signature page — so we can verify
revenue. Target: within 5 business days."

Now write three more stipulation requests in this exact style for these
items: [LIST].

One good example beats three paragraphs of description.

Pattern 3: Constrain the Output

Vague prompts produce sprawling answers. Constraints produce usable ones:

• Length: "In exactly 3 sentences." / "Under 100 words."
• Structure: "As a markdown table with columns X, Y, Z." / "As a numbered checklist."
• Audience: "For a borrower with no finance background." / "For a loan committee."
• Scope: "Cover only repayment sources — ignore collateral for now."

Stacking constraints is how you get a draft that needs almost no editing.

Pattern 4: Anti-Hallucination Guards

The highest-stakes prompt skill for a banker is preventing confident wrong answers — especially on numbers and regulations. Build these phrases into your prompts:

• "Use only the figures I provide. Do not invent or estimate any number."
• "If you are not certain, say so rather than guessing."
• "Show your arithmetic line by line so I can check it."
• "Do not state any regulation or requirement unless I've given it to you; instead, tell me to verify it."
• "Quote directly from the document I pasted; if it's not there, say 'not found.'"

These don't make AI perfect, but they dramatically cut the plausible-sounding errors that are dangerous precisely because they look right.

Pattern 5: Chain Your Steps

Complex tasks work better as a sequence than one giant prompt. To build a credit write-up:

1. "Extract these figures from the redacted financials and show your math."
2. "Now calculate DSCR, current ratio, and debt-to-worth from those figures."
3. "Now draft the financial-analysis section of a credit memo using only those results."
4. "Now list the five biggest risks and a mitigant for each."

Each step is verifiable before you move on, so an error never compounds silently into the final draft. This "chaining" mirrors how you'd actually think through a file.

Iterating Like a Pro

When output misses, diagnose rather than restart:

• Too generic? Add context and an example.
• Wrong format? Specify structure explicitly.
• Made up a number? Add an anti-hallucination guard and re-run.
• Wrong tone? Name the audience and the feeling you want.
• Too long? Add a hard word limit.

Usually one targeted follow-up fixes it. You're steering, not gambling.

Building Your Prompt Library

The biggest productivity unlock is to stop writing prompts from scratch. Keep a personal document of your best, proven prompts — organized by task: product explanations, stip requests, memo sections, follow-ups, decline-letter clarity. When one works well, save it with a placeholder for the variable part:

[SAVED: Stip request]
Draft a borrower email requesting these items: [ITEMS]. For each, say
exactly what's needed and one friendly sentence why. Numbered list,
5-business-day deadline, reassuring tone, under 150 words. No rate
statements.

Over a few weeks you'll accumulate 15-20 reliable prompts that cover most of your day. Paste-and-fill becomes faster than writing from memory — and the quality stays consistently high.

Key Takeaways

• The core pattern is Role + Task + Context + Format — fill every slot precisely.
• Few-shot prompting (showing one good example) is the fastest route to house-style output.
• Stack constraints on length, structure, audience, and scope to get drafts that need little editing.
• Use anti-hallucination guards on every numeric or regulatory task, and chain complex work into verifiable steps.
• Build a personal prompt library of proven, fill-in-the-blank prompts to make AI faster and more consistent every week.