Enterprise Policy Data is where your group office uploads one combined policy file covering every member MGA or carrier, then lets AI route each policy to the correct member and match it to that member's agencies, agents, and products. It is the single workspace where you can run matching across the whole group, teach the AI member-specific rules, and inspect match quality member by member without logging into each member account.

Enterprise Policy Data turns one roll-up upload into matched, member-attributed policy records. You upload a single combined extract, the platform routes each row to the right child member, and AI resolves the underlying agency, agent, and product references against each member's own downstream directory.

Who uses it. Compliance and operations leads at a parent MGA or carrier group who own rolled-up reporting and member onboarding across two or more child entities. They need group-wide visibility into match quality and a way to intervene when a member's data needs context rules or a clarification answer, all from one screen.

What you can do from this page:

Left sidebar → Tools → Policy Data. The page opens with the breadcrumb Tools / Policy Data.

The page stacks several zones from top to bottom. Most appear only when there is something to show (a paused member, a running match, uploaded policies):

To inspect a single policy, click any row in the Overview, Product, or Agencies tab. The policy detail view opens scoped to the member that owns it.

When you'd do this. Your next monthly or weekly extract is ready and you want to load policies for every member in one pass, instead of asking each member to upload on their own account.

Tip: Once a template is active, later uploads reuse the same column mapping and member routing, so you only walk the full wizard the first time or when you click Edit mappings.

Note: The {n} ingested · {m} members count in the toolbar reflects every policy already loaded across the group. It updates after an upload finishes ingesting.

When you'd do this. You've uploaded policies and want AI to match them to agencies, agents, and products across the group, or you want to re-run matching after changing a member's rules.

Note: Running matching from the toolbar fans the run out across every member that has policies in the selected buckets. To run a single member only, use the Run matching button on that member's row in the Member Breakdown (see below).

Warning: While any member is still ingesting an upload, the Run Matching button is replaced by Ingesting policies… and matching is blocked until the upload finishes. Run Matching is also disabled while a run is already in progress.

When you'd do this. AI is mis-matching a particular member's agencies or products because that member uses abbreviations, naming conventions, or product names that aren't obvious from the data alone. You want to teach the AI a member-specific rule once so every future run respects it.

Note: Saving updates the stored context but does not change existing matches — it applies on the next matching run. To apply new rules now, re-run matching for that member from its Member Breakdown row.

Tip: Switching to another member while you have unsaved edits prompts Discard unsaved changes? first, so you won't lose work by clicking the wrong member.

When you'd do this. A member's matching paused because the AI couldn't confidently decide between two reasonable interpretations of a source value (for example, two agencies with near-identical names). You answer the question so that member's matching resumes.

Note: A paused member halts only that member's matching pipeline, not the others. You can also reach a paused member from its tab in the AI activity log — paused tabs carry a pulsing yellow ring.

When you'd do this. A matching run is underway and you want to watch progress, see which agencies and products are being resolved, or stop or resume a member's run.

The dark activity-log panel appears the moment you start a run in the current session and stays open after completion so you can review results. It hides only when you close it or reload the page.

While a member is processing or paused, Stop and Resume controls are available on that member's panel. Click the X in the top-right to close the log; closing only hides the panel and does not stop any running matchers.

When you'd do this. You want a fast read on group-wide match quality, how it has trended over six months, and how each member is contributing.

The Policy Overview card renders once there are policies and contains:

Directly beneath it, the Member Breakdown lists each member (sorted by total policies, 10 per page):

The bordered panel at the bottom holds four tabs. Each tab has its own filter bar, its own table, and its own bulk actions. Every tab adds a Member column (with a building icon) because rows span every member in the group. Switching tabs keeps each tab's filters and pagination independent.

The policy-identity view across all members. Click any row to open that policy's detail page.

The product-matching view. Click any row to open the policy detail.

The agency-matching view. Click any row to open the policy detail.

The transaction-level view, used for agent assignment.

When you'd do this. You spot a batch of policies for one member that all belong to the same agency or product, and you want to fix them in one pass instead of opening each policy.

Note: Bulk re-matches run as background jobs. Progress surfaces in the AI activity log under the affected member's tab.

Each tab has its own filter bar. Every tab includes a search box, a Member multi-select (defaulting to All members), and tab-specific filters.

The Member filter is the key control for everything member-scoped: set it to a single member before running bulk actions, or use it to silence noise from every other member when auditing one member's data quality.

Member matching status in the activity-log tab bar:

Policy lifecycle status (the Status column / filter on the Overview and Policy Transactions tabs):

Agency match status (the Status column on the Agencies tab):

Product match (Auto Matched / User Confirmed are green, Needs Clarification is yellow, Unmatched is red) and agent match (Auto Matched / User Confirmed green, Unmatched red) follow the same color logic.

Why does a policy number have a building icon next to it? That row was loaded through the enterprise upload on this page. A member policy that also exists in the enterprise upload additionally shows an Also in Enterprise badge.

Why can't I bulk-act on policies from more than one member at once? The agencies, agents, and products being matched against are specific to each member's directory, so bulk actions are scoped to a single member. Narrow your selection or set the Member filter first.

A member's tab says "No policies to match." Is that an error? No. That member's upload had no rows the matching pipeline needed to process (every row was already resolved or had no agency reference). This is expected.

I saved a member's Matching Context but nothing changed. Why? Saving updates the stored context but does not re-match existing policies — it applies on the next run. Use the Run matching button on that member's Member Breakdown row to apply it now.

What's the difference between the upload instructions and Matching Context? Upload instructions are scoped to that single upload's template. Matching Context on this page is persistent and per-member — updates here apply to every future matching run for that member.

What happens to Manual Review policies after a run finishes? They stay in Manual Review until a person opens the policy and confirms the suggested match or picks a different one. They are never auto-decided.

If you have questions about Enterprise Policy Data or encounter any issues, contact our support team at support@turris.com.