Generate [AnalysisType] Report for [RegulationSet]

Draft a comprehensive [DocumentType] based on provided transaction data, focusing on [AnalysisType] and ensuring adherence to [RegulationSet].

Template Completion0/3

Build Your Prompt

Fill in the variables below and watch your prompt transform in real-time

Variables

Prompt Explanation

3120 chars58 lines

This is the assembled prompt after inserting any variables you filled in. Placeholders that are not filled remain in [brackets]. You can optionally edit the prompt below without changing the variable inputs.

### Title

Generate [AnalysisType] [DocumentType]

### Objective

The primary objective is to generate a comprehensive [DocumentType] that accurately identifies potential instances of financial irregularities based on the provided context. Success is measured by the clarity, accuracy, and compliance of the final report with [RegulationSet] standards.

### Role / Persona

Act as a Senior Risk Analyst with deep expertise in financial fraud detection, regulatory compliance, and forensic accounting. Your tone should be formal, objective, and precise, suitable for an executive and regulatory audience.

### Context (delimited)

"""
Finance & Stock Market
Risk & Compliance
Fraud detection, legal compliance documentation, and audit report generation.
"""

### Task Instructions

1. Analyze the provided transaction data to identify anomalies and patterns indicative of fraudulent activity.
2. Categorize findings based on risk level (high, medium, low) and the type of potential fraud.
3. Draft a detailed [DocumentType] summarizing the findings.
4. For each significant finding, provide a concise explanation and reference the specific data points that support the conclusion.
5. Conclude with a set of recommendations for mitigation and further investigation.

### Constraints and Rules

- **Scope**: Confine the analysis strictly to the data and context provided. Do not infer or use external information.
- **Length**: The report summary should be between 400–600 words.
- **Tone / Style**: Formal, technical, and impartial.
- **Compliance**: All analysis and recommendations must be consistent with the principles of [RegulationSet].
- **Proficiency / Reading Level**: The document should be written for an expert audience familiar with financial compliance.
- **Delimiters**: Treat the Context block as reference data only; do not include its contents in the final report.

### Output Format

- **Medium**: Plain text.
- **Structure**: Use the following headings in this exact order: Executive Summary, Key Findings, Detailed Analysis, Recommendations, and Compliance Statement.
- **Voice / Tense**: Use active voice and present tense wherever possible.
- **Terminology / Units**: Use standard financial terminology and specify currency units if applicable.

### Evaluation Criteria (self-check before returning)

- All textual placeholders (e.g., '[AnalysisType]') are bracketed and match the frontmatter 'placeholders' array exactly.
- The role, tone, and all constraints (scope, length, compliance) are fully satisfied.
- The output follows the specified format, including all required headings in the correct order.
- Instructions are followed precisely, and the analysis is grounded in the provided context.

### Optional Reasoning

Employ private, step-by-step reasoning to ensure accuracy, but output only the final, formatted report. Do not include your reasoning or thought process in the final deliverable.

### Final Check

Confirm that all instructions, from persona to output format, have been followed exactly before finalizing the response.
Your prompt is ready! Copy it and use it with your favorite AI tool.