Skip to content
Back to Resources
ClaudeLoan OriginationBeginnerGuide

Claude CoWork for Loan Officers

A practical guide to using Claude as your AI co-worker for pipeline updates, LOEs, Loan Estimate explainers, and realtor co-marketing — with TRID, ECOA, and fair-lending guardrails on every draft.

Claude CoWork for Loan Officers

What is Claude CoWork?

Claude CoWork is the practice of configuring Claude as a persistent AI co-worker that knows your NMLS-licensed-LO context — your lender, your product mix, your license states, your house compliance posture — and produces drafts you can review and send rather than drafts you have to rewrite. For loan officers in 2026, the leverage is in the four workflows that eat the day: borrower pipeline updates, Letters of Explanation, Loan Estimate / Closing Disclosure walk-throughs, and realtor co-marketing.

Claude-native prompts. The prompts in this guide use Claude's XML tag structure (<context>, <instructions>, <format>, <avoid>) for precise, consistent output. These tags reduce ambiguity and give Claude clear parsing boundaries. They work in ChatGPT too but are optimized for Claude.

20–30% of borrowers drop off between application and Clear-to-Close. The LOs who keep that number low don't type faster — they communicate more often, more clearly, and with the right framing for each audience (borrower vs buyer agent vs listing agent vs processor). AI handles the structured-writing layer so you can run more pipeline without burning out.

This guide covers setup, five high-leverage workflows, and the compliance posture that keeps your drafts defensible.

Install the Loan Officer Plugin

This guide works on three Claude surfaces. The plugin is the fastest path on two of them.

If you're on Cowork (desktop or mobile app)

Claude Cowork is Anthropic's agentic workspace — Claude completes work autonomously and returns finished deliverables. The Loan Officer plugin packages the workflows below as native skills and slash commands.

  1. Open the Cowork plugin directory in your desktop app.
  2. Filter by Cowork, search for "Loan Officer", and click Install.
  3. The plugin's slash commands and ambient skills are now available in any Cowork task.

If you don't see the plugin in the directory yet, install via custom marketplace: paste alexclowe/awesome-claude-cowork-plugins in your Cowork plugin settings.

If you're on Claude Code (CLI)

Install from your terminal:

claude plugin add alexclowe/awesome-claude-cowork-plugins/loan-officer

The plugin's slash commands and skills load on next session.

If you're on Claude.ai (web chat only)

Plugins aren't directly installable on the web chat surface. You have two options:

  1. Use the prompts in this guide directly in a Claude Project (covered in the next section). Same outputs, more typing.
  2. Upload the plugin's skills as a zip via Settings → Features → Custom Skills (Pro/Max/Team/Enterprise plans).

What the plugin gives you (any surface)

Slash command What it does
/pipeline-update Generate audience-tailored pipeline status updates (borrower / buyer agent / listing agent / processor) from one input
/loe-draft Draft a Letter of Explanation for an underwriting condition from the borrower's verbal explanation
/le-explainer Turn a Loan Estimate or Closing Disclosure into a borrower-friendly walk-through
/realtor-comarketing Generate joint open house materials, co-branded social, just-funded shoutouts with RESPA / fair-lending guardrails

Auto-activating skills (no command needed — Claude applies them when relevant):

  • TRID Timing Awareness — flags TRID timing risks in drafts (LE delivery windows, CD waiting periods, locked-vs-revised terms) before send
  • Fair-Lending Language — flags ECOA / HMDA-relevant red flags (protected-class references, prohibited basis language) in marketing copy

The plugin works standalone for one-off tasks. Pair it with the surface-specific setup below for persistent context across every task.

Setting Up Claude for Loan Officer Work

Surface note: The Project setup below is for claude.ai web users. Cowork users have their own task-context mechanism. Claude Code users get the plugin's ambient skills automatically.

Step 1: Create a Loan Officer Practice Project. In Claude, open Projects and create one called "Loan Practice — [your name]". One project per LO, not per loan.

Step 2: Set your custom instructions. In Project settings, add:

You are my loan officer co-worker. Here is my context:

<practice-profile>
- NMLS #: [number]
- Lender: [employer]
- License states: [e.g., CA, TX, FL]
- Loan products I originate: [Conventional, FHA, VA, USDA, Jumbo, Non-QM, HELOC, etc.]
- My typical borrower: [e.g., first-time buyers; move-up buyers; veterans; high-LTV refi]
- Realtor partners: [e.g., 8 active referral partners across 3 brokerages]
- Voice: [e.g., warm but precise; never hype-y; never makes rate predictions]
</practice-profile>

