Large policy workflow using policy data spreadsheet import/export

Using policy data spreadsheet import/export, you can directly import policy details directly from a standard spreadsheet. To ensure the format and structure of the captured data, you can export both a template and a full spreadsheet from PolicyCenter. The template contains column headings only and is used as a basis for capturing data for new coverages. The full spreadsheet contains both column headings and existing policy data for a specific policy transaction. You can use the full spreadsheet for reviewing a policy and for capturing additions, deletions, and changes to the details of existing coverages. You can use this spreadsheet to manipulate a large number of changes in a bulk operation. For example, you can add 10% to a certain coverage term in the spreadsheet, and then import the change back into the policy transaction. Furthermore, PolicyCenter imposes no arbitrary restrictions on the number of coverables and coverages it can track. Therefore, there is no need to keep a paper trail as a separate system of record for any part of a policy.

In the base configuration, policy data spreadsheet import/export exports a representative set of fields for the locations and buildings in the Commercial Property line of business. You can extend Policy data spreadsheet import/export to include additional fields as needed, including fields that have been added in specific PolicyCenter implementations. You can also extend Policy data spreadsheet import/export to provide similar capabilities in other lines of business.

Within the set of fields that have been enabled for export, an administrator with appropriate permissions can define formats that remove selected fields (columns) from individual export operations. You can define the format so that it exports spreadsheets that contain exactly the data you want to review or capture in a particular policy transaction.

Each exported spreadsheet is identified with a single PolicyCenter policy transaction. As a general rule, the spreadsheet is only imported into the same policy transaction or a policy transaction (job) whose basedOn property leads back to the exported policy transaction. PolicyCenter displays an error if you attempt to import a spreadsheet into an incompatible policy transaction. To help you match a spreadsheet to a policy transaction, the file name that PolicyCenter suggests contains the policy number, policy transaction type, transaction number, and date. Although you may change the file name when saving an exported spreadsheet, Guidewire recommends that you retain the transaction number for ease of matching spreadsheets to policy transactions.

After completing an import operation, PolicyCenter can save a log file. The log file contains information such as the number of coverables read, added, changed, or removed. You can consult this log file if there are errors on import. The log file identifies the spreadsheet row and column where each error occurred.