# Asking Effective Compliance Questions: Get Accurate Answers from RuleWise Getting the right answer starts with asking the right question. RuleWise's AI is powerful, but like any tool, it works best when you know how to use it effectively. This guide will help you craft questions that get you accurate, actionable compliance guidance from your organization's knowledge base. ## How RuleWise Understands Your Questions ### The Knowledge Base Search Process When you ask a question, RuleWise goes through several steps: 1. **Analyzes Your Query**: Understands the intent and key concepts in your question 2. **Searches Organization Policies**: Looks through all your organization's uploaded compliance documents 3. **Searches Jurisdiction Regulations**: Checks regulations for all jurisdictions your organization has enabled (EU, US, UK, Guernsey, etc.) 4. **Ranks Results**: Finds the most relevant sections based on semantic similarity to your question 5. **Synthesizes Answer**: Combines relevant information into a coherent, contextualized response 6. **Provides Sources**: Shows exactly where the information came from **Key Insight**: RuleWise doesn't just match keywords—it understands concepts. You can ask "How should I handle a customer complaint?" and it will find relevant sections even if your policy uses terms like "client grievance procedure" or "customer dispute resolution." ### What Makes a Good Question **Good questions are:** - **Specific**: Focus on a particular situation or requirement - **Contextual**: Include relevant details about your role or scenario - **Action-Oriented**: Ask what you should do or know, not just theoretical information - **Clear**: Use straightforward language without unnecessary complexity ## Question Patterns That Work Well ### Scenario-Based Questions Frame your question as a real scenario you're facing: **Example 1 - Client Interaction:** "A client has asked me to expedite their wire transfer request outside of normal procedures. What does our policy say about handling these requests?" **Why This Works:** - Describes a specific situation - Implies you need procedural guidance - RuleWise can find both the wire transfer policy and exceptions procedures **Example 2 - Data Handling:** "I received an email from a customer asking to delete all their information from our systems. What is our process for handling this request, and what are the timelines?" **Why This Works:** - Clear scenario (GDPR right to erasure request) - Multiple specific questions (process AND timelines) - Actionable—you need to know what to do next ### Policy Lookup Questions Ask directly about policies and procedures: **Example 1 - Finding Specific Requirements:** "What are the documentation requirements for onboarding a new corporate client?" **Why This Works:** - Specific process (onboarding) - Specific client type (corporate) - Clear information need (documentation requirements) **Example 2 - Understanding Limits:** "What is the monetary threshold for requiring additional approval on client transactions?" **Why This Works:** - Asks for a specific data point (threshold) - Clear scope (client transactions) - Practical application (when do I need approval) ### Comparative Questions Ask how different requirements or policies relate: **Example 1 - Cross-Jurisdiction:** "How do our data retention requirements differ between our EU and US operations?" **Why This Works:** - Leverages multi-jurisdiction capability - Clear comparison request - Practical implications (do I handle EU vs US clients differently?) **Example 2 - Policy Relationships:** "How does our gifts and entertainment policy interact with our anti-bribery procedures?" **Why This Works:** - Recognizes that policies overlap - Asks about practical application - RuleWise will find relevant sections from multiple documents ### Clarification Questions When you need something explained more clearly: **Example 1 - Simplification:** "Can you explain our AML risk assessment process in simpler terms? What are the basic steps I need to follow?" **Why This Works:** - Explicitly asks for simpler explanation - Requests step-by-step breakdown - Acknowledges you need practical guidance **Example 2 - Definition:** "What exactly counts as 'suspicious activity' under our transaction monitoring policy?" **Why This Works:** - Asks for specific definition - References the relevant policy - Helps understand application criteria ## Adding Context for Better Answers ### Mention Your Role Including your role helps RuleWise tailor the answer: **Without Role Context:** "What are the compliance requirements for client communications?" **With Role Context:** "As a financial advisor, what compliance requirements apply to my email communications with clients?" **The Difference:** The second version will get you guidance specific to advisor-client communications, not general corporate communications policies. ### Specify the Situation Type **General Question:** "What is our escalation procedure?" **Specific Question:** "What is the escalation procedure when I identify a potential conflict of interest with a client relationship?" **The Difference:** The specific version will find the right escalation path for compliance issues, not general operational escalations. ### Include Relevant Timeframes **Vague:** "What are our record retention requirements?" **Specific:** "How long must I retain client meeting notes and correspondence under our record retention policy?" **The Difference:** The specific version will give you exact retention periods for the document types you care about. ## Question Techniques by Use Case ### For Daily Operations **Ask About Workflows:** "What is the step-by-step process for reporting a suspicious transaction?" **Ask About Requirements:** "What information am I required to collect during client account opening?" **Ask About Deadlines:** "What is the timeline for completing mandatory compliance training?" ### For Client Interactions **Ask About Permissions:** "Under what circumstances can I share client information with third parties?" **Ask About Limitations:** "What investment products am I not permitted to recommend to retail clients?" **Ask About Documentation:** "What documentation do I need to keep when a client makes an investment decision against my recommendation?" ### For Unusual Situations **Ask About Exceptions:** "Are there any exceptions to our standard client onboarding procedures for emergency situations?" **Ask About Edge Cases:** "How should I handle a compliance training requirement if I was on medical leave during the required completion period?" **Ask About Grey Areas:** "If a client gives me a holiday gift, at what value does it become a compliance issue?" ### For Learning and Development **Ask About Principles:** "What are the core principles behind our market abuse prevention policies?" **Ask About Rationale:** "Why does our policy require dual authorization for transactions over $50,000?" **Ask About Examples:** "Can you give me examples of situations that would violate our code of conduct?" ## Interpreting Answers and Sources ### Understanding Source Citations RuleWise shows you exactly where information came from: **Example Citation Format:** > Source: Anti-Money Laundering Policy, Section 4.2, Pages 12-14 > Source: GFSC Handbook, Module 2.3 (Jurisdiction: Guernsey) **What This Tells You:** - **Document Name**: Which policy or regulation - **Section/Page**: Where to find the original text - **Jurisdiction**: If it's regulatory content, which jurisdiction it applies to **Why Sources Matter:** - Verify the answer if needed - Reference in your own documentation - Understand if it's organizational policy vs. regulatory requirement - Know which jurisdiction's rules apply ### When Multiple Sources Appear Sometimes RuleWise will cite multiple documents: > Based on your organization's policies and applicable regulations: > > **Internal Policy**: Your Client Onboarding Procedure (Section 2) requires... > > **Regulatory Requirement**: GDPR Article 6 (Jurisdiction: EU) mandates... > > **Best Practice**: The FCA's guidance (Jurisdiction: UK) recommends... **How to Use This:** - **Must-Dos**: Regulatory requirements and internal policies are mandatory - **Should-Dos**: Best practices and guidance are strong recommendations - **Context**: Understand which requirements apply to which situations ### When RuleWise Doesn't Have an Answer If your knowledge base doesn't contain relevant information, RuleWise will tell you: > "I couldn't find specific information about [your question] in your organization's uploaded policies. However, based on general regulatory guidance..." **What This Means:** - Your organization may not have uploaded a policy covering this area - You might want to flag this to your compliance team - The general guidance provided is a starting point, not organizational policy **What to Do:** - Contact your compliance officer or manager - Suggest uploading relevant policies if they exist - Document the gap for policy development ## Following Up for Deeper Understanding ### Building on Previous Answers RuleWise remembers your conversation context. Use this to dig deeper: **First Question:** "What is our policy on accepting client gifts?" **Follow-Up Questions:** - "Does this apply to gifts from prospective clients as well?" - "How should I report a gift I've received?" - "What if the gift is below the threshold but I receive multiple small gifts from the same client?" - "Are there different rules for gifts versus entertainment?" **Why This Works:** Each follow-up builds on the previous answer, creating a comprehensive understanding of the topic. ### Asking for Examples or Scenarios If a policy seems abstract, ask for concrete examples: **After Receiving a Policy Answer:** "Can you give me three specific examples of situations where this policy would apply to my daily work?" **Asking for Counterexamples:** "What would be examples of situations where this policy does NOT apply?" ### Requesting Procedural Breakdowns Turn policy into action steps: **Policy-Focused Question:** "What is our data breach response policy?" **Action-Focused Follow-Up:** "What are the specific steps I should take in the first hour after discovering a potential data breach?" ## Common Mistakes to Avoid ### Too Vague **Problem Question:** "Tell me about compliance." **Better Version:** "What are the key compliance requirements I need to know as a new financial advisor?" **Why:** Compliance is too broad. The better version has scope (financial advisor) and purpose (key requirements for new role). ### Too Many Questions at Once **Problem Question:** "What are our AML policies, CTF procedures, sanctions screening requirements, and PEP identification processes?" **Better Approach:** Ask these as separate questions, or: "What are the main components of our financial crime prevention framework?" **Why:** Focused questions get more detailed answers. If you need comprehensive information, start broad then drill down. ### Assuming RuleWise Knows Your Specific Case **Problem Question:** "What should I do about the Johnson account?" **Better Version:** "I have a client account where suspicious wire transfers have been flagged by our monitoring system. What is our procedure for investigating and potentially filing a SAR?" **Why:** RuleWise doesn't have access to specific account data. Describe the scenario generally and ask about the procedure. ### Using Only Keywords **Problem Question:** "GDPR Article 17" **Better Version:** "What does GDPR Article 17 require our organization to do when a customer requests deletion of their personal data?" **Why:** RuleWise can give you more helpful answers when you explain what you need to know about the regulation. ## Advanced Question Techniques ### Combining Jurisdictional Requirements If your organization operates in multiple jurisdictions: **Example:** "We're launching a new investment product available to both EU and UK clients. What are the key regulatory differences in how we must disclose risks to clients in each jurisdiction?" **Why This Works:** - Specific scenario (new product launch) - Clear jurisdictional scope (EU and UK) - Focused question (risk disclosure requirements) - Comparative (differences between jurisdictions) ### Asking About Policy Changes **Example:** "Have there been any updates to our remote work policy in the last six months, particularly regarding data security requirements?" **Why This Works:** - Specific policy area - Timeframe specified - Particular aspect highlighted (data security) ### Requesting Compliance Checklists **Example:** "Can you create a checklist of all the compliance steps required before launching a new marketing campaign for investment products?" **Why This Works:** - Specific process (marketing campaign launch) - Product context (investment products) - Actionable format (checklist) - RuleWise can compile requirements from multiple policies ## Getting the Most Value ### Regular Question Patterns Develop regular habits: **Weekly:** "Are there any new regulatory updates in our enabled jurisdictions this week?" **Before Key Activities:** "What are the compliance requirements I need to check before conducting client reviews?" **After Training:** "Can you quiz me on the key points from our insider trading policy?" ### Building Compliance Knowledge Use RuleWise to learn, not just to get quick answers: **Learning Questions:** - "What are the most common compliance violations in financial services and how does our policy address them?" - "Can you explain the rationale behind our client suitability assessment requirements?" - "How do different regulatory frameworks approach the same compliance issue?" ### Collaborating with Your Team Share effective questions with colleagues: - If you get a particularly helpful answer, share the question phrasing with your team - Create a team knowledge base of common compliance questions - Use RuleWise in team meetings to resolve policy questions in real-time ## Conclusion Asking effective compliance questions is a skill that improves with practice. The key principles are: 1. **Be Specific**: Describe your actual situation or need 2. **Add Context**: Include your role, the scenario, and relevant details 3. **Ask for Action**: Focus on what you need to do or know 4. **Follow Up**: Build on answers to deepen understanding 5. **Use Sources**: Pay attention to where information comes from Remember, RuleWise is designed to help you navigate complex compliance requirements. Don't hesitate to ask follow-up questions, request clarification, or approach the same topic from different angles until you have the understanding you need. The more thoughtfully you ask questions, the more valuable RuleWise becomes as your compliance assistant. Happy questioning! **Next Steps**: Check out our guide on "Working with AI Agents" to learn how specialized agents like Insight, Quest, and Probe can help with different types of compliance tasks.