This project is essentially adding fields from the Property LOB in Epic to the Locations schedule in Indio so that Indio can push/pull commercial property data with Epic.

As of our November 19, 2024 release, the Locations schedule has been renamed “Locations with SOV” and includes additional property coverage columns. The Statement of Values schedule has been renamed to “Legacy SOV” and by default is now in the inactive area of schedule templates.

Indio can historically import data from the Property screens in Epic but cannot push data back to Epic. The core objective of this project is passing commercial property data back and forth with Epic. This also simplifies Indio schedules to more closely reflect how many agencies use excel for their Statement Of Values (SOVs).

In Epic, property coverage details are split between several different screens, including:

Now in Indio, data from all three screens is combined in the Locations with SOV schedule in the workbook. This closely aligns with how many agencies will have an excel file with a list of locations that also includes columns for property details such as COPE info and limits.

To maintain backwards compatibility, instead of creating a new schedule property columns connected to Epic have been added to the Locations schedule, which is now renamed Locations with SOV. If a particular client does not have property information those columns will be be blank. The schedule can be renamed back to Locations either in a specific submission, or as part of the schedule template.

Note the Locations with SOV schedule can now import and export data from Property policies in Epic!

We expect most agents will prefer using the the Locations with SOV schedule to collect and update property coverage details with their insureds because it can connect to Epic. However to maintain backward-compatibility the original Statement of Values schedule is still available. To avoid user confusion about which schedule to use we have renamed it as “Legacy SOV” and marked it inactive. If your agency still wants to use it, simply have your admin go to the schedule template page, choose the Inactive tab, and then choose Set Template as Active. Note that if you re-activate this schedule you can also rename it from Legacy SOV back to Statement of Values if preferred.

Note that if an agency has multiple schedule templates and wants to reactivate the Legacy SOV they would need to reactivate it on each schedule template individually.

Because we default to changing Legacy SOV to be inactive on the all schedule templates , when importing schedules from Epic the user will often see Legacy SOV greyed out. This is expected, and we recommend using the Locations with SOV instead.

Yes! The Locations with SOV schedule can import data from Epic and export data back into Epic just like our other supported schedules. Make sure your policy in Epic is closed and remember we can only export back into in-process policies in Epic. See the below help articles for more details:

The below 17 Subjects of Insurance will import and export data between Indio and Epic. We also expect to add support for the subject BUSEE (Business Income without Extra Expense) soon after the initial release.

Although Epic supports around 300 different Subjects of Insurance (aka property limits), many of these are very niche and not listed on many commercial policies. Instead, the Locations with SOV schedule supports only about 20 different limits, which were chosen based on data and agency feedback. These include widely used limits like Building, Business Personal Property, Business Income, Tenants Improvements & Betterments, etc.

By limiting support to a small number of widely used limits this allows us to show all the information on one spreadsheet (adding 300+ columns would be very unwieldy) and also cleans up data by encouraging agents to choose the same type of limits across clients, enabling better benchmarking and other insights.

If you require other non-supported subjects of insurance you may rename custom columns in the Locations with SOV schedule. However data in those columns will not export back to Epic, and any non-supported subjects in Epic will not be imported into Indio.

Unfortunately Indio does not yet support import and export with Epic based on the Acord 140 form. Indio users will need to add a workbook in Indio and import the Locations with SOV schedule from Epic to get property information into Indio. To generate an Acord 140 from the Locations with SOV schedule in Indio, we recommend going to the Actions menu in Indio on the submission → choose Export to Epic → select to export schedules → then choose the policy you’d like to export into. Once that data is exported to Epic, you can open the policy in Epic and will see the data from Indio, and then you can generate the Acord 140 form from within Epic as normal.

Property premises are dependent on a location, therefore if a location is deleted we also delete the property premise. If you delete a location or have an error with it it will also delete the property premise and Subject of Insurance associated with it.

The default schedule template for locations currently only shows a few fields, and does not include all the many new property details. Users can show those columns by opening the columns menu, choosing Hide All and then Show Data, or an Indio admin user can edit the Locations with SOV schedule template to add those columns so they show up on future clients. Here’s a 1-min video of how to update the schedule templates to add more columns.

Note that if the agency would like, you can create a two schedule template groups, one of which the Locations with SOV schedule has all the columns pre-selected, and another which has the Locations with SOV schedule with only the basic columns. You can also rename a schedule in the schedule template.

Coming up on another project, where users will be able to import data from excel and the columns will be auto-picked based on predefined categories or criteria, streamlining the process and reducing the need for manual mapping.

To remove boolean data, such as entries in the historical register, users must press the Delete key (often labeled as Del) on their keyboard. This action will remove the selected data entry from the schedule workbook.

No, the order of the fields are not consistent between Epic and Indio.

To remove the selected radio field values within the workbook, users need to press the Delete key (often labeled as Del) on their keyboard. This will remove the chosen values and clear the field.

Currently, the scope of this project did not cover blanket limits, so currently blanket limits are not able to be exported from Epic.

Even if there are no property columns when creating a location in the Locations with SOV schedule in Indio, a property premise will still be created in the policy automatically.

No, the Statement of Values section on Epic is not connected to the property SOV on Indio. The data that is being imported/exported between Epic and Indio refers specifically to property Line of Business exposures that can be found on the Epic Premises screen and Subjects screen.

The count of changes will show "1" if only one row is changed, regardless of how many individual changes are made within that row. However, the details section will provide a breakdown of the specific changes made in that row.

Location #, Building #, and Address are always required.

When you are exporting schedules you have to choose which Line of Business to match to. Previously the Locations schedule only connected to the Commercial Application screen in Epic, but now Locations with SOV actually maps to two LOBS (Commercial Application AND Property) even though the Indio UI just shows Commercial Application.
​
​

Just like with the other schedules, Epic can be very picky about what data is acceptable in a column or not and so user-input data in particular can cause validation errors. If you encounter an error, Indio will export all the data that it can (a partial-export) and provide you details about how to correct the errors within Indio, then attempt to export to Epic again. Details on that process are in this help article: Partial Exports: How to fix an Export Error