Leveraging Epic's structure and activity codes within the interface (download) configuration enables separate workflows for RWL* status codes received for Commercial and Personal lines renewal downloads.  This structure is critical for splitting workflows, as you’ll need to ensure Commercial and Personal lines are properly divided using Departments within the interface configuration.  

*In some cases, the status code used will vary depending on how the carrier operates. For example, for Progressive we will be using the RWQ status code, but everything else will be the same. 

Key considerations for the split:

1. Review the Epic Structure

• Ensure Commercial and Personal are defined as separate Departments. This will allow workflows to be automatically driven by the department level. 

2. Activity Code Configuration:

• The split between Commercial and Personal workflows will primarily be driven by assigning separate activity codes by department.
• Create distinct Activity Codes for each department. For example, create a QREN for Personal Lines, and let remaining departments use the pre-existing activity code, such as EREN or DREN.  

3. Configuration for Multiple Companies:

• Changes can be applied either to all companies or selected ones. Quandri recommends either applying these changes to all companies or specifically the ones with which Quandri is compatible. Ask your implementation manager for this list of compatible companies if you do not have it. 
• Quandri recommends starting small, maybe with one or two companies. Let Quandri process these companies for at least one day, and if everything looks good, then go ahead and complete the rest.  
• Once you configure for one company, you can use the Copy feature to replicate the configuration across other companies, simplifying the process.

Areas of Caution in Workflow Splits

1. Ripple Effects on Workflow:

• Changes in activity codes and department settings can have an immediate and broad impact on how files and tasks are directed. It may take 1-2 days for issues to surface, and resolving them will be a manual process. If not handled carefully, it could disrupt business processes significantly.
• It’s critical to fully understand the existing workflows, the people involved in each step, and the overall Epic configuration before making any changes.

2. Crossed Departmental Assignments:

• There are often Commercial policies incorrectly assigned to the Personal department (and vice versa). Making these configuration changes does not guarantee that commercial policies will not end up getting processed by Quandri.  
• The setup of an account and the assignment of structure outside of agency best practice could cause a commercial renewal to be assigned to the Renewal Reviewer. 

3. Handling of Special Cases (Rewrites, Reissues, Renewals):

• Some carriers use Rewrites or Reissues to process Renewals. Misconfiguration or misunderstanding of how these codes are linked can cause these transactions to be handled incorrectly, creating potential issues in workflows.
• Ensure that special cases are accounted for when mapping status codes to activity codes, particularly if carriers deviate from standard practices.

Steps to Configuration Changes in Epic

• The first step is to create a new activity code or repurpose an existing activity code for the Personal Renewal RWLs that download. In the activity settings under Basic Settings, set the Activity Owner to “Specific Person” = “Quandri”. Default the activity to Open. 
• Navigate to Configure > Interface > Company/Broker. In the Company Interface Setup section (at the top) highlight the appropriate carrier and select the edit (pencil) icon.
• Select the Status Codes tab and move down to the “R” codes, highlighting the RWL code and select the ADD icon. The available structure window will open, and here change the department to Personal* and select locate. Check the appropriate structure combination and click Finish. After selecting Finish, the Policy/Activity Code & Status window will appear. In the Policy box, make sure that the RWL policy status code (usually REN) is selected from the Status code dropdown. In the Activity box, select your activity code (QREN for this example) from the Policy download dropdown. Select Finish, and then select Finish again on the Interface Setup page.
• Once this has all been completed, you can now use the Copy function under Actions to copy to the appropriate carriers. 

Examples of Interface Configuration

• This is how the Interface configuration for one carrier looks prior to splitting by department. With this configuration, all RWLs for this carrier will generate the specified activity (in this case, DREN).

• Changing the configuration of the “Structure” fields will create QRENs for those specific combinations, but as you can see with the top row, everything else unspecified will still create a DREN. Having a default row for unspecified structure combinations (eg. <ALL> <ALL> <ALL> <ALL>) is important to ensure that the RWLs for other departments etc. still function as they did previously.