The PDB Report tab on an agent's detail page is your single-screen, Producer-Database-style compliance summary for that agent. Use it when you need to confirm an agent's identity, see every state they have on file, drill into their licenses, appointments, and regulatory history, or send a stakeholder a clean PDF copy of any part of the report.

The PDB Report is where you review an agent's full NIPR footprint without leaving Turris and request a shareable PDF copy of any subset of it.

Who uses it. Licensing managers and compliance analysts at upstream entities (carriers, MGAs, wholesalers) who need to audit an agent's standing across every jurisdiction, prepare onboarding or appointment paperwork, or respond to a regulator inquiry without juggling raw NIPR exports.

From this tab you can:

While the report assembles, the page shows the branded Turris loader with the title "Assembling the PDB report" and the rotating messages "Pulling compliance records", "Grouping data by state", and "Compiling the report".

The tab header sits at the top, followed by the Demographics card, then a vertical stack of collapsible state bands, one per state where the agent has at least one record on file.

States with zero records are hidden. If the agent has no per-state records at all, the page shows "No per-state records on file" in place of the state stack.

If the agent has not completed an NIPR data sync, the tab renders the Compliance data not synchronized yet empty state instead of the report. The empty state shows the agent's current sync status as a pill next to the Current sync status: label (for example, Not started, Queued, Processing, Failed, NIPR error, or Manual review required), a one-line hint ("Find this agent in the list and click the Compliance Data column to start the sync."), and a Go to Agents list button. From the list you can find the agent and start the sync from the Compliance Data column.

If the request to fetch the report errors out, the tab shows an Unable to load PDB report card asking you to refresh the page or try again in a few moments. Per-state record fetches use a separate request: if a single state errors, you see Unable to load {state code} records, and the fix is to collapse and re-open that band to retry.

The Demographics card at the top of the page collects the identity fields NIPR returns for the agent. Its subtitle reads "Source-of-truth identity fields for the producer." Blank fields show a short dash.

Below the identity grid, the Other Names strip lists every alternate name reported for the agent. Each entry is a pill row containing:

The Other Names strip is hidden when the agent has no alternate names on file.

When you'd do this. You're auditing the agent in a specific state, confirming a license is still active before approving an appointment, or pulling the full per-state record set for a regulator response.

Note: Records are fetched the first time you open a state, then kept for the rest of the session, so subsequent opens are instant.

Once the band is open, the contents are grouped into up to five sections: Contacts, Addresses, Licenses, Appointments, and Regulatory Actions. Each section header shows its name next to a small count pill (for example, Licenses with a 3 pill). Sections with zero records are omitted entirely.

Every contact value NIPR returns for the state appears as its own row, grouped by channel. A single contact record can produce up to three rows (one each for Business Email, Business Phone, and Fax).

Empty channels are skipped, so a state with only a business phone on file produces a single row.

Each address NIPR returns for the state renders as its own row with a leading map-pin icon and a colored type badge.

Each license renders as its own card so you can read the renewal timeline at a glance.

Below the grid, the Lines of Authority sub-table lists every LOA on the license. When NIPR returns no LOAs, you see the inline note "No lines of authority on file."

The bottom panel of the card shows the license's CE status: the In compliance / Exempt / Not in compliance / Not supplied badge, the next CE renewal date, and how many credits are still needed when NIPR provides them. When NIPR returned no license-level CE, you see "No license-level CE on file."

Every appointment NIPR has on file for the state renders in a table.

Every regulatory action NIPR has reported for the state is listed here.

When you'd do this. You need to send the agent's compliance picture to someone who doesn't have a Turris seat (your VP of Compliance, a partner carrier, or a regulator), or you want a timestamped archival copy of the report as it stands today.

Tip: Need only a license snapshot? Uncheck every section except Licenses to keep the PDF compact when you're sharing it with a single-purpose stakeholder.

Note: While the request is being submitted, you can't dismiss the modal by clicking the backdrop or pressing Escape, and Cancel is disabled. Wait for the submission to finish, or click Cancel before submitting.

The same vocabulary is used across every per-state section. Each row below names the badge color, the label, the meaning, and the action you'd typically take.

NIPR returns a variable set of LOA status values. The PDB Report capitalizes anything outside the known set.

Why does the page say "Compliance data not synchronized yet"? The PDB Report renders only after a successful NIPR data sync. Until the sync reaches Synchronized status, the empty state shows the current sync status and a Go to Agents list button so you can return to the list and start (or troubleshoot) the sync.

Why are some states missing from the report? States with zero records on file across all five sections are hidden. The page focuses on jurisdictions where the agent has at least one contact, address, license, appointment, or regulatory action.

A state I expected to see is missing. What should I check? Confirm the sync status reads Synchronized. If the sync completed and the state is still missing, NIPR did not return any records for that jurisdiction. Verify the agent's license footprint with the state regulator if the absence is unexpected.

What's the difference between Other Names on the Demographics card and Contacts inside a state band? Other Names captures alternate identities for the agent (DBA, former, fictitious). The per-state Contacts section is about communication channels (business email, business phone, and fax) for the agent in that state.

Can I edit anything on this tab? No. The PDB Report is a read-only view of NIPR-reported data. Corrections must be filed with the relevant state regulator. Once they flow into NIPR, the next compliance data sync refreshes the report.

How current is the data? It reflects the most recent NIPR sync for this agent. Re-running the agent's compliance data sync refreshes every section together: demographics, contacts, addresses, licenses, appointments, and regulatory actions.

Where does the PDF get sent? To the email tied to your Turris account. The download modal confirms the destination email before you submit, and the success confirmation repeats it.

I requested a PDF but didn't receive it. What should I do? Check your spam or junk folder first. PDF rendering can take a moment for agents with many states or many licenses. If the email still hasn't arrived after several minutes, re-submit the request from the Email PDB report modal. If the problem persists, contact support.

If you have questions about the PDB Report tab or encounter any issues, contact our support team at support@turris.com.