Actions Required is the landing tab of License Management. It collects every active license across your agencies and agents that is inside its renewal window (approaching its renewal date or already lapsed) into one sortable worklist, so you can request renewals (or fix the data that is blocking them) before a lapse interrupts a producer's ability to write business.

Actions Required is your renewal queue. It draws from the most recent NIPR data on every agency and agent associated with your organization, keeps only the licenses that need attention, and tells you for each one whether it is ready to renew or blocked by missing information.

A license shows up here when it is an active license whose renewal date falls inside the renewal window for its state and license class (Turris uses the per-state NIPR rules, with a fallback that surfaces licenses up to roughly six months ahead of expiry and recently lapsed ones). Licenses on a paused NIPR subscription are excluded.

Who uses it. Licensing managers and compliance leads at the agency. The tab is meant as a daily or weekly queue for the person responsible for keeping producer credentials current and for pushing renewals through Turris.

From this page you can:

Note: The view is action-oriented. A license that already has a pending renewal request stays visible but cannot be selected again, so you never submit the same renewal twice.

In the left sidebar, click License Management. The default tab is Actions Required, shown first in the secondary navigation row. The other tabs in that row are License Requests, Agencies, and Agents. All four share the same page header (with the New button on the right) and the same breadcrumb.

License Management is a premium feature. If your organization does not have it enabled, the table is replaced by a feature-availability prompt and the New button is hidden.

Note: The Agencies and Agents tab labels follow your organization's terminology. Some organizations see customized names in place of "Agencies" and "Agents."

Renewals are the primary workflow on this page. You can renew one license at a time from the row-level Actions menu, or many at once from the header Actions dropdown.

When you'd do this. A row is Expiring or Expired, its Request Eligibility is Eligible, and you want Turris to submit the renewal through NIPR on your behalf.

On success Turris shows the alert License renewal request sent successfully and takes you to the License Requests tab so you can track the new request. The row's Request Status updates to reflect the pending renewal and its selection checkbox becomes disabled, so the same license cannot be submitted again while a renewal is pending.

Note: If the license already has a pending renewal, clicking Renew shows the inline alert Renewal Already Requested instead of opening the modal.

When you'd do this. You have a batch of expiring licenses (often a quarterly renewal cohort) and you want them submitted in one request group, so they land on one invoice and resolve on the same timeline.

Note: If some of the licenses you selected already had a pending renewal request, Turris automatically skips them and shows a Some Licenses Skipped notification with the exact skipped count, so you know how many were left out of the request.

A license is marked Eligible when Turris has everything NIPR needs to submit the renewal. It is marked Ineligible when something is missing. The blocking reasons you will see on this page are data-completeness issues:

For an agent's license:

For an agency's license:

Hover the question-mark icon next to the Ineligible badge in the Request Eligibility column to read the exact blocking reason for that license.

When a license is Ineligible, the row-level Actions menu surfaces shortcuts to fix the underlying problem. Each shortcut appears only when your role has the matching permission.

After you complete one of these actions, the license is re-evaluated. If the blocker was the only problem, the license becomes selectable for renewal on the next page load.

Tip: Fix the blockers first, then bulk-renew. Otherwise the licenses you most needed to renew are silently skipped because they were still ineligible at the moment you submitted.

When you'd do this. A row's Request Eligibility is Ineligible and the popover names a missing agent date of birth or SSN.

Note: Both fields are individually optional, but at least one must be filled in (and changed) for the save to go through. A SSN on file indicator tells you whether a Social Security Number is already stored. Whatever you provide is encrypted at rest.

When you'd do this. A row's eligibility popover says the agency has no DRLP designated for the issuing state, so NIPR cannot accept the renewal.

If no agents are associated with the agency, the slideover shows the empty state No Agents Found with a link to the Agents page so you can add agents first.

Tip: Assign DRLPs before bulk renewal. Once the right DRLPs are in place, the affected agency licenses move from Ineligible to Eligible automatically.

