A CIRO request for a trader's recorded calls, run with Claira
An invented Montreal dealer receives a request from CIRO Enforcement Staff for one trader's calls, chats and email. This is how its outside counsel could run the review with Claira, from the first look at the recordings to the record of how the review was done.
- Cenário
- A Montreal investment dealer answering a CIRO request about a trader's recorded calls
- Tribunal
- Canada: an investigation by CIRO Enforcement Staff under the Investment Dealer and Partially Consolidated Rules
- Em nome de
- The dealer, through its outside counsel
Um cenário inventado que segue uma situação comum. As partes são fictícias, e nada aqui constitui aconselhamento jurídico.
A request for information arrives
In this invented matter, a mid-sized investment dealer in Montreal receives a Request for Information from CIRO Enforcement Staff under Rule 8100 of the Investment Dealer and Partially Consolidated Rules. Staff want eight months of records on one fixed-income trader's dealings with an institutional client: the recorded calls, the chats and the email, along with the order and trade records. We act for the dealer as its outside counsel. The trader has separate counsel, which limits what the dealer's team can discuss with the trader as the review goes on.
CIRO's Enforcement Document Production Guide, in force since May 1, 2026, sets the shape of the delivery. Staff prefer records in their native format, audio from telephone recording systems goes with the call information for each recording, and a production carries a .dat metadata load file. The collection is loaded into Nuix Discover, and before anyone promises Staff a date, the team needs to know what the dealer actually holds.
Measuring the collection before the first prompt
Claira's early case assessment opens from the Claira menu under More. It works from metadata alone, reading no content and writing nothing to Discover, and reports volume, people, date coverage and suggested segments, with a PDF the team can keep on file. In this matter it would show the share of audio in the set, the custodians behind the mail and chat, and the busiest months on the trader's lines.
That picture lets the team scope the review set the way Claira's relevance workflow recommends. The supervising partner agrees the custodians, the date range and the document types, families stay together, and the set is saved in a binder with its count. The same picture shows gaps early. If the recordings for one desk line stop for three weeks, the team wants to find that before Staff do, so the dealer can explain the outage in its written response.
A Review Mandate built from the request letter
Case Context comes next. Under New context, the Regulatory investigation template creates a Review Mandate for the regulator's scope. The team selects up to five key documents in Discover, such as the Request for Information, the surveillance summary and the client's account agreement, and clicks Generate from selection. Claira fills in the sections and lists the missing information it still needs, and a lawyer works through those questions with Answer with Agent. A partner then clicks Approve, which locks the mandate and makes it available to the Prompt Generator.
The prompt follows from the mandate. For the calls, a single Multi-Code instruction can fill several fields in one pass: the primary language, a two-sentence English summary, whether the call touches the client's orders, and a relevance call against the request. The team tries it with Single Review on a dozen recordings that a bilingual associate has already heard, and revises the wording until the answers match what the associate expects.
Scanning the trading desk's recordings
The dealer records its trading lines, and the calls in this set run in French and English. With the Scan as dropdown set to Audio, Claira reads the recording itself, which suits call recordings of up to about eight hours each. The email and chat go through a separate pass as text.
A bulk scan starts from Bulk Scanning mode once the prompt version is marked Final. The confirmation dialog shows the document count, the input mode, the destination field and an estimated duration. Ticking Write the prompt to each document's Prompt Log keeps the instruction on record beside the results. A set of this size suits Run as background processing task, which also raises the file size Claira accepts for media from 23 MB to 50 MB. The answers arrive in the dealer's own Discover fields, where reviewers search and batch them as they always have, and the English summaries tell the team which calls to hear first.
Checking the calls and finding the privileged mail
Before the results go anywhere, the team checks them. Following Claira's relevance workflow, they open the finished task under Bulk Tasks, read the counts of succeeded, failed and skipped documents with the reasons given, and build samples from searches on the result fields: relevant, not relevant, and the calls the prompt rated with low confidence. A bilingual associate listens to the sampled calls and records agreement in a separate field, and the agreement rate goes in the file.
Privilege needs its own pass. Some of the email runs between the trader's supervisor, compliance and the dealer's in-house lawyers, and some was written after the request arrived. Claira's privilege review prompt analyses documents under Canadian law and, as written, asks for the privilege call, the types, the parties involved, a justification and supporting excerpts. With the in-house lawyers named in the Case Context, those answers give the team a first sort. Any document withheld from Staff is still a decision for counsel, made after reading it.
A chronology of the client's orders
Staff's questions turn on the order of events around the client's trades. A second pass over the relevant calls, chats and email uses Claira's chronology prompt, which turns a document into one dated sentence in the form [YYYY/MM/DD]: [Event summary], with a fallback for undated items. Because the dates sort as text, the team can export the field and lay the calls beside the trade records the dealer already keeps.
Insights then gathers those results into one output. In Insights mode the team picks the bulk task, writes a prompt asking for a timeline of the client's orders and the calls around them, sets the format to Timeline and clicks Generate Insight. The output links its entries to the source documents and exports to Word, Excel or PDF. A citation shows that a document was in the set, so a lawyer still checks the entries that matter against the recording or message they point to.
The decisions that stay with counsel
Several decisions in this matter belong to the lawyers. The dealer and the trader may come to differ on what happened, and the dealer's counsel has to watch what passes to the trader's lawyer. If the review turns up conduct beyond the request, the dealer has to decide whether to raise it with Staff and how. Where a French call matters to the response, it goes to a professional translator, because Claira's translation summaries are meant for triage and are no substitute for a certified translation in a regulatory submission.
Claira can help with the inputs to those decisions. The Agent, opened from the Modes menu, knows the case's early case assessment, can read back its custodian and document counts, and can read and summarise an Insight by reference, which helps a lawyer prepare for a meeting with the dealer's management. The judgement on cooperation, on self-reporting and on the trader's position remains with the people who sign the response.
Answering Staff and keeping the record
The production itself is a Nuix Discover task. The litigation support team exports the responsive records in their native formats with the load file the guide asks for, and the recordings go out with their call information. Claira's part is the answers in the review fields, which drive the searches that build the production set and the list of documents withheld for privilege.
Counsel drafts the narrative of the response from the chronology Insight, checking each entry against its source, and keeps a record of how the review was run in case Staff ask. Claira's relevance workflow lists what to keep: the Bulk Task History Report downloaded from Bulk Tasks, the prompt's version history as a PDF from Prompt History, the approved Case Context as PDF or Word, and the early case assessment PDF, along with the sample counts and the comments added to the bulk tasks. Together they document the review from the first scope to the final production.