<rules>
- Never invent a rate or quote a rate to a borrower — rates are pulled from my LOS, not from you
- Never make a binding pre-approval representation — pre-approvals are issued from my LOS
- For TRID timing: flag any communication that touches an LE delivery window, CD waiting period, or locked-vs-revised terms — escalate to my processor or compliance team
- For fair-lending: flag any language that could be read as protected-class reference (race, color, religion, national origin, sex, familial status, disability) — escalate to my compliance team
- For RESPA: flag any co-marketing material that could imply a thing of value exchanged with a settlement service provider — escalate to my compliance team
- Borrower communications: warm, clear, no hype. Realtor communications: direct, status-focused, no fluff
</rules>

Step 3: Upload your house style references. Add: prior pipeline updates you've sent (with PII stripped), prior LOEs you've used as templates, your lender's approved marketing copy guidelines, your state license disclosures.

Step 4: Pin a starter prompt. Begin every session with: "We're working in [Project name]. Confirm you have the practice profile loaded and summarize the top-level rules before we start." Ten seconds; prevents context drift.

Five High-Leverage Workflows

1. Multi-Audience Pipeline Update

One loan, three or four audiences with different needs. Generate all of them from one status input.

<context>
Loan stage: [e.g., conditional approval received; 3 remaining conditions]
Borrower: [first name only; no last name, no MRN-equivalent]
Property: [address city/state only; no full address]
Current conditions: [list the 3 remaining]
Closing date target: [date]
Risk flags: [anything that could affect the closing date]
Audiences: borrower, buyer agent, listing agent, processor
</context>

<instructions>
Generate four audience-tailored pipeline updates. For each:
- Borrower: warm reassurance, the one thing they need to do (if anything), next step
- Buyer agent: closing trajectory, risk flags, any borrower action needed
- Listing agent: confidence-level signal, condition status without borrower-detail
- Processor: condition-clearance status, anything I need from them

Keep each under 120 words. No rate quotes, no pre-approval representations. Flag any TRID timing risk before the message body.
</instructions>

<format>
Four sections, one per audience. Subject line + body for borrower/buyer agent/listing agent. Processor as direct message.
</format>

<avoid>
Rate quotes, pre-approval language, hype language ("you're going to love this!"), protected-class references, anything that suggests urgency that isn't real.
</avoid>

2. Letter of Explanation (LOE) Drafting

The single biggest time sink in LO work. Turn the borrower's verbal explanation into a properly-structured LOE.

<context>
Underwriting condition: [e.g., "Please provide LOE for 3 credit inquiries within the last 90 days that did not result in new accounts"]
Borrower's verbal explanation: [paste]
Supporting documentation borrower has: [e.g., screenshots showing inquiries were rate-shopping for auto loan]
</context>

<instructions>
Draft an LOE addressed to the underwriter that:
- States the borrower's name and loan number (placeholders)
- Addresses the specific condition language directly
- Provides the borrower's explanation in their voice (lightly cleaned up; first-person)
- References supporting documentation the borrower will attach
- Closes with a clear statement of intent (the inquiries did/did not result in new debt)
- Ends with signature line for the borrower

Do NOT invent facts. Where the borrower's explanation is unclear, leave a [borrower-confirm: ...] placeholder.
</instructions>

<format>
Standard business letter. Date, recipient, salutation, body, closing, signature line.
</format>

<avoid>
Legalese, defensive language, anything that overexplains beyond what the condition asks. LOEs should answer the condition cleanly — not invite follow-up questions.
</avoid>

3. Loan Estimate / Closing Disclosure Explainer

Borrowers receive an LE and immediately ask follow-up questions about every fee. A structured walk-through cuts the 30-minute phone call to a 10-minute call with informed questions.

<context>
LE/CD type: [Loan Estimate / Closing Disclosure / Revised LE]
Loan product: [Conventional 30-year fixed / FHA / VA / etc.]
Loan amount: [amount]
APR: [rate]
Fees with values: [paste the LE Section A/B/C/E/F/G/H rows that the borrower will see — origination, services borrower did/didn't shop for, prepaids, initial escrow]
Borrower context: [first-time buyer / refi / move-up — drives explainer depth]
</context>

<instructions>
Generate a borrower-friendly explainer that:
- Walks each major fee section in order (origination, services, taxes/insurance, prepaids, escrow)
- Explains what each fee IS (one sentence), why it's charged, and whether the borrower can shop it
- Calls out fees that drive 90% of borrower questions: origination, discount points, escrow waiver options, prepaid interest, transfer taxes
- For revised LE: flag what changed vs the original and trigger language for the change (changed circumstance, borrower request, etc.)
- Closes with three suggested borrower questions for our follow-up call
</instructions>

<format>
Section-by-section breakdown. Each section: section name, total, fee-by-fee explanation, shop-or-not callout.
</format>

<avoid>
TRID timing claims (those go to compliance), rate predictions, anything that suggests the borrower should waive a right.
</avoid>

4. Realtor Co-Marketing

Joint open house, co-branded social, just-funded shoutouts, quarterly partner check-ins — the LO who runs these consistently wins the referral relationship.

<context>
Realtor partner: [name + brokerage]
Co-marketing type: [joint open house / joint social post / just-funded shoutout / buyer guide / monthly check-in]
Property or transaction: [address city/state; loan product if just-funded]
Realtor's brand voice: [warm + community-focused / direct + business-focused / luxury / etc.]
My voice: [from practice profile]
</context>

<instructions>
Generate a co-marketing piece that:
- Reflects both my voice AND the realtor's brand voice (lean toward the realtor's voice; co-marketing should feel like their content with my participation, not the reverse)
- Uses fair-lending-safe language: no protected-class references, no demographic targeting, no language that could be read as ECOA-prohibited basis
- For RESPA: no implication of a thing of value exchanged with a settlement service provider beyond the co-marketing piece itself
- Includes both NMLS # (mine) and license info (realtor's) in the footer
- Includes Equal Housing Opportunity language and Equal Housing Lender language where applicable
</instructions>

