THADDEUS FOR BANKING / WORKFLOWS
Banking work.
Clearer control.
Give staff more time for customers and less time assembling review files. Explore CIP evidence, customer-information security, policy support, and document checks through narrowly scoped, read-only pilots.
Use synthetic or bank-approved, deidentified examples initially. Introduce real customer data only after the required agreements and the bank’s security review. No automatic payments, credit decisions, or changes to bank records are part of an initial read-only pilot.
START HERE / AN INTERNAL AI COORDINATOR
One place for requests.
People accountable for results.
Consider an internal AI help desk: a trained coordinator turns staff requests into approved assignments, checks the information and access needed, and returns work to a named reviewer. Start with a small group rather than giving every employee unrestricted access.
This is a proposed operating approach, not a packaged help-desk service or a replacement for your core banking system. Use the workflows below to define and evaluate the first assignments.
Match the work to the bank’s controls ↗Request. Scope.
Prepare. Review.
Coordination does not replace controls. A trained operator still needs tested access boundaries and bank-approved review responsibilities.
CUSTOMER ONBOARDING / CIP REVIEW
Prepare the evidence.
Keep customer information protected.
Use approved procedures and a synthetic onboarding packet to organize Customer Identification Program (CIP) evidence, source references, and open questions for bank staff. Keep identity verification separate from the cybersecurity review of access and information handling. Account-opening decisions stay with your bank.
See the CIP & cybersecurity visual on Security & Data01 / INTERNAL POLICY SUPPORT
Find the policy.
Keep the source in view.
Use approved policies and procedures to prepare draft answers to staff questions. Tie each answer to its source, preserve version and effective-date information, and leave conflicting guidance for the policy owner.
A useful assignment
“Use only these approved procedures. Cite the document, section, effective date, and relevant passage for each answer. Flag missing dates, conflicts, and anything the sources do not establish.”Explore evidence-led research ↗
The answer.
The basis for it.
A review format, not live bank policy.
Keep policy authority clear. A fluent answer is not an approved procedure. Verify the source and interpretation before staff rely on it.
02 / EXAMINATION-EVIDENCE PREPARATION
Prepare the evidence.
Show what is missing.
Map an examination request list to approved policies, reports, and records. Build an index reviewers can trace back to the originals, with owners, versions, and gaps. Keep files unchanged and submission with the authorized bank team.
A useful assignment
“Prepare an evidence index for these requests. Record source locations, dates, versions, and owners. Mark missing or conflicting evidence. Do not claim that attaching a file satisfies a request.”Explore reviewable deliverables ↗
Requests linked.
Gaps left visible.
Preparation is not assurance. An organized packet is not a certification, a completed submission, or a guarantee of an examination outcome.
03 / DOCUMENT REVIEW & RECONCILIATION
Compare the records.
Review the differences.
Compare versions, extract agreed fields, and reconcile sample reports. Start with synthetic or approved, deidentified inputs and flag missing values or ambiguous matches without changing the originals.
A useful assignment
“Compare these synthetic reports using the agreed reference fields. Show source locations for discrepancies, recalculate totals, and list missing items. Do not change either report or choose an uncertain value.”Explore scoped assignments ↗
Exceptions to check.
Not automatic corrections.
Human validation remains necessary. Verify extraction and calculations against the originals. A proposed reconciliation is not a verified balance or authorization for a transaction.
BANKING RESOURCE / PLAYBOOK
The Bank AI Help Desk Playbook
Learn how a supervised internal AI service can turn staff requests into useful, reviewable work. Two fictional examples explain intake, preparation, human review, and handoff.
- Qualify requests before an assignment starts.
- Define operator, reviewer, and escalation responsibilities.
- Keep completed work separate from policy or action approval.
A CONTROLLED FIRST STEP
One bank workflow.
A clearly bounded pilot.
Examples are illustrative, not customer results. A dedicated LLM on your bank’s hardware has an individually agreed scope for information handling, access, integrations, support, and operating responsibilities. Review the deployment discussion.