Skip to main content
All CollectionsAGENT - Account FeaturesData Collection
ACORD 125 Phase 1: Fix exposure duplication in Indio schedules and allow individual schedule rows to be exported
ACORD 125 Phase 1: Fix exposure duplication in Indio schedules and allow individual schedule rows to be exported

Indio corrects exposure duplication in schedules when importing from multiple policies & allows agents to export individual schedule rows.

Alfonso Quant avatar
Written by Alfonso Quant
Updated over a week ago

Why did we enable these features?

Previously, when importing multiple policies from Epic into Indio, if an exposure in a schedule was on multiple policies, the exposure would be duplicated per each policy association in Indio rather than being consolidated into a single row. Later when the agent chose to export schedule data back to Epic, the duplicate rows were pushed back to Epic, creating a mess of the client’s policy data and subjecting the agency to E&O exposure.

Additionally, when exporting schedule data to Epic, all schedule rows from all selected schedules are exported. This all-or-nothing approach prevented agents from splitting policies and opening them up to E&O issues.

Benefits of the Features:

This first phase of the ACORD 125 features will fix exposure duplication in Indio schedules when importing from multiple Epic policies by consolidating duplicate exposures into a single row. Also, it will allow agents to export individual schedule rows.

How Do the Features Work:

De-duplicating Exposures in Schedule Rows

After the agent has imported schedule data from more than one policy:

  • Exposures corresponding to more than one policy are now consolidated into a single row.

  • With the addition of the “Imported From” and “Policy Type” columns, agents can quickly see which policies an exposure corresponds to.

A screenshot of a computer

Description automatically generated

Imported From column

  • The policy number(s) that an exposure corresponds to are listed in the Imported From column. Policy numbers are displayed in alpha order and are separated by semicolons.

  • This column is read-only and cannot be edited by the agent.

  • The Imported From column should only display for the agent. The agent can hide the column if they so choose.

  • The Imported From column will display by default for schedules imported from Epic. The agent can then choose to hide the column if they want.

  • Available column actions for "Imported From" column

    • Sort Ascending

    • Sort Descending

    • Filter Column

    • Group by this Column

    • Hide Column

Policy Type column

  • The policy type abbreviations displayed in the Policy Type column will be listed in the same order in which its corresponding policy number is listed in the Imported From column.

  • This column is read-only and cannot be edited by the agent.

  • The Policy Type column displays for both the agent and the insured. In the insured view, policy type will display in its non-abbreviated version. If the agent hides the Policy Type column, it will also be hidden for the insured.

  • The Policy Type column should display by default for schedules imported from Epic. The agent can then choose to hide the column if they want.

  • Available column actions for "Imported From" column

    • Sort Ascending

    • Sort Descending

    • Filter Column

    • Hide Column

Allow Agents to Export Individual Schedule Rows

The agent clicks Export to Epic in the Actions menu.

The Export to Epic modal is triggered.

The agent opts to export to schedules and clicks the Next button.

The agent is navigated to the Select Policy step in the export flow.

The agent selects a policy to export form data to and clicks the Next button.

The agent is navigated to the Map Schedules step. The agent confirms the mappings and clicks the Next button.

Once the agent is navigated to the Select Data step, they will now have the option to export specific rows from a schedule. As such, a new step in the flow will need to be implemented.

The agent opts to select individual rows from schedules.

The agent is then navigated to the select schedule rows page.

Table cells are read-only in the select schedule rows view.

Rows that were newly added by the agent or insured in the current submission term should be displayed as a group at the bottom of the list. “Added this renewal period ” placeholder text should populate the cell.

The agent selects schedule rows to export and clicks the Done button.

The agent is navigated back to the Select Data screen. The agent goes through the same process for the Drivers schedule and clicks the Next button.

The system checks for changes between Indio and Epic data.

The agent is navigated to the Review Changes screen. The agent clicks the Review Changes button for vehicles.

The agent is navigated to the view schedule changes screen. The agent reviews the changes and clicks the back button.

Note: in this context, the system will compare schedule data in Indio vs schedule data in Epic. This is different from how view schedule changes works within a submission in Indio.

Since we’re comparing data in Indio vs data in Epic, the “Show Changes Since” filter should be hidden.

The agent clicks the Proceed with Export button.

The Confirm Export modal is triggered. The agent clicks the Export button.

The system exports data to Epic.

The agent is navigated to the Finish Export screen and clicks the Finish button.

The agent is navigated to the submission details screen.

Still have questions? Feel free to chat with our support team using the chat feature located in the bottom right-hand corner of the platform or email support@useindio.com.

Note: The Indio Technologies platform is most optimized on the browsers such as Google Chrome or Firefox. If you use Internet Explorer there may be limited functionality as a result.

Did this answer your question?