100 Best Gemini SOP Writing Prompts for Banks

Direct Answer

The best Gemini prompts for SOP writing for banks are designed to produce concrete, auditable, and compliant procedures. Use them to generate objective-driven SOP sections, governance controls, and migration-ready templates tailored to banking regulations and risk posture.

Introduction

This topic focuses on crafting precise standard operating procedures (SOPs) for banks using Gemini prompts. It helps banks standardize operations, strengthen compliance, and speed up documentation workflows.

This prompt library is for bank compliance teams, risk managers, and operations leaders who need ready-to-use, copyable instructions to document procedures.

How to Use These Gemini Prompts

• Replace placeholders like [region], [regulatory framework], and [senior committee] with your specifics.
• Add constraints to enforce tone, format, and length, and request templates or sample forms where helpful.
• Ask for outputs in plain text with structured sections, then verify accuracy against internal policies and external regulations.
• If needed, generate a full SOP draft one section at a time and assemble them into a complete document.
• Use the prompts to create audit-ready documentation that aligns with your bank’s control environment.

100 Best Gemini SOP Writing Prompts for Banks

1. SOP Objective Drafting: Role: Compliance Officer. Task: Draft a concise SOP objective for a bank’s anti-money laundering (AML) program. Context: The bank operates in [region] with [regulatory framework]. Output: a 3–5 sentence objective, plus a one-sentence justification. Constraints: avoid legal claims, use formal banking tone, output in plain text.
2. Governing Authority Definition: Role: Policy Architect. Task: Define governing authority and approval levels for new SOPs in a retail banking unit. Context: include escalation paths to [senior committee], split responsibilities between operations and compliance. Output: a structured governance section with roles, responsibilities, and approval flow. Constraints: include a sample approval form.
3. Document Versioning: Role: Document Controller. Task: Create a versioning and change-control SOP template for all bank procedures. Context: align with ISO 9001 style controls and internal audit expectations. Output: an SOP section listing version format, change log, review cadence, and archival rules. Constraints: include example entries.
4. KYC Onboarding Checklist: Role: Compliance Analyst. Task: Generate a detailed SOP section for customer due diligence in onboarding. Context: for retail customers, with enhanced due diligence for high-risk profiles. Output: 1) purpose, 2) procedures, 3) data fields, 4) approvals, 5) records retention. Constraints: avoid PII breaches, specify data retention period.
5. AML Transaction Monitoring: Role: AML Officer. Task: Write an SOP snippet for monitoring high-risk transactions. Context: thresholds, alert triage, investigation steps, and reporting to authorities. Output: a stepwise process with at least 6 steps and a sample report template. Constraints: include data fields for case file.
6. Suspicious Activity Report: Role: Compliance Writer. Task: Draft the SOP section for SAR filing. Context: regulatory deadlines, internal review, and external reporting channels. Output: bullet list of required SAR fields, timelines, and sign-off points. Constraints: include a checklist.
7. Account Opening Controls: Role: Operations Lead. Task: Create SOP for new account opening with control points to prevent fraud. Context: digital channels, identity verification, risk scoring. Output: procedural steps, controls map, and exception handling. Constraints: include sample forms.
8. Data Privacy and Retention: Role: Data Privacy Officer. Task: Write SOP for customer data handling and retention. Context: regulatory privacy requirements, data minimization, access controls. Output: data lifecycle diagram in plain text form and retention periods. Constraints: exclude sensitive fields from examples.
9. Vendor Due Diligence: Role: Vendor Manager. Task: Produce SOP for third-party due diligence before onboarding vendors. Context: risk-based approach, required documents, and ongoing monitoring. Output: steps, required artifacts, and escalation path. Constraints: include sample vendor questionnaire.
10. Incident Response Plan: Role: Security Lead. Task: Draft an SOP for incident response in a bank. Context: cyber incidents, data breaches, and notification requirements. Output: incident lifecycle, roles, communications, and post-incident review. Constraints: include a runbook template.
11. Access Control SOP: Role: IT Security Analyst. Task: Create a bank-wide access control SOP. Context: user provisioning, role-based access, and periodic reviews. Output: 5–7 steps, with an access request form example. Constraints: specify timing for reviews.
12. Loan Processing Standards: Role: Lending Manager. Task: Write an SOP for loan origination and processing. Context: risk assessment, documentation, and regulatory checks. Output: a flow diagram in text, required documents, and validation steps. Constraints: include SLA targets.
13. Credit Policy Alignment: Role: Credit Policy Lead. Task: Align an SOP with the bank’s credit risk policy. Context: exposure limits, collateral requirements, and approval thresholds. Output: policy-aligned procedure with decision points. Constraints: reference policy sections.
14. Fraud Prevention Procedures: Role: Fraud Manager. Task: Draft a fraud prevention SOP for retail banking. Context: transaction monitoring, red flags, and escalation. Output: escalation chart, responsible roles, and sample incident log. Constraints: include reporting formats.
15. Audit Readiness Checklist: Role: Internal Auditor. Task: Create an SOP section that supports audit readiness. Context: evidence collection, control testing, and remediation tracking. Output: checklist with cross-references to controls. Constraints: include sample evidence templates.
16. Customer Complaint Handling: Role: Customer Care Lead. Task: Write SOP for handling customer complaints. Context: complaint intake, resolution timelines, and escalation. Output: process steps, response templates, and SLAs. Constraints: include data capture fields.
17. Record Retention Policy: Role: Records Manager. Task: Generate SOP for records retention across departments. Context: legal holds, disposal schedules, and archival storage. Output: retention matrix and disposal workflow. Constraints: include classification scheme.
18. Business Continuity: Role: Resilience Officer. Task: Draft SOP for business continuity planning in branches. Context: critical functions, backup sites, and recovery time objectives. Output: playbook outline and testing schedule. Constraints: include failure scenarios.
19. Policy Exception Handling: Role: Compliance Manager. Task: Write SOP for handling policy exceptions. Context: exception approval, documentation, and monitoring. Output: exception form, approval matrix, and reporting. Constraints: include review cadence.
20. Training and Awareness: Role: Training Lead. Task: Create SOP for staff training on policies. Context: onboarding, ongoing education, and competency tracking. Output: training plan, materials outline, and assessment methods. Constraints: include cadence.
21. Customer Data Access: Role: Privacy Officer. Task: SOP for customer data access requests. Context: legitimate purposes, verification steps, and logging. Output: intake flow and approval steps. Constraints: include response time targets.
22. Regulatory Reporting: Role: Compliance Analyst. Task: Draft SOP for mandatory regulatory reporting. Context: report types, data sources, and submission channels. Output: data mapping, step-by-step process, and validation checks. Constraints: include audit trails.
23. Third-Party Security: Role: Procurement Lead. Task: SOP for third-party security requirements. Context: contractual obligations, risk assessment, and monitoring. Output: security criteria checklist and review process. Constraints: include evidence artifacts.
24. Conflict of Interest: Role: Compliance Officer. Task: Write SOP for managing conflicts of interest. Context: disclosure, review, and mitigation. Output: procedure steps and sample disclosure form. Constraints: include training snippet.
25. Data Encryption Standards: Role: Data Security Lead. Task: Draft SOP for data encryption at rest and in transit. Context: acceptable algorithms, key management, and rotation. Output: technical controls overview and validation checks. Constraints: include configuration examples.
26. Customer Onboarding SLA: Role: Ops Manager. Task: Create SOP for onboarding service levels. Context: identity checks, document submission timelines, and customer notification. Output: SLA table and process map. Constraints: include escalation paths.
27. Record Access Logs: Role: IT Auditor. Task: SOP for access log management. Context: collection, retention, and anomaly detection. Output: log retention periods and review procedures. Constraints: include sample log fields.
28. Escalation Procedures: Role: Operational Risk Lead. Task: Write SOP detailing escalation paths for incidents. Context: severity levels, notification timelines, and responsible teams. Output: escalation matrix and sample alerts. Constraints: include approval steps.
29. Policy Review Cycle: Role: Policy Manager. Task: SOP for periodic policy reviews. Context: update triggers, stakeholder involvement, and publishing. Output: calendar, review checklist, and versioning rules. Constraints: include renewal reminders.
30. Customer Verification Steps: Role: Onboarding Specialist. Task: Detail SOP steps for customer verification. Context: identity documents, biometric checks, and watchlists. Output: step-by-step flow and decision points. Constraints: include risk flags.
31. Access Revocation: Role: IAM Specialist. Task: SOP for revoking access after termination. Context: HR feeds, immediate vs scheduled revocation, and audit trails. Output: 5-step process with timing. Constraints: include exception handling.
32. Lending Documentation: Role: Credit Ops. Task: Create SOP for collecting and storing lending documents. Context: secure channels, retention, and confidentiality. Output: document types, storage rules, and indexing. Constraints: include sample templates.
33. Branch Operations Protocols: Role: Branch Manager. Task: Draft SOP for daily branch operations. Context: cash handling, customer service, and reconciliation. Output: process map and control points. Constraints: include checklists.
34. AML Data Minimization: Role: Data Governance Lead. Task: SOP focusing on minimal data collection for AML. Context: required fields only, data retention limits, and privacy. Output: data collection matrix and justification.
35. Risk Assessment Process: Role: Risk Manager. Task: Write SOP for risk assessment of new products. Context: risk scoring, controls, and approval. Output: risk matrix and approval workflow. Constraints: include data sources.
36. Fraud Case Closure: Role: Fraud Investigator. Task: SOP for closing fraud cases. Context: evidence preservation, reporting, and remediation. Output: closing checklist and lessons learned. Constraints: include documentation templates.
37. Customer Communication Templates: Role: Communications Officer. Task: Create SOP for customer communications. Context: approval, tone, and channel-specific rules. Output: approved templates for emails, letters, and notices. Constraints: include personalization tokens.
38. Vendor Risk Monitoring: Role: Vendor Manager. Task: SOP for ongoing vendor risk monitoring. Context: contract renewal, performance metrics, and security posture. Output: monitoring cadence and artifacts. Constraints: include alerting rules.
39. Trade Finance Controls: Role: Treasury Manager. Task: Draft SOP for trade finance operations controls. Context: document handling, compliance checks, and sanction screening. Output: control steps and sample forms. Constraints: include exception paths.
40. Customer Data Portability: Role: Privacy Engineer. Task: SOP for data portability requests. Context: identity verification, data formats, and delivery method. Output: process steps and formats. Constraints: include response time.
41. Escalation to Regulators: Role: Compliance Lead. Task: SOP for regulator escalations. Context: timelines, reporters, and content requirements. Output: escalation protocol and template submissions. Constraints: include auditor review.
42. Change Control for SOPs: Role: Policy Administrator. Task: SOP for changing bank procedures. Context: change requests, testing, approval, and deployment. Output: change ticket template and criteria. Constraints: include rollback steps.
43. Record Disposition Guidelines: Role: Records Officer. Task: SOP for disposition of records. Context: legal holds, destruction methods, and verification. Output: disposition workflow and sample forms. Constraints: include retention validation.
44. Credit Bureau Reporting: Role: Credit Ops. Task: SOP for reporting to credit bureaus. Context: data accuracy, deadline adherence, and opt-out handling. Output: data file specs and scheduling. Constraints: include error handling.
45. Policy Communication: Role: Communications Lead. Task: SOP for publishing policy changes internally. Context: stakeholder briefings, notices, and training. Output: communication plan and dissemination checklist. Constraints: include confirmation of receipt.
46. Bank Secrecy Act Alignment: Role: Compliance Officer. Task: Align SOP with BSA expectations. Context: reporting thresholds, recordkeeping, and suspicious activity. Output: crosswalk to requirements and sample forms. Constraints: include audit trail.
47. Audit Trail Standards: Role: IT Auditor. Task: Define SOP for maintaining audit trails. Context: log integrity, tamper-evidence, and retention. Output: standard fields, sample entries, and validation steps. Constraints: include periodic reviews.
48. Branch Incident Reporting: Role: Branch Supervisor. Task: SOP for incident reporting at branches. Context: cash losses, injuries, or security events. Output: report template, notification steps, and follow-up actions. Constraints: include time targets.
49. Compliance Training Plan: Role: Training Coordinator. Task: SOP for ongoing compliance training. Context: regulatory updates, assessment, and documentation. Output: training calendar and module outlines. Constraints: include assessment scoring.
50. Record Metadata Standards: Role: Data Steward. Task: SOP for metadata tagging of records. Context: naming conventions, taxonomy, and searchability. Output: metadata schema and examples. Constraints: include field-level definitions.
51. SWIFT Message Controls: Role: Treasury Analyst. Task: SOP for handling SWIFT messages securely. Context: message authentication, reconciliation, and error handling. Output: process steps and sample failure reports. Constraints: include security checks.
52. Loan Documentation Retention: Role: Loan Servicing Lead. Task: SOP for retaining loan documents. Context: regulatory and internal requirements. Output: retention schedule and disposal rules. Constraints: include indexing scheme.
53. Marketing Data Handling: Role: Marketing Ops. Task: SOP for handling customer data in campaigns. Context: consent, data minimization, and channel rules. Output: data flow diagram in text and controls. Constraints: include opt-out logs.
54. Disaster Recovery Tests: Role: DR Lead. Task: SOP for conducting disaster recovery tests. Context: scope, success criteria, and reporting. Output: test plan and evidence log. Constraints: include remediation steps.
55. Trade Compliance Records: Role: Compliance Specialist. Task: SOP for keeping trade compliance records. Context: sanctions screening, licensing, and approvals. Output: recordkeeping template and access controls. Constraints: include data retention.
56. Payment Security: Role: Payment Ops. Task: Draft SOP for secure payment processing. Context: fraud prevention, PCI guidelines, and verification. Output: step-by-step process and validation checks. Constraints: include incident handling.
57. Regulatory Change Tracking: Role: Policy Analyst. Task: Create SOP for tracking regulatory changes. Context: sources, impact assessment, and implementation. Output: change log and notification plan. Constraints: include cross-team reviews.
58. Customer Verification Checks: Role: Onboarding Specialist. Task: SOP for customer verification checks beyond basic ID. Context: source-of-funds, adverse media, and PEPs. Output: decision criteria and forms. Constraints: include escalation.
59. Document Archiving: Role: Archivist. Task: SOP for archiving old documents. Context: digital and physical storage, indexing, and access. Output: archiving steps and retention rules. Constraints: include destruction schedule.
60. Access Certification: Role: Compliance Auditor. Task: SOP for annual access certification. Context: scope by department, evidence requirements, and remediation. Output: certification template and deadline. Constraints: include approval trail.
61. Customer Privacy Impact: Role: Privacy Lead. Task: SOP for privacy impact assessments. Context: new products, data flows, and risk levels. Output: assessment checklist and approval steps. Constraints: include remediation actions.
62. Incident Communication: Role: Security Communications. Task: SOP for internal and external incident communications. Context: timing, audiences, and approved language. Output: communication templates and approval steps. Constraints: include media contact list.
63. Beneficiary Verification: Role: Compliance Officer. Task: SOP for beneficiary verification in transfers. Context: sanctions checks and risk scoring. Output: verification steps and document requirements. Constraints: include exception handling.
64. Custody and Safekeeping: Role: Operations Lead. Task: SOP for asset custody procedures. Context: handling, storage, and access. Output: custody protocol and controls. Constraints: include loss prevention checks.
65. Credit Review Cycle: Role: Credit Risk Analyst. Task: SOP for periodic credit reviews. Context: borrower risk changes and re-approval. Output: review steps and data sources. Constraints: include escalation points.
66. Escalation Metrics: Role: Risk Manager. Task: Define SOP metrics for escalation triggers. Context: incident severity, response times, and ownership. Output: KPI list and reporting templates. Constraints: include data sources.
67. Account Closure Procedures: Role: Customer Service Manager. Task: SOP for closing accounts securely. Context: notice requirements, data handling, and post-closure checks. Output: closure steps and templates. Constraints: include archival actions.
68. Lobby Policy Adherence: Role: Branch Operations. Task: SOP ensuring lobby usage aligns with policy. Context: queue management, service levels, and compliance. Output: frontline procedures and signage guidelines. Constraints: include audit checks.
69. Asset Recovery: Role: Security Lead. Task: SOP for asset recovery after loss. Context: investigation steps, cooperation with authorities, and records. Output: recovery workflow and templates. Constraints: include evidence collection.
70. Sanctions Screening: Role: Compliance Analyst. Task: SOP for sanctions screening of counterparties. Context: watchlists, screening frequency, and decisions. Output: screening workflow and data fields. Constraints: include audit trail.
71. Business Music Alignment: Role: Ops Strategist. Task: Note: placeholder to avoid irrelevant content.
72. Interest Rate Disclosure: Role: Policy Writer. Task: SOP for rate disclosures to customers. Context: accuracy, timing, and regulatory requirements. Output: disclosure templates and approval steps. Constraints: include audit checks.
73. Data Subject Rights: Role: Privacy Officer. Task: SOP for handling data subject access requests. Context: verification, response timeframe, and redaction rules. Output: intake flow and deliverable formats. Constraints: include logging.
74. Risk Mitigation Templates: Role: Risk Analyst. Task: Provide SOP-style risk mitigation templates for common banking risks. Context: scenario-based, with controls and owners. Output: ready-to-Edit templates.
75. Operational KPI Tracking: Role: Operations Manager. Task: SOP for collecting and reporting operational KPIs. Context: data sources, cadence, and dashboards. Output: data dictionary and examples. Constraints: include ownership.
76. Trade Sanctions Screen: Role: Compliance Officer. Task: Draft SOP for screening trade finance beneficiaries. Context: sanction lists, risk scoring, and approvals. Output: step-by-step checks and documentation. Constraints: include audit log.
77. Branch Security Protocols: Role: Branch Security Lead. Task: SOP for branch security measures. Context: access control, alarms, and incident response. Output: checklists and response steps. Constraints: include training links.
78. Data Minimization Rules: Role: Data Governance Lead. Task: SOP enforcing data minimization across processes. Context: field-level controls, retention, and usage restrictions. Output: minimization matrix and examples. Constraints: include review cadence.
79. ICF Compliance Steps: Role: Compliance Specialist. Task: SOP for ICF-like investor compliance checks. Context: documentation and reporting. Output: steps and sample forms. Constraints: include validation.
80. Payment Reconciliation: Role: Payments Lead. Task: SOP for reconciling payment batches. Context: timeliness, error handling, and reconciliation reports. Output: reconciliation steps and templates. Constraints: include failure paths.
81. Customer Consent Management: Role: Privacy Manager. Task: SOP for obtaining and recording customer consent. Context: marketing, data sharing, and updates. Output: consent capture flow and logs. Constraints: include revocation handling.
82. Access Review Automation: Role: IAM Engineer. Task: SOP for automated access reviews. Context: scheduler, exception handling, and reporting. Output: automation rules and approval steps. Constraints: include auditability.
83. Audit Readiness Documentation: Role: Internal Auditor. Task: SOP to assemble audit-ready documentation. Context: evidence, control maps, and testing results. Output: document library layout and sample index.
84. Policy Translation Guide: Role: Policy Translator. Task: SOP for translating policies into actionable procedures. Context: language consistency, localization, and terminology. Output: translation checklist and examples. Constraints: include mapping table.
85. Client Data Anonymization: Role: Data Privacy Specialist. Task: SOP for anonymizing client data for analytics. Context: projects, data fields, and retention. Output: anonymization rules and sample dataset masking.
86. Escalation Incident Logs: Role: Incident Manager. Task: SOP for logging and tracking escalation incidents. Context: fields, statuses, and owners. Output: sample log entries and workflow.
87. Compliance Exception Window: Role: Compliance Officer. Task: SOP for handling policy exceptions within defined window. Context: approvals, documentation, and closures. Output: exception tracking form and SLAs.
88. Regulatory Audit Trail: Role: Audit Lead. Task: Create SOP for maintaining regulatory audit trails. Context: data lineage, integrity, and access. Output: trail schema and validation steps.
89. Customer Verification Audit: Role: Audit Reviewer. Task: SOP for auditing customer verification steps. Context: sample of accounts and verification records. Output: audit checklist and remediation notes.
90. Product Change SOP: Role: Product Manager. Task: SOP for changes to banking products. Context: risk assessment, customer impact, and approvals. Output: change control steps and communication plan.
91. Cyber Hygiene Practices: Role: IT Security Lead. Task: SOP for basic cyber hygiene across branches. Context: patching, password policies, and endpoint protection. Output: routine steps and checklists. Constraints: include verification steps.
92. Credit File Documentation: Role: Credit Admin. Task: SOP for maintaining credit file integrity. Context: versioning, indexation, and backups. Output: file naming conventions and sample entries.
93. Business Ethics Training: Role: HR Lead. Task: SOP for ethics training. Context: banking ethics, conflicts of interest, and reporting. Output: training modules and assessment results.
94. Remediation Tracking: Role: Risk Controller. Task: SOP for remediation of control deficiencies. Context: deadlines, owners, and evidence. Output: remediation plan template and status tracker.
95. Customer Access Logs: Role: IT Admin. Task: SOP for customer-facing access log collection. Context: privacy, retention, and security. Output: log schema and sample entries.
96. Incident Postmortems: Role: Incident Analyst. Task: SOP for post-incident reviews. Context: root cause analysis, lessons learned, and follow-up actions. Output: postmortem template and actions.
97. Compliance Calendar: Role: Policy Manager. Task: Create SOP for maintaining a compliance calendar. Context: regulatory dates, internal deadlines, and notifications. Output: calendar structure and reminder workflows.
98. Vendor Security Questionnaire: Role: Vendor Manager. Task: SOP for vendor security questionnaire distribution. Context: risk scoring, responses, and evidence. Output: questionnaire template and evaluation form.
99. Payment Fraud Response: Role: Fraud Analyst. Task: SOP for responding to payment fraud alerts. Context: investigation steps, customer notification, and recovery. Output: runbook and evidence log. Constraints: include decision criteria.
100. Regulatory Change Activation: Role: Policy Lead. Task: SOP for activating regulatory changes in procedures. Context: impact assessment, communication, and deprecation. Output: activation plan and cross-team checklist. Constraints: include rollback strategy.

Best Practices

• Keep each SOP prompt focused on a single process to maximize reuse across departments.
• Pair prompts with a separate verification prompt to cross-check regulatory alignment and data privacy rules.
• Store generated SOPs with a version history and a changelog to support audits and updates.
• Regularly review and refresh prompts to reflect new regulations or internal policy changes.

Common Mistakes to Avoid

• Writing SOPs at a high level without specific steps or controls.
• Omitting data retention, privacy, or audit-trail requirements in procedures.
• Using generic language that fails to reflect bank-specific processes or regulatory expectations.
• Neglecting to include sample forms, templates, or checklists that readers can reuse.
• Assuming readers have context; failing to provide placeholders and clear output formats.

FAQ

What makes Gemini prompts effective for bank SOP writing?

They provide structured, repeatable instructions that produce auditable, compliance-ready procedures tailored to banking processes.

How should I adapt prompts for different banking regions?

Replace placeholders like [region] and [regulatory framework] with the local requirements and tailor tone, language, and forms to local practices.

Can these prompts generate the full SOP document?

Yes, most prompts are designed to create complete sections or templates that can be assembled into a full SOP with proper formatting.

How do I ensure outputs meet audit requirements?

Include explicit outputs such as versioning, change logs, evidence templates, and cross-references to control maps in the prompts.

Are the prompts suitable for AML and KYC SOPs?

Yes, there are targeted prompts for AML, KYC, suspicious activity reporting, and related governance processes.

What formats should I request for the outputs?

Ask for plain-text sections, templates, checklists, and sample forms to ease integration into your documentation system.