<format>
Title or subject + body + visual direction (if applicable) + footer with required disclosures.
</format>

<avoid>
Anything that implies the realtor and I have an exclusive arrangement (RESPA risk); anything that targets a protected class; rate quotes; anything that implies pre-approval without a documented application.
</avoid>

5. Just-Funded Workflow + Referral Ask

The closing happened. Most LOs stop the relationship there. The LOs who win referrals run a four-touch just-funded workflow.

<context>
Borrower: [first name only]
Loan product: [Conventional / FHA / VA / etc.]
Realtor partner(s): [buyer agent / listing agent names]
Closing date: [date]
Anything special about this loan: [first-time buyer; veteran; complex underwriting that closed]
</context>

<instructions>
Generate four touches:
1. Day-of-closing thank-you to borrower (warm, no immediate referral ask)
2. Day-of-closing congratulations to buyer agent (acknowledging the partnership, no immediate referral ask)
3. Day-3 follow-up to borrower with one practical "now you've moved in" tip (utilities setup, address change checklist, no referral ask)
4. Day-14 referral ask to borrower (gentle, acknowledging the closing experience, asking for two specific kinds of referrals — first-time buyers + recent retirees, or whatever fits my book)

Do NOT include rate predictions or refi recommendations in the just-funded workflow. The borrower just closed.
</instructions>

<format>
Four messages, one per touch. Subject line + body for each. Day 0 / Day 3 / Day 14 timing labels.
</format>

<avoid>
Refi predictions ("rates are likely to fall — let me know when you want to discuss"), rate watching offers, anything that turns the closing into the next sales call.
</avoid>

What This Looks Like in Your Week

Monday. Pipeline review. Run Workflow 1 for the 8 active loans in your pipeline. Send the four-audience updates from your LOS or email client. Yesterday this took 4 hours; today it takes 45 minutes.

Tuesday. Three LOEs land in your inbox from your processor. Run Workflow 2 for each, collect borrower verbal explanations on a quick call or text, route the drafts for borrower signature.

Wednesday. You're at a realtor lunch. Pull up Workflow 4 on your phone, generate a joint open house piece for this weekend's listing, send to the realtor before you leave the table.

Thursday. Two LEs and a revised LE need to go out. Run Workflow 3 on each, send the borrower-friendly explainer alongside the formal LE from your LOS so the borrower has both.

Friday. Three loans closed this week. Run Workflow 5 for each — Day-0 messages today, the Day-3 and Day-14 messages schedule themselves.

What to Avoid

Letting AI quote a rate. Ever. Rates come from your LOS, not from Claude. The plugin's TRID Timing Awareness skill exists in part to catch this — but the discipline starts with the prompt rules above.

Sending LE explainers that contradict the LE itself. AI-generated explainers should reference the actual LE values you paste in. Verify the explainer before send. A rounding-error mismatch between explainer and LE is a borrower-trust hit.

Using AI for borrower communications without the practice profile loaded. Generic Claude output reads like marketing copy. Practice-profile-loaded Claude output reads like you. Without the profile, every LO sounds the same — and the realtors and borrowers notice.

Skipping compliance review on co-marketing pieces. Fair-lending and RESPA risks in co-marketing are real and your compliance team has seen the patterns before. The AI flags red flags; your compliance team certifies.

Treating AI as a replacement for the relationship. AI generates the just-funded touches and the realtor check-ins. The relationship is built when you pick up the phone for the borrower whose appraisal came in low. Don't let the AI workflow replace the calls that actually decide whether the borrower refers you.

Resources

This guide is general guidance for NMLS-licensed loan officers. It is not legal, compliance, or licensing advice. TRID, TILA, RESPA, ECOA, HMDA, state-specific licensing requirements, and your lender's compliance policies govern actual LO practice. Your compliance officer and your lender's counsel are the appropriate references for compliance-sensitive questions. AI-drafted communications must be reviewed by the LO before sending; compliance review of marketing copy and disclosure-adjacent communications is the LO's responsibility.

Get weekly AI prompts for Loan Origination professionals

Join professionals already saving hours every week. Free. No spam.