SQL Editor and Report Copilot: Overview
1. Overview
1.1 SQL Editor Overview
The SQL Editor is a powerful capability within the BriteCore ecosystem, designed to empower expert users at insurance carriers to take full control of their analytics and reporting capabilities.
It is part of our broader Self-Service Reporting initiative, enabling business intelligence teams, IT specialists, and data-driven professionals to query their datasets directly, safely, and efficiently.
Traditionally, carriers relied heavily on BriteCore support or engineering teams to generate custom reports or extract critical insights. With the SQL Editor, this dependency is reduced. Advanced users can now write, run, and refine their own SQL queries in real time, reducing turnaround times and accelerating data-driven decision-making.
1.2 Self-Service Reporting Workspace
SQL Editor is BriteCore's self-service reporting workspace for users who already think in terms of datasets, joins, filters, and report grain.
Teams can now build repeatable reporting logic in-house.
Reporting users cannot modify the underlying database. SQL Editor exposes logical views, not writable raw tables. These logical views reduce hundreds of physical database tables into a smaller set of well-organized, pre-joined datasets, removing much of the traditional complexity of data access.
1.3 Choosing the Right Tool
We position reporting tools for different user personas:
[Image: Report Copilot modules]
Report Copilot modules
SQL Editor
Best for SQL experts who want full control.
Ideal for users who: - Write and optimize queries and joins manually - Modify stock reports in SQL - Control grain, filters, and parameters - Manage the full report lifecycle
The editor supports: - Authoring - Validation - Saving - Publishing - Movement between sites
Report Copilot - Build Mode
Best for users who want to use AI to build structured reports without focusing on SQL.
In Build Mode: - Users describe what they need in plain language - The system guides them through a structured set of questions - A complete, executable report is generated
This mode is ideal when users want a repeatable report but prefer not to author SQL directly.
Report Copilot - Data Exploration Mode
Best for users who want to derive insights quickly with no SQL familiarity.
In Data Exploration Mode: - Users ask questions in natural language - The system makes reasonable assumptions about fields, grain, and filters - Results are generated immediately
Additional English commands can refine the output, modify fields, or adjust filters.
This mode is ideal for exploratory analysis when speed and accessibility are more important than granular SQL control.
1.4 Unified Operating Model
All three modes (SQL Editor, Report Copilot Build Mode, and Data Exploration Mode) run in the same reporting environment and use the same logical data views.
No matter which tool you select, the following is true:
You can switch between modes as your needs change. For example, you might explore data in natural language first, then move to SQL Editor for deeper customization, all without changing the underlying data source.
Choose the tool that fits how you think and work. The data foundation remains the same.
2. What You Can Do with SQL Editor and Report Copilot
With SQL Editor and Report Copilot, you can:
Build custom reports from BriteCore logical views.
Modify and extend stock reports instead of starting from scratch.
Create reusable parameterized reports for common business questions.
Validate query logic quickly by running reports in the editor.
Format and inspect results before publishing.
Publish reports for other authorized users to run from the standard Report List.
Export and import report definitions in JSON format for movement between environments.
Use AI to build reports in plain English or explore data without writing SQL.
In practice, this means users can choose the level of control that fits their comfort level, from fully manual SQL authoring to guided AI-assisted reporting.