When you'd do this. DRLPs are assigned, but at least one is still missing personal data (date of birth or SSN) that NIPR requires before a renewal can be submitted.

If there are no active DRLPs, the slideover shows the empty state No active DRLPs found with the message Please assign DRLPs for this agency first. In that case, close the slideover and use Assign DRLP(s) instead.

The New button in the page header opens a separate workflow that is not a renewal. Use it when you need a license the producer does not yet have.

When you'd do this. You are expanding an agency or agent into a new state, or adding a new line of authority, and you want Turris to handle the application end to end.

Note: The New button is gated by the License Management create permission. If you do not see it, ask your administrator to adjust your role.

Three filter controls sit above the table. They are URL-backed, so a filtered view is shareable and bookmarkable.

The header search box matches against entity name, entity category, license class, license number, lines of authority, license status, and request status. Partial matches work for text columns (typing Trav finds Travelers); license numbers require a contiguous substring match.

Filters compose. Selecting Expiring plus Agency plus California narrows the list to expiring agency licenses in California. Changing the Entity Category filter also clears any entity-name filter that was applied.

If filters produce no rows, the empty-state box reads No licenses match the selected filters with the message Try adjusting your filter criteria to see more results. If your organization has no licenses needing action at all, the page shows No action required with the message You do not have any expiring or expired licenses.

Note: Export CSV always exports the complete Actions Required list, regardless of the filters or search currently applied. The downloaded file is named actions-required-YYYY-MM-DD.csv.

Any value other than Not Requested in the Request Status column is clickable. Clicking it opens the License Requests tab pre-filtered to that status and the same entity, so you can review the existing request without rebuilding your filters by hand.

Why don't I see a license I know is expiring?

Three things to check, in order. (1) Compliance data sync: Actions Required is built from synchronized NIPR data, so if the agency or agent has not been synced recently, a newly expiring license may not have flowed in yet. Run a compliance data sync on the producer and reload. (2) Filters: if Expired is selected but the license is still in its expiring window, the row is hidden, so clear the filters. (3) Renewal window: a license only appears once it is inside the renewal window for its state and class, so a license far from its renewal date will not be here yet. Paused NIPR subscriptions are also excluded.

What's the difference between Actions Required and License Requests?

Actions Required is the list of licenses that need a renewal request. License Requests is the list of renewals and new-license applications that have already been submitted to Turris, with their progress through pending, awaiting-payment, submitted, and completed states. Submitting a renewal here moves the license from this worklist into License Requests.

Why can't I select a license for bulk renewal?

The checkbox is disabled for two reasons. (1) Ineligible: something is blocking renewal. Hover the question-mark icon in Request Eligibility for the exact reason, then use the row-level Update Agent, Assign DRLP(s), or Update DRLP(s) actions to clear it. (2) Already requested: a renewal for this license already exists in License Requests. Clicking the dimmed row shows an inline License Cannot Be Selected alert that explains which case applies.

What does Add to existing mean when I bulk-renew?

When you have an open renewal request group that has not been paid, Turris asks whether to attach the newly selected licenses to that group or to start a separate one. Adding to the existing group keeps everything on one invoice and one timeline; creating a new request opens a separate group with its own payment. The modal heading is Unpaid Renewal Request Exists, and it tells you when the existing group was created and how many licenses it already contains.

Can I renew a license from another tab?

Yes. The row-level Renew action also appears in License Management > Agencies and License Management > Agents for any license that needs action. Actions Required simply collects every such row across all your agencies and agents so you do not have to drill into each producer one at a time.

How does Export CSV behave with filters applied?

It ignores them. Export CSV always exports the complete Actions Required list (every license your organization has that needs action), regardless of the filters or search currently applied. Use the CSV for offline reporting, board updates, or to feed your renewal queue into another system.

Who can renew licenses?

Renewal actions are gated by your role's License Management permissions. If you do not see the Actions dropdown in the header or the Renew option in a row's Actions menu, your role lacks the required permission. Ask your administrator to adjust your role.

If you have questions about Actions Required or encounter any issues, contact our support team at support@turris.com.