Beta Note: Report Copilot is currently in beta and is being rolled out to clients in stages. If you do not see Enable AI in your SQL Editor toolbar, contact your BriteCore account team.
Report Copilot is a single assistant that handles the whole reporting task for you. Describe the report you need or ask a question about your data. The Copilot works out what it needs to know, asks you only when something is ambiguous, plans the query, writes and tests the SQL against your data, and returns the results in the output pane. You then refine in conversation, save the report, or take the SQL into the editor.
Open Report Copilot
- Open Reports, then SQL Editor.
- To the right of the main toolbar, select Enable AI. The Copilot panel opens on the right.
- Type your request in the panel, or select one of the suggested prompts.
Build a New Report
The process is largely self-guided:
- Tell the Copilot what report you want, including the fields, filters, aggregations (such as count or sum), and sorting. You can also attach documentation or a specification to the request, though very large files may exceed system limits.
- Answer the Copilot's clarifying questions. It asks for the report name and purpose, and for anything it cannot infer, such as what a claim amount should include, which closed claims to count, or how a date should be defined. It also interprets and corrects obvious typing errors.
- Review the plan the Copilot presents and confirm it. If something is wrong, say so and the Copilot revises the plan.
- Wait while the Copilot generates the report. It writes the SQL, runs it, checks the output, and refines the query before returning the final results in the output pane.
- Refine the report with follow-up instructions until it meets your needs, for example “Add the agency name” or “Sort by paid amount, largest first.”
- Save the report using the SQL Editor tools. The generated SQL, parameters, and column formats are saved with it. See Saving, Publishing, and Moving Reports.
Answer a Data Question
You do not have to build a report to get an answer. Ask the Copilot a question such as “How many homeowners policies did we write in Texas last quarter?” or “Which agencies had the highest loss ratio in 2025?” The Copilot chooses the relevant views and fields, applies the most likely interpretation of your question, runs the query, and gives you the answer with the supporting rows. If its assumptions are not what you meant, tell it and it adjusts. When an answer turns out to be something you need regularly, ask the Copilot to turn it into a report and save it.
Modify an Existing Stock Report
When BriteCore already has a similar report and you want to make slight modifications, open the report in the editor and run it once so you can see the output in its standard configuration. Then tell the Copilot in plain language what you want to change, for example “Please remove claim_id and add the description field.” The Copilot edits the SQL, runs it, and shows the result. Save the modified report under a new name so the stock report is unchanged.
Migrate a BriteData Report
When you open a legacy BriteData report in SQL Editor, the Copilot offers to translate it into a SQL Editor report and validate the result against the report's most recent output. See Migrating BriteData Reports with Report Copilot.
Write Better Prompts
- Be specific about metrics, filters, dimensions, and output shape. “One row per claim, with claim number, loss date, state, and paid amount, for claims closed in 2025” gets a better first result than “a claims report.”
- State the grain in plain language, for example “one row per policy per month.”
- Ask the Copilot to explain its assumptions before it generates the final SQL if the question is open to interpretation.
- Review the generated SQL. Copilot output is a strong draft, but you are responsible for validating the results before publishing. See Running Reports and Interpreting Results.
