Broker guideUse a watchlist CSV without confusing it with history
Choose the right scope and protect private review notes when exporting.
Updated 2026-09-13 · CarrierTrail product workflow
Select the intended list
Decide whether you need the current filtered results or the full active watchlist before exporting. Review the filter and row count so the recipient understands what is included. An empty filtered result should not be described as an empty workspace.
Explain the snapshot and audience
A CSV represents current operational values, which can differ from a historical decision. It may contain private notes and decisions. Share only with people who need that information under your organization’s handling process, and label the scope and export date clearly.
Illustrative example
A supervisor requests carriers currently needing attention. Export the filtered list and identify the filter in the handoff. Sending the full list without context could obscure the intended review queue and disclose notes unrelated to the task.
CSV handoff note
Export date: __. Full or filtered: __. Filter used: __. Row count: __. Intended use: __. Private fields included: __. Historical evidence required separately: __.
Worked review example
Illustrative scenario. A team downloads a watchlist to prepare a weekly review. The spreadsheet is edited locally and later forwarded as if it were the current application state. A CSV is useful for analysis, but its extraction time and purpose need to travel with it.
A practical review sequence
Define
Decide whether the file supports a review queue, operational comparison or a historical discussion. Choose the export that fits that purpose.
Inspect
Verify the identifiers and a few known rows after opening the file. Keep the original download separate from a locally edited working copy.
Label
Add extraction date, workspace context and the meaning of local annotations. Do not present spreadsheet edits as changes saved in the application.
What to put in the review record
Maintain original file, working-copy name, extraction time and a note explaining added columns. Use USDOT as the join key when comparing versions rather than relying on company-name spelling.
Before closing this review
A watchlist export describes the saved list at extraction. For the evidence behind a particular approval or rejection, use the corresponding decision record and revision instead.
How should two CSV downloads be compared?
Keep their extraction times, align rows by the resolved USDOT identifier and distinguish a changed field from a row that was added, paused or absent. Preserve the unedited downloads before adding analysis columns. If one file has been filtered manually, record the filter so a difference in row counts is not mistaken for a change in the application. Spreadsheet comparisons need the same attention to definitions and dates as other reports.
Can edits to a CSV update the workspace?
Do not assume that a local spreadsheet edit changes a saved application record. Treat the CSV as a separate working artifact and use the application's supported workflow for changes that need to be saved there.
Use these steps alongside your organization’s verification process. CarrierTrail presents public records and saves team decisions; it does not certify carriers or insurance coverage.
Read the data methodology → · All broker guides →