Guidewire PolicyCenter™

Application Guide
Release: 10.2.3
© 2023 Guidewire Software, Inc.
For information about Guidewire trademarks, visit https://www.guidewire.com/legal-notices.
Guidewire Proprietary & Confidential — DO NOT DISTRIBUTE

Product Name: Guidewire PolicyCenter

Product Release: 10.2.3
Document Name: Application Guide
Document Revision: 29-November-2023
 Guidewire PolicyCenter 10.2.3 Application Guide

Contents
Support.......................................................................................................................................................... 27

Part 1
Introduction to PolicyCenter..............................................................................................................29

1 Product model................................................................................................................................................. 31
Lines of business in the base application......................................................................................................... 31
2 The policy lifecycle...........................................................................................................................................33
3 Integration with other Guidewire applications.............................................................................................. 35
4 PolicyCenter users........................................................................................................................................... 37

Part 2
PolicyCenter user interface................................................................................................................ 39

5 Navigating PolicyCenter.................................................................................................................................. 41
Logging into PolicyCenter................................................................................................................................. 41
PolicyCenter login requirements.............................................................................................................. 41
Log in to PolicyCenter............................................................................................................................... 41
Setting preferences.......................................................................................................................................... 42
Changing interface settings.............................................................................................................................. 42
Change the visual theme.................................................................................................................................. 44
Data entry support for input fields...................................................................................................................45
Using the currency macro in currency fields............................................................................................ 45
As-you-type formatting support for input fields...................................................................................... 46
Highlight changed values..........................................................................................................................46
Selecting language and regional formats in PolicyCenter................................................................................ 47
My Summary.................................................................................................................................................... 48
PolicyCenter tabs..............................................................................................................................................48
Desktop tab.............................................................................................................................................. 48
Account tab.............................................................................................................................................. 52
Policy tab.................................................................................................................................................. 52
Contact tab............................................................................................................................................... 53
Reinsurance tab........................................................................................................................................ 53
Search tab.................................................................................................................................................53
Team tab................................................................................................................................................... 54
Administration tab................................................................................................................................... 54
6 Changing the screen layout............................................................................................................................. 55
Adjusting list views........................................................................................................................................... 55
Change list view column order................................................................................................................. 55
Change list view column widths............................................................................................................... 55
Sort list views........................................................................................................................................... 56
Hide and show columns in a list view.......................................................................................................56
Arrange list view rows into groups........................................................................................................... 56
Reset list view columns............................................................................................................................ 57

Contents 3
Guidewire PolicyCenter 10.2.3 Application Guide

Disable list view customization................................................................................................................ 57

Change the sidebar width................................................................................................................................ 58
7 QuickJump....................................................................................................................................................... 59
Using QuickJump.............................................................................................................................................. 59
Chaining QuickJump destinations together............................................................................................. 60
QuickJump behavior in wizards................................................................................................................ 60
Configuring QuickJump.................................................................................................................................... 60
QuickJump reference....................................................................................................................................... 60
8 Basic search..................................................................................................................................................... 65
Basic search overview...................................................................................................................................... 65
Indexing free-text search data..................................................................................................................65
Query and filter basic search fields.......................................................................................................... 66
Exact or inexact basic search and ranking................................................................................................ 66
Basic search results for fields with multiple matches...............................................................................66
Basic policy search overview............................................................................................................................ 67
Basic search user interface............................................................................................................................... 67
Policy basic search screen........................................................................................................................ 67
Working with basic search............................................................................................................................... 70
Use basic policy search.............................................................................................................................70
Basic search index updates automatically................................................................................................ 71
9 Advanced search..............................................................................................................................................73
Advanced search overview...............................................................................................................................73
Minimum search requirements for advanced search...............................................................................73
Advanced search for policies.................................................................................................................... 74
Search contacts........................................................................................................................................ 75
Working with the Advanced Search tab........................................................................................................... 75
Assign a user to one or more policies or open policy transactions.......................................................... 75
Search quotes user interface.................................................................................................................... 76
10 Saving your work............................................................................................................................................. 77
Unsaved work list............................................................................................................................................. 77
Saving your work in PolicyCenter wizards........................................................................................................ 77
11 Accessibility in Guidewire InsuranceSuite...................................................................................................... 79
Screen reader support......................................................................................................................................79
User interface settings for accessibility............................................................................................................ 80
Keyboard navigation and interaction............................................................................................................... 81

Part 3
PolicyCenter policy transactions..................................................................................................... 83

12 Common features of policy transactions........................................................................................................ 85

Preempting policy transactions........................................................................................................................ 86
Out-of-sequence changes and policy transactions...........................................................................................86
Configuring policy transactions........................................................................................................................ 87
13 Submission policy transaction.........................................................................................................................89
Submission general steps................................................................................................................................. 89
Understanding name clearance and risk reservation....................................................................................... 91
The difference between quick quote and full application................................................................................91
Answering pre-qualification questions in a submission................................................................................... 92
Selecting an underwriting company in a submission....................................................................................... 92
Reasons for underwriter review in submissions.............................................................................................. 93
Closing a submission........................................................................................................................................ 93

4 Contents
 Guidewire PolicyCenter 10.2.3 Application Guide

Differences between binding and issuing a policy in a submission.................................................................. 93

Expiring submissions........................................................................................................................................ 94
Copying submission information...................................................................................................................... 94
Submission manager........................................................................................................................................ 94
Creating a submission...................................................................................................................................... 95
Create a submission................................................................................................................................. 95
Copy a submission.................................................................................................................................... 96
14 Issuance policy transaction............................................................................................................................. 97
Issuance general steps..................................................................................................................................... 98
Working with issuance..................................................................................................................................... 99
Issue a policy............................................................................................................................................ 99
15 Renewal policy transaction........................................................................................................................... 101
Renewal flows................................................................................................................................................ 102
Renewal general steps....................................................................................................................................102
Pre-renewal directions................................................................................................................................... 104
Referral reasons on renewals......................................................................................................................... 105
Underwriting issues in renewals.................................................................................................................... 105
Add an underwriting issue through the user interface.......................................................................... 106
Policy changes and renewals.......................................................................................................................... 106
Starting renewals........................................................................................................................................... 106
Starting renewals manually in the user interface...................................................................................106
Starting renewals using the Policy Renewal web service....................................................................... 106
Starting renewals using a batch process................................................................................................ 106
Working with pre-renewal directions.............................................................................................................107
Create a pre-renewal direction.............................................................................................................. 107
View, edit, or delete an existing pre-renewal direction..........................................................................107
Delete a pre-renewal direction.............................................................................................................. 108
Working with renewals.................................................................................................................................. 108
Create a manual renewal....................................................................................................................... 108
Create a renewal from a batch process.................................................................................................. 109
View your renewals................................................................................................................................ 110
Create multiple versions of a renewal.................................................................................................... 110
16 Cancellation policy transaction..................................................................................................................... 111
Scheduling a cancellation versus cancel now................................................................................................. 112
Default cancellation effective date.................................................................................................................112
Changing a cancellation................................................................................................................................. 113
Rescinded versus withdrawn cancellations.................................................................................................... 114
Cancellation with pending renewals.............................................................................................................. 114
Cancellation general steps............................................................................................................................. 115
Working with cancellations............................................................................................................................ 116
Cancel a policy........................................................................................................................................ 116
Rescind a cancellation............................................................................................................................ 117
Change the cancellation effective date in a quoted cancellation........................................................... 117
Change the cancellation effective date in a scheduled cancellation...................................................... 117
17 Policy change transaction.............................................................................................................................. 119
Using the Policy Review screen to verify changes.......................................................................................... 120
Editing the effective date of a policy change..................................................................................................120
New effective date in policy change must be within the same slice and policy term............................ 120
Underwriting issues and editing the effective date in policy change..................................................... 122
Handling out-of-sequence policy transactions in a policy change................................................................. 123
Using preemption in a policy change............................................................................................................. 123

Contents 5
Guidewire PolicyCenter 10.2.3 Application Guide

Policy change general steps........................................................................................................................... 124

Working with policy changes..........................................................................................................................126
Create policy change.............................................................................................................................. 126
Edit the policy change effective date..................................................................................................... 127
Change the policy expiration date in a policy change............................................................................ 127
18 Reinstatement policy transactions................................................................................................................129
Reinstatement general steps.......................................................................................................................... 129
Working with reinstatements......................................................................................................................... 131
Reinstate a policy................................................................................................................................... 131
19 Rewrite policy transactions........................................................................................................................... 133
Rewrite general steps..................................................................................................................................... 134
Working with rewrites.................................................................................................................................... 135
Rewrite a policy...................................................................................................................................... 135
Approve, request changes, or decline a rewrite.....................................................................................135
View rewritten policies...........................................................................................................................136
20 Rewrite new account policy transaction.......................................................................................................137
Restrictions to rewrite new account started on source policy....................................................................... 138
Rewrite to new account on or after expiration date.............................................................................. 138
Rewrite to new account on cancellation date........................................................................................ 139
Rewrite to new account on future date within the policy term............................................................. 140
Rewrite to new account on a future date beyond the policy term........................................................ 141
Restrictions to rewrite new account started on target policy........................................................................ 142
Rewrite new account and the Policy Renewal Start batch process................................................................ 142
Working with rewrite new account................................................................................................................ 142
Rewrite policy to new account............................................................................................................... 142
21 Premium audit policy transaction................................................................................................................. 143
Final audit overview....................................................................................................................................... 143
Where does the insurer send premium audit information?.................................................................. 144
Reversing and revising final audits......................................................................................................... 145
Adding a final audit................................................................................................................................ 145
Final audit general steps................................................................................................................................ 146
Premium report overview.............................................................................................................................. 146
Premium report audit schedules............................................................................................................ 147
Premium report trend analysis...............................................................................................................148
Adding a premium report.......................................................................................................................148
Premium reports general steps...................................................................................................................... 148
Premium audit roles....................................................................................................................................... 150
Premium audit and other policy transactions................................................................................................ 150
Working with final audits............................................................................................................................... 152
View final audit schedule....................................................................................................................... 152
View audit activities............................................................................................................................... 153
Edit, start, or waive a final audit.............................................................................................................153
Add a new audit..................................................................................................................................... 154
Enter audit data and complete final audit..............................................................................................154
Revise a final audit................................................................................................................................. 155
Working with premium reports......................................................................................................................155
View a premium report.......................................................................................................................... 155
View premium report activities.............................................................................................................. 156
Select premium reports..........................................................................................................................156
Start a premium report.......................................................................................................................... 156
Create activities for overdue premium reports...................................................................................... 156

6 Contents
 Guidewire PolicyCenter 10.2.3 Application Guide

Enter premium report data.................................................................................................................... 157

Edit or waive a premium report............................................................................................................. 157
Add a new premium report.................................................................................................................... 157
22 Side-by-side quoting...................................................................................................................................... 159
Side-by-side quoting versus multi-version quoting........................................................................................ 159
Side-by-side availability overview.................................................................................................................. 159
Base data overview in side-by-side quoting................................................................................................... 160
Side-by-side data overview............................................................................................................................ 160
Side-by-side quoting process flow..................................................................................................................161
Side-by-side quoting in the user interface..................................................................................................... 162
Tools menu items for side-by-side quoting............................................................................................ 162
Side-by-Side Quoting screen.................................................................................................................. 162
Policy Versions screen............................................................................................................................ 164
Working with side-by-side quoting................................................................................................................ 165
Select side-by-side quoting in a submission........................................................................................... 165
Edit a version in a policy transaction with side-by-side quoting............................................................ 165
Bind and issue a side-by-side submission...............................................................................................166
23 Multi-version quoting.................................................................................................................................... 167
Multi-version quoting versus side-by-side quoting........................................................................................ 167
Working with multi-version quoting.............................................................................................................. 167
Create and compare multi-version quotes............................................................................................. 167
Setting the maximum number of multi-version quotes................................................................................. 168

Part 4
Policies......................................................................................................................................................169

24 Policy basics................................................................................................................................................... 171

Copying data between policies...................................................................................................................... 171
Configuring copy data for a line of business...........................................................................................172
Split and spin-off policies............................................................................................................................... 172
Configuring split and spin-off policies.................................................................................................... 173
Earned premium.............................................................................................................................................174
Loss ratio........................................................................................................................................................ 174
Policy object model overview........................................................................................................................ 174
Policy term and policy period entities.................................................................................................... 176
Policy file user interface................................................................................................................................. 177
Info bar in policy file............................................................................................................................... 177
Actions menu in policy file..................................................................................................................... 178
Policy contract in policy file.................................................................................................................... 178
Tools menu in policy file......................................................................................................................... 178
Policy Summary in policy file.................................................................................................................. 179
Working with policies..................................................................................................................................... 180
Copy data from one policy to another................................................................................................... 180
Split an existing policy into two policies................................................................................................. 181
25 Policy forms................................................................................................................................................... 183
26 Policy data spreadsheet import/export........................................................................................................ 185
Large policy workflow using policy data spreadsheet import/export............................................................ 185
Policy data spreadsheet import/export in commercial property................................................................... 186
Using spreadsheets generated by policy data spreadsheet import/export................................................... 187
Export buildings and locations to a spreadsheet....................................................................................187
Using exported spreadsheets................................................................................................................. 188

Contents 7
Guidewire PolicyCenter 10.2.3 Application Guide

Import spreadsheet into policy transaction........................................................................................... 191

27 Policy revisioning........................................................................................................................................... 193
Basic revisioning structure of a policy............................................................................................................ 195
The policy period and effective date fields.................................................................................................... 197
Structure of revisioning across effective time................................................................................................ 200
Unbound policy revisions....................................................................................................................... 202
Slice mode and window mode overview................................................................................................202
Slice mode APIs...................................................................................................................................... 203
Window mode API overview.................................................................................................................. 204
Safely accessing foreign keys with slice mode........................................................................................206
Version list API........................................................................................................................................ 207
Working with window mode (unsliced) objects..................................................................................... 211
Comparing window mode edits to slice edits........................................................................................ 212
Out-of-sequence jobs..................................................................................................................................... 213
Out-of-sequence job user interface....................................................................................................... 213
Back-dated versus out-of-sequence job................................................................................................. 214
Validation issues and out-of-sequence jobs........................................................................................... 215
Preempted jobs.............................................................................................................................................. 215
Create a preempted job......................................................................................................................... 217
Applying changes to future renewals............................................................................................................. 218
Revisioning rewrite jobs................................................................................................................................. 218
Summary of revisioning terminology............................................................................................................. 219
Revisioning properties reference................................................................................................................... 220
Revisioning properties on a policy......................................................................................................... 220
Revisioning properties on a policy period.............................................................................................. 221
Revisioning properties on PolicyPeriod subobjects................................................................................222
Details of merging and applying changes....................................................................................................... 223
Applying changes details........................................................................................................................ 224
Merging changes details.........................................................................................................................225
Policy differences between revisions............................................................................................................. 227
28 Multicurrency features.................................................................................................................................. 229
Multicurrency overview................................................................................................................................. 229
Single currency and multicurrency in PolicyCenter................................................................................ 229
Multicurrency terminology.................................................................................................................... 229
Types of multicurrency policies.............................................................................................................. 230
Exchange rate for multicurrency policies............................................................................................... 230
Multicurrency and rating........................................................................................................................231
Multicurrency and reinsurance.............................................................................................................. 233
Multicurrency and basis units................................................................................................................ 234
Multicurrency object model........................................................................................................................... 235
Multicurrency properties....................................................................................................................... 235
Multicurrency in a policy line................................................................................................................. 235
Multicurrency user interface.......................................................................................................................... 236
Multicurrency fields on policy transactions screens.............................................................................. 237
Multicurrency fields on the Contact screen........................................................................................... 238
Multicurrency fields on the Account screen...........................................................................................238
Multicurrency fields on the Organization screen................................................................................... 238
Multicurrency fields on the Producer Code screen................................................................................ 239
Multicurrency field in reinsurance......................................................................................................... 239
Multicurrency fields for underwriting authority.................................................................................... 239
29 Contingencies................................................................................................................................................ 241

8 Contents
 Guidewire PolicyCenter 10.2.3 Application Guide

Working with contingencies........................................................................................................................... 241

Viewing contingencies............................................................................................................................241
Creating contingencies........................................................................................................................... 242
Adding notes, documents, and activities to contingencies.................................................................... 243
Changing contingency status.................................................................................................................. 243

Part 5
Lines of business................................................................................................................................. 245

30 Businessowners............................................................................................................................................. 247
Businessowners screens................................................................................................................................. 247
Offerings screen for businessowners..................................................................................................... 247
Qualification screen for businessowners................................................................................................247
Policy Info screen for businessowners................................................................................................... 247
Businessowners line screen....................................................................................................................249
Locations screen for businessowners..................................................................................................... 250
Buildings screen for businessowners..................................................................................................... 251
Modifiers screen for businessowners.....................................................................................................252
Risk Analysis screen for businessowners................................................................................................ 252
Policy Review screen for businessowners.............................................................................................. 252
Quote screen for businessowners.......................................................................................................... 253
Forms screen for businessowners.......................................................................................................... 253
Payment screen for businessowners...................................................................................................... 253
Businessowners object model........................................................................................................................253
31 Commercial auto........................................................................................................................................... 257
Commercial Auto screens.............................................................................................................................. 257
Offerings screen for commercial auto.................................................................................................... 257
Qualification screen for commercial auto.............................................................................................. 258
Policy Info screen for commercial auto.................................................................................................. 258
Commercial auto line screen for commercial auto................................................................................ 260
Locations screen for commercial auto................................................................................................... 261
Vehicles screen for commercial auto..................................................................................................... 261
State Info screen for commercial auto................................................................................................... 263
Drivers screen for commercial auto....................................................................................................... 264
Covered Vehicles screen for commercial auto....................................................................................... 264
Modifiers screen for commercial auto................................................................................................... 264
Risk Analysis screen for commercial auto.............................................................................................. 265
Policy Review screen for commercial auto............................................................................................. 265
Quote screen for commercial auto.........................................................................................................265
Forms screen for commercial auto.........................................................................................................266
Payment screen for commercial auto.....................................................................................................266
Commercial auto object model...................................................................................................................... 266
32 Commercial package policy........................................................................................................................... 269
Commercial Package screens......................................................................................................................... 269
Offerings screen for commercial package.............................................................................................. 269
Qualification screen for commercial package........................................................................................ 270
Policy Info screen for commercial package............................................................................................ 270
Line Selection screen for commercial package.......................................................................................272
Locations screen for commercial package..............................................................................................272
Line of business screens for commercial package.................................................................................. 272
Modifiers screen for commercial package............................................................................................. 273

Contents 9
Guidewire PolicyCenter 10.2.3 Application Guide

Risk Analysis screen for commercial package.........................................................................................273

Quote screen for commercial package................................................................................................... 273
Forms screen for commercial package................................................................................................... 274
Payment screen for commercial package............................................................................................... 274
Commercial package object model................................................................................................................ 275
Commercial package product model..............................................................................................................275
33 Commercial property.....................................................................................................................................277
Working with Commercial Property............................................................................................................... 277
Add locations and buildings in commercial property............................................................................. 277
Copy coverages to other buildings in commercial property...................................................................278
Add blanket coverages in commercial property..................................................................................... 278
Configure blankets for commercial property in the product model.......................................................279
Commercial Property screens........................................................................................................................ 279
Policy Info screen for commercial property........................................................................................... 279
Buildings and Locations screen for commercial property...................................................................... 281
Blankets screen for commercial property.............................................................................................. 282
Modifiers screen for commercial property.............................................................................................282
Risk Analysis screen for commercial property........................................................................................283
Policy Review screen for commercial property...................................................................................... 283
Quote screen for commercial property.................................................................................................. 284
Forms screen for commercial property.................................................................................................. 284
Payment screen for commercial property.............................................................................................. 285
Commercial property object model............................................................................................................... 285
34 General liability............................................................................................................................................. 291
General Liability policy basis examples.......................................................................................................... 291
General Liability screens................................................................................................................................ 293
Qualification screen for general liability.................................................................................................293
Policy Info screen for general liability.....................................................................................................293
Locations screen for general liability...................................................................................................... 295
Coverages screen for general liability.....................................................................................................295
Exposures screen for general liability..................................................................................................... 296
Modifiers screen for general liability......................................................................................................297
Risk Analysis screen for general liability................................................................................................. 298
Policy Review screen for general liability............................................................................................... 298
Quote screen for general liability........................................................................................................... 298
Forms screen for general liability........................................................................................................... 299
Payment screen for General Liability......................................................................................................299
General Liability object model....................................................................................................................... 299
35 Homeowners................................................................................................................................................. 301
Homeowners rating........................................................................................................................................303
Homeowners wizard flow...............................................................................................................................304
Homeowners field validation......................................................................................................................... 305
Homeowners screens..................................................................................................................................... 306
Qualification screen for homeowners.................................................................................................... 306
Policy Info screen for homeowners........................................................................................................ 307
Dwelling screen for homeowners...........................................................................................................309
Dwelling Construction screen for homeowners..................................................................................... 309
Coverages screen for homeowners........................................................................................................ 310
Modifiers screen for homeowners......................................................................................................... 310
Risk Analysis screen for homeowners.................................................................................................... 310
Policy Review screen for homeowners...................................................................................................311

10 Contents
 Guidewire PolicyCenter 10.2.3 Application Guide

Quote screen for homeowners.............................................................................................................. 311

Forms screen for homeowners...............................................................................................................312
Payment screen for homeowners.......................................................................................................... 313
Homeowners data model............................................................................................................................... 313
Homeowners cost data model............................................................................................................... 316
Additional homeowners coverables data model....................................................................................319
Homeowners typelists............................................................................................................................321
Homeowners product model......................................................................................................................... 322
36 Inland marine................................................................................................................................................ 325
Inland marine screens.................................................................................................................................... 326
Policy Info screen for inland marine....................................................................................................... 326
Coverage part selection screen for inland marine..................................................................................328
Buildings and Locations screen for inland marine..................................................................................328
Accounts Receivable screen for inland marine.......................................................................................328
Contractors Equipment screen for inland marine.................................................................................. 329
Signs screen for inland marine............................................................................................................... 329
Risk Analysis screen for inland marine................................................................................................... 329
Policy Review screen for inland marine..................................................................................................330
Quote screen for inland marine............................................................................................................. 330
Forms screen for inland marine............................................................................................................. 331
Payment screen for inland marine......................................................................................................... 331
Inland marine object model........................................................................................................................... 331
Inland marine product model........................................................................................................................ 332
37 Personal auto................................................................................................................................................. 335
Motor vehicle records in personal auto......................................................................................................... 335
Working with personal auto........................................................................................................................... 337
Copy coverages to other vehicles........................................................................................................... 337
Personal auto screens.................................................................................................................................... 337
Policy Info screen for personal auto....................................................................................................... 337
Drivers screen for personal auto............................................................................................................ 339
Vehicles screen for personal auto.......................................................................................................... 340
PA Coverages screen for personal auto.................................................................................................. 341
Risk Analysis screen for personal auto................................................................................................... 341
Policy Review screen for personal auto..................................................................................................342
Quote screen for personal auto............................................................................................................. 342
Forms screen for personal auto..............................................................................................................343
Payment screen for personal auto......................................................................................................... 343
Personal auto object model........................................................................................................................... 343
Motor vehicle record object model in personal auto.............................................................................346
Configuring personal auto motor vehicle records.......................................................................................... 349
System table for retrieving personal auto motor vehicle records.......................................................... 349
Workflow for personal auto motor vehicle records............................................................................... 349
Plugin for personal auto motor vehicle records..................................................................................... 350
Underwriting rules for motor vehicle records........................................................................................ 350
38 Workers’ compensation................................................................................................................................ 351
Jurisdictions in workers’ compensation......................................................................................................... 351
Split rating periods in workers’ compensation....................................................................................... 353
Workers’ compensation options.................................................................................................................... 354
Inclusions and exclusions in workers’ compensation............................................................................. 354
Policy plan types in workers’ compensation.......................................................................................... 354
Specialty operations in workers’ compensation.....................................................................................355

Contents 11
Guidewire PolicyCenter 10.2.3 Application Guide

Workers' compensation screens.................................................................................................................... 355

Qualification screen for workers’ compensation....................................................................................355
Policy Info screen for workers’ compensation........................................................................................356
Locations screen for workers’ compensation......................................................................................... 358
WC Coverages screen for workers’ compensation................................................................................. 358
Supplemental screen for workers’ compensation.................................................................................. 361
WC Options screen for workers’ compensation..................................................................................... 361
Risk Analysis screen for workers’ compensation.................................................................................... 362
Policy Review screen for workers’ compensation.................................................................................. 363
Quote screen for workers’ compensation.............................................................................................. 363
Forms screen for workers’ compensation.............................................................................................. 363
Payment screen for workers’ compensation.......................................................................................... 364
Workers’ compensation object model........................................................................................................... 364

Part 6
Product model........................................................................................................................................369

39 Product model patterns................................................................................................................................ 371

Products overview..........................................................................................................................................371
Policy line pattern overview........................................................................................................................... 371
Coverage pattern overview............................................................................................................................ 372
Product model categories...................................................................................................................... 372
Coverages, exclusions, conditions, and coverables overview.................................................................372
Product model existence........................................................................................................................ 373
Coverage term pattern overview................................................................................................................... 373
40 Product model availability overview............................................................................................................ 375
Determining the reference date for availability............................................................................................. 375
Making a product model pattern available by policy transaction type.......................................................... 376
Grandfathering in the product model............................................................................................................ 376
Reloading availability in PolicyCenter.............................................................................................................376
41 Offerings in the product model..................................................................................................................... 379
Filtering the product model in availability..................................................................................................... 379
Offering question sets.................................................................................................................................... 380
Select and change an offering........................................................................................................................ 380
42 Schedules overview....................................................................................................................................... 381

Part 7
Common features of PolicyCenter................................................................................................ 383

43 Account file.................................................................................................................................................... 385

Account features............................................................................................................................................ 385
Account security .................................................................................................................................... 385
Related accounts.................................................................................................................................... 385
Moving and rewriting policies between accounts..................................................................................386
Merging accounts................................................................................................................................... 386
Service tier in accounts.......................................................................................................................... 387
Account status........................................................................................................................................ 387
Account screens............................................................................................................................................. 387
Account Summary.................................................................................................................................. 389
Account Holder Summary...................................................................................................................... 391

12 Contents
 Guidewire PolicyCenter 10.2.3 Application Guide

Billing screen for accounts......................................................................................................................392

Account actions.............................................................................................................................................. 393
Working with accounts...................................................................................................................................394
Search for an account.............................................................................................................................394
Create an account.................................................................................................................................. 394
Track your accounts................................................................................................................................ 395
Move a policy from one account to another.......................................................................................... 395
Rewrite policies from one account to an existing account.....................................................................396
Merge accounts...................................................................................................................................... 397
Add an account relationship.................................................................................................................. 398
Modify an account relationship............................................................................................................. 399
Remove an account relationship............................................................................................................ 399
Search for accounts with a shared contact.............................................................................................399
Configuring accounts......................................................................................................................................399
Account object model............................................................................................................................ 399
Account rule sets.................................................................................................................................... 400
Account web service.............................................................................................................................. 401
Withdraw accounts................................................................................................................................ 401
Configuring moving policies between accounts............................................................................................. 401
Configuring account relationships..................................................................................................................402
Account relationship object model........................................................................................................ 402
Account relationship typelist..................................................................................................................402
Account relationship methods in the Account plugin............................................................................ 403
Account relationship rule sets................................................................................................................ 403
Account relationship methods in Gosu classes...................................................................................... 403
Configuring shared contact search criteria.............................................................................................405
44 Locations........................................................................................................................................................ 407
Types of location information........................................................................................................................ 407
Geocoding locations....................................................................................................................................... 407
Synchronizing and revisioning location information...................................................................................... 408
Changing location information....................................................................................................................... 408
Hiding location information on accounts....................................................................................................... 409
Location object model....................................................................................................................................409
Account synchronization classes for locations............................................................................................... 410
Working with account locations..................................................................................................................... 411
Add a new location.................................................................................................................................411
Edit a location......................................................................................................................................... 412
Make a location primary........................................................................................................................ 412
Make a location active or inactive.......................................................................................................... 412
Working with policy locations........................................................................................................................ 413
Viewing locations on bound policies...................................................................................................... 413
Editing location information on a policy transaction..............................................................................413
Adding or removing locations at the policy level................................................................................... 413
Location numbering............................................................................................................................... 414
Risk assessment with Spotlight...................................................................................................................... 414
Risk assessment with Spotlight overview...............................................................................................414
Risk assessment user interface...............................................................................................................414
45 Activities........................................................................................................................................................ 417
Activities creation and assignment................................................................................................................ 418
Activity ownership..........................................................................................................................................418
Activity escalation.......................................................................................................................................... 418

Contents 13
Guidewire PolicyCenter 10.2.3 Application Guide

Localizing activity patterns............................................................................................................................. 418

Working with activities................................................................................................................................... 419
Create an activity....................................................................................................................................419
Assign an activity.................................................................................................................................... 419
Complete or skip an activity................................................................................................................... 419
Select an activity from a queue.............................................................................................................. 420
Activity patterns............................................................................................................................................. 420
Activity pattern components.................................................................................................................. 420
Creating and editing activity patterns.................................................................................................... 421
Using Gosu to edit activity patterns....................................................................................................... 422
Activity object model..................................................................................................................................... 422
Activity batch process.................................................................................................................................... 423
46 Notes.............................................................................................................................................................. 425
Differences between notes and documents.................................................................................................. 425
Working with notes........................................................................................................................................ 425
Searching for notes................................................................................................................................ 426
Viewing notes......................................................................................................................................... 426
View notes related to an activity............................................................................................................426
Edit a note.............................................................................................................................................. 426
Delete a note.......................................................................................................................................... 427
How to print a note................................................................................................................................ 427
Create a note.......................................................................................................................................... 427
Create a note from a note template.......................................................................................................427
Creating a note in an activity..................................................................................................................428
Note security.................................................................................................................................................. 428
Permissions related to notes.................................................................................................................. 428
Configuring notes and note templates........................................................................................................... 428
Note plugin interfaces............................................................................................................................ 428
Note fields.............................................................................................................................................. 429
Creating a note template....................................................................................................................... 429
47 Contacts......................................................................................................................................................... 431
Contact overview........................................................................................................................................... 431
Centralized view of contacts on the Contact tab....................................................................................431
Sharing contacts with a contact management system........................................................................... 432
Contacts and roles.................................................................................................................................. 432
Types of contact information................................................................................................................. 432
Linking an address between multiple contacts...................................................................................... 432
Revisioning contact information in policies....................................................................................................433
Contact revisioning when contacts are synchronized............................................................................ 434
Contact revisioning in future-dated changes......................................................................................... 434
Contact revisioning in back-dated changes............................................................................................ 435
Working with the Contact tab........................................................................................................................ 435
Create a new contact..............................................................................................................................435
Search for a contact................................................................................................................................436
Selecting recently viewed contacts........................................................................................................ 437
View contact file details......................................................................................................................... 437
Create new account from contact.......................................................................................................... 437
Viewing accounts associated with a contact.......................................................................................... 437
View policies associated with a contact................................................................................................. 438
View policy transactions associated with contact.................................................................................. 438
View claims associated with a contact................................................................................................... 439

14 Contents
 Guidewire PolicyCenter 10.2.3 Application Guide

Contact File Claims screen......................................................................................................................439

Viewing billing information for a contact............................................................................................... 440
Contact tab behavior.............................................................................................................................. 441
Working with contacts in policies and accounts............................................................................................ 441
Adding a contact to an account..............................................................................................................441
Adding a contact from the address book............................................................................................... 441
Edit a contact..........................................................................................................................................442
Remove a contact from an account........................................................................................................443
Change the active status on a contact from an account........................................................................ 443
Adding or removing a contact from a policy.......................................................................................... 443
Add or remove a contact role.................................................................................................................443
Working with linked addresses...............................................................................................................444
Changing revisioned contact information in future-dated policy change.............................................. 445
Changing revisioned contact information in a back-dated policy change.............................................. 447
Viewing revisioned contact information in the account.........................................................................449
Working with contacts in policies and accounts............................................................................................ 449
Contact object model..................................................................................................................................... 450
Linked addresses object model.............................................................................................................. 450
Contact roles for accounts and policies..................................................................................................451
Account synchronization classes for contacts................................................................................................ 452
Configuring contacts...................................................................................................................................... 453
Gosu classes for contacts....................................................................................................................... 454
Plugins for contacts................................................................................................................................ 454
Contact batch process............................................................................................................................ 455
Configuring the Contact tab........................................................................................................................... 455
Gosu classes that implement features for the Contact tab.................................................................... 455
PCF files in the Contact tab.................................................................................................................... 455
Configuring contact roles............................................................................................................................... 456
Data model patterns for contact roles................................................................................................... 457
Creating entities that define the new subtypes..................................................................................... 457
Create an implementation of the contact configuration plugin............................................................. 459
Add display key and entity name........................................................................................................... 460
Modify PCF files and Gosu classes..........................................................................................................461
Adding a revisioned field to a contact............................................................................................................ 461
Defining the revisioned field on the account audit contact................................................................... 461
Defining the revisioned field on the policy audit contact.......................................................................462
Defining field as syncable on the policy contact role............................................................................. 463
Define the field as syncable on the account contact role.......................................................................465
Extend entity and Gosu class for future-date policy changes................................................................ 466
Add get and set methods to the policy contact role.............................................................................. 467
Add revisioned field to PolicyCenter user interface............................................................................... 468
Configuring linked addresses for contacts......................................................................................................468

Part 8
Quoting and rating............................................................................................................................... 471

48 Quoting and rating basics.............................................................................................................................. 473

Working with the Quote screen..................................................................................................................... 473
Entities associated with costs and transactions............................................................................................. 473
Cost delegate.......................................................................................................................................... 474
Transaction delegate.............................................................................................................................. 477

Contents 15
Guidewire PolicyCenter 10.2.3 Application Guide

Policy period fields for costs and transactions....................................................................................... 477

Cost and transaction model for businessowners line.............................................................................478
Cost and transaction model for commercial auto line........................................................................... 480
Cost and transaction model for commercial property line.....................................................................481
Cost and transaction model for general liability line..............................................................................482
Cost and transaction model for inland marine line................................................................................ 483
Cost and transaction model for personal auto line................................................................................ 484
Cost and transaction model for workers’ compensation line.................................................................486
Calculating transactions................................................................................................................................. 487
Internal tools for rating: financial transactions screen...................................................................................488
49 Rating overrides.............................................................................................................................................491
Rating overrides permissions......................................................................................................................... 491
Underwriting issues for rating overrides........................................................................................................ 492
Processing rating overrides across policy transactions.................................................................................. 492
Rating overrides in the user interface............................................................................................................ 492
Rating overrides on the Quote screen................................................................................................... 492
Rating Overrides screen......................................................................................................................... 493
Override a rating............................................................................................................................................ 493
Adding rating overrides to a line of business................................................................................................. 494
Enable Override Rating button............................................................................................................... 494
Create panel set for rating overrides......................................................................................................494
Update the rating engine to handle overrides....................................................................................... 495
50 Quote purging................................................................................................................................................ 497
Quote purging overview.................................................................................................................................497
Quote purging configuration business cases.......................................................................................... 498
Quote purging: what gets purged or pruned?........................................................................................498
51 Quote cloning for business intelligence........................................................................................................ 501
Quote cloning business example....................................................................................................................502
52 Improving quoting and rating performance................................................................................................. 503
Improving performance with parallel rating.................................................................................................. 504
Improving performance with parallel product model synchronization..........................................................505
Improving performance with asynchronous quoting..................................................................................... 505
Asynchronous quoting flow....................................................................................................................505
Asynchronous quoting threshold........................................................................................................... 506
Asynchronous quoting for multi-version and side-by-side?................................................................... 506
Asynchronous quoting user interface.....................................................................................................506
Improving performance with two-step quoting............................................................................................. 508
One and two-step quoting workflows.................................................................................................... 508

Part 9
Rating Management............................................................................................................................. 511

53 Rating Management overview...................................................................................................................... 513

Rating Management user interface................................................................................................................514
Rate flow design............................................................................................................................................. 514
Versioning in Rating Management................................................................................................................. 515
Rating worksheets in Rating Management.................................................................................................... 516
Extracting and purging rating worksheets.............................................................................................. 517
Testing Rating Management...........................................................................................................................517
Impact testing for Rating Management................................................................................................. 517
General guidelines for testability of Rating Management......................................................................518

16 Contents
 Guidewire PolicyCenter 10.2.3 Application Guide

Working with impact testing in Rating Management.............................................................................518

Reducing Rating Management components.................................................................................................. 522
Rating Management component applies to all...................................................................................... 522
Combine similar rate routines and parameter sets................................................................................ 522
Examples of working with Rating Management.............................................................................................523
Creating and using a rate table with multiple factors............................................................................ 523
Adding parameters to an in-use rate table definition............................................................................ 525
54 Rate tables in Rating Management............................................................................................................... 529
Rate table definition....................................................................................................................................... 530
Value provider in rate table definition................................................................................................... 530
Physical tables and entities for rate table definitions.............................................................................531
Rate table lookup in memory or database............................................................................................. 532
Rate table normalization for overlapping ranges........................................................................................... 532
Rate table normalization user interface................................................................................................. 533
Considerations for rate table size................................................................................................................... 533
Matching a factor in the rate table.................................................................................................................534
Example of finding a factor in a rate table............................................................................................. 534
Example of finding a factor with a range parameter in a rate table....................................................... 535
Rate table with multiple factors............................................................................................................. 536
Considerations for single or multiple factor rate tables......................................................................... 536
Rate table with interpolated rate factor.................................................................................................537
Working with rate table definitions................................................................................................................539
Search for rate table definition.............................................................................................................. 539
Add a new rate table definition.............................................................................................................. 540
Rate Table Definition screen...................................................................................................................540
Working with the Rate Table editor............................................................................................................... 545
Selecting a rate table.............................................................................................................................. 545
Rate Table screen................................................................................................................................... 545
Edit rate table content in PolicyCenter................................................................................................... 546
Edit rate table content in Excel............................................................................................................... 547
Rate table update validations.................................................................................................................547
Excel rate table import validations......................................................................................................... 548
55 Rate routines in Rating Management........................................................................................................... 549
Rate routine overview.................................................................................................................................... 549
Rate routine design................................................................................................................................ 549
Rate routine versions............................................................................................................................. 550
Rate routine variant identifiers.............................................................................................................. 550
Accessing entity properties and class extensions...................................................................................550
Rate routines that do not calculate properties on the cost............................................................................550
Rate routine steps.......................................................................................................................................... 551
Considerations for rate routine functions...................................................................................................... 552
Working with rate routines............................................................................................................................ 553
Access rate routines............................................................................................................................... 553
Add new rate routine............................................................................................................................. 553
Delete rate routine................................................................................................................................. 554
Actions on rate routines......................................................................................................................... 554
Adding steps to a rate routine................................................................................................................ 555
Instruction and operand types in rate routine steps.............................................................................. 558
Specify function as operand in rate routine step................................................................................... 564
Create rate routine for another jurisdiction........................................................................................... 564
In rate routine, specify coverage as flat-rated........................................................................................ 565

Contents 17
Guidewire PolicyCenter 10.2.3 Application Guide

Editing long rate routines....................................................................................................................... 565

View rating worksheets.......................................................................................................................... 566
56 Parameter sets in Rating Management.........................................................................................................567
Parameter set design..................................................................................................................................... 567
Parameter set performance considerations................................................................................................... 568
Combine similar parameter sets with wrappers............................................................................................ 568
Working with parameter sets in Rating Management................................................................................... 569
Access parameter sets in Rating Management...................................................................................... 569
Add parameter set in Rating Management............................................................................................ 569
Alter parameters in parameter set in Rating Management................................................................... 569
Adding policy line rate modifiers to a parameter set............................................................................. 570
57 Rate books in Rating Management............................................................................................................... 571
Managing rate books and rate tables............................................................................................................. 571
Considerations for rate book maintainability......................................................................................... 572
Rate book storage self-contained........................................................................................................... 572
Changes to parameters in rate table definitions............................................................................................ 573
Adding parameters to rate table definitions.......................................................................................... 573
Deleting parameter from rate table definitions..................................................................................... 574
Editing parameter details in a rate table definition................................................................................574
Changing factors in rate table definitions...................................................................................................... 574
Other types of changes in rate table definitions............................................................................................ 574
Working with rate books................................................................................................................................ 575
Search for rate book............................................................................................................................... 575
Add new rate book................................................................................................................................. 575
Delete rate book..................................................................................................................................... 576
Rate Book screen.................................................................................................................................... 576
Rate book status and available actions.................................................................................................. 578
Rate book actions and permissions........................................................................................................ 579
Merge rate books................................................................................................................................... 579
Export rate book to spreadsheet............................................................................................................580
Importing and exporting rate books to XML.......................................................................................... 581
Importing rate tables from spreadsheet................................................................................................ 583
Selecting the rate book edition during policy rating...................................................................................... 585
Rate book matching process.................................................................................................................. 585
Filtering for the most appropriate rate book......................................................................................... 586
Filtering for cascaded lookup rate books................................................................................................587
Example of cascaded lookup in rate book.............................................................................................. 587
Overlapping effective policy periods and rate-as-of date in rate book.................................................. 588
Rate book lifecycle and moving to production............................................................................................... 589
Synchronize development rate books with production..........................................................................590
Development environment with Rating Management...........................................................................591
Stage environment with Rating Management....................................................................................... 591
Production environment with Rating Management...............................................................................591

Part 10
Reinsurance Management................................................................................................................ 593

58 Reinsurance program overview.................................................................................................................... 595

Reinsurance program design.......................................................................................................................... 596
Reinsurance program example....................................................................................................................... 597
Reinsurance program example: risk and loss in treaty composition...................................................... 597

18 Contents
 Guidewire PolicyCenter 10.2.3 Application Guide

Reinsurance program example: risks and coverables when applying program treaties to a loss.......... 598
Example: attaching policies to reinsurance programs and treaties........................................................598
Reinsurance agreements................................................................................................................................ 599
Facultative agreements.......................................................................................................................... 600
Proportional agreements....................................................................................................................... 600
Non-proportional agreements............................................................................................................... 603
Summary of agreement types................................................................................................................ 607
How Reinsurance Management links reinsurance to policies........................................................................ 607
How Reinsurance Management attaches programs to policies............................................................. 607
How Reinsurance Management attaches agreements to policies......................................................... 608
Calculating ceded premiums in Reinsurance Management........................................................................... 610
Ceding premium to excess of loss agreements...................................................................................... 612
Ceding premium to proportional agreements....................................................................................... 612
Ceding premium to facultative net excess of loss agreements.............................................................. 612
Example: ceded premiums in Reinsurance Management...................................................................... 613
Gross retention.............................................................................................................................................. 614
Shared reinsurance agreements.................................................................................................................... 615
Differential rates of commission in reinsurance..................................................................................... 615
Location groups and reinsurance................................................................................................................... 615
59 Working with the Reinsurance tab................................................................................................................617
Search for agreements in reinsurance............................................................................................................617
Search for all agreements in reinsurance....................................................................................................... 617
Create a new treaty in reinsurance................................................................................................................ 618
Create a new program in reinsurance............................................................................................................ 618
Edit a program in reinsurance........................................................................................................................ 618
Disable a program that has attached policies in reinsurance.........................................................................619
Create a new facultative agreement in reinsurance.......................................................................................619
Validate an agreement in reinsurance............................................................................................................619
Make an agreement active in reinsurance..................................................................................................... 620
60 Working with Reinsurance Management in policies.................................................................................... 621
Add reinsurance to a policy............................................................................................................................ 621
Create a location group.................................................................................................................................. 622
View ceded premiums....................................................................................................................................623
Modify the gross retention............................................................................................................................ 624
Adding or linking to a facultative agreement................................................................................................. 624
Add a new facultative agreement.......................................................................................................... 625
Link to an existing facultative agreement...............................................................................................625
Edit ceding parameters.................................................................................................................................. 625
61 Reinsurance Management screens............................................................................................................... 627
Treaty or Facultative Agreement screen........................................................................................................ 627
Reinsurance Program screen.......................................................................................................................... 633
Search Agreements screen for reinsurance....................................................................................................634
Search Programs screen for reinsurance........................................................................................................ 635
Reinsurance screen in the policy file.............................................................................................................. 636

Part 11
Underwriting authority........................................................................................................................639

62 Underwriting authority overview................................................................................................................. 641

Underwriting authority components............................................................................................................. 641
Choosing between validation and underwriting authority............................................................................ 641

Contents 19
Guidewire PolicyCenter 10.2.3 Application Guide

Underwriting issue flow................................................................................................................................. 642

Implement underwriting authority................................................................................................................ 642
63 Underwriting rules........................................................................................................................................ 645
Underwriting rules overview..........................................................................................................................645
Business rule execution flow.................................................................................................................. 645
Accessing business rules........................................................................................................................ 646
Setting up business rules........................................................................................................................ 646
Business rule states................................................................................................................................ 646
Guidelines for designing underwriting rules.................................................................................................. 647
Underwriting issues with values.............................................................................................................649
Checking sets and blocking points for underwriting issues....................................................................651
Underwriting referral reasons raise underwriting issues....................................................................... 654
Approvals of underwriting issues........................................................................................................... 654
Underwriting Rules screen............................................................................................................................. 656
Externally managed rules....................................................................................................................... 657
Clone business rules............................................................................................................................... 657
Promote business rules.......................................................................................................................... 657
View business rule history......................................................................................................................657
Enabling or disabling a business rule..................................................................................................... 658
Deleting a business rule version............................................................................................................. 658
Underwriting Rule screen...............................................................................................................................659
Rule Details tab on Underwriting Rule screen........................................................................................659
Advanced Info tab on Underwriting Rule screen....................................................................................661
Entering expressions in business rules................................................................................................... 661
Working with business rule variables..................................................................................................... 665
Specifying business rule conditions........................................................................................................667
Operations in business rule conditions.................................................................................................. 667
Specifying underwriting issue details..................................................................................................... 669
Managing business rule export and import................................................................................................... 670
Exporting and importing data lookup tables ......................................................................................... 670
Exporting and importing underwriting issue types................................................................................ 670
Manage Data Lookup Tables screen............................................................................................................... 671
Create New Lookup screen.....................................................................................................................671
64 Underwriting issues....................................................................................................................................... 673
Working with underwriting issues..................................................................................................................673
Underwriting issues on the Risk Analysis screen....................................................................................673
Risk Approval Details popup for risk analysis......................................................................................... 674
Add underwriting referral reasons................................................................................................................. 676

Part 12
PolicyCenter administration.............................................................................................................677

65 Security: roles, permissions, and the community model............................................................................. 679

Community model overview.......................................................................................................................... 679
Producers in the community model....................................................................................................... 680
Types of security............................................................................................................................................ 681
Role-based security................................................................................................................................ 681
Data-based security for accounts and policies....................................................................................... 682
Data-based security for the community model......................................................................................685
System and application permissions...................................................................................................... 686
Security restrictions using the status field............................................................................................. 686

20 Contents
 Guidewire PolicyCenter 10.2.3 Application Guide

Producer of record and producer of service.................................................................................................. 687

Producers of service can edit the account............................................................................................. 687
Changing the producer........................................................................................................................... 687
Adding a third producer......................................................................................................................... 687
Managing the PolicyCenter community......................................................................................................... 688
Understanding internal and external administration............................................................................. 688
Creating external users...........................................................................................................................688
Security object models................................................................................................................................... 688
Object model for producer codes.......................................................................................................... 689
Working with users and security.................................................................................................................... 689
View permissions on selected roles....................................................................................................... 689
Create a permission................................................................................................................................690
Remove a permission............................................................................................................................. 690
Add a permission to a role..................................................................................................................... 690
Add a new role....................................................................................................................................... 690
Remove a role........................................................................................................................................ 691
Turn on producer code security............................................................................................................. 691
Working with regions............................................................................................................................. 691
Designating a client data integration handler........................................................................................ 692
Working with affinity groups.................................................................................................................. 692
Security and configuration scenarios related to producer codes................................................................... 693
Producer codes assigned by level...........................................................................................................693
Producer codes assigned by line of business......................................................................................... 694
Producer codes assigned by level and line of business.......................................................................... 694
Producer codes roles customized by user.............................................................................................. 695
Producer code security for agents working for multiple agencies......................................................... 695
Producer code currency......................................................................................................................... 696
Security Dictionary......................................................................................................................................... 697
Access control for documents and notes....................................................................................................... 697
Working with access control for documents and notes......................................................................... 698
su, the Super User.......................................................................................................................................... 699
66 Authority profiles.......................................................................................................................................... 701
Working with authority profiles..................................................................................................................... 703
View or edit an authority profile............................................................................................................ 703
Assign an authority profile to a user...................................................................................................... 703
67 Team management........................................................................................................................................ 705
Groups and the Team tab............................................................................................................................... 705
Team tab user categories............................................................................................................................... 706
Reporting categories on the Team tab........................................................................................................... 706
Working with the Team tab............................................................................................................................ 707
Assign activities on the Team tab........................................................................................................... 707
Assign submissions, renewals, and other policy transactions................................................................ 707
68 Policy holds administration........................................................................................................................... 709
Underwriting holds for natural disasters........................................................................................................709
Policy holds for regulatory changes............................................................................................................... 710
Specifying policy holds................................................................................................................................... 710
Prevent back-dating policy transaction to avoid underwriting hold.............................................................. 711
Working with policy holds.............................................................................................................................. 711
Example: creating a simple policy hold.................................................................................................. 711
Work with policy hold actions................................................................................................................ 714
Deleting or disabling a policy hold......................................................................................................... 715

Contents 21
Guidewire PolicyCenter 10.2.3 Application Guide

Policy hold actions in renewals.............................................................................................................. 716

Policy Holds screen.........................................................................................................................................716
Create or edit a policy hold.................................................................................................................... 716
Policy Hold Details tab............................................................................................................................ 716
Policy Hold Regions tab.......................................................................................................................... 717
Copying a policy hold............................................................................................................................. 718
Configuring policy holds................................................................................................................................. 718
Policy hold object model........................................................................................................................ 718
Policy hold permissions.......................................................................................................................... 719
Policy hold authority grant..................................................................................................................... 719
Policy hold underwriting issue types......................................................................................................719
Policy hold Gosu classes......................................................................................................................... 719
Policy Hold batch process.......................................................................................................................720
69 Holidays and business weeks........................................................................................................................ 721
Specifying holiday dates................................................................................................................................. 721
Holiday types.......................................................................................................................................... 721
Working with holidays and zones................................................................................................................... 722
Add a holiday..........................................................................................................................................722
Edit a holiday.......................................................................................................................................... 722
Delete a holiday......................................................................................................................................723
Create a new zone or type..................................................................................................................... 723
Using Gosu methods to work with holidays................................................................................................... 723
Gosu holiday methods that use zones and types................................................................................... 723
Business weeks and business hours............................................................................................................... 723
Business hours........................................................................................................................................724
Gosu methods for business hours.......................................................................................................... 724
70 Policy form pattern administration............................................................................................................... 725
About forms................................................................................................................................................... 725
Form basics............................................................................................................................................ 726
Working with form patterns........................................................................................................................... 726
Search for form pattern.......................................................................................................................... 726
Add form pattern....................................................................................................................................727
Specifying removal or replacement forms for policy changes................................................................727
Importing and exporting policy form patterns....................................................................................... 728
Form Pattern or New Policy Form screen.......................................................................................................728
Basics tab for form patterns................................................................................................................... 728
Products tab for form patterns...............................................................................................................729
Transaction Types tab for form patterns................................................................................................ 730
Jurisdictions tab for form patterns......................................................................................................... 730
Policy Change tab for form patterns.......................................................................................................731
Inference tab for form patterns..............................................................................................................733
Form configuration......................................................................................................................................... 734
Adding a custom inference class for form patterns................................................................................734
Configuring custom form inference........................................................................................................736
Configuring form inference by coverage part and policy type............................................................... 737
Configuring generic form inference........................................................................................................738
Form pattern validation..........................................................................................................................738
71 Archiving in PolicyCenter...............................................................................................................................739
Advantages of archiving................................................................................................................................. 740
Impact archiving on your PolicyCenter configuration.................................................................................... 740
More information on archiving...................................................................................................................... 740

22 Contents
 Guidewire PolicyCenter 10.2.3 Application Guide

Archiving policy terms.................................................................................................................................... 740

Policy terms that PolicyCenter does not archive.................................................................................... 741
Entities retained after archiving............................................................................................................. 741
Run Archive Policy Term batch process.................................................................................................. 742
Exclude policy from archiving.........................................................................................................................743
Searching for archived policy periods............................................................................................................ 743
Search archived policy periods............................................................................................................... 743
Desktop and Team tabs and archiving.................................................................................................... 744
Retrieving archived policies............................................................................................................................744
Request retrieval of an archived policy.................................................................................................. 744
Retrieve archived policies that have been requested............................................................................ 745
72 Personal data destruction............................................................................................................................. 747
Encapsulation of business logic for retention and destruction...................................................................... 747
Notification of data protection officer on errors or conflicts......................................................................... 748
Wide-swath data destruction......................................................................................................................... 748
Individual-entity data destruction.................................................................................................................. 748
Integration with other systems...................................................................................................................... 748
Notification of downstream systems..............................................................................................................749
73 Administration utilities..................................................................................................................................751
Importing and exporting data........................................................................................................................ 751
Administering script parameters.................................................................................................................... 751
Reviewing data changes................................................................................................................................. 751
Importing and exporting policy data spreadsheets........................................................................................752
Spreadsheet export formats user interface............................................................................................752
Define export formats............................................................................................................................ 752
Using inbound files integration...................................................................................................................... 753
Using outbound files integration....................................................................................................................753
Using runtime properties............................................................................................................................... 753
74 Guidewire Analytics.......................................................................................................................................755
Analytics Manager..........................................................................................................................................755
Required permissions for Analytics Manager.........................................................................................756
Working with the analytics solutions............................................................................................................. 756
Activating a Guidewire analytics solution.............................................................................................. 757
Enabling a Guidewire analytics solution.................................................................................................757
PolicyCenter demonstration analytics solutions............................................................................................ 757
The Utility tab................................................................................................................................................. 758
Predictive Analytics Solutions........................................................................................................................ 759
Activate a Predictive Analytics solution..................................................................................................759
Create a custom Predictive Analytics solution....................................................................................... 760
Create a Predictive Analytics test solution............................................................................................. 762
The Predictive Analytics Errors screen................................................................................................... 762
Cycence Analytics Solutions........................................................................................................................... 762
Activate a Cyence Analytics solution...................................................................................................... 762

Part 13
PolicyCenter external system integration.................................................................................. 765

75 Document management................................................................................................................................767
Document storage overview.......................................................................................................................... 768
Document metadata properties............................................................................................................. 768
Working with documents............................................................................................................................... 769

Contents 23
Guidewire PolicyCenter 10.2.3 Application Guide

Viewing documents................................................................................................................................ 769

Searching for documents....................................................................................................................... 770
Create a new document......................................................................................................................... 771
Edit content for a document.................................................................................................................. 773
Edit metadata properties of a document............................................................................................... 774
Hiding a document................................................................................................................................. 774
Delete a document................................................................................................................................. 775
Configuring and integrating document management.................................................................................... 775
Document security................................................................................................................................. 775
Configuration parameters for document management......................................................................... 776
Document management integration...................................................................................................... 776
Creating a document template.............................................................................................................. 777
76 Document production with Smart Communications for PolicyCenter.........................................................779
Smart Communications for PolicyCenter features......................................................................................... 780
Third-party software requirements for Smart Communications for PolicyCenter......................................... 780
Document types in Smart Communications for PolicyCenter........................................................................ 780
Network flows in Smart Communications for PolicyCenter........................................................................... 781
Synchronous draft document creation flow in Smart Communications for PolicyCenter.............................. 781
Document production flow with Smart Communications for PolicyCenter................................................... 784
Asynchronous bulk document production in Smart Communications for PolicyCenter................................ 785
Attaching documents to objects in Smart Communications for PolicyCenter................................................785
Specifying when Smart Communications for PolicyCenter creates documents............................................. 786
77 Billing system integration.............................................................................................................................. 787
Billing system integration overview............................................................................................................... 788
Organizations and producer codes in PolicyCenter and billing system.................................................. 788
Producer organizations in PolicyCenter and BillingCenter..................................................................... 788
Multicurrency and producer organizations............................................................................................ 788
Multicurrency and producer codes........................................................................................................ 789
Accounts in PolicyCenter and billing system.......................................................................................... 789
Multicurrency and accounts................................................................................................................... 790
Policies in PolicyCenter and billing system............................................................................................. 790
Sending charges and other information to the billing system................................................................791
Payment screen in PolicyCenter............................................................................................................. 791
Contacts in PolicyCenter and billing system........................................................................................... 791
Billing system and policy transactions that create a new policy period......................................................... 791
Billing system and policy transactions that create midterm changes............................................................ 794
Cancellations in the billing system integration....................................................................................... 795
Reinstatements in the billing system integration................................................................................... 795
Renewals or rewrites in the billing system integration.......................................................................... 796
Final audits in the billing system integration.......................................................................................... 796
Premium reporting in the billing system integration..............................................................................797
Working with the billing system integration.................................................................................................. 797
Working with the Payment screen......................................................................................................... 797
Working with charge breakdowns.......................................................................................................... 801
View policy period in BillingCenter........................................................................................................ 804
Working with accounts from the billing system..................................................................................... 804
Working with policies in the billing system integration..........................................................................805
Multicurrency integration between BillingCenter and PolicyCenter.............................................................. 805
Limitations of multicurrency billing and policy integration.................................................................... 806
Multicurrency accounts in PolicyCenter and BillingCenter.................................................................... 806
Using commission plans to select currencies for producer codes..........................................................806

24 Contents
 Guidewire PolicyCenter 10.2.3 Application Guide

Single currency producer codes in PolicyCenter and BillingCenter........................................................ 807

Multicurrency producer codes and producer organizations.................................................................. 807
Default billing and policy multicurrency integration.............................................................................. 807
78 Claim system integration............................................................................................................................... 809
Accessing summary loss information from the claim system.........................................................................810
Viewing loss claims for policies.............................................................................................................. 810
Viewing claim on policy in claim system................................................................................................ 811
Viewing loss claims from an account..................................................................................................... 811
Loss claims notification at renewal................................................................................................................ 811
Large loss notification from ClaimCenter....................................................................................................... 813
Permissions for working with claims.............................................................................................................. 813
Restricted fields in claims....................................................................................................................... 813
Claim Search plugin........................................................................................................................................ 813
79 Contact management system integration..................................................................................................... 815
Contact management system integration overview.......................................................................................815
Searching for contacts within a contact management system....................................................................... 816
New and updated contacts and contact management system...................................................................... 816
Pushing new and updated contacts to contact management system.................................................... 817
Pushing new and updated contact to ContactManager......................................................................... 817
Adding a contact from the contact management system...................................................................... 817
New contact when integrated with contact management system.........................................................818
Detecting duplicates in the contact management system............................................................................. 819
Detecting duplicates when integrated with ContactManager................................................................819
Duplicate contacts in PolicyCenter................................................................................................................. 822
Deleting, removing, and inactivating a contact.............................................................................................. 823
Customizing the contact management system integration............................................................................ 823
Contact management entry points into PolicyCenter............................................................................ 824
Integrating with multiple contact management systems....................................................................... 824

Contents 25
Guidewire PolicyCenter 10.2.3 Application Guide

26 Contents
Support

For assistance, visit the Guidewire Community.

Guidewire customers
https://community.guidewire.com
Guidewire partners
https://partner.guidewire.com
part 1

Introduction to PolicyCenter

PolicyCenter is a web-based underwriting and policy administration system designed for personal and commercial line
insurers in the property and casualty insurance (P&C) industry. In PolicyCenter, producers and underwriters can submit
applications, renew policies, and manage policy changes. Auditing is available for certain types of policies.
PolicyCenter provides access to agents, and supports producer relationships and underwriting risk assessment. Typical
users, such as underwriters and producers, can create and manage policies, service accounts, evaluate risks, view
policies, create activities, and handle inquiries. PolicyCenter also provides access management tools for viewing
groups and repurposing workloads.
PolicyCenter stores information about a policy and manages a set of processes that, if completed successfully, result in
changes to the policy. Examples of policy changes are: creation of a new policy, renewal of a policy for a new term, or
cancellation of a policy. As a result of each policy transaction (such as adding an additional driver to an auto policy),
the system determines the price of the transaction. If successfully completed, PolicyCenter forwards this pricing
information to a billing system. The pricing information is also important for reporting to regulators.
In PolicyCenter, you can tailor your products. Before you can use PolicyCenter to manage policies, you must first
define your product line. In other words, what products are you going to offer? Products are the first level of the
product model hierarchy. Insurers or agents sell these products (such as personal auto or workers’ compensation
policies) to customers. Each individual policy is an instance of a product. Therefore, personal auto, businessowners,
and workers’ compensation are all products.
While PolicyCenter comes with certain lines of business, it is flexible. You can customize the default lines of business
to meet your business needs. You can also create your own lines of business in Guidewire Product Designer.
(PolicyCenter includes Product Designer.)
How do you configure PolicyCenter? Use Guidewire Studio as the integrated development environment (IDE) to
configure PolicyCenter to meet your business needs. In Studio, you can control workflow, policy transactions, PCF
screens, typelists, rules, and Gosu.
How are lines different from products? For example, general liability and commercial property are both lines. If you
represent a business, you can buy a general liability product, which just includes the general liability line. Then you can
buy a commercial property product, which includes just the commercial property line. However, you can also buy a
commercial package product, which may include both the general liability and commercial property lines. Commercial
package is a multi-line product, as opposed to a monoline product. Conversely, an insurer can sell multiple products,
each of which includes the same line or lines. A product can be targeted to a particular group. For example, an insurer
can offer a commercial package for shopping centers, one for hotels, and one for universities.
How do you manage policies? You create and manage policies through a web interface. On this virtual Desktop, you
create policy transactions (or jobs) that process policies in various ways. Through policy transactions, you can submit,
issue, change, renew, cancel, reinstate, rewrite, and audit policies.

Introduction to PolicyCenter 29
Guidewire PolicyCenter 10.2.3 Application Guide

Types of policy transactions include: submission, issuance, policy change, renewal, cancellation, reinstate, rewrite, and
audit.

30 Introduction to PolicyCenter
chapter 1

Product model

The PolicyCenter product model is at the core of its line of business configuration. It defines the products that insurers
offer through PolicyCenter. PolicyCenter stores these product definitions as patterns. PolicyCenter uses these patterns
during the submission process to generate instances of policies or the subcomponents of policies. Use Guidewire
Product Designer to create and manage your product model.
You can configure PolicyCenter to meet your business needs. You can define a product, select a policy line, and offer
different coverages and coverage terms.
PolicyCenter is dynamic – you can define, create and implement products. For each product, the product model defines
what each product can cover. For example, an auto policy includes information about collision coverage and uninsured
motorist property damage coverage. You configure the business logic in Product Designer. The backing data model,
code, and PCF pages required to support a line of business must be created by a developer using Guidewire Studio.

Example
Janet Jones, an Acme Insurance producer, has noticed many people driving the new hybrid auto (gas and electric). She
has an idea that she thinks her manager will like. So she begins to research the idea of offering a new coverage that can
bring more revenue to the company. Her extensive research indicates that more than 20% of new car drivers in three
surrounding cities drive the new vehicle. Further research also indicates that the life span of the battery is about 80,000
miles. She proposes to her manager that Acme can be the first insurance company in their area to offer special coverage
on the hybrid that would cover batteries. Her manager likes the proposal. Offering a new hybrid coverage can be
implemented in PolicyCenter in weeks, instead of the years that it would take an IT department to make changes on a
legacy system. This speed gives insurance companies the competitive edge to get to market quickly.

Lines of business in the base application

The PolicyCenter base application contains several lines of business. Each line of business contains a reference
implementation that you can use to accelerate your implementation. Each line of business includes reference
implementations for policy transactions, policy file screens, and sample rating rules. A line of business may contain
forms and forms logic. A line of business may also contain rules to determine eligibility. Each reference
implementation also provides sample content, though the extent of this content varies by line of business.
PolicyCenter includes the following lines of business:
• Businessowners
• Commercial auto
• Commercial property
Product model 31
Guidewire PolicyCenter 10.2.3 Application Guide

• General liability
• Homeowners
• Inland marine
• Personal auto
• Workers’ compensation
Note: The PolicyCenter default application is not a compliance system. Guidewire designed the product model
so that you can maintain your lines of business within your jurisdictions, as necessary. For example, the system
tables in the default application can accommodate multiple classifications per jurisdiction over time. Lines of
business can accommodate many coverages and exclusions per jurisdiction over time. The default application
contains a sample set of these classifications, coverages, and exclusions.
There is a corresponding product for each line of business. In addition, commercial package is a multi-line product that
includes commercial property, inland marine, and general liability.

32 Product model
chapter 2

The policy lifecycle

The core of PolicyCenter revolves around the policy. So it is helpful to understand the lifecycle of a policy, which
includes policy transactions, within PolicyCenter.
The following diagram shows the policy lifecycle, from submission and issuance, through various policy transactions
such as renewal and rewrite, to cancellation. This diagram does not display details in each policy transaction, but rather
provides a high level view. You can find detailed descriptions for each policy transaction in subsequent topics.

Policy lifecycle

Policy change
Policy creation begins with
a submission

Renewal Non renewal

Submission/
Issuance Policy
Expiration
Pre-qualify
Evaluate
Bind/Issue
Cancellation Policy Ends
De bm
su
ta iss
ils io
of n
a

Reinstatement Rewrite

Final
Audit

A PolicyCenter policy
transaction or job

Submission
The goal of the submission process is to create a policy and have the policyholder accept it. After entering the
policyholder’s information, the producer gives a quote. If the policyholder agrees and accepts it, then the producer
The policy lifecycle 33
Guidewire PolicyCenter 10.2.3 Application Guide

binds the policy and sends it out with the accompanying documentation. The producer also forwards the billing
information to an external billing system (not shown in the diagram).

Policy change
Any changes to a policy can require additional evaluation on the part of an underwriter and result in a change to the
premium. A typical change might include additions to the policy (such as adding drivers or cars) or changes to
coverage limits and deductible amounts.

Renewal
The normal progression just before a policy expires is to renew it for another period of time – six to 12 months is
typical. After PolicyCenter renews a policy, it returns the policy to maintenance mode until the policy changes, expires,
cancels, or renews again.

Cancellation and reinstatement

You can also cancel policies. Before the cancellation processes completes, a cancellation can be rescinded. An example
is a producer mailing a cancellation notice for non-payment to a policyholder. If the policyholder corrects this by
submitting payment before the cancellation date then the cancellation can be rescinded with no break in coverage.

Reinstatement
Reinstatements go hand in hand with cancellations and are a type of policy change that returns a canceled policy to in-
force status. The policy is in-force as of the reinstatement date. The reinstatement removes the cancellation from the
policy period since the period is no longer canceled. The expiration date remains the same.

Rewrite
When there are many errors are on a policy, it becomes necessary to rewrite it. Policies must first be canceled before
being rewritten.

Audit
The audit policy transaction lets the insurer verify information about the policyholder so that they can determine the
accuracy of premiums paid. The audit policy transaction provides final audit and premium reports.
PolicyCenter supports only final audit for the workers’ compensation line of business. You set up the method of final
audit (physical, voluntary, or by phone) when you create the workers’ compensation policy.
With premium reports, the policyholder is billed for premium based on periodic requests for actual basis amounts, such
as payroll. A deposit, usually a percentage of the estimated annual premium, is billed at the beginning of the policy. As
each reporting period ends, the policyholder is billed based on the actual basis reported by them.

34 The policy lifecycle

chapter 3

Integration with other Guidewire

applications

The default installation of PolicyCenter provides integrations with:

• Guidewire BillingCenter
• Guidewire ClaimCenter
These integrations are easily enabled. You can customize these integrations for your business needs.
See also
• “Billing system integration” on page 787
• “Claim system integration” on page 809

Integration with other Guidewire applications 35

Guidewire PolicyCenter 10.2.3 Application Guide

36 Integration with other Guidewire applications

chapter 4

PolicyCenter users

There are several types of users in PolicyCenter. Typically, users spend much time working on policy transactions or
looking up a policy’s status to answer questions. Looking up information is relatively simple: users search for an
account or a policy and view available data through the user interface. Managing policy transactions is more complex.
Users initiate some transactions (for example, an agent fills out a submission to get a quote). Other transactions are a
mix of automated and manual handling. For example, renewals are usually automated, but are sometimes referred to an
underwriter. PolicyCenter also supports activities, notes, attached documents, history, team views, and more to help
users keep track of their work, collaborate with others, and keep these processes moving.
The following table lists typical PolicyCenter users and their roles:

Users Typical Activities

Agents • Answer queries regarding policies

(independent, captive, or • Submit a quote
direct)
• Change or cancel a policy

Policy Service Reps • Data entry and tracking policies

Policy Processors • Answer simple queries

Underwriters • Review accounts and policies

• Review policy changes
• Rewrite policies
• Evaluate (do risk analysis on) policies and policyholders

Underwriting Management Use team screens to:

• Monitor work loads of subordinates
• View subordinate activities
• View polices assigned to subordinates

Claims staff • View policies

• Leave notes or attach documents to accounts and policies
• Send messages (such as a risk alert) indicating that a policy has a large loss

Accounting staff • View policies

PolicyCenter users 37
Guidewire PolicyCenter 10.2.3 Application Guide

Users Typical Activities

• Leave notes or attach documents to accounts and policies

• Send messages (such as a non-renewal alert) recommending to not renew a policy due to non-
payment

Auditors • Audit policies

(internal and external) • Provide input to underwriters

38 PolicyCenter users
part 2

PolicyCenter user interface

In PolicyCenter, you create and manage policies through a web interface.

Common areas in the PolicyCenter user interface

The PolicyCenter main user interface contains the following areas:

PolicyCenter user interface 39
Guidewire PolicyCenter 10.2.3 Application Guide

Area Description

1 The Tab bar contains:

• Tabs
• QuickJump box is the text box that displays Go to (Alt+/). For more information, see “QuickJump” on page 59.

• Unsaved Work list. For more information, see “Saving your work” on page 77.

• Options menu contains various links including International, Help, About, Preferences, and Log Out.

2 The Info bar displays information pertaining to your immediate task as seen in the main screen area (#4). The Info bar is not
always visible. In the base configuration, the Info bar is visible only on the Account and Policy tabs. The Info bar may have
links that allow you to navigate up a level, such as from a policy to an account.

3 The Sidebar contains menu links and the Actions menu. Use the Sidebar menu links to navigate to different pages. The items
in the Sidebar are contextual and change depending on the policy object.
The Date field displays the as of date of the policy term. PolicyCenter displays the policy data effective as of this date.
In most cases, when viewing a bound policy, the Quote screen displays the premium of the bound policy, regardless of the
date.
If you enter this screen by selecting a policy transaction on the Account File Policy Transactions screen, PolicyCenter displays
the policy transaction with the initial quote. If you change the date, PolicyCenter switches to a mode that displays the
bound policy as of a certain date. In this mode, PolicyCenter displays the bound quote, whatever the date.

4 The Screen Area displays most of the business information.

5 The Workspace can display information separate from the Screen Area, such as modifying your Preferences or viewing or
adding a note.

40 PolicyCenter user interface

chapter 5

Navigating PolicyCenter

This topic describes how to access PolicyCenter and provides instructions on how to navigate the user interface.

Logging into PolicyCenter

You log in to PolicyCenter by running the application and logging in with your user name and password.

PolicyCenter login requirements

Logging in to PolicyCenter requires the following:
• A web browser – For information about supported browsers, see the Installation Guide.
• The URL (web address) for connecting to PolicyCenter – Contact your system administrator for details on
installation and the web address to use. You can set up a Favorite link to the URL or create a shortcut on your
computer desktop that starts a web browser with that URL.
• A user name and password
Because PolicyCenter generates screens dynamically:
• You cannot create Favorites to screens other than the login screen.
• The Back button of the browser is not supported.

Log in to PolicyCenter

Procedure
1. Launch PolicyCenter by opening up an instance of a web browser, entering the appropriate web address, such as:
http://localhost:8180/pc/PolicyCenter.do

2. Enter your User Name and Password on the login screen.

Results
If your login is successful, PolicyCenter displays your startup view, or landing page. In the default configuration,
PolicyCenter initially opens to the My Activities screen on the Desktop tab. This screen lists all open activities that have
been assigned to you.
Navigating PolicyCenter 41
Guidewire PolicyCenter 10.2.3 Application Guide

Setting preferences
You can set user preferences by selecting Preferences from the Options menu . Your changes take effect the next
time you log in.
In the Preferences worksheet you can specify:
• Email notification – Request email notification when an activity is assigned to you. In the default configuration,
selecting this item does not enable email notification. This feature must be configured.
• Password – Change your password.
• Regional Formats – Set the regional formats that PolicyCenter uses to enter and display dates, times, numbers,
monetary amounts, and names.
• Default Country – Determines the settings for names and addresses.
• Default Phone Region – Determines how phone number entries are handled, especially the country code setting.
• Startup Page – Change the page that PolicyCenter displays when you log in by selecting a Startup Page.
• Recent activity – Determine how many recent accounts, policies and policy transactions, or contacts display at the
end of the Account, Policy, and Contact tab menus. For each user, the recently viewed list is initially empty.
Accounts, policies and policy transactions, and contacts are added as the user views these items over multiple
sessions. More recently viewed items appear higher on the list. Once the maximum number of recent items has
been reached, older items are removed and replaced by newer ones.
The value of this field must be between 1 and 10, inclusive.
If the field has no value, PolicyCenter uses a value from config.xml in Studio. In the default configuration, the
parameter value is 5. The value can be between 1 and 10, inclusive. Other values generate an error when
PolicyCenter starts. The parameters in config.xml are:

Preferences label config.xml parameter

Maximum Recent Accounts MaxRecentAccounts

Maximum Recent Policies And Policy Transactions MaxRecentPoliciesAndJobs

Maximum Recent Contacts MaxRecentContacts

Changing interface settings

Change interface settings to control the behavior of certain functions in the user interface.
On the top tab bar, in the Options menu, click Settings.

Appearance settings

Setting Description
Application font size The base font size, in points, of the text used on the application screens.
Global spacing modifier A multiplier that decreases (when less than 1) or increases (when greater than 1) the
amount of whitespace surrounding visual elements.
Theme The theme to use as the visual style of the application. If you require higher color
contrast, try the Guidewire Cloud High Contrast theme.
Left align top toolbars Set to align the toolbar at the top of the screen to the left instead of the right.
Highlight changed values Set to have the background of edited input elements change to a different color.
Scrolling the page hides and shows the Set to hide and show the tab bar when scrolling the page.
navigation bar
Combine top level navigation Set to move elements in the top navigation bar under the More icon menu:

42 Navigating PolicyCenter
 Guidewire PolicyCenter 10.2.3 Application Guide

Setting Description

• Do Not Combine - Leave navigation elements in their standard locations.

• Combine Menus - Move icons and other elements in the top menu bar under the
More menu.
• Combine Menus and Bars - Move all tabs, menus, and toolbars under the More
menu.

Dates settings

Setting Description
Use complex date picker options Adds a Selected Day button to date pickers, which navigates the calendar to the
currently selected date.
Use small date picker Reduces the size of date pickers by reducing the font size and spacing.
Open date/time pickers on focus Set to open a date picker automatically when you navigate to a date input. When this
setting is not set, you must click the icon next to the date picker to open it.
Today button in date picker selects today and Set to have the date picker close automatically after you click Today to set the date
closes picker input to the current date.
Cap user input to max values for days, In a date input, automatically change values that are greater than the allowed values
months, minutes, and hours to the maximum allowed values.

General settings

Setting Description
Always confirm browser navigation When using browser navigation, such as by clicking the Back button, show a
confirmation alert before changing the page.
Disable browser autocomplete Disable the browser's autocomplete function to avoid having it suggest values for text
inputs.
Scroll the screen to the top on any errors When an input error occurs, automatically show the top of the screen, where the error
message appears.
Navigating rows of a List Detail using up and When set, using the arrow keys to move up and down in a list detail view also selects
down arrow keys also selects the row the current row and shows its detail. When not set, using the arrow keys highlights a
row but does not select it; to select it, click on it or press Enter.
Replace special word processor characters in When set, special characters typed in editable text boxes are automatically changed to
editable fields with standard versions. standard characters. For example, ¾ is changed to 3/4, and curly quotes (“”) are
changed to straight quotes ("").
Use an illegal value instead of 'off' when The interface tries to disable autocomplete on certain form fields by setting the
trying to disable browser autocomplete autocomplete attribute to off. Some browsers instead disable autocomplete only if
the attribute is set to an invalid value. To use an invalid value instead of off, select
this setting.

Debug settings

Setting Description
Highlight elements that are redrawn Screen elements that are redrawn after an update pulsate for a short time. The visual
effect identifies which elements were affected by the update.
Ignore PCF widths and heights Render screen elements as if they do not have any width or height values set for them.
Ignoring the width and height settings helps you see what they would look like without
those values set.
Highlight widgets with PCF widths and Surround all PCF widgets that have width and height attributes set with a highlight
heights color. The highlighting helps you identify elements that have widths and heights
explicitly set.

Navigating PolicyCenter 43
Guidewire PolicyCenter 10.2.3 Application Guide

Setting Description
Show widget types as inline titles Places a title near each PCF widget that shows its widget type. The titles help you
identify the widgets on a page.
Load application in mock visual launcher Surround the application with a non-functional visual representation of the Guidewire
wrapper Cloud application launcher.

Currency settings

Setting Description
Enable macro characters in currency inputs Enhances the input and display options for currency values. For example, 1.5k is
changed to 1500, and 7m is changed to 7000000.
Include the currency symbol when copying an When selecting and copying the text in a currency element, specifies whether the
amount currency symbol is included.
Show 0 as the currency input placeholder for For currency elements, whether 0 is shown when the value is null. If not set, the
null values element is empty.

Accessibility settings

Setting Description
Force text shadows on When set, dark text is displayed with a white shadow, and light text is displayed with a
black shadow. This setting may assist with readability when there is low contrast
between the text and its background.
Disable outlines on focused elements When not set, the input elements with focus have an extra outline to make them
easier to identify.
Attempt to be smart about what touch inputs When using touch devices, some touches may be intended to interact with the
to ignore. Essentially allowing 'ignore errant application, and other touches may be incidental or accidental. When this setting is
thumb' and 'palm rejection' behavior. set, the application attempts to identify meaningful touches and ignore all others.
Add additional context to visible labels Add additional information to text labels of inputs. For example, the label might
indicate that the field is required or show what the expected date format is.
Use standard menu formatting Renders multi-column menus as standard single-column menus. This is useful for
screen readers and keyboard-only navigation.
Use radio buttons to select List Detail rows Provides an alternate way of interacting with List-Detail tables, where there is a list
view table and a detail view underneath. Instead of clicking on a row in the table to
select it, a new column is added with radio buttons used to select the row. This is
intended for use with some screen readers, which are otherwise unable to select rows.
Allow all tooltips to be displayed and read by When set, any screen element that has a tooltip is included in the sequence of
screen readers on focus. Affects page tab elements that you can navigate to by using the Tab key. When an element is in focus,
sequence. Requires browser restart. its tooltip appears, which is also useful for screen readers. After changing this setting,
you must restart your browser.

See also
• “Managing interface settings” in the Configuration Guide

Change the visual theme

You can choose a new theme for the application, which changes the visual appearance and behavior.

About this task

When you set a theme, the application immediately changes to reflect that theme.

Procedure
1. On the top tab bar, in the Options menu, click Settings.

44 Navigating PolicyCenter
 Guidewire PolicyCenter 10.2.3 Application Guide

2. In the Appearance section, in the Theme drop-down list, click the theme to use.

Data entry support for input fields

As you type in data for some types of input fields, PolicyCenter formats the data appropriately for the field.
See also
• “Using the currency macro in currency fields” on page 45
• “As-you-type formatting support for input fields” on page 46
• “Highlight changed values” on page 46

Using the currency macro in currency fields

PolicyCenter includes a currency macro, which is a user interface feature that converts alphanumeric values entered in
currency fields into numeric values. For example, in the base configuration, the user can enter an alphanumeric like
1.54k, and the currency macro immediately converts it to 1,540.
The characters that you enter depend on your regional format and whether the currency accepts decimal values. The
macro can support up to three decimal values, but the number you can enter might be limited by the currency field.
In the base configuration, this macro supports the following values:
• k for thousand
◦ If the regional format is United States (English), entering 1.54k produces 1,540.
◦ If the regional format is Germany (German), entering 1,54k produces 1.540.
◦ If the regional format is France (French), entering 1,54k produces 1 540.
• m for million
◦ If the regional format is United States (English), entering 1.54m produces 1,540,000.
◦ If the regional format is Germany (German), entering 1,54m produces 1.540.000.
◦ If the regional format is France (French), entering 1,54m produces 1 540 000.
• b for billion
◦ If the regional format is United States (English), entering 1.54b produces 1,540,000,000.
◦ If the regional format is Germany (German), entering 1,54b produces 1.540.000.000.
◦ If the regional format is France (French), entering 1,54b produces 1 540 000 000.
• t for trillion
◦ If the regional format is United States (English), entering 1.54t produces 1,540,000,000,000.
◦ If the regional format is Germany (German), entering 1,54t produces 1.540.000.000.000.
◦ If the regional format is France (French), entering 1,54t produces 1 540 000 000 000.

Enabling and disabling the currency macro

In the base configuration, the currency macro is enabled by default.
To disable the currency macro, log in to PolicyCenter and click the Options menu , and in the Settings dialog under
Currency, clear the check box for Enable macro characters in currency inputs.

To enable the currency macro, select the check box for Enable macro characters in currency inputs.

Navigating PolicyCenter 45
Guidewire PolicyCenter 10.2.3 Application Guide

Configuring the currency macro keys

The macro characters are defined in the following display keys:

Web.Preferences.Currency.macroCharacter.Billion = b
Web.Preferences.Currency.macroCharacter.Million = m
Web.Preferences.Currency.macroCharacter.Thousand = k
Web.Preferences.Currency.macroCharacter.Trillion = t

You can change these keys or localize them. If you do so:

• The new value must be a single character that can be typed with a single stroke on a keyboard.
• The macro produces groups of three for each order of magnitude. For example, if the locale is United States:
◦ One thousand is formatted as 1,000.00.
◦ One million is 1,000,000.00.
◦ One billion is 1,000,000,000.00.
◦ One trillion is 1,000,000,000,000.00.
See also
• Globalization Guide
• Configuration Guide

As-you-type formatting support for input fields

As the user types in data for some types of input fields, the data is formatted appropriately for the field. This user input
support is additional to currency macro support for currency fields.
In general, the formatting support does the following as the user types in the field:
Currency fields
Formats the user entry as currency, with appropriate group and radix characters for the locale.
Date fields
Formats the user entry as a date as set in the application.
Time fields
Formats the user entry as a time as set in the application.
Fields with an input mask
Formats by adding the input mask characters automatically as the user types.
See also
• “Using the currency macro in currency fields” on page 45
• Configuration Guide
• Globalization Guide

Highlight changed values

When you modify a data value, its background color changes so you can easily identify what data has been changed on
the page.

About this task

If you revert the changed data back to its previous value, the highlighting is removed. The data remains highlighted
until you click Update and submit the changes. If you do not want to highlight changed values, you can disable this
behavior.

46 Navigating PolicyCenter
 Guidewire PolicyCenter 10.2.3 Application Guide

Procedure
1. On the top tab bar, in the Options menu, click Settings.
2. In the Appearance section, set or clear Highlight changed values.

Selecting language and regional formats in PolicyCenter

In Guidewire PolicyCenter, each user can set the following:
• The language that PolicyCenter uses to display labels and drop-down menu choices.
• The regional formats that PolicyCenter uses to enter and display dates, times, numbers, monetary amounts, and
names.
You set your personal preferences for display language and for regional formats by using the Options menu at the
top, right-hand side of the PolicyCenter screen. On that menu, click International, and then select one of the following:
• Language
• Regional Formats
To take advantage of international settings in the application, you must configure PolicyCenter with more than one
region or language.
• PolicyCenter hides the Language submenu if only one language is enabled.
• PolicyCenter hides the Regional Formats submenu if only one region is configured.
• PolicyCenter hides the International menu option entirely if a single language is enabled and PolicyCenter is
configured for a single region.
PolicyCenter indicates the current selections for Language and Regional Formats by putting a check mark to the left of
each selected option.

Options for setting the display language

In the base configuration, Guidewire configures PolicyCenter to use a single display language, which is United States
English. To view another language, you must enable at least one additional language and configure PolicyCenter for
that language.
If your installation has more than one configured language, you can select among the available choices using the
PolicyCenter Language submenu. The LanguageType typelist defines the set of language choices that the menu
displays.
If you do not select a display language from the Language submenu and your user administrator has not set your
language, PolicyCenter uses the language specified by your web browser. Configuration parameter
DefaultApplicationLanguage specifies the primary language for PolicyCenter screens, but it does not specify the
default browser language. In the base configuration, Guidewire sets the primary language to U.S. English.

Options for setting regional formats

If your installation contains more than one configured region, you can select a regional format for that locale from the
Regional Formats submenu. At the time you configure a region, you define regional formats for it.

Regional formats specify the visual layout of the following kinds of data:
• Date
• Time
• Number
• Monetary amounts
• Names of people and companies

Navigating PolicyCenter 47
Guidewire PolicyCenter 10.2.3 Application Guide

The LocaleType typelist defines the names of regional formats that users can select on the Regional Formats menu. The
base configuration defines the following locale types:

• Australia (English) • Germany (German)

• Canada (English) • Great Britain (English)
• Canada (French) • Japan (Japanese)
• France (French) • United States (English)

The default regional format for a user is set in the profile of that user on the Administration tab.
Unless you select a regional format from the Regional Formats menu, PolicyCenter uses the regional formats of the
default region. The configuration parameter DefaultApplicationLocale specifies the default region. In the base
configuration, the default region is en_US, United States (English). If you select your preference for region from the
Regional Formats menu, you can later use the default region again only by selecting it from the Regional Formats menu.

My Summary
General use
The screen serves as your "to do" list. It displays your:
• Activities
• Submissions
• Renewals
• Change Requests
It is meant for underwriters, but it appears the same for all users, and serves as a hub for work - you can keep coming
back to it throughout your day.

How to access
It appears when you log onto PolicyCenter, unless you have a different screen configured as your starting location.
You can also access it by clicking Desktop in the top menu.

PolicyCenter tabs
In PolicyCenter, tabs group together logical functions. Tabs can also contain menus with shortcuts to screens on that
tab. To see these menus, click the down arrow next to the tab name and select the link from the drop-down menu.

Desktop tab
The Desktop tab is the electronic desktop that organizes the user’s activities, accounts, and other items. In the left
sidebar and from the Desktop drop-down menu, the Desktop tab has links to screens. These screens have search drop-
down lists that filter activities, accounts, and other items related to the current user.

My Activities screen
The My Activities screen displays activities that have been assigned to you. With activities, you can track tasks
associated with an account, policy, or policy transaction.
You can reassign an activity to another user, skip an activity, or mark an activity as complete. Skipping an activity
indicates that you no longer wish to do the activity. Completing an activity marks it as finished.
On the My Activities screen, users see the following items in the search drop-down list:

48 Navigating PolicyCenter
 Guidewire PolicyCenter 10.2.3 Application Guide

• All open – Display all activities assigned to the current user.

• My activities today – Display all activities for the current user that are due today.
• Due within 7 days – Display all activities for the current user that are due within seven days.
• Overdue only – Display all activities for the current user that are overdue.
• Closed in last 30 days – Display all activities for the current user that were closed in the last 30 days.
See also
• “Activities” on page 417

My Accounts screen
The My Accounts screen displays accounts that you recently created or are working on. Click an account number link to
go directly to the Account Summary screen in the Account tab for that account.
To view this screen, the user must have the View my accounts permission. The code for this permission is
viewmyaccounts. In the default configuration, the Producer and Producer Code - Basics roles have this permission.

Users see the following items in the search drop-down list:

• All pending – Display all pending accounts on which the current user has a role.
• Created in past 7 days – Display all account created in the past seven days on which the current user has a role.
The UserRoleAssignment object, accessed through Account.RoleAssignments array, contains the users with roles on
the account. An account is pending if Account.AccountStatus is Pending. The Account.CreateTime property is
used to determine whether the account was created in the past seven days.
See also
• “Account file” on page 385

My Submissions screen
In a submission, you can gather information for binding and issuing a policy. For certain user types, the My Submissions
screen displays submission or issuance policy transactions that the user created or is working on. For other user types,
the screen displays submissions that the user is associated with through an activity. This is similar to how the Team
screen displays policy transactions depending upon whether the user is a by-role or by-activity user. For more
information, see “Team tab user categories” on page 706.
Use the search drop-down list to filter your search. Filters expected to return the largest number of results are only
available with certain permissions. Permissions limit the search results for users involved in many different
submissions.
The My Submissions screen has the following fields:

Field Description

Primary Insured The name of primary insured on the submission.

Effective Date The PolicyPeriod.EditEffectiveDate from the policy period used to determine the Status. By default,
this field is used to sort the list.

Quote Needed For submission policy transactions, this field displays Submission.DateQuoteNeeded. For issuance policy
transactions, this field is blank.

Transaction # The transaction number.

Type The type of submission.

Status The status of the submission.

Issued This field displays Policy.Issued.

Navigating PolicyCenter 49
Guidewire PolicyCenter 10.2.3 Application Guide

Field Description

Product The product of the submission.

Producer This field is visible if the user does not have the View Producer Desktop Details permission.

Underwriter This field displays the user with the Underwriter role in the Job.RoleAssignments array.

To view this screen, you must have the View my submissions permission. The code for this permission is
viewmysubmissions. Users with the View producer style desktop details permission see additional items in the search
drop-down list. In the base configuration, the Producer and Producer Code - Basics roles have the View producer style
desktop details permission. The code for this permission is viewproducerstyledesktopdetails.

By-role users have the View my submissions and View producer style desktop details permissions. These users see the
following items in the search drop-down list:
• Open with activity for me – Display open submissions and issuance policy transactions for which the current user is
assigned to an open activity.
• Open with activity for me due within 7 days – Display open submissions and issuance policy transactions for which
the current user is assigned to an open activity that is due within 7 days.
• Open bound – Display the current user’s open issuance policy transactions.
• All open – Display all open submissions for the current user.
• Created in past 7 days – Display all submissions that the current user created in the past 7 days.
• Completed in last 30 days – Display all submissions that the current user completed in the last 30 days.
By-activity users have the View my submissions permission but not the View producer style desktop details permission.
these users see the following items in the search drop-down list:
• Open with activity for me
• Open with activity for me due within 7 days
• Open bound
The View producer style desktop details permission affects which columns the user sees. A user who has the permission,
sees columns relevant to the policy’s producer. For example, this user sees the Underwriter column which displays the
submission’s underwriter. This information is relevant to a producer.
A user who does not have this permission, sees columns relevant to a user who is not the policy’s producer, such as the
underwriter. For example, this user sees the Producer column which displays the submission’s producer. This
information is relevant to an underwriter.
A user is related to a submission if one of the following is true:
• If the user has a UserRoleAssignment for the policy transaction.
• If an activity on the policy transaction is assigned to the current user, and the activity has been modified within
SearchActivityThresholdDays before the current date. The Activity.UpdateTime field contains a timestamp of
when the activity was last modified.

Commercial Property submissions

If configured, this screen displays additional information on submission prioritization and risk for Commercial
Property policies. For this additional information to be available:
• Guidewire PolicyCenter must be integrated with Guidewire Predictive Analytics.
• An administrator with the appropriate permissions must enable this functionality in the Administration > Analytics
Manager screens.
See also
• “Submission policy transaction” on page 89 and “Issuance policy transaction” on page 97

50 Navigating PolicyCenter
 Guidewire PolicyCenter 10.2.3 Application Guide

• Configuration Guide

My Renewals screen
The My Renewals screen displays renewals you recently created or are working on.
To view this screen, the user must have the View my renewals permission. The code for this permission is
viewmyrenewals. Users with the View producer style desktop details permission see additional items in the drop-down
list.
The items in the search drop-down list that the user sees are similar to the ones on the My Submissions screen but apply
to renewal policy transactions. This screen does not have the Open bound item. For descriptions of these items, see
“My Submissions screen” on page 49.
See also
“Renewal policy transaction” on page 101

My Other Policy Transactions screen

The My Other Policy Transactions screen displays other policy transactions you created or are working on. This screen
has the following fields:

Field Description

Type The type of the policy transaction.

Primary Insured The name of the primary insured on the policy transaction.

Effective Date The PolicyPeriod.EditEffectiveDate from the query used to determine the Status. By default, this field is
used to sort the list.

Transaction # The transaction number.

Status The status of the policy transaction

Product The product of the policy transaction.

Producer This field is visible if user does not have the View Producer Desktop Details permission.

Underwriter This field displays the user with the Underwriter role in the Job.RoleAssignments array.

To view this screen, the user must have the View my policy changes permission. The code for this permission is
viewmypolicychanges. Users with the View producer style desktop details permission see additional items in the drop-
down list.
The items in the search drop-down list that the user sees are similar to the ones on the My Submissions screen. The filter
applies to policy change, cancellation, reinstatement, renewal, rewrite, rewrite new account, and audit policy
transactions. This screen does not have the Open bound item. For descriptions of these items, see “My Submissions
screen” on page 49.

My Queues screen
The My Queues screen displays activities that have been assigned to groups you belong to, but have not been assigned
to a specific individual.
To view this screen, you must have the View my queues permission. The code for this permission is viewmyqueues.
Click Assign Next to Me to assign the activity to yourself and remove it from the queue. A queue is a repository which
contains activities assigned to a group but not to a particular user in that group.

Navigating PolicyCenter 51
Guidewire PolicyCenter 10.2.3 Application Guide

Configure search drop-down lists

About this task
You can configure the search drop-down lists on the Desktop tab screens. The changes you can make to the
functionality include:
• Adding or removing list items
• Changing the functionality that determines what the list item displays
• Adding or changing user permissions that control list item visibility
The My Activities screen provides a simple example.
Use these steps to view or modify the search filters for the My Activities screen.

Procedure
1. In Studio, open the DesktopActivitiesLV PCF file.
2. Select the activitiesFilter ToolbarFilter PCF element.
3. At the bottom of the screen, click the Filter Options tab.
4. Select gw.api.web.desktop.DesktopActivityFilters.filters().
The filter is defined by gw.api.web.desktop.DesktopActivityFilters.filters().
5. Open DesktopActivityFiltersEnhancement.gsx in the gw.api.filters package.
You can view or modify the code that filters the drop-down list items on the My Activities screen.
See also
• Integration Guide

Account tab
From the Account tab, you can either create a new account or find an established one. If you select the Account tab
directly, PolicyCenter displays accounts that you recently worked on at the bottom of the drop-down menu. Select an
account to display that account information in the Account File. The Account File includes information about the
account itself, its contacts and locations, the policies held by the account, and policy transactions (such as submissions
and renewals) for the account.
You can edit account information, or change the account holder to another person or company. To learn about
managing account information, see “Account file” on page 385.
For information about setting the number of recent accounts that PolicyCenter displays on the Account tab, see “Setting
preferences” on page 42.

Policy tab
Like the Account tab, the Policy tab remembers the last few policies you worked on. Clicking on Policy takes you
directly to the policy file for the last policy you worked on. The policy file includes both the policy contract
information and the policy tools information. The policy contract describes what the policy covers. The policy tools
provide supporting information about the work done on the policy, such as notes, documents, workplan, and risk
analysis.
You can also do the following:
• Create a submission.
• Find a submission or policy.
To learn about the policy file, see “Policies” on page 169.

52 Navigating PolicyCenter
 Guidewire PolicyCenter 10.2.3 Application Guide

For information about setting the number of recent policies and policy transactions that PolicyCenter displays on the
Policy tab, see “Setting preferences” on page 42.

Contact tab
The Contact tab provides a central place to view information associated with a contact such as:
• Details including name, phone, date of birth, addresses, and other information
• Accounts
• Policies
• Work orders
• Claims if PolicyCenter is integrated with claims system
• Billing if PolicyCenter is integrated with a billing system
Using the Contact tab, you can create new contacts, search for existing contacts, or select a recently viewed contact.
You can also create an account for the contact.

Reinsurance tab
The Reinsurance tab is accessible if you have Guidewire Reinsurance Management enabled. Reinsurance Management
is available within PolicyCenter. However, Reinsurance Management is licensed separately from PolicyCenter.
Use the Reinsurance tab to view and define reinsurance agreements and programs.
See also
• “Reinsurance Management” on page 593

Search tab
Use the Search tab to find:
• Policies
• Accounts
• Producer Codes
• Activities
• Contacts
PolicyCenter includes two types of searches: basic and advanced.

Navigating PolicyCenter 53
Guidewire PolicyCenter 10.2.3 Application Guide

PolicyCenter Search Architecture

Relational database

Advanced search
(database search)

PolicyCenter application

Policy updates

Real-time index Batch-load index

documents documents
Policy Search

Basic search
(free-text search)

Full-text database

Basic search is a free-text search for quick access against very large databases. Free-text search also provides exact and
inexact matching. Inexact matching returns results that partially match, are synonyms, and sound-like the search
criteria. In PolicyCenter, free-text search uses an integration with the full-text search engine Solr. PolicyCenter includes
basic search for policies.
Advanced search uses database search, which directly searches the PolicyCenter database. PolicyCenter includes
advanced search for policies, accounts, producer codes, activities, and contacts. For large data sets, advanced search
can take longer than basic search.
See also
• “Basic search” on page 65
• “Advanced search” on page 73

Team tab
In the PolicyCenter Team tab, supervisors and managers can manage their teams, obtain instant status information,
monitor case loads, identify backlogs, and reassign activities. In some respects, this tab serves as a reporting tool. For
example, a supervisor can see real time summaries of activities based on groups, then navigate to view and manage a
subordinate’s workload.
The Team tab has no drop-down menu choices.
To learn about team management, see “Team management” on page 705.

Administration tab
Certain users with assigned roles, such as producers, can use the Administration tab. This tab contains menu items to
search for users, organizations, or producer codes. These users can search for information about the insurer and see the
insurer’s organization. The permissions on the role determine which fields are available. For example, an administrator
or supervisor can complete system management tasks such as creating users and groups, modifying user permissions,
and importing information.
To learn more about system administration tasks, see “PolicyCenter administration” on page 677.

54 Navigating PolicyCenter
chapter 6

Changing the screen layout

You can adjust several aspects of the screen layout according to your own preferences.

Adjusting list views

You can change the default appearance and behavior of individual list views, including the column order, sort order,
and which columns are visible. Changes to list views are stored as user settings, and remain in effect until you change
or reset them.

Change list view column order

About this task
You can change the order in which columns appear in a particular list view.

Procedure
1. Click and hold the left mouse button on the heading of the column that you want to move.
2. Drag the mouse pointer across the other column headings until it is between the two columns where you want to
place the moved column.
If it is valid to move the column there, the column turns from gray to highlighted.

3. Release the mouse button.

Change list view column widths

About this task
You can resize a list view column to make it wider or narrower than it currently is. This change remains in effect until
you reset customized columns.

Changing the screen layout 55

Guidewire PolicyCenter 10.2.3 Application Guide

Procedure
1. Position the mouse pointer over the left or right border of the column heading. The pointer turns into a double
arrowhead .
2. Drag the column border to the new width.

Sort list views

About this task
You can change the column on which a list view is sorted, and also the sorting direction. You can sort on only one
column at a time.

Procedure
Click the heading of a column to sort the list view on that column.
• To sort a list view on a particular column, click the column heading.
• To change the sort direction of a list view column, click the up or down arrow on the heading of the column on
which the list is currently sorted:

Results
The up or down arrow is highlighted, indicating the direction in which the list is sorted.

Hide and show columns in a list view

About this task
You can change which columns appear in a list view.

Procedure

1. At the right edge of the list view toolbar or title row, click Columns .
2. In the drop-down list, click the columns that you want to change:
• To hide a column, clear the check box for the column.
• To show a column, set the check box for the column.

Arrange list view rows into groups

When multiple rows in a list view have the same value for a particular column, you can arrange them to be listed
together in a group.

About this task

Each group appears in the list view under a new heading row for the common value. For example, if you have a list of
activities, you can group them by their values in the Due Date column. The related activities are then listed together
under a heading for each due date.
The following example shows rows grouped by Due Date.

56 Changing the screen layout

 Guidewire PolicyCenter 10.2.3 Application Guide

To collapse or expand a group, click the up arrow or down arrow next to the group name.
You can group a list view only by one column at a time.

Procedure

1. At the right edge of the list view toolbar or title row, click Columns .

2. In the drop-down list of columns, click Group/Ungroup next to the column on which to base the group.

If the list view is already grouped by that column, then clicking Group/Ungroup disables the grouping.

Reset list view columns

Restore the appearance and behavior of list views to the default settings.

About this task

If you have changed any list view columns, those changes will be reset. Resetting list view columns applies to all list
views in the application.

Procedure

1. At the right edge of the list view toolbar or title row, click Columns .
2. In the drop-down list, click Reset Customized Columns.

Disable list view customization

Set the disableUserCustomization property to prevent users from making changes to the appearance and behavior of
a particular list view.

About this task

When customization is disabled, users will not be able to make changes to the list view, including changing the column
order, sort order, and which columns are visible. You must disable customization on each relevant list view. There is no
global setting to disable list view customization for the entire application.
You can disable customization on a ListViewInput or a ListViewPanel widget. In most situations, list view
customization is enabled by default. However, in some configurations such as a ListViewInput defined inside of an
InputColumn, customization may be disabled by default. If desired, you can then edit the list view and change the
property setting.

Changing the screen layout 57

Guidewire PolicyCenter 10.2.3 Application Guide

Procedure
1. In Guidewire Studio, open the PCF file containing the list view.
2. Click the list view widget.
3. In the Properties tool window, set the disableUserCustomization property to true.

Change the sidebar width

About this task
You can resize the sidebar to made it wider or narrower than it currently is. This change remains in effect until you log
out.

Procedure

1. Position the mouse pointer over the right border of the sidebar. The pointer turns into a double arrowhead .
2. Drag the sidebar border to the new width.

58 Changing the screen layout

chapter 7

QuickJump

QuickJump overview
QuickJump is a feature in the PolicyCenter user interface that can be used to perform navigation to a screen using the
keyboard only. It is intended primarily for users who prefer to navigate without using a mouse.
The QuickJump box provides a fast way to navigate to a particular screen in the application.
Some of the PolicyCenter screens are:
• Desktop tab
• Search tab
• Team tab
• Admin tab
The QuickJump box can also retrieve and show information about a particular entity. In the base configuration, entities
that PolicyCenter provides are Policy and Account. You can add additional entities.

Using QuickJump
The QuickJump box, as shown in the following, appears at the upper right corner of most PolicyCenter screens. The
box is not available in pop-ups.

To use the box, position the cursor in it or use the shortcut key Alt /, and then enter a QuickJump command. To view
a list of available commands, press the Down Arrow key.
For example, to retrieve an account, type account and the account number, as in Account C000143542, to jump to the
Account File Summary screen. If you want to see a policy, type policy and the policy number, as in Policy
25-123436, to jump to the Policy File Summary screen.

The QuickJump box provides automatic command and parameter completion. Type the first few letters of a command,
and the QuickJump box automatically provides a list of the possible commands. For example, type the letter A to list all
commands or parameters that begin with the letter A.

QuickJump 59
Guidewire PolicyCenter 10.2.3 Application Guide

Chaining QuickJump destinations together

It is possible to chain multiple QuickJump destinations together to jump to a specific screen.
For example, while viewing an account on the Account tab, suppose you want to retrieve information on a policy
transaction. You can type Account C000212105, press the Spacebar, and then type the letter A. The screen displays
a list of commands beginning with the letter A that are relevant to the account. Selecting Account C000021215
AccountWorkOrders takes you to that screen.

QuickJump behavior in wizards

Wizards are typically used to advance sequentially through a series of steps. QuickJump can be used to skip steps and
jump to a screen listed in the Sidebar.
QuickJump actions available in a wizard are active only when operating in the wizard. For example, it is not possible to
jump from an account screen to a specific wizard screen.
When operating in a wizard, if you want to jump to another part of PolicyCenter, save your work before jumping. After
the jump, if you did not save your work, your wizard work will be lost.

Configuring QuickJump
The QuickJump box can be configured in various ways.
• You can add new commands that jump to newly-created screens.
• You can change existing QuickJump commands. For example, you can provide commands that users were
accustomed to using on another system.
• You can remove the QuickJump box from the user interface.
You can use the XML Editor in Studio to configure the QuickJump box. In the Project window, navigate to
configuration > config > Page Configuration and open quickjump-config.xml to edit QuickJump resources. Labels for a
particular language are defined in the display_languageCode.properties file.
See also
• Configuration Guide
• Globalization Guide

QuickJump reference
The tables in the topics that follow list the QuickJump commands that PolicyCenter provides. Some commands can be
chained—appended with other information, such as another entity name or a policy number.

Static items

Screen Command

Account > Account Summary Account account number

Account > New Submissions NewSubmission

Administration tab Admin

Administration > Business Settings > Activity Patterns ActivitySearch

Administration > Users & Security > Organizations OrganizationSearch

Search > Producer Codes ProducerCodeSearch

Administration > Users & Security > Producer Codes AdminProducerCodeSearch

60 QuickJump
 Guidewire PolicyCenter 10.2.3 Application Guide

Screen Command

Administration > Users & Security > Users UserSearch

Desktop tab Desktop

Desktop > My Activities MyActivities

Desktop > My Other Policy Transactions MyOtherTransactions

Desktop > My Queues MyQueues

Desktop > My Renewals MyRenewals

Desktop > My Submissions MySubmissions

Policy > Summary Policy policy_number

Search > Search Accounts AccountSearch

Search > Search Policies PolicySearch

Search > Search Producer Codes ProducerCodeSearch

Super user items

Screen Command

Administration > Business Settings > Activity Patterns Activity Patterns

Administration > Business Settings > Policy Form Patterns PolicyForms

Administration > Monitoring > Event Messages Event Messages

Administration > Monitoring > Workflows Workflows

Administration > Users & Security > Attributes Attributes

Administration > Users & Security > Regions Regions

RegionSearch

Administration > Users & Security > Roles Roles

Administration > Utilities > Script Parameters ScriptParameters

Team tab Team

Team > Activities TeamActivities

Team > Other Policy Transactions TeamPolicyChanges

Team > Renewals TeamRenewals

Team > Submissions TeamSubmissions

Team > Summary TeamSummary

Server Tools > Batch Process Info RunBatchProcess process_name

Account file items

The following items are accessible in the QuickJump box from within an account file, policy file, or policy transactions
that contain an account object. They can also be chained to the end of the Account command.

Screen Command

Account Roles AccountRoles

QuickJump 61
Guidewire PolicyCenter 10.2.3 Application Guide

Screen Command

Billing AccountBilling

Claims AccountClaims

Account File Contacts AccountContacts

Account File Documents AccountDocuments

Account File Locations AccountLocations

New Document – Create a new document from a template AccountNewDocumentCreate

New Document – Link to an existing document on this account AccountNewDocumentsLinkToExisting

New Note AccountNewNotes

Account File Notes AccountNotes

Account File Contacts > Role AccountRoles

Submission Manager AccountSubmissionManager

Account File Summary AccountSummary

Underwriting File AccountUnderwritingFiles

Account File Policy Transactions AccountTransactions

Example:

Account account_number AccountRoles

Policy file items

The following items are accessible with the QuickJump box only from within a policy file. They can also be chained to
the end of the Policy command.

Screen Command

Audit Schedule PolicyAudit

Billing PolicyBilling

Cancel Policy CancelPolicy

Change Policy ChangePolicy

Contacts PolicyContacts

Documents PolicyDocuments

History PolicyHistory

Locations PolicyLocations

New Document – Create a new document from a template PolicyNewDocumentCreateNew

New Document – Link an existing document to this policy PolicyNewDocumentsLinkToExisting

New Note PolicyNewNote

Notes PolicyNotes

Participants PolicyParticipants

Payment PolicyPayment

62 QuickJump
 Guidewire PolicyCenter 10.2.3 Application Guide

Screen Command

Policy Info PolicyInfo

Pre-Renewal Direction PolicyPreRenewalDirection

Quote PolicyQuote

Referral Reason PolicyReferralReason

Risk Analysis PolicyRiskAnalysis

Summary PolicySummary

Policy Transactions PolicyTransactions

Example:

Account account_number AccountRoles

QuickJump 63
Guidewire PolicyCenter 10.2.3 Application Guide

64 QuickJump
chapter 8

Basic search

PolicyCenter provides basic search which is a free-text search for quick access against very large databases. Free-text
search also provides exact and inexact matching. Inexact matching returns results that partially match, are synonyms,
and sound-like the search criteria.
Note: In addition to basic search, PolicyCenter also includes advanced search. Advanced search uses database
search, which directly searches the PolicyCenter database. PolicyCenter provides advanced search for policies,
policy transactions, accounts, producer codes, activities, and contacts. For more information, see “Advanced
search” on page 73.

Basic search overview

In PolicyCenter, basic search uses free-text search which provides faster search than database search against very large
databases. The search is faster because it searches through text-based representations of selected data. You can choose
to enable or disable basic search. Basic search is disabled in the default configuration.
PolicyCenter includes basic search for policies and submissions. You can configure basic search for policies and
submissions.
The Search Policies > Basic screen has fields to enter data by name, address, and other criteria. For each field, there is a
corresponding search index to optimize retrieval of that data. One search field may map to more than one object or
property in the database. For example, entering a value in the Name field compares the search string against an index
field that consists of concatenated First Name and Last Name or Company Name.
Note: When entering a phone number as a free-text search criterion, enter a phone number appropriate for your
default phone region and do not use an extension. If free text search finds a match, it returns the phone number
formatted according to your default phone region.
In PolicyCenter, free-text search uses an integration with the full-text search engine Solr. Free-text search is disabled
by default. For more information on enabling and configuring free-text search, see the Configuration Guide.

Indexing free-text search data

The free-text search process consists of three steps:
1. Initial population of the search index database using a batch process.
2. Continuous index updates in production using messaging.
3. Executing a search query to Solr server.
As users make and save changes, PolicyCenter updates the indexes dynamically.
Basic search 65
Guidewire PolicyCenter 10.2.3 Application Guide

Query and filter basic search fields

On the search screen, the fields for entering search criteria are of two types:
• Query fields – PolicyCenter sends the query fields to the search engine.
• Filter fields – Narrow down the results returned by the query.
Basic search requires that you enter at least one query field. PolicyCenter displays a message if you do not specify at
least one query field.

Exact or inexact basic search and ranking

Search fields are configured to match exactly or inexactly. An exact match of a field returns a result that matches the
search string exactly. An inexact match of a field returns a result that starts with, contains, is a synonym of, or sounds
like the search string.
For example, exact and inexact matching returns the following names if you search for Mary:
• Mary – Exact.
• Marybeth – Starts with.
• Rosemary – Contains.
• Molly – Synonym. A synonym is a word that has the same meaning. For names, you can think of a synonym as a
nickname.
• Marie – Sounds like.
PolicyCenter ranks the search results with a score that reflects the degree to which the result matches the search
criteria.
A configuration file defines for each search field how to rank exact matches and the various types of inexact matches.
For more information, see the Configuration Guide.

Search type selection shortcuts

Search type selection shortcuts allow the user to enter a one-character or two-character string that directs the free-text
search function to return only matches of a particular type. Search types with a corresponding shortcut string include
exact match, prefix match, synonym match, and phonetic match. Adding the corresponding shortcut string to the end of
a free-text search field entry activates the corresponding search type in the search algorithm.
The next example will contrast the results that the user obtains when not using a search type selection shortcut versus
when using one. The user not inputting a search type selection shortcut enters a name such as "john" in the name field.
The user then searches on the specified name. The results of this search can include matches of all types.
The search type selection shortcut feature allows the user to add a short string such as "-n" directly to the end of the
search string, "john". The search string as modified is "john-n". Adding the shortcut restricts the results of the search.
The results only contain matches of the type corresponding to the shortcut. In this case, the results would include only
synonyms for "john". They would not include matches of any other type.
The following is a list of the search type selection shortcuts that Guidewire supports:
• -e : exact match only
• * : prefix match only
• -n : synonym (nickname) match only
• -p : phonetic match only

Basic search results for fields with multiple matches

A search field may return matches from two or more pieces of information on the search object. The search ranks the
matching information.

66 Basic search
 Guidewire PolicyCenter 10.2.3 Application Guide

When searching for policies for example, a name search attempts to match the names of the primary named insured and
additional named insureds on the policy. However, the results display only the Name of the Primary Named Insured.
Assume you have a policy that insures Ray Newton as the primary named insured. Christina Newton and Maggie
Newton are additional named insureds. You search for Maggie Newton. The search finds Maggie on the Ray Newton
policy and displays the Ray Newton’s name on the policy.

Although you searched for Maggie Newton, the Name field in the results displays Ray Newton. A symbol appears
after Ray Newton. Hover over the symbol to view Maggie Newton as an additional named insured.

Basic policy search overview

In the default configuration, PolicyCenter contains basic search for policies. Basic search for policies has the following
features:
• The Name search field matches a concatenated first and last name or company name.
• The Name search field matches the primary named insured or additional named insured on the policy. In personal
auto line of business, the search also matches the secondary named insured.
• The Phone search field matches a home, mobile, fax or work phone number on the policy.
• The Address fields match against the current and former addresses on the policy. If there are multiple addresses, the
Address field in the search results only displays the matching address.
• Basic search returns bound policies and unbound policy transactions.
Note: PolicyCenter includes advanced search for additional object types. For more information, see “Advanced
search” on page 73.

Basic search user interface

This topic describes the basic search user interface.

Policy basic search screen

Basic search provides search for policies.

Access policy basic search

Procedure
1. Navigate to Search > Policies and view the Basic tab.
2. Enter search criteria in the top of this screen, and PolicyCenter displays results at the bottom.

Basic search criteria for policies

On the Basic tab of the Search Policies screen, the following search fields appear at the top of the screen.

Field Description Matching Type

Policy Number Search for a policy number. This field requires an exact match or a match that contains the Inexact Query
search string. A result that starts with the search string has better search score than a string
that only contains the search string.

Name Search for first and last name of a person or company name. Searches for matches in primary Inexact Query
named insured and additional named insureds. For details, see “Basic name search” on
page 69.

Basic search 67
Guidewire PolicyCenter 10.2.3 Application Guide

Field Description Matching Type

Phone Search for a matching work, home, mobile, or fax phone number. You must enter the whole Exact Query
phone number. Valid telephone number formats are:
• 650-555-1234
• 650 555 1234
• 6505551234
• (650)555-1234
• (650) 555-1234
• 650.555.1234

Official ID Search for a Social Security number (SSN) or employer identification number (EIN) number. Exact Query

Address

Street Search for the street address. The search ranks the results from highest to lowest as follows: Inexact Query
• Exact
• Starts with
• Sounds like
• Contains

City Search for the city. The search ranks the results from highest to lowest as follows: Inexact Query
• Exact
• Starts with
• Sounds like
• Contains

State Search for the state. Exact Filter

Postal Code Search for the postal code. Exact Filter

Filters

Product Search for the product of the policy or policy transaction. Exact Filter

Jurisdiction Search for the jurisdiction of the policy or policy transaction. Exact Filter

Producer of Record Search for policies or policy transactions owned by a particular producer of record. Exact Filter

Producer Code Search for the producer code of service for the policy or policy transaction. Exact Filter

In Force On Search for policies or policy transactions in force on this date. Exact Filter

The Matching column indicates whether the field matches exactly or inexactly. For more information, see “Exact or
inexact basic search and ranking” on page 66.
The Filter column indicates whether the field is a query or filter field. You must specify at least one query field such as
Policy Number or Name. For more information, see “Query and filter basic search fields” on page 66.

Basic search results for policies

On the Basic tab of the Search Policies screen, the following Search Results fields appear at the bottom of the screen.

Field Description

Result type Displays an icon representing the result type. The result types are:

68 Basic search
 Guidewire PolicyCenter 10.2.3 Application Guide

Field Description

• – The policy icon represents a bound policy.

• – The policy transaction icon represents a policy transaction, such as a submission or policy change.

Rank The rank indicates the relevance of the result to the search criteria. The lowest rank corresponds to the most
relevant match.

Policy # The policy number. If the result is not a bound policy period and does not have a policy number, Unassigned
appears in this column.

Name The first and last name of the person or the company name returned by the search results. This field displays the
primary named insured on the policy. A symbol appears after the name if there are additional named insureds
on the policy. Hover over the symbol to view the names of the additional named insureds.

Address The policy address of the policy.

Product The product of the policy or policy transaction.

Status The status of the policy or policy transaction.

Effective Date The effective date for the policy term.

Expiration Date The expiration date for the policy term.

Producer The Organization and Producer Code as it appears in the Producer of Service on the Policy Info screen.

Basic name search

The Name field finds matches in the primary named insured and additional names insureds on a policy. A match on
primary named insured has a better ranking than additional named insureds. This is an inexact search field.
Starting with the best match, basic search ranks the matching names as follows:
1. Exact
2. Starts with
3. Synonym
4. Sounds-like
5. Contains
If you enter more than one word in the name field, the search gives a better rank to results containing both words. A
match has a better ranking if the words exist in the same order. If only part of the words match, the match has an
inferior ranking.
A multiple word search that fully matches the additional named insured has a better rank than a match that only
partially matches the primary named insured. For example, you search for Ray Newton. Policy 1 has Ray Newton as
an additional named insured, and policy 2 has Ray Brussard as a primary named insured. Policy 1 has a better ranking
than policy 2.
You can search for historical names, such as maiden names, on a policy over time. For more information, see “Basic
search with in force on” on page 70.

Basic address search

The address search finds current and historical addresses. Search returns a matching address in the primary address of a
primary named insured or additional named insured. Search returns a result if an address matches the Street and/or City
fields. These fields are query fields. Basic search filters the query results by State and Postal Code fields. These fields
are filter fields.

Basic search 69
Guidewire PolicyCenter 10.2.3 Application Guide

Basic search with in force on

The In Force On filter field returns only those policies that are in force on that date.
For example, Robert Brown took out policy on January 1 two years ago. He renews the policy every year but makes no
other changes. To view the policy in force on October 1 of this year, set the In Force On field to this date. The search
returns the policy period in force on this date.
The In Force On search has special behavior for the Name field. Suppose you enter an In Force On date and specify the
Name field. The search returns only policies that were in force on that date and have that name at some point on the
policy. For example, Jane Doe has a policy in force from January 1 of this year through January 1 of the following year.
Jane married and changed her name to Jane Smith on July 1. You search for either Jane Doe or Jane Smith with an
in force date of August 1 of this year. The search returns Jane’s policy that is in force on August 1 of this year. If you
search for Jane Smith with an in force date of August 1 of the previous year, then the search returns no matches.

Working with basic search

This topic provides step-by-step instructions for working with basic search.

Prerequisites
These examples assume that you have loaded the Free-text Search sample data set. For more information about loading
sample data, see the Installation Guide.

Producer code access controls basic search results

Basic search results returns policies for which the user has producer code access. If producer code security is enabled,
the producer of service on the policy must match one of the user’s producer codes. For more information, see
“Producer code security and policies” on page 683 and “Turn on producer code security” on page 691.

Use basic policy search

About this task
This topic provides step-by-step instructions for doing some simple policy searches.

Procedure
1. Select Search > Policies to navigate to the Search Policies > Basic tab.
2. In Name, enter ray, then click Search.
The Search Results displays policies which contain a primary or additional named insured with ray in the first
name or last name. For example, the results contain rows for Ray Newton and Ann-Marie Ray.

In the Name field, a number of entries have a symbol at the end.

3. Hover over the symbol next to Ann-Marie Ray.
PolicyCenter displays Ray’s Rockhouse as an additional named insureds on the policy.
4. In Name, enter rock, then click Search.
PolicyCenter displays Ann-Marie’s policy in the results because the search string matches Ray’s Rockhouse, an
additional named insured on the policy.
5. Click the Policy # link to jump to the policy.
If the search result is a bound policy, then PolicyCenter opens the policy file.
If the result is an unbound policy period, then PolicyCenter opens the policy transaction (job) wizard for that
policy period.

70 Basic search
 Guidewire PolicyCenter 10.2.3 Application Guide

In the result type column, the policy transaction icon appears for unbound policy periods such a submission or
other policy transaction. The policy icon appears for bound policy periods.
6. Click Policy Info in the left sidebar.
Notice that Additional Named Insureds includes Ray’s Rockhouse.

Basic search index updates automatically

About this task
In PolicyCenter, if you commit a change that is part of the search index, that change is updated automatically in the
search index database.
These instructions continue “Use basic policy search” on page 70.

Procedure
1. Go to the Ann-Marie Ray policy.
2. Select Actions > Change Policy.
3. Advance to the Policy Info screen.
4. On the Policy Info screen, change the primary named insured to John Smith.
5. Click Quote or Save Draft.
6. Copy the policy number, then return to the Search Policies > Basic screen.
7. Enter the Policy Number and click Search.
The search results display the John Smith policy as a policy transaction and the Ann-Marie Ray policy as a bound
policy.
You may have to wait a short time for the index update to occur.

Basic search 71
Guidewire PolicyCenter 10.2.3 Application Guide

72 Basic search
chapter 9

Advanced search

PolicyCenter includes advanced search to find matching policies, policy transactions, accounts, producer codes,
activities, and contacts. The advanced search uses a database search of the PolicyCenter database. This topic describes
advanced search in PolicyCenter.
Note: In addition to advanced search, PolicyCenter also includes basic search that uses free-text search. Free-
text search improves performance for large data sets and includes inexact matching. PolicyCenter provides
basic search for policies. For more information, see “Basic search” on page 65.

Advanced search overview

You can access the advanced search from the Search tab. For policies, you access advanced search on the Advanced
screen in the Search > Policies.
Note: The Search Policies > Basic screen uses free-text search not database search. For more information, see
“Basic search” on page 65.
Some fields on the advanced search screens are text fields. If you enter text into one of these fields, PolicyCenter
searches for a match that starts with that text. For example, if you enter Jones into the last name field, the search
returns all last names that start with Jones. The search results include: Jones, Jonesburg, or Jones-Smith. It does not
find McJones.
You must enter an exact match in the Account Number and Policy Number fields.
During a search, PolicyCenter uses only those fields in the form in which data exists. For example, if you search for a
Policy and enter a Last Name but not a Policy Number, PolicyCenter omits Policy Number from the search.

The search results returns accounts, policies, or policy transactions with links to view details. Accounts, policies, or
policy transactions for which you do not have sufficient producer code permissions do not appear in the search results.
See also
• “Data-based security for accounts and policies” on page 682
• Configuration Guide

Minimum search requirements for advanced search

This topic describes the minimal requirements for advanced search on the following search screens:
• Search Policies > Advanced

Advanced search 73
Guidewire PolicyCenter 10.2.3 Application Guide

• Search Accounts
• Search Contacts
You can search on the following fields without specifying additional search information:
• Official ID
• Account Number
• Policy Number
• Phone

Personal names
Both the first and last name fields have a check box to indicate whether the name must be an exact match.
The name of the person requires the following:
• Both first and last name.
• For the first or last name, the name must be an exact match. If exact match is not selected, you must provide the
first three letters of the name.
• If the last name is not an exact match, you must provide either city and state or postal code.

Company names
There is now a check box to specify whether the company name is an exact match.
The name of the company requires the following:
• The name must be an exact match, or you must provide the first five letters of the name.

Producer code
You can enter a producer code without specifying additional search information.

Phone number
On the search screen, the Phone field matches the contact’s Work Phone. Searches on phone number require an exact
match. The extension for a phone number is stored in the same field as the phone number itself. If a phone number has
an extension, a search omitting the extension is not a match.
The phone number matches the contact’s work phone number.

Advanced search for policies

The Search Policies > Advanced screen allows you to search for policies and policy transactions. By using the Search
For drop-down menu, you can search for the following policy transaction types:

• Cancellation
• Final Audit
• Policy Change
• Premium Report
• Reinstatement
• Renewal
• Rewrite
• Submission
When you choose Final Audit or Premium Report, options appear that allow you to search by date. You can search by
Audit period end date or Audit due date and specify a date range. This search finds already started audit policy

74 Advanced search
 Guidewire PolicyCenter 10.2.3 Application Guide

transactions. The search does not find audit policy transactions with a status of Scheduled. Managers can use this
search to find all final audits due between a set of dates. Then the manager can assign the audits.
In the Search Policies > Advanced screen, you can assign a user to one or more policies or open policy transactions. For
the selected policies or policy transactions, you can choose a user for an assignment role such as auditor, producer, or
underwriter. The selected user replaces the user who previously held that assignment role. If a user is a member of
more than one group, you must also assign the group.When you assign the user, the group is also assigned. You cannot
assign a user to completed or bound policy transaction.
See also
• “Working with the Advanced Search tab” on page 75
• “Assign submissions, renewals, and other policy transactions” on page 707 for a similar feature on the Team tab.

Search contacts
The Search > Contacts menu item displays the same screen as the Contact > Search menu item. For more information,
see “Search for a contact” on page 436.
Click the contact Name to display the Contact File Details screen. For more information about the Contact File Details
screen, see “Contact tab” on page 53.

Working with the Advanced Search tab

The following topic describes how to work with the Advanced Search tab in PolicyCenter.

Assign a user to one or more policies or open policy transactions

About this task
In the Search Policies > Advanced screen, you can assign a user to one or more policies or open policy transactions. For
the selected policies or policy transactions, you can choose a user for an assignment role such as auditor, producer, or
underwriter. The selected user replaces the user who previously held that assignment role. If a user is a member of
more than one group, you must also assign the group. When you assign the user, the group is also assigned. You cannot
assign a user to completed or bound policy transaction.

Procedure
1. Select Search > Policies and click the Advanced tab.
2. Make a selection from the Search For drop-down list. For example, you can select Policy or a policy transaction
such as Submission.
3. Enter search criteria and click Search. You must meet the minimal search criteria as described in “Minimum
search requirements for advanced search” on page 73.
If you have loaded the small sample data set, the following searches return results:
• Enter the Producer Code as 100-002541.
• Enter First Name as Ray and Last Name as Newton.
4. Select one or more policies or policy transactions and select an assignment role from the Assign drop-down list.
You cannot assign a user to completed or bound policy transactions. Therefore, the Assign button is disabled if the
selection includes one of these policy transactions.
PolicyCenter displays the Assign transactions screen. For each policy or policy transaction, this screen displays
the type, policy transaction or policy number, and assignment role.
5. Enter a User Name, First Name, or Last Name and click Search.
PolicyCenter displays matching users. For each user, PolicyCenter displays the Group and Parent Group. A user
appears multiple times if the user belongs to more than one group. For example, you can search for users with last

Advanced search 75
Guidewire PolicyCenter 10.2.3 Application Guide

name Applegate. The search returns two rows for Alice Applegate because Alice is a member of the Easter
Region Underwriting and Los Angeles Branch UW groups.
6. In the search results, click Assign to assign a user for the chosen role. If a user is a member of more than one
group, select the user’s row that displays the group of your choice.
See also
• “Assign submissions, renewals, and other policy transactions” on page 707 for a similar feature on the Team tab.

Search quotes user interface

The Search > Quotes screen enables you to search for quotes in the quote store and unbound submissions on the current
system created from quotes in the quote store. To exclude the current system from search results, select Only search
Quote Store.

Search requires that you specify at least one of the following:

• Quote ID
• First Name and Last Name
• Work Phone
• Email Address
• Company Name
See also
• Configuration Guide

Submission number
In Search Results, quotes from the quote store have a Convert to Submission link in the Submission Number column.
When you click Convert to Submission, you must link the submission to an account on the Account for Submission
screen. This screen is populated with account holder contact information from the quote. Use this information to search
for an existing account or to create a new account. You can link to any existing account, even if it does not appear in
the search results.
After attaching the account, the quote is copied to the current system as a submission with quoted status.

Quote ID
Quote-only instances generate the quote ID. In the base configuration, the Quote ID appears only in the Search Quotes
screen. When you convert to submission, the quote ID is saved on the policy period
(PolicyPeriod.QuoteIdentifier).

76 Advanced search
chapter 10

Saving your work

PolicyCenter automatically saves your work to the database in wizards and through the Unsaved Work list in the user
interface.

Unsaved work list

You can access your unsaved work from the Unsaved Work list in the Tab Bar. PolicyCenter automatically saves
your work whether you are in the Account or Administration tabs or in a wizard such as a submission or policy change.
If you leave one of those screens with unsaved changes, and navigate to another section of PolicyCenter, the server
keeps your information in memory. The database does not store your information. You are able to retrieve your work
from the Unsaved Work list, as seen in the following example. Selecting it returns you to that screen with your unsaved
data. You can finish your work and save it by clicking Update.
The Unsaved Work list is useful if you must navigate away from a screen but need to return to it later. After you
complete and save your work, PolicyCenter removes that item from the Unsaved Work list. However, if you attempt to
log out without saving, PolicyCenter alerts you that your unsaved work will be lost if you continue.
Autosaving is the mechanism PolicyCenter uses to save work that can be retrieved by using the Unsaved Work list.
Both autosaveable and countsAsWork default to true in the default application, which you can see in the PCF Editor
in Studio.
Unsaved work is also lost when the application session expires. The session expiration time is set by the
SessionTimeoutSecs configuration parameter.

Saving your work in PolicyCenter wizards

When you work in any policy transaction (job) wizard, PolicyCenter saves your information to the database. It saves
every time you advance or go back in the wizard (by clicking wizard buttons such as Back, Next, Quote, or Bind). It
also saves when you navigate to a different step by using the sidebar menu choices. However, there are times when you
are in a PolicyCenter wizard, where you may need to enter additional information that is technically not in a wizard
step. Popup windows are an example of this.

Popup window behavior

In PolicyCenter, a popup is a page that appears on top of another page. It is part of the wizard process, but it is not a
wizard step.
When you make changes or add information in a popup, PolicyCenter does not commit those changes immediately to
the database, but saves the changes to the enclosing parent page. The Unsaved Work list captures the changes to the
Saving your work 77
Guidewire PolicyCenter 10.2.3 Application Guide

parent page and the popup so that you can finish your work if you navigate away without saving the parent page. For
example, suppose you modify a location in a workers’ compensation submission and click OK. Then you navigate to
the Desktop, or log out without first clicking Save Draft. In this case, the new location data is not saved to the database,
but will be stored in the Unsaved Work list.

78 Saving your work

chapter 11

Accessibility in Guidewire
InsuranceSuite

Guidewire InsuranceSuite provides accessibility features to ensure that all users have a successful and productive user
experience. Guidewire is guided by the WCAG 2.0 AA standard for accessibility.

Screen reader support

The InsuranceSuite user interface is designed with standard HTML elements. The HTML includes attributes defined by
ARIA (Accessible Rich Internet Applications) to provide additional meaning for screen readers and other assistive
devices. Guidewire tests accessibility using a variety of screen readers, including JAWS, NVDA, and VoiceOver.

Inputs and labels

Inputs and labels on application pages are associated by a parent-child relationship. An input widget is labeled with the
value of its child widget using an aria-labelledby attribute. Automated accessibility checks flag this relationship as
an issue. However, manual accessibility assessments demonstrate that this relationship is properly voiced by screen
readers.

Alternative text on icons

The alternative text values for icons are specified by the aria-label attribute. The default value is the name of the
icon. For example:
• A green circle with a check mark indicating 'complete' includes the ARIA attribute aria-label="circle-
checkmark".
• A red circle with an 'X' indicating 'not complete' includes the ARIA attribute aria-label="circle-x".
To change the aria-label value, edit the associated PCF file and set the *AltText property.

Page titles
When you navigate to a new page in a web application, a screen reader reads the contents of the HTML <title> tag.
The title of the browser window describes the content of the page, distinguishes it from other pages, and provides
contextual information. In InsuranceSuite, the browser window title automatically includes the main heading text of the
page. If desired, you can override the title by setting the browserTitle attribute of the PCF page.

Accessibility in Guidewire InsuranceSuite 79

Guidewire PolicyCenter 10.2.3 Application Guide

Error, warning, and information messages

If a form submission generates errors or warnings, they are displayed within a notification widget. The notification
widget is located after the main page heading, and it is titled with a heading level 2 element. Notifications of this type
are communicated to screen readers by using aria-live.
For example:
• This page contains error, warning, and informational messages. Errors: (3).
Warnings: (2). Infos: (1).
• This page contains error and informational messages. Errors: (2). Infos: (2).
• This page contains warning messages. Warnings: (1).
Notifications may include supplemental explanatory information, such as the detailed messages that were generated. To
reduce cognitive load and make understanding easier, the additional information is not included in the initial
notification. To get the detailed information, navigate to the heading level 2 widget title and read the content within it.

Bold label widgets are assigned ARIA heading level 3

All bold label widgets are assigned the following ARIA attributes by default:
role="heading" aria-level="3"

Not all bold label widgets are necessarily headings, but they often function as headings. Bold label widgets most
commonly appear within areas that are labeled by widgets of type heading level 2. They can also occur directly within
areas that are labeled by title heading level 1. Although this might raise an automated structure flag, the benefits of this
approach generally outweigh the negatives for screen reader users.

ariaInfo property of PCF elements

Many PCF elements have an ariaInfo property. This property is reserved and is not functional. Do not use this
property.

Keyboard interaction with JAWS

If you use JAWS, then you may need to use modifier keys when triggering buttons and links within the main
application screen. In addition to the Enter or Space keys, you may also need to use the Alt or Insert modifier
keys. To remove the requirement for the modifier key, press Insert+Z, which toggles the virtual cursor (virtual
viewer) to 'off'.

User interface settings for accessibility

InsuranceSuite applications provide several user interface settings designed to improve accessibility. These include the
following:
Setting Description
Application font size The base font size, in points, of the text used on the application screens.
Global spacing modifier A multiplier that decreases (when less than 1) or increases (when greater than 1) the
amount of whitespace surrounding visual elements.
Theme The theme to use as the visual style of the application. If you require higher color
contrast, try the Guidewire Cloud High Contrast theme.
Left align top toolbars Set to align the toolbar at the top of the screen to the left instead of the right.
Force text shadows on When set, dark text is displayed with a white shadow, and light text is displayed with a
black shadow. This setting may assist with readability when there is low contrast
between the text and its background.
Disable outlines on focused elements When not set, the input elements with focus have an extra outline to make them
easier to identify.

80 Accessibility in Guidewire InsuranceSuite

 Guidewire PolicyCenter 10.2.3 Application Guide

Setting Description
Attempt to be smart about what touch inputs When using touch devices, some touches may be intended to interact with the
to ignore. Essentially allowing 'ignore errant application, and other touches may be incidental or accidental. When this setting is
thumb' and 'palm rejection' behavior. set, the application attempts to identify meaningful touches and ignore all others.
Add additional context to visible labels Add additional information to text labels of inputs. For example, the label might
indicate that the field is required or show what the expected date format is.
Use standard menu formatting Renders multi-column menus as standard single-column menus. This is useful for
screen readers and keyboard-only navigation.
Use radio buttons to select List Detail rows Provides an alternate way of interacting with List-Detail tables, where there is a list
view table and a detail view underneath. Instead of clicking on a row in the table to
select it, a new column is added with radio buttons used to select the row. This is
intended for use with some screen readers, which are otherwise unable to select rows.
Allow all tooltips to be displayed and read by When set, any screen element that has a tooltip is included in the sequence of
screen readers on focus. Affects page tab elements that you can navigate to by using the Tab key. When an element is in focus,
sequence. Requires browser restart. its tooltip appears, which is also useful for screen readers. After changing this setting,
you must restart your browser.

See also
• “Changing interface settings” on page 42

Keyboard navigation and interaction

Guidewire InsuranceSuite provides complete navigation through the application interface using the keyboard. Use the
following for keyboard navigation:
• Press Enter or Spacebar to act as a mouse click.
• Press Tab or Shift+Tab to navigate through the interface elements.
• Press the arrow keys to navigate in menus and list views.
• Press Alt+Shift+Arrow (using any of the arrow keys) to navigate to the primary interface panels. For example,
Alt+Shift+Left Arrow navigates to the sidebar.

Date picker navigation

Use the following keyboard navigation to interact with the date picker widget:
Windows (no screen reader)
• Spacebar: Toggle the date picker.
• Ctrl+Right Arrow or Ctrl+Left Arrow: Proceed forward or backward by day.
• Ctrl+Down Arrow or Ctrl+Up Arrow: Proceed forward or backward by week.
• Alt+Right Arrow or Alt+Left Arrow: Proceed forward or backward by month.
• Alt+Down Arrow or Alt+Up Arrow: Proceed forward or backward by year.
• Enter: Select the date.

macOS (no screen reader)

• Spacebar: Toggle the date picker.
• Cmd+Right Arrow or Cmd+Left Arrow: Proceed forward or backward by day.
• Cmd+Down Arrow or Cmd+Up Arrow: Proceed forward or backward by week.
• Option+Right Arrow or Option+Left Arrow: Proceed forward or backward by month.

Accessibility in Guidewire InsuranceSuite 81

Guidewire PolicyCenter 10.2.3 Application Guide

• Option+Down Arrow or Option+Up Arrow: Proceed forward or backward by year.

• Enter: Select the date.

With JAWS screen reader on

• Spacebar: Toggle the date picker.
• Ctrl+Shift+Right Arrow or Ctrl+Shift+Left Arrow: Proceed forward or backward by day.
• Ctrl+Shift+Down Arrow or Ctrl+Shift+Up Arrow: Proceed forward or backward by week.
• Alt+Right Arrow or Alt+Left Arrow: Proceed forward or backward by month.
• Alt+Down Arrow or Alt+Up Arrow: Proceed forward or backward by year.
• Enter: Select the date.

With NVDA screen reader on

• Spacebar: Toggle the date picker.
• Ctrl+Right Arrow or Ctrl+Left Arrow: Proceed forward or backward by day.
• Ctrl+Down Arrow or Ctrl+Up Arrow: Proceed forward or backward by week.
• Alt+Right Arrow or Alt+Left Arrow: Proceed forward or backward by month.
• Alt+Down Arrow or Alt+Up Arrow: Proceed forward or backward by year.
• Enter: Select the date.

82 Accessibility in Guidewire InsuranceSuite

part 3

PolicyCenter policy transactions

On a daily basis, producers and agents do work associated with policies. This work includes creating submissions,
changing policies mid-term, and any number of similar activities. In PolicyCenter, you do this work in policy
transactions. Policy transactions play a central role in PolicyCenter. This topic provides an introduction to policy
transactions and describes how policy transactions process information. Subsequent topics contain details on each type
of policy transaction.
Policy transactions coordinate all the work associated with creating a new policy period and modifying the policy.
Policy transactions are almost always referred to by type, that is to say, a submission, a policy change, or a
cancellation.
Note: In PolicyCenter, the user interface uses the term policy transaction to refer to submissions, policy
changes, and other policy transactions. Policy transactions are implemented as jobs in the data model, and
referred to as jobs in PCF files, Gosu classes, and other configuration files. Therefore, the configuration
documentation refers to policy transactions as jobs.
See also
• “Policies” on page 169

Submission
Submission is the only policy transaction that creates a policy. A potential policyholder contacts the insurer or agent
and requests a quote. The agent gathers information in order to generate one or more quotes. Based upon the apparent
risk of policyholder, PolicyCenter raises underwriting issues that may require approval. If both parties agree upon a
quote, then the agent binds and (optionally) issues the policy.

Issuance
Issuance is part of the submission process. It allows you to edit and requote a bound submission before officially
issuing the policy (sending out the accompanying policy forms). For example, a potential customer has a new
limousine business and must insure all 30 vehicles today. The customer contacts you, the insurance agent, requesting a
business auto policy. You require the VIN number and license of all vehicles, but the customer does not have these
readily available. You still proceed with generating a quote and agreeing on the terms. The policy is bound (legal)
today, so the customer’s limousines have coverage. The next day, the customer contacts you, provides the required
information, and adds another limousine, bringing the total number of vehicles to 31. You edit, requote, and now issue
the policy by using an issuance policy transaction.

Renewal
The renewal process extends the policy for another term beyond the current expiration date. It creates a new policy
period for an existing policy.
PolicyCenter policy transactions 83
Guidewire PolicyCenter 10.2.3 Application Guide

The renewal policy transaction is often automatic. For example, if there are no changes to the policy and no claims
were made against it, the system creates a new policy period and sends a renewal notice. Renewal can also require that
an underwriter review the policy. Processing occurs prior to expiration, but actual renewal is at expiration. Like
submissions, you can create one or more quotes on a renewal.

Cancellation
The cancellation process is a type of policy change which marks a policy as canceled. A cancellation can be initiated
by the insurer. A cancellation initiated by the insurer typically requires advance notice to the policyholder. Therefore,
the insurer starts the cancellation on one date, and the cancellation completes some period of time later. For example, a
policyholder forgets to pay his auto policy by the due date of June 10th. On June 11th, the system starts a cancellation
policy transaction for non-payment with termination of coverage effective as of a future date. The future date is usually
based on regulatory requirements.
A policyholder can also initiate a cancellation. For any number of reasons, a policyholder may no longer want coverage
by the insurer. According to the policyholder’s wishes, the insurer cancels the policy effective immediately or at some
future date.

Policy change
To create a policy change, you modify a policy in between the effective and expiration dates. A change can be as
simple as adding an additional vehicle to an auto policy. Or it can be an out-of-sequence event, such as adding another
driver to a policy on a date prior to the addition of another vehicle to the policy.

Reinstatement
Reinstatements go hand in hand with cancellations and are a type of policy change that uncancels the policy.
Reinstatement restores a canceled policy. The reinstatement date must be the same as the cancellation effective date.

Rewrite
Policies are rewritten to make the types of changes that cannot be done in a policy change policy transaction, to correct
significant errors, or to make changes to the policy. A rewrite, which can only occur on a canceled policy, effectively
ends the first policy and creates a new one in its place. For example, a customer requests a workers’ compensation
policy. However, when the customer receives the policy, he notices many errors: the dates and payroll amounts are
incorrect, and the building and location are in the wrong jurisdiction. The customer notifies you, the agent. If you
choose to fix the errors in a policy change, the system would send out an addendum, calling out the mistakes in the
policy. But because there are so many mistakes in the policy, you decide to rewrite the policy which sends out
completely new policy documentation.

Rewrite new account

When you rewrite a policy to a new account, PolicyCenter creates a rewrite new account policy transaction. This policy
transaction takes data from an existing policy and creates a new policy with a new policy number in the new account.
Unlike a rewrite policy transaction, a rewrite new policy transaction can have pre-qualification questions. You can only
rewrite canceled or expired policies to a new account.

Audit
The audit policy transaction lets the insurer verify information about the policyholder and determine the accuracy of
premiums paid. The audit policy transaction provides final audit and premium reports.
PolicyCenter supports final audit for the workers’ compensation line of business. You set up the method of final audit
(physical, voluntary, or by phone) when you create the workers’ compensation policy. PolicyCenter creates audits
when the current time reaches the initiation date of an audit schedule item. Unlike other policy transactions, the audit
policy transaction does not create a new version of the policy, and therefore does not affect the coverage.
With premium reports the policyholder is billed for premium based on periodic requests for actual basis amounts, such
as payroll. A deposit, usually a percentage of the estimated annual premium, is billed at the beginning of the policy. As
each reporting period ends, the policyholder is billed based on the actual basis reported by them.

84 PolicyCenter policy transactions

chapter 12

Common features of policy

transactions

There are a number of policy transaction features that apply to one or more policy transaction types. In the following
table, the marked cells indicate which features are available for each policy transaction type in the default application.

Common Feature Submission Issuance Policy Cancellation Reinstatement Rewrite Rewrite Renewal Audit
Change New
Account

Can get new policy • • • •

number

Change policy effective • • • • •

date

Change policy • • • • • •
expiration date

Change producer code • • • • •

of record

Change producer code • • • • • •

of service

Create new period • • • •

Decline • • •
Multiple versions • • •
Not taken or non- • •
renewed

Policy holds • • • • • • •
Qualification questions • •
Quick quote •
Referral reasons • • • • • • •
copied over to
underwriting issue

Common features of policy transactions 85

Guidewire PolicyCenter 10.2.3 Application Guide

Common Feature Submission Issuance Policy Cancellation Reinstatement Rewrite Rewrite Renewal Audit
Change New
Account

Select UW company • • • • •
Underwriting issues • • • • • • •
block progress

UW approval • • • • • • •
See also
• “Underwriting issues” on page 673
• “Policy holds administration” on page 709

Preempting policy transactions

Preemption occurs if there are two or more concurrent policy transactions in process on a policy. When one policy
transaction finishes, the other policy transactions needs to adjust to the fact that the policy information has changed.
The first policy transaction that finishes preempts any other changes in concurrent policy transactions.
See also
• “Preempted jobs” on page 215

Out-of-sequence changes and policy transactions

PolicyCenter supports out-of-sequence policy transactions. A policy transaction is out-of-sequence if its effective date
is earlier than the effective date of another policy transaction that is already bound on the policy for that contractual
period. PolicyCenter warns you that the policy transaction is out-of-sequence and prompts you to address any conflicts
that occur as a result.
When a policy transaction begins, PolicyCenter checks to see if the transaction is out-of-sequence. The transaction is
out-of-sequence if at least one completed transaction on the policy has an edit effective date later than the edit effective
date of the current policy transaction. So when you click Start either on the Start Policy Change, Start Cancellation, or
Start Reinstatement screens, PolicyCenter displays a confirmation message about the out of sequence change. If you
click OK, then the policy transaction starts.
See also
• “Out-of-sequence jobs” on page 213

Out-of-sequence policy transaction combinations

Since there are many different types of policy transactions, it is helpful to know which policy transactions may be out-
of-sequence with respect to another. The following table shows all possible pairs of policy transactions. A cell marked
in row X and column Y indicates that policy transaction X may be out-of-sequence with respect to policy transaction Y.
Policy transaction X may be started and completed even if its edit effective date is earlier than the edit effective date of
a previously bound policy transaction Y.

Out-of-sequence Rewrite
policy transaction Policy new
type Submission Issuance change Cancellation Reinstatement Rewrite account Renewal Audit

Submission

Issuance

Policy Change • • • • •
86 Common features of policy transactions
 Guidewire PolicyCenter 10.2.3 Application Guide

Out-of-sequence Rewrite
policy transaction Policy new
type Submission Issuance change Cancellation Reinstatement Rewrite account Renewal Audit

Cancellation • • • • •
Reinstatement • • • • •
Rewrite • • • • •
Rewrite New Account • • • •
Renewal

Audit

Note the following:

• Cancellation and reinstatement – When you cancel or reinstate a policy, you cannot make additional changes to
that policy. Therefore, if a policy transaction is out-of-sequence with respect to a cancellation or reinstatement
policy transaction, there are no conflicts to resolve.
• Rewrite – If rewrite is out-of-sequence with respect to renewal, then you receive a warning that the rewrite changes
are not applied to the renewal.
• Submissions, issuances, and rewrite new account – Can never be future-bound policy transactions.
• Submissions – Can never be out-of-sequence because no policy exists until a submission is complete.
• Renewals – Can never be out-of-sequence because no other policy transactions with later effective dates can be
started until the renewal completes. However, if PolicyCenter promotes a renewal period, then any subsequent
policy transaction in the expiring period will always be out-of-sequence with respect to the renewal.
• Audits – Since PolicyCenter never promotes audit branches, they are never in an out-of-sequence relationship.
• Rewrite new account – If rewrite new account is out-of-sequence to another policy transaction, the out-of-
sequence policy transaction occurred on the source policy. (Remember that rewrite new account rewrites a source
policy to a new target policy on a different account.) That out-of-sequence policy transaction is a transaction on the
source policy but not on the target policy. However, both the source and target policies have a slice representing the
out-of-sequence policy transaction.
Note: Only cancellation policy transactions can be started on non-issued policies.

Configuring policy transactions

Configuring PolicyCenter policy transactions involves making changes to the product model, Gosu classes and rules,
page configuration files (PCF files), wizards, configuration parameters, plugins, and sometimes workflows. Each can
be configured based on your business requirements. It is the combination of these elements that enables you to create
or modify a policy.
Note: In PolicyCenter, the user interface uses the term policy transaction to refer to submissions, policy
changes, and other policy transactions. Policy transactions are implemented as jobs in the data model, and
referred to as jobs in PCF files, Gosu classes, and other configuration files. Therefore, the configuration
documentation refers to policy transactions as jobs.
In contrast to policy transactions, the product model defines the types of policies that you can offer to your customers.
Each product can contain one or more lines of business offering various coverages. For more information, see “Product
model” on page 369.
See also
• Configuration Guide

Common features of policy transactions 87

Guidewire PolicyCenter 10.2.3 Application Guide

88 Common features of policy transactions

chapter 13

Submission policy transaction

Creating a submission policy transaction is one of the most common activities in PolicyCenter. The goal is to bind and
issue the submission which turns it into a policy. In a typical scenario, a producer receives an inquiry for coverage,
establishes an account, asks some pre-qualification questions. If the answers are correct, meaning that the risks are
reasonable, the producer asks the applicant for additional information. If the answers are not correct, then the policy
may be referred to underwriting. If both sides agree to terms and price, then PolicyCenter generates the policy and
accompanying documents, and the documents are sent to the applicant. The policy is legally binding to both parties.
Note: In PolicyCenter, the user interface uses the term policy transaction to refer to submissions, policy
changes, and other policy transactions. Policy transactions are implemented as jobs in the data model, and
referred to as jobs in PCF files, Gosu classes, and other configuration files. Therefore, the configuration
documentation refers to policy transactions as jobs.
This topic explains what a submission is, how to work with submissions in PolicyCenter, and how you can configure it
to meet your business requirements.
See also
• Configuration Guide

Issuance wizard
PolicyCenter handles submissions through the submission wizard. After getting account information, the submission
wizard guides you through the process of gathering the required information for the policy. Typically, the first and last
wizard steps are the same for all lines of business.
However, the wizard steps differ slightly for each line. In personal auto, some steps gather information about the driver,
the type of vehicle, the garage location, and the type of coverages. In workers’ compensation, some wizard steps
require information about the business, the types of workers, locations, and coverages. So how does a submission end?
The outcome goal is to bind and issue the submission. You can choose to issue the policy at a later date. In this case,
you search for the policy then run an issuance policy transaction.

Submission general steps

The following diagram shows the basic steps to create a submission in the base configuration of PolicyCenter. Your
business requirements can alter the process. Also, the steps may differ slightly between personal and commercial lines
and in how you access the submission screens.

Submission policy transaction 89

Guidewire PolicyCenter 10.2.3 Application Guide

Submission General Steps

1) An applicant (person or
company) wants a policy 5) Pre-qualify the applicant.

2) Name Clearance occurs. 6) Gather more information.

3) Select a product. 7) Generate a quote.

4) Determine the type of 8) Regenerate a quote, if

submission. necessary.

9) End a submission.

The steps are sequential:

1. An applicant wants a policy and contacts a producer about purchasing a policy.
2. Name clearance occurs: This is the process of checking against one or more agent or account databases to ensure
that the account is not already an existing customer and is not represented by another producer for this policy
type. Once an account has bound or issued a particular policy type for a specific policy period, it may be risk
reserved. If there is no existing account, then a new account is established.
3. Select a product: A product can be thought of as a line of business, such as personal auto policy, workers’
compensation, or businessowners.
4. Determine the type of submission: A producer can select either:

90 Submission policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

• A Quick Quote which requires less information and produces a quote which is not bindable. Quick quotes are
useful for determining if the policy can be priced at an amount that is agreeable to the applicant.
• A Full Application which requires more information but produces a bindable quote.
5. Prequalify the applicant: A producer may ask a series of prequalification questions to determine eligibility.
Depending on the answers, the submission may be referred to underwriting. In either case, continue to the next
step.
6. Gather more information: A producer asks specific questions regarding exposures, coverages, and terms for each
coverage. Questions can be different depending on the business line.
7. Generate a quote: If quick quote was selected, then a producer can convert it to a full application. This step
requires additional information and is bindable.
8. Regenerate a quote, if necessary: If the quote is not competitive, then the prior step can be repeated (using
multiple versions) until it becomes competitive.
9. End a submission: Possible outcomes to a submission:
• A policy is issued. In other words, if the submission can be bound and issued, the submission becomes a
policy.
• A submission is closed. It can be withdrawn (when there are mistakes), declined (the insurer decides not to
offer a policy), or not taken (the applicant decides not to accept.)

Understanding name clearance and risk reservation

PolicyCenter has the ability to perform name clearance and risk reservation. It does this through the IAccountPlugin
methods performNameClearance and isRiskReserved.

Name clearance
Name clearance ensures that a person or company is not an existing account and that another producer does not
represent them for the given policy type. PolicyCenter checks the name against one or more producer or account
databases. You must complete name clearance before creating a new account in PolicyCenter. You can use the
performNameClearance method to check against external databases when populating the list of available products.
This check helps to prevent an insurer from inadvertently competing with itself.

Risk reservation
In the default application, risk reservation is the process of associating a product and period to a producer code. If a
product is risk reserved by a producer code that the current user does not have, then the product’s status on the New
Submission screen is Risk reserved. The current user cannot create new submissions for that product.

The difference between quick quote and full application

In a submission in PolicyCenter, you have the option of creating either a quick quote or a full application submission.
• Quick Quote gathers the minimal information needed to generate a quote.
• Full Application gathers the complete set of information needed to apply for a bindable quote.

What are the advantages of quick quote?

Select Quick Quote if you need to generate a quote with minimal information. Quick quote provides a rapid assessment
of whether or not the insurer can provide a policy premium that is in the applicant’s price range. If both parties are
agreeable to the quote, then additional information must be gathered in a Full Application before a policy can be bound.
You can generate as many quick quotes as you need and save them, but you cannot bind them. From Quick Quote, you
can continue to Full Application.
In all lines except personal auto, selecting Quick Quote skips selected steps in the full submission wizard. Quick quotes
skip the Risk Analysis and Policy Review steps, because PolicyCenter can generate a quote without the information

Submission policy transaction 91

Guidewire PolicyCenter 10.2.3 Application Guide

requested in these steps. Quick quotes also skip the Forms and Payment steps, because these items do not apply to a
non-bindable quote.
In personal auto submissions, selecting Quick Quote does more than skip steps in the full quote submission wizard.
Instead, personal auto line quick quotes use a separate wizard that reduces the quote process to two steps, producing
quotes for up to two drivers with up to two vehicles. As with any quick quote, the resulting quote is not bindable.
You can continue to create quick quotes if a submission has never had a full application quote generated.

Answering pre-qualification questions in a submission

Pre-qualification questions are a screening tool used to determine applicant risk and to reflect the insurer’s desire for
the business. These questions determine if an applicant qualifies for the type of insurance being sought. You access and
modify the questions in Guidewire Product Designer. (Not all products in the default application have pre-qualification
question sets.) Questions have risk points and correct answers. Depending on the answers, PolicyCenter can raise
underwriting issues that cause the policy to be referred to an underwriter. If not approved, these issues may prohibit
quoting the policy.
The outcomes of answering the questions are:
• The applicant answers the questions correctly. The submission process continues normally.
• The applicant answers some of the questions incorrectly. Incorrect answers can raise underwriting issues which
an underwriter needs to review. In the base configuration, underwriting issues are raised before quoting the policy.
◦ The underwriter reviews the underwriting issues and approves them. The agent can quote the policy and
continue the submission.
◦ The underwriter decides that the applicant does not meet the base requirements, and declines the underwriting
issues. The agent cannot quote the policy. The agent can revise the pre-qualification questions and other parts of
the policy. These changes may remove underwriting issues blocking the submission.
You can configure the error message that appears when the applicant answers a question undesirably. In some cases,
the insurer wants the message to be as explicit as possible so that agents know exactly what the eligibility requirements
are. In other cases, they want the answer to be less straightforward to prevent users for knowing how to beat the system
and pre-qualify an undesirable applicant.
Questions can be filtered. They can only be tied to a single answer. For example, if a question has a drop-down list, a
filtered question can appear if the user selects a certain value from the drop-down. You cannot configure the system to
have a single question appear if the user selects one of two values.
See also
• “Underwriting issues” on page 673
• Product Model Guide
• Configuration Guide

Selecting an underwriting company in a submission

Large insurers can license more than one underwriting company to underwrite policies on their behalf. The primary
reason for having these multiple underwriting companies is to accommodate jurisdictional regulatory requirements.
Many jurisdictions do not allow insurers to have more than one set of rates per underwriting company. Therefore, if an
insurer wants to offer multiple sets of rates in that jurisdiction, they must file each set of rates under a separate
underwriting company for that jurisdiction. Underwriting companies may also offer different coverages or limits.
Underwriters typically profile an account to determine what segment an account falls into, and therefore which
underwriting company would actually underwrite the policy. By extension, this determines the set of rates the account
is eligible for. The appropriate set of rates would then be used to quote the policy. For example, a workers’
compensation insurer may segment accounts into three different groups: high hazard, medium hazard, and low hazard.
The insurer has three underwriting companies that correspond to each segment. To generate a quote for the policy, an

92 Submission policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

underwriter uses the underwriting company automatically selected by PolicyCenter or selects a different underwriting
company. The rating engine calculates a quote for the policy based on the underwriting company.
In the Policy Info screen, you can select a different underwriting company.
Segmentation can determine which underwriting companies are available for a given submission, since underwriting
companies may be able to accept only certain types of risks.
See also
• Configuration Guide

Reasons for underwriter review in submissions

Applications may need to be referred to an underwriter for manual revie w and approval. Some of the reasons an
underwriter might review them are:
• PolicyCenter raised underwriting issues because:
◦ Choices on the policy period are considered too risky. For example, the insurer raises an underwriting issue for
cars valued at over $100,000 on a personal auto policy.
◦ There are referral reasons on the policy. For example, there have been too many claims in previous policy
periods.
◦ The default pricing of the policy has been overridden through rating overrides.
◦ The applicant did not answer the pre-qualification questions correctly.
• The producer did not have the permission to bind submissions. In this case, the Bind Options menu choice triggers
the underwriting review.
See also
• “Underwriting issues” on page 673
• Configuration Guide

Closing a submission
You have the option to close a submission by selecting Withdraw Transaction, Decline, or Not Taken under Close
Options in the submission wizard. Having separate closing options for a submission that was not bound allows you to
track information such as how many were not bound or why they were not bound.
Withdraw Transaction – A submission can be withdrawn for any reason, such as mistakes were made on the policy. You
can only withdraw a submission in Draft or Quoted status. The withdrawn submission, and all its versions are no
longer editable.
Decline – An underwriter may decide to decline a submission, and if so, must provide a reason by entering a Reason
Code. A submission may be declined for reasons including loss history, payment history, or requested coverages and/or
limits not available. The declined submission is no longer editable.
Not Taken – Select this option when the applicant decides not to take the offered policy. You must enter a reason. You
can also enter text to create a Not Taken letter. You can select this option from both the submission wizard and the
Submission Manager. Generate the Not Taken letter from the Submission Manager.

Differences between binding and issuing a policy in a

submission
PolicyCenter makes a distinction between binding and issuing a submission. Binding is the agreement that there is
coverage, and issuance is the production of the policy contract.

Submission policy transaction 93

Guidewire PolicyCenter 10.2.3 Application Guide

You bind a policy when the insured and the insurer have agreed to terms and price and a policy is in force. If the
insured has a car accident one hour after the submission is bound, the policy covers the incident even though the
insured has not received official documents.
You may wish to bind but not issue a policy because the policy documents have not yet been issued. Or perhaps the
insurer needed to collect or verify additional information so the issuance of the policy occurs after adding the
information to the policy.
In PolicyCenter you:
• Bind a submission by clicking Bind Only under Bind Options in the user interface. This binds the policy but does not
issue it.
• Issue a submission in the submission wizard by clicking Issue Policy under Bind Options in the user interface. This
binds and issues the policy.
• If a policy has only been bound, you can issue a submission at a later date through an issuance policy transaction.
See to “Issuance policy transaction” on page 97 for more information.

Expiring submissions
A submission is expired after a sufficient and configurable interval of time has elapsed. A policy version can be
expired when its status is either New, Draft, or Quoted. When a policy version expires, its status changes to Expired.
You can view the status in the Submission Manager screen or in the toolbar if you are in the submission wizard. An
expired branch is not editable.
See also
• Configuration Guide

Copying submission information

In PolicyCenter, you can copy submission information from an existing submission to create a new submission. Why?
After losing the business to a competitor, a producer may copy submissions that were not taken and try to capture that
business again. Another reason to copy submissions is if you need to reenter information for a new submission.
Copying saves you data entry time and lessens the chance of errors. You can copy a submission with any status. If you
copy a quoted submission, then PolicyCenter invalidates the quote (you must quote again) and the submission is in
Draft status. If you copy a submission which is bound, then the newly copied submission is also in Draft status.
However, you can copy only one version of a multi-version submission. This version is the version on view in the user
interface when you select Copy.
If you select Copy from the Actions menu, the Submission Wizard creates a new submission which is based on the
original, but with a new submission number. This new submission contains the same policy information, producer,
underwriter company, and effective and expiration dates as the original. You can change any of that information.
However, PolicyCenter does not copy the pre-qualification status, underwriter approval, and all financial information,
so you must enter that information and obtain a quote prior to binding.
See also
• “Copy a submission” on page 96 for an example of how to copy a submission
• “Multi-version quoting” on page 167
• Configuration Guide

Submission manager
The Submission Manager screen contains summary information such as line of business, quote type, effective date,
status of the transaction, and the premium. You can access this screen from the sidebar of an account. You can use this
screen to do actions, such as withdrawing a submission. Use the Submission Manager to view multiple submissions on
an account and view the aggregate premium of all policies on the account.

94 Submission policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

The Submission Manager has the following filters: All Submissions, Open Submissions, and Complete Submissions. All
Submissions is the default. If you select Open Submissions, then the screen displays only submissions that have at least
one version in an open status. If you select Complete Submissions, then the screen displays only submissions with no
open versions. Therefore, a submission that has an open version appears under Open Submissions but not under
Complete Submissions.

From the Submission Manager > Actions drop-down list, you can withdraw, decline, or not take the submission. This
drop-down list applies to both Quick Quote and Full Application and appears if the submission has not been bound.
See “Closing a submission” on page 93 for additional information on these actions.

Creating a submission
PolicyCenter has several places in the user interface where you can create a submission. However, you must have an
account before you create a submission. Generally, if you have not selected an account and want to create a
submission, PolicyCenter guides you to select an account first. If you already have an account, you then confirm the
producer, product, quote type, and number of desired policies. You can create a submission in these ways:
• Actions > Create > New Submission menu when viewing the Desktop and Account tabs and Submission Manager
screen
• Policy tab, select New Submission from the drop-down list
• Actions > Copy Submission when viewing a submission or policy
• Actions > Spin-off Policy from this One when viewing a policy
• Actions > Split Policy into Two when viewing a policy

Create a submission
About this task
The following steps explain the process for creating a submission whether it is a Quick Quote or a Full Application.
Other steps are variations on this basic process.
Note: You must have an account before you can create a submission. To learn about accounts, see “Account
file” on page 385.

Procedure
1. If an account already exists, you can begin a submission by selecting the account from the Account tab or from
the Desktop tab, select My Accounts in the Sidebar.
2. While viewing the account, click Actions > New Submission. Since you have already defined an account,
PolicyCenter directs you to the New Submissions screen which has default values for organization, producer code,
and date.
3. Under the Product Offers section, select either Single or Multiple. Selecting Multiple allows you to enter the
number of submissions you want to create. In the base application, you can create up to five per line of business.
You can configure this maximum in Studio. In this example, you create only one submission, so click Single.
4. In Quote Type, select the type of quote you want (Quick Quote or Full Application). In this example, select Full
Application.
5. Choose from the available product offerings.
• Quick Quote gathers the minimal information needed to generate a quote.
• Full Application gathers complete information needed to bind and quote.
6. Depending on the line of business, there may be Pre-Qualification questions that need to be answered. If
answered successfully, then the next screen is the Policy Info screen.
7. The Policy Info screen allows you to collect information, determine policy details

Submission policy transaction 95

Guidewire PolicyCenter 10.2.3 Application Guide

If you have the correct permissions, you can change producer information and underwriting companies. You can
also create or add other contacts as named insureds on the policy. These named insured contacts might be a
spouse or child of the primary named insured. Named insureds can be a company, a person, or selected from an
address book.
8. Continue entering required information in the submission wizard. Each line of business has specific requirements
that need to be captured in the policy. For example, a workers’ compensation policy can require additional
information on locations, coverages, supplemental information, and workers’ compensation options.
• See “Workers’ compensation” on page 351 for more information on workers’ compensation.
• See “Personal auto” on page 335 for more information on personal auto.
• See “Businessowners” on page 247 for more information on businessowners.
9. After entering the required information, you can review it in the Policy Review screen. If you are satisfied, then
click Quote.
10. After the submission has been successfully quoted, you can:
• Edit and requote. To edit submissions, you must have the viewsubmission and editsubmission system
permissions.
• Create a new version.
• Save the draft.
• Select from close options.
• If you selected Quick Quote, then you can select Full Application to continue to enter additional information
and bind the policy.
11. (Optional) Select Forms to view the list of forms that will be attached to the policy.
12. Select Payment. Enter the type of billing plan, payment type, and the deposit collected on the Payment screen.
13. Select a bind option from Bind Options:
• Bind Only, legally binds both the insurer and the applicant, generates billing information, but does not issue
the policy.
• Issue Policy, binds, generates billing information, and issues the policy.

Copy a submission
About this task
You can copy information from a submission to create a new submission. For additional information on this see
“Copying submission information” on page 94.

Procedure
1. Navigate to a policy or submission.
2. From the Actions menu, select Copy Submission.
3. Make changes to the policy.
4. As with any submission, you can create a new version, save the draft, select from the bind options, or select from
the close options.

96 Submission policy transaction

chapter 14

Issuance policy transaction

A submission may be bound, but its policy documents may not yet be issued because the insurer may need to collect or
verify additional information. The mechanism that PolicyCenter uses to support this final step is the issuance policy
transaction.
Note: In PolicyCenter, the user interface uses the term policy transaction to refer to submissions, policy
changes, and other policy transactions. Policy transactions are implemented as jobs in the data model, and
referred to as jobs in PCF files, Gosu classes, and other configuration files. Therefore, the configuration
documentation refers to policy transactions as jobs.
There are times that you may choose to bind a submission without issuing it. Perhaps you need to collect additional
information that binding does not require but issuing the final policy contract requires, such as:
• Verification of eligibility for discounts in an auto policy.
• Name and address of the additional interest because the insured does not own the vehicle (but the bank does).
• Receipt of VIN (Vehicle Identification Numbers) for vehicles on a business auto policy.
The point is, that while the insurer has agreed to provide coverage, there are some details that must be confirmed
before generating the paperwork.
See also
• Configuration Guide

How issuance works

To start an issuance policy transaction, the policy must already be bound, but not issued. In addition, the policy must be
no other open policy transactions. The issuance wizard behaves in much the same way as the submission wizard. You
can edit in the Policy Info screen, review the policy, requote, and change payment options. To issue a policy, you must
have the bindissuance system permission. An insurer can use this permission to specify the set of users who can issue
policies. This set may differ from the set of users who can create policies.
Validation rules run at the Ready for Issue validation level. If validation fails with errors, then the process stops and
remains in the previous Quoted status. If validation fails with warnings the first time, you can override the warnings by
clicking Issue Submission again. Before binding the policy, PolicyCenter first executes evaluation and then sends the
Issue Submission message.
After a policy has been successfully issued, PolicyCenter sends billing instructions to the billing system through the
IBillingSystemPlugin.

Issuance policy transaction 97

Guidewire PolicyCenter 10.2.3 Application Guide

Issuance general steps

The following diagram indicates the basic steps to issue a policy. These steps are for the base configuration of
PolicyCenter. Your business requirements and even lines of business can alter the process.

Issuance General Steps

Find the policy

Start the issue

process

Make changes and

review

Requote

Issue the policy

The steps are sequential:

1. Find the policy: Verify that the policy has not been issued.
2. Start the issuance process: Select Issue Submission from the Policy Actions menu.
3. Make changes and review: Finalize policy details.
4. Requote: Policies must be requoted before issuing.
5. Issue the policy: Paperwork is generated.

98 Issuance policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

Working with issuance

Issue a policy
About this task
To issue a policy, you must first have a submission that has been bound but not issued.

Procedure
1. Navigate to the Policy Summary screen, or any screen in the policy.
2. From the Actions menu, select Issue Policy.
3. Beginning with the Policy Info screen, make any necessary changes. You can make any changes to the policy,
including changing the effective and expiration dates.
4. Click Quote to requote the policy.
5. Click Issue Policy. A dialog box asks you to verify your action. In a production system, PolicyCenter might send
the policy information to be generated and mailed by a print issuance system. The outcomes are:
If PolicyCenter successfully issues the policy, then the Issuance Bound confirmation screen appears and the status
is set to Bound. Your options are to:
• View your issuance policy transaction
• View your policy
• Go to the Submission Manager for the selected account
• Submit an application for a different account
• Go to your Desktop
If issuance fails, PolicyCenter sets the UWApproval to Review status and creates an Issuance failed activity. The
activity is assigned to the underwriter.

Issuance policy transaction 99

Guidewire PolicyCenter 10.2.3 Application Guide

100 Issuance policy transaction

chapter 15

Renewal policy transaction

Insurers typically begin the process of renewing a policy for another period of time before its expiration. The most
efficient way is to have PolicyCenter process these renewals automatically. However, sometimes an underwriter or
producer must review or make adjustments to the policy before deciding whether it can be renewed. PolicyCenter is
flexible in handling both automatic and manual renewals.
Note: In PolicyCenter, the user interface uses the term policy transaction to refer to submissions, policy
changes, and other policy transactions. Policy transactions are implemented as jobs in the data model, and
referred to as jobs in PCF files, Gosu classes, and other configuration files. Therefore, the configuration
documentation refers to policy transactions as jobs.
A renewal policy transaction extends a policy for another period of time.
The goals of renewal processing are to:
• Maximize retention of the best customers of an insurer.
• Reduce expenses associated with the renewal process.
For both the producer and the insurer, renewing an existing customer is more profitable than acquiring a new customer
with a similar profile because of acquisition and processing costs. An insurer’s retention ratio (the percentage of
insurance policies that renew) is a closely watched metric. Too low a retention rate might indicate poor customer
service to producers, noncompetitive pricing, or unfavorable claim service. Because the bulk of business is from
existing customers, having an efficient renewal process has a great impact to minimizing overhead and optimizing
revenue.
By design, PolicyCenter handles renewals efficiently. In the default configuration, policies nearing the end of their term
are examined. If a policy can be renewed without requiring an underwriting decision, the renewal progresses
automatically. However, if manual intervention (review of the policy) is necessary, then PolicyCenter guides you
through this process.
An underwriter may need to review a policy for a variety of reasons, including:
• Manual rating required
• Insurer practices for that class of customer
• Unfavorable claims or payment history
• Significant changes in risks or exposures
PolicyCenter can track these variables through business rules evaluation, referral reasons, or pre-renewal directions
which stop a policy from automatically renewing. This tracking allows an underwriter to review and make a decision
on whether to renew, modify, or decline the policy.

Renewal policy transaction 101

Guidewire PolicyCenter 10.2.3 Application Guide

See also
• Configuration Guide

Renewal flows
PolicyCenter supports the following renewal process flows:
• Bind and cancel
• Renewal offer
• Confirmed renewal
In the default configuration, PolicyCenter uses the bind and cancel renewal flow for all lines of business. When you
bind a renewal, PolicyCenter sends charges to the billing system. PolicyCenter then does a flat cancel for reason Policy
not taken if no payment is received for that period. If partially paid, then PolicyCenter cancels for reason Non payment.
The default configuration contains the renewal offer renewal flow which binds only after payment. You can configure
this renewal flow for a particular line of business. Under this approach, you make the decision to renew or not renew,
but instead of actually binding the renewal, you consider it a renewal offer. When you make the renewal offer,
PolicyCenter sends a renewal notice (including pricing and payment plans). PolicyCenter does not send charges to the
billing system (since no policy transaction has been completed). When the billing system receives payment, it sends a
message to PolicyCenter to bind the renewal. If payment is not received, the PolicyCenter renewal flow times out. The
renewal is considered not taken.
The default configuration contains the confirmed renewal flow which provides confirmation from the billing system
that the insured has completed payment. PolicyCenter knows if the policy was confirmed and is legally binding. The
bind and cancel flow does not provide either of these.
See also
• Integration Guide

Renewals create new policy periods

The renewal policy transaction creates a new policy period with new effective and expiration dates.
The only restriction is that the effective date of the renewal policy must not overlap with the policy period of the
current in-force policy.

Renewal restrictions
Any policy that has been issued and is in-force can be renewed, however there are limitations to starting a renewal.
• There can be no open rewrite policy transactions on the policy.
• There can be no open renewals on the policy.
• The policy cannot be canceled.

Renewal outcomes
Renewals can have one of the following outcomes:
• Renewed – A policy is renewed for another period of time.
• Not Taken – The insured declines the offered policy, and PolicyCenter marks the renewal as not taken.
• Not Renewed – The insurer decides not to renew the policy, and the policy expires on the expiration date.

Renewal general steps

The diagrams in this topic show the basic steps used in an automatic and manual renewal policy transaction in the
default application. You can customize the flows based on your business requirements.

102 Renewal policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

PolicyCenter uses an automatic process to renew a policy without human intervention. To view the default steps, see
the Configuration Guide. The following flow chart shows the steps in automatic renewal.

Automatic Renewal General Steps

The number of days is based on renewal

A renewal typically starts x process lead time, expiration date, line of
days before the expiration business, jurisdiction, and time of year.
The number of days is configurable.
date.
PolicyCenter keeps track of when a policy
is due to expire and automatically starts
the process using a workflow.

Issues include having any pre-renewal

The system checks to see if
directions attached to policy, any referral
there are any issues. reasons, or unhandled preemptions.

No issues? Issues?

Send policy for underwriter

Begin renewal review, and exit the
workflow.

Policy is in draft status

Quote automatically No valid quote Manually review the policy. and is editable.
Goes to manual steps.

Wait until policy effective date is Y days from expiring. *

First check for open issues If there are issues

* Y = 80 days
Wait until policy effective date is Z days from expiring.* Z = 75 days
Both are configurable.

Final check for open issues If there are issues

Bind only
Send conditional renewal after
Wait for payment Payment not received
documents payment
flow

Bind and cancel flow Payment received

Issue renewal Issue renewal Policy not taken

Cancel if not paid

The two checks for open issues occur 80 and 75 days before the policy expires. You can configure these in the
PendingRenewalFirstCheckDate and PendingRenewalFinalCheckDate methods in RenewalProcess.gs.

An underwriter may use the manual process if the renewal needs modification and the renewal needs to be started
before the scheduled time for the renewal batch process. An underwriter may also use the manual process if a renewal
was previously declined (not taken), then the insured changed their mind, and now wants the policy renewed.

Renewal policy transaction 103

Guidewire PolicyCenter 10.2.3 Application Guide

The following flow chart shows the steps in a manual renewal. It does not include issues that may need to be dealt with
first.

Manual Renewal General Steps

Find the policy through the

An underwriter finds the policy and starts the renewal
user interface and create a
process.
renewal.

Having issues associated with a policy is a common reason

Review the renewal. that a renewal needs to be reviewed. These issues can
modify a policy or result in the policy not being renewed at all.

Create new version. Edit the renewal. Modify the policy and/or create a new version.

Quote (or requote) the

renewal. You must requote the policy if it is edited.

Possible decisions for a renewal:

Review the renewal. - A policy is renewed. In other words, the policy is bound
for another term. The user selected Renew Now.
- A policy is submitted for automatic renewal. The user
selected the Renew button. The renewal goes to the “First
check for open issues” box in the previous diagram.
- A policy is non-renewed. The carrier did not want to
Make renewal decision. renew it due to risk or it was financially unfavorable.
- A policy is not taken. The insured decided not to renew it
for any reason.

Pre-renewal directions
A pre-renewal direction is a special type of note which indicates how to handle the renewal. PolicyCenter attaches this
special note to a policy, but you cannot view the note in the user interface. Creating these directions can save the
underwriter from revisiting the renewal policy transaction at a later time.
Note: If you want the policy to be automatically processed, do not create a pre-renewal direction that assigns
renewals to a user.
Pre-renewals have the following broad directions:
• Non-renew – Indicates not to renew the policy.
• Not taken – Indicates that the insured did not take the renewal policy.
• Refer to an individual for review – Indicates that a person needs to manually review the policy before deciding its
outcome. This person can be an underwriter, a customer service representative, or an underwriter assistant.
Usually, a user who knows how to handle the renewal creates the pre-renewal direction.

Examples
• The policy has become high risk, so an underwriter now must review it.

104 Renewal policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

• The claims department finds that the policy has too many outstanding claims, therefore the insurer will not renew
the policy.
• The insured contacts the producer and indicates that a better rate can be found through a competitor, so the insured
will not take the policy.
A policy can have, at any given time, only one active pre-renewal direction. If a policy has a pre-renewal direction,
then the renewal process uses this pre-renewal direction.
Note: You cannot create pre-renewal directions for a policy period which has already been renewed. Pre-
renewal direction cannot be set/edited on a policy if there is a renewal on the active policy.

Referral reasons on renewals

You can use referral reasons to record underwriting issues for a policy outside of the context of a policy transaction.
Because you add referral reasons to the policy, you can create referral reasons at any time, even when there is no policy
transaction. PolicyCenter creates underwriting issues for these referral reasons the next time a user processes a policy
transaction on the policy. It also checks for referral reasons at various point in the policy transaction progress. Referral
reasons can block progress of policy transactions on the policy. In the default application, the renewal policy
transaction checks to see if there are any open referral reasons in the prior term.
Referral reasons can be added manually through the user interface or programmatically by using the
addReferralReason method in PolicyEnhancement.gsx.

Note: Referral reasons affect all policy transactions that handle underwriter issues, not just renewals.
See also
To obtain detailed information on referral reasons:
• “Add underwriting referral reasons” on page 676
• “Underwriting referral reasons raise underwriting issues” on page 654
• Configuration Guide

Underwriting issues in renewals

Underwriting issues allow you to track issues with a policy version that are of interest to an underwriter. Among other
things, each issue can specify:
• An issue type
• A description
• A point in the policy transaction where the issue is raised
• A point where the issue blocks progress
Underwriting issues are raised based on the underwriting authority of the current user. Issues are sent for approval to a
user with greater underwriting authority. Open issues must be reviewed and approved before a renewal can be
successfully completed. You can create underwriting issues in the following ways:
• Add an underwriting issue through the user interface You can only do this in the context of policy transactions.
• Create issues automatically in the Evaluation rule sets in Guidewire Studio. When PolicyCenter calls the
Evaluation rule sets at various points during renewal, the system identifies and generates underwriting issues.
• Create a referral reason on the policy PolicyCenter creates underwriting issues from referral reasons at the start
of a renewal policy transaction and at various points during the policy transaction. Use referral reasons for issues
that apply to the policy as a whole, not just the policy period.
Automated renewal policy transactions usually approve issues automatically based on the underwriting authority of an
automated renewal user that you specify.
Instructions on how to work with underwriting referral reasons and underwriting issues are provided in:

Renewal policy transaction 105

Guidewire PolicyCenter 10.2.3 Application Guide

• “Underwriting issues on the Risk Analysis screen” on page 673

• “Add underwriting referral reasons” on page 676

Add an underwriting issue through the user interface

Procedure
1. Click Risk Analysis from the Tools menu, and select the Underwriting Issues tab.
2. Add a new issue, close an existing issue, or reopen a closed issue.
3. For a new issue, select a type and enter a description.

Policy changes and renewals

If a user changes a policy in the current period but a future renewal revision already exists, PolicyCenter displays a
special screen. That screen asks the user whether to apply (merge) changes forward to the renewal period. This is not
preemption.
See also
• “Applying changes to future renewals” on page 218

Starting renewals
Starting renewals manually in the user interface
There may be times that you need to start the process manually. For example, you may want to start a renewal policy
transaction earlier than the predetermined number of days. Or you may want to start a renewal if the insured originally
declined the renewal, then changed their mind, and now requests that their policy be renewed.

Start a renewal through the user interface

About this task
See also
• “Create a manual renewal” on page 108

Procedure
1. Find an in-force policy.
2. Select Renew Policy from the Actions menu.
3. Use the renewal wizard to complete the necessary steps.

Starting renewals using the Policy Renewal web service

Renewals can be started by an external system through the Policy Renewal web service. The web service provides
methods to start renewals on existing policies and to import a policy to PolicyCenter and start a renewal. The web
service also provides methods for renewals in a billing system.
See also
• Configuration Guide

Starting renewals using a batch process

PolicyCenter has a batch process that automatically finds policies that are ready for renewal. In the default
configuration, PolicyCenter starts renewals based upon the expiration date, the renewal process lead time, line of

106 Renewal policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

business, jurisdiction, and time of year. PolicyCenter first checks whether the expiration date of the policy period falls
within the renewal process lead time. Then PolicyCenter determines the lead time required by regulations.
PolicyCenter adds additional time for company practices. Finally, PolicyCenter adds a delay for concurrent policy
transactions, if any. Because the renewal process lead time is checked first, no policy will start automatic renewal
sooner than this.

Factors to consider in scheduling the Renewal batch process

There are several factors to consider in the schedule of the renewal batch process. Some of these factors are:
• Frequency – Suppose you have a batch process that runs every Sunday. A renewal that could start on Wednesday
will not start until the batch process runs several days later on Sunday.
• Start time – The batch process starts at 11 p.m. on Sunday, and it may take several hours to run. Therefore, the
batch process starts some renewals on Sunday and others early Monday morning.
• Postal service – The renewal paperwork depends upon the working days of the postal service. Although the
renewal was started on Sunday, the postal service picks up the renewal paperwork on Monday.
See also
• Configuration Guide

Working with pre-renewal directions

Create a pre-renewal direction
About this task
There can only be one pre-renewal direction on a policy.
Creating or changing a pre-renewal direction adds an entry to the history of the policy.

Procedure
1. Navigate to a policy.
2. Select Pre-Renewal Direction from the Actions menu to view the Pre-Renewal Direction screen. If the policy has no
pre-renewal direction, then the Details in the pre-renewal direction screen is initially blank.
3. To create a pre-renewal direction or modify an existing one, click Edit.
4. Select a direction from the drop-down list and set the security level which controls who can view it.
In the base configuration, you can specify that the renewal:
• Ends in non-renewal
• Ends in not taken
• Be referred to a customer service representative, underwriter, or underwriter assistant
5. If you selected a non-renew direction, click Add in Selected Non-Renewal Explanations to add a non-renewal
explanation.
See also
• Configuration Guide

View, edit, or delete an existing pre-renewal direction

Before you begin
“Create a pre-renewal direction” on page 107

Renewal policy transaction 107

Guidewire PolicyCenter 10.2.3 Application Guide

About this task

You can view, edit, or delete a pre-renewal direction on a policy.

Procedure
1. In this example, navigate to a policy that has a pre-renewal direction.
2. Click the Summary link under the Tools menu to display the Policy Summary screen.
In the Details listview, a link to the pre-renewal direction appears under This policy has pre-renewal direction.
3. Click the pre-renewal direction link view the pre-renewal direction on the Pre-Renewal Direction for Policy Term
screen.
From this screen you can Edit, Delete, or View Notes on the pre-renewal direction.

Delete a pre-renewal direction

About this task
Pre-renewals can be removed.

Procedure
1. Navigate to a policy.
2. Navigate to the Summary screen as in the previous example.
3. Click the Pre-Renewal link. The Pre-renewal Direction for the Policy Term screen appears.
4. Click Delete.

Working with renewals

Create a manual renewal
About this task
This example is useful if you need to create a renewal before its scheduled time and need to make changes to the
policy.

Procedure
1. Navigate to the policy you wish to renew.
2. From the Policy Summary screen (or any screen in the policy), select Actions > Renew Policy. A dialog box asks
you to confirm your selection and the renewal wizard begins.
3. Advance to the Policy Info screen.
4. Click Edit Policy Transaction. Make the required changes to the policy.
5. At this point, you can click one of the following:
• Quote – You must generate a quote. If the policy had not been edited, the renewal wizard would perform the
quote step and obtain a new premium.
• Save Draft – You can return to work on it at a later time.
• Close Options > Withdraw Transaction – You can withdraw the renewal.
• Close Options > NonRenew – The policy is not renewed, and PolicyCenter asks you to give a reason.
• Close Options > Not Taken – Use if the insured declines to renew the policy.
6. For this example, click Quote.

108 Renewal policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

7. On the View Quote screen, first review the quote and the policy in general.
8. Now you have various options for binding or closing the policy.
9. Renew the policy by selecting Bind Options > Renew.
10. Select a Renewal Code on the Renewal Data Entry popup:
• <none>
• Renew - account consideration
• Renew - assigned risk
• Renew - good risk
• Renew - legal requirement
• Renew - producer consideration
You can use this field to document renewal exceptions. For example, all values except Good Risk indicate that
the policy is being renewed because of market or statutory compulsion. The default would typically be Good
Risk. You can configure the Renewal Data Entry typelist values to meet specific needs or customize reason codes.

Create a renewal from a batch process

About this task
Creating a renewal from a batch process is the most common way for renewals to be created. The renewal batch
process looks for policies that expire in X days (the default is 180 days). Then the Policy Renewal plugin further
evaluates each policy and determines whether to creates a renewal for that policy. A system administrator can also run
this batch process outside of its schedule.
The frequency of the batch process is a factor in when a renewal starts. For example, you can have a batch process that
runs every Sunday. Renewals that could start on Wednesday will not start until the batch process runs on Sunday,
several days later.
Note: You must have the View BatchProcess tools page permission. The code for this permission is
toolsBatchProcessview. The Tools View role has this permission.

Procedure
1. In PolicyCenter, type Shift + Alt + T to display ServerTools.
2. Select the Batch Process Info link in the left sidebar.
The Batch Process Info screen contains useful information about the batch process, including:
• Current status
• The last time it ran
• The time of the next scheduled run
• The schedule
The Cron-S M H DOM M DOW column header stands for seconds, minutes, hours, day of month, month, and day
of week.
The * means every. The ? is typically only on day of week or day of month and means, “I do not care when it
runs”.
3. Find Policy Renewal Start under the Batch Process column.
4. Click Run under the Action column to start the batch process immediately.
See also
• The scheduler-config.xml file to see the frequency of the batch process. You can view this file by navigating to
configuration > config > scheduler in Studio.

Renewal policy transaction 109

Guidewire PolicyCenter 10.2.3 Application Guide

• The config.xml file for the RenewalProcessLeadTime lead time parameter. This parameter contains the number of
days before the policy expires and renewal processing starts. You can view this file by navigating to configuration >
config in Studio.
• Configuration Guide

View your renewals

About this task
The My Renewals screen displays a renewal if:
• You have been assigned a role on that renewal.
• You have or had an activity assigned to you on that renewal.

Procedure
1. Go to the Desktop and select My Renewals.
2. You can filter your search by selecting from the drop-down menu.

Create multiple versions of a renewal

About this task
You can create multiple versions of a renewal to help you and the insured agree on the policy contents. For example, in
a personal auto policy, the applicant may select different levels of coverages to see the difference in premium.

Procedure
1. Select New Version in the renewal wizard to create a new version of the renewal where you can make changes and
obtain a different quote.
2. Under the Tools menu, click Policy Versions to display the Policy Versions screen where you can:
• Rename your version (for convenience).
• Click Diff to compare the differences between two versions.
• Make one version the selected version.
• Withdraw a version, while keeping the other versions.
See also
• “Create a manual renewal” on page 108 for an example.

110 Renewal policy transaction

chapter 16

Cancellation policy transaction

A cancellation policy transaction is the process of voiding a policy while it is in force. Initiated either by the insurer or
the policyholder, it results in the policy:
• Being canceled
• Remaining in force because the cancellation was rescinded
An example of a cancellation policy transaction is when the policyholder does not pay the premium, so the insurer
begins the cancellation process. The policyholder receives notice of a pending cancellation in the mail, contacts the
producer, and explains that there was a billing mix-up and sends another payment to the producer. The policy was in
the process of being canceled but had not completed cancellation. Upon receipt of payment, the insurer rescinds the
cancellation, and PolicyCenter withdraws the cancellation.
Another example of cancellation is when the insurer cancels the policy. The insurer issues a liability policy to a
restaurant for two locations with 10% liquor sales. An audit reveals that the restaurant actually has four locations with
80% liquor sales. The insurer begins the cancellation process and, after a set number of days, the policy is canceled.
The insured can initiate a cancellation. For example, the insured calls to cancel their businessowners policy because
they are no longer in business.
A cancellation can be generated and rescinded automatically. For example, a billing system can initiate a cancellation
for non-payment of premiums or rescind a cancellation after receiving payment.
A canceled policy can be reinstated. For more information, see “Reinstatement policy transactions” on page 129.
Note: In PolicyCenter, the user interface uses the term policy transaction to refer to submissions, policy
changes, and other policy transactions. Policy transactions are implemented as jobs in the data model, and
referred to as jobs in PCF files, Gosu classes, and other configuration files. Therefore, the configuration
documentation refers to policy transactions as jobs.
See also
• Configuration Guide

Overview
A policy cancellation ends the policy contract. A flat cancellation cancels the policy as of the policy effective date and
voids the contract. Other cancellations are effective after the policy effective date but prior to the policy expiration
date. The contract ends midterm.
A cancellation policy transaction can be started either manually through the policy file or programmatically. The
selected source and reason determine if premium will be calculated pro rata or with penalties. The selected source and
reason also determine the date on which the policy cancellation completes.
Cancellation policy transaction 111
Guidewire PolicyCenter 10.2.3 Application Guide

The source of a cancellation can be either the insured or the insurer. You can configure the cancellation reasons based
on your business needs. In the default configuration, some of the reasons for cancellation by insured are:
• Policy not taken
• Out-of-business
In the default configuration, some of the reasons for cancellation by the insurer are:
• Fraud
• Failure to comply with terms and conditions
• Underwriting reasons
• Policy to be rewritten or replaced by company
• Or more commonly, non-payment
The source, reason, and effective date affect the premium calculation method. Premium calculation methods are:
• Pro rata – The insurer bills the policyholder for the time that the policy that was already in effect.
• Short rate – The insurer charges the policyholder a penalty in addition to the pro rata amount.
• Flat – The insurer refunds the total amount of the policy.

Scheduling a cancellation versus cancel now

In the user interface, you have the option to select Bind Options > Schedule Cancellation or Cancel Now.
If you choose Schedule Cancellation, the cancellation is completed as of the cancellation effective date. The cancellation
source, reason, and policy type determine the default cancellation effective date.
If you choose Cancel Now, PolicyCenter sets the cancellation completion date to the current date and issues the
cancellation. Once the cancellation is issued, you cannot rescind it. If you want to undo the cancellation, you have to
reinstate the policy. Although the cancellation is completed when the user selects Cancel Now, the cancellation does not
go into effect until the cancellation effective date.
Until a cancellation is completed, it is considered an open cancellation.
See also
• Configuration Guide

Default cancellation effective date

The insurer usually bases the default cancellation effective date on the type of cancellation, the regulations of the
governing jurisdiction, and the line of coverage that is being canceled. For example, two policies in the same
jurisdiction may require different notification periods due to differing lines of business. A commercial property policy
may have different notification periods in adjacent jurisdictions. Non-payment may require only 10 days notification in
one jurisdiction, but 30 days in another. In very limited conditions, the insurer can also cancel immediately.
The system allows the user to override the default cancellation effective date in all circumstances, except in the case of
a flat cancellation. For example, in a cancellation initiated by the insurer, suppose that at least 30 days must elapse
before the cancellation becomes effective. The default cancellation effective date reflects the regulatory requirements
for notifying a customer that their policy is being canceled. Therefore, the user can override the cancellation effective
date only by moving it further out, allowing more days to elapse before the cancellation becomes effective. In most
cancellations initiated by the insured, the cancellation effective date can be moved further in or further out. The user
can never override the cancellation effective date for a flat cancellation because the whole policy term has been
canceled. The user must have the Cancellation override effective date permission. The code for this permission is
cancelovereffdate.

The following table shows how some choices are configured in the default installation.

112 Cancellation policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

Source Reason Refund method Default cancellation effective date

Insured Insured’s request- (finance co. nonpay) Pro rata System’s current date*

Insured Insured’s request- (N.O.C.) Short rate System’s current date*

Insured No employees/operations Pro rata System’s current date*

Insured Out of business/sold Pro rata System’s current date*

Insured Policy not taken Flat The date the policy went into effect.

Insurer Cancellation of underlying insurance Pro rata Calculated based on jurisdiction and line of business.*

Insurer Condemned/unsafe Pro rata Calculated based on jurisdiction and line of business.*

Insurer Non payment Pro rata Calculated based on jurisdiction and line of business.*

Insurer Policy rewritten (mid-term) Pro rata System’s current date*

Insurer Policy rewritten or replaced (flat cancel) Flat The date the policy went into effect.

Insurer Fraud Pro rata Calculated based on jurisdiction and line of business.*

Note: “*” indicates that the user can override the default cancellation effective date.
See also
• Configuration Guide

Changing a cancellation
There are a limited number of ways that you can change an existing cancellation. You can change the cancellation
effective date of a policy. You can change the reason description.
You can make other types of changes to an open cancellation such as changing the source or reason. You can make
these changes by withdrawing or rescinding the cancellation, or by scheduling an additional cancellation on the policy.
If the cancellation notice has not yet been sent, you can withdraw the cancellation. If the cancellation notice has already
been sent, you can rescind the cancellation. If the cancellation has already completed, you can reinstate the policy as
described in “Reinstatement policy transactions” on page 129.

Canceling a policy at an earlier effective date

Because of regulatory requirements, you usually cannot change the cancellation effective date of an already scheduled
cancellation to an earlier effective date. However, you can create a new cancellation on the same policy with an earlier
effective date if the regulatory requirements associated with the reason for that cancellation allow it. For example, you
have a policy that has an open cancellation for non-payment. The insured calls and asks to cancel the policy
immediately. You create another cancellation on the policy, select Insured as the Source and select a Reason. On the
Confirmation screen, select Cancel Now. This cancellation preempts all open cancellations on the policy. When you
bind a cancellation, PolicyCenter withdraws existing cancellations.
If a policy has a completed cancellation, you can also cancel that policy on an earlier effective date. There can be
multiple open scheduled cancellations (for different reasons) on the same policy.

Canceling a policy on the same or later effective date by changing the cancellation
There are several reasons for changing the cancellation effective date. For example:
• A policy holder receives cancellation notices stating that their policy will be canceled unless they submit payment.
The policy holder contacts the insurer and asks for a few extra days to reestablish the policy by submitting
payment. The agent reschedules the cancellation by adding three days to the cancellation effective date.
• A catastrophe takes place in a certain region The insurer decides to give an extension on scheduled cancellations for
all policies in or near the catastrophe. The insurer gives the extension to policies with a cancellation effective within
a certain date range.

Cancellation policy transaction 113

Guidewire PolicyCenter 10.2.3 Application Guide

When you change the cancellation effective date, PolicyCenter sends a replacement cancellation notice. (You must
configure this in PolicyCenter.)
If you have the Cancellation reschedule permission, you can change the cancellation effective date on an open
cancellation. The code for this permission is cancelreschedule. In the base configuration, underwriters and
underwriter supervisors have this permission. An open cancellation is a cancellation that has not completed.
You can change the following fields on an open cancellation:
• Reason Description – You can provide a new description.
• Cancellation Effective Date – You can move the effective date.
You cannot change the following fields:
• Source
• Reason
• Refund Method
The cancellation effective date can be moved to a date on or after the earliest allowable cancellation effective date. The
earliest allowable cancellation effective date continues to be based on the date the cancellation was originally
scheduled. It is not based on the date that you make the change. Because this is just a change to the policy transaction,
the original restrictions on the cancellation effective date remain the same. For more information, see the Configuration
Guide.

Other ways to cancel a policy on the same or later effective date

It is possible to change the cancellation effective date to the same or a later effective date even if you do not have the
Cancellation reschedule permission. If you have an open cancellation on a policy, create a new cancellation and issue it
by selecting Cancel Now. (When you issue a cancellation, PolicyCenter withdraws existing cancellations.)
If the cancellation has already completed, but you want to cancel the policy at a later effective date, you can reinstate
the policy, then cancel it. To learn about reinstatement, see “Reinstatement policy transactions” on page 129.

Rescinded versus withdrawn cancellations

Rescinded and withdrawn cancellations have identical results: the outcome is that the policy remains in force.
However, rescinded and withdrawn cancellations are two different actions. A cancellation may be withdrawn at any
time before cancellation notices are sent. If notices have already been sent, then the cancellation must be rescinded so
that rescindment notices can be generated. One exception is if multiple cancellations were started for the same policy;
if one of them completes successfully, then all the others are withdrawn. This exception occurs because the policy did
get canceled, so no rescind notices need to be sent. Having different statuses for rescind and withdrawal can also be
useful for statistical analysis and reporting.

Cancellation with pending renewals

If you cancel a policy that has a future renewal, the renewal is handled in various ways depending upon whether the
renewal is bound.

Renewal is bound
If the policy has a future renewal that is bound, start a cancellation for the bound renewal term.

Renewal is unbound
If the policy has a future renewal that is not bound, the renewal is handled in the following ways:
• If renewal documents have not been sent, then withdraw the renewal. This removes the renewal job and all policy
periods associated with the renewal.

114 Cancellation policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

• If renewal documents have been sent and there is enough time to send non-renewal documents, then withdraw the
renewal. This withdraws the selected version of the policy period and blocks other policy periods in the renewal job
through an underwriting issue.
• If renewal documents have been sent and there is not enough time send non-renewal documents, then block the
renewal. This block all policy periods in the job with an underwriting issue.

Cancellation general steps

The following diagram shows the basic steps in a manual cancellation in the default configuration of PolicyCenter.
Your business requirements and lines of business can alter the process. For example, the steps may differ slightly
between personal and commercial lines.

Cancellation General Steps

The carrier or insured wants

to cancel the policy

Begin cancellation.

Enter cancellation
information.

Schedule or do the
cancellation now.

The steps are sequential:

1. The insurer or insured wants to cancel the policy: The insured contacts the insurer to cancel the policy, or the
insurer decides to cancel the policy.
2. Begin cancellation: The user locates the policy and selects Cancel Policy in the user interface.
3. Enter cancellation information: The user enters the Source, Reason, Refund Method, and Cancellation Effective
Date.

Cancellation policy transaction 115

Guidewire PolicyCenter 10.2.3 Application Guide

4. Schedule or do the cancellation now: If the user selects Schedule Cancellation, the status changes to Canceling.
When the Transaction Effective Date is reached, the status changes to Canceled. If the user selects Cancel Now, the
cancellation is bound and the status is Canceled.

Working with cancellations

Cancel a policy
Procedure
1. Navigate to a policy and select Cancel Policy from the Actions menu.
2. Enter the following information:
a) For Source, select Insured or Insurer.
b) Select a Reason from the drop down list.
The list varies depending on the selected Source.
c) Optionally, enters a Reason Description for canceling the policy.
d) Select a refund method.
Certain source and reason choices result in a default refund method.
e) Select a different date or accept the default cancellation effective date.
The reason also determines the default cancellation effective date. The system defaults to the earliest
allowable date, based on the cancellation reason. The regulations for each jurisdiction govern the earliest
allowable date. In most cases, you may add additional days.
You can configure this in CancellationEnhancement.gsx and in the notifcationconfigs.xml system table.
See the Configuration Guide.
3. Click Start Cancellation.
4. On the Confirmation screen, select Bind Options > Cancel Now or Schedule Cancellation.
• If you select Cancel Now, PolicyCenter sets the cancellation process date to the current date, and soon
completes the cancellation after which the cancellation cannot be rescinded. PolicyCenter begins the
cancellation process immediately. PolicyCenter sends a notification to the document production system to
prepare and mail the appropriate notifications.
To undo the cancellation, you must reinstate the policy.
• If you select Schedule Cancellation, the cancellation process date defaults to the cancellation effective date,
which is set by the system. See “Default cancellation effective date” on page 112. If you select Schedule
Cancellation, then PolicyCenter might notify the document production system to prepare and mail the
appropriate notifications. PolicyCenter schedules the cancellation, but you have the option to rescind it before
the cancellation effective date.
The workflow waits until the system time is equivalent to the CancelProcessDate before the cancellation
completes. For example, if you select Insured as the source with a reason Out of business, then the default date
is one day after the date you started the cancellation. What happens is that the CancelProcessDate is set to
the Cancellation Effective Date.
If the policy cancellation is scheduled but has not gone past its cancellation process date, you can rescind the
policy.

116 Cancellation policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

Rescind a cancellation
About this task
Rescinding a cancellation on a policy changes the current status of the cancellation to rescinded, and the policy remains
in force. PolicyCenter keeps a record of this activity so that you can see rescinded cancellations. Follow these steps to
rescind a cancellation:

Procedure
1. Navigate to a policy with a cancellation pending.
Policies awaiting cancellation display The Policy is Pending Cancellation on the Policy Summary screen.
2. From the Actions menu, select Rescind Cancellation then select the cancellation.
The Confirmation screen appears and the status is Canceling.
3. Select Close Options > Rescind Cancellation.
The policy remains in force. You can view the rescinded cancellation in the Policy Transactions screen.

Change the cancellation effective date in a quoted cancellation

Before you begin
Follow the steps in “Cancel a policy” on page 116 until you arrive at the Confirmation screen.

About this task

You must have the Cancellation reschedule (cancelreschedule) permission to change the cancellation effective date
in an open cancellation.

Procedure
1. Click Back to return to the Entry screen.
2. Click Edit Policy Transaction.
You can now edit the Reason Description and Cancellation Effective Date.

Change the cancellation effective date in a scheduled cancellation

Before you begin
Follow the steps in “Cancel a policy” on page 116 and select to schedule a cancellation in the future.

About this task

You must have the Cancellation reschedule (cancelreschedule) permission to change the cancellation effective date
in an open cancellation.

Procedure
1. Navigate to a policy with a cancellation pending.
Policies awaiting cancellation display a message that the policy is pending cancellation. The policy Summary
screen displays Pending Policy Transactions.
2. Click the Transaction # link for the cancellation.
3. Click Edit Policy Transaction on the Confirmation screen.
On the Entry screen, you can edit the Reason Description and Cancellation Effective Date.

Cancellation policy transaction 117

Guidewire PolicyCenter 10.2.3 Application Guide

118 Cancellation policy transaction

chapter 17

Policy change transaction

A policy change transaction is a modification made to a policy while it is in-force. The types of changes that might
happen to a policy mid-term include:
Common personal auto examples include:
• Adding another person to your policy as a driver
• Increasing your deductible so that you have a less expensive premium
• Adding or removing a vehicle and changing some of the vehicle coverages
Common workers’ compensation examples include:
• Adding or changing a location
• Updating the number of employees
• Updating the basis
Common businessowners examples include:
• Changing your business location
• Changing the type or amount of coverage
Note: In PolicyCenter, the user interface uses the term policy transaction to refer to submissions, policy
changes, and other policy transactions. Policy transactions are implemented as jobs in the data model, and
referred to as jobs in PCF files, Gosu classes, and other configuration files. Therefore, the configuration
documentation refers to policy transactions as jobs.
The main purpose of a policy change is to modify one or more elements of a policy. For example, you can use a policy
change to change a coverage, exposure, or location. You can add a driver or change the terms of payment. Policy
changes occur fairly regularly.
For example, three months into the policy period, the insured contacts the producer to add a second vehicle to the
insured’s personal auto policy. The producer finds the policy, makes the requested changes to it, requotes the policy,
and then binds it. Two months later, the producer receives another call from the insured to have another family member
added to the policy as a second driver on the first vehicle. Again, the producer makes changes. This type of example
represents the majority of change policy transactions in PolicyCenter: adding, removing, or changing coverages and
coverables, or changing coverage terms. These changes usually have an impact on the premium.
There are other types of less commonly used policy changes, such as out-of-sequence policy changes and preemption.
See “Handling out-of-sequence policy transactions in a policy change” on page 123 and “Using preemption in a policy
change” on page 123 for more information.

Policy change transaction 119

Guidewire PolicyCenter 10.2.3 Application Guide

See also
• Configuration Guide

Using the Policy Review screen to verify changes

In PolicyCenter, you can see your policy changes prior to binding, by viewing the Policy Review screen. Use this screen
to review your changes and to verify that there are no conflicts. The contents of this screen are dynamic, and it
displays:
• Changes you have made
• Conflicts that you need to resolve before binding (if the policy change is out-of-sequence)
• Conflicts related to preemption
Although the Policy Review screen displays changes to the policy, view the Quote screen to see how your changes affect
the premium:
• The Cost Change Detail tab displays the transaction cost (offsets and onsets) resulting from the policy change.
• The Policy Premium tab displays the breakdown of the premium for the entire policy period.

Editing the effective date of a policy change

You can edit the effective date of an unbound policy change by selecting Actions > Edit > Effective Date. However, after
the policy is bound and issued, you can no longer edit the effective date.
Editing the effective date of a policy change is often useful in personal lines of business. A policyholder calls to make a
policy change. The agent starts a policy change, enters new policy information and generates a quote. Later, the
customer calls requesting a change to the effective date of the policy change.
For example, in a personal auto policy, the policyholder may not know exactly the effective date of a policy change for
the purchase of a new vehicle. The policyholder calls the insurance company to determine the cost of coverage for the
new vehicle. The agent starts a policy change but does not complete it. The policyholder initially expects to receive the
vehicle on a certain date (February 1), so the agent enter February 1 as the effective date of policy change. However,
the vehicle actually arrives two weeks late (February 15).
The agent accesses the policy change and changes the effective date. The agent can also make other changes to the
policy such as adding additional coverages. The agent quotes the policy. If the policyholder is satisfied, the agent binds
and issues the policy.
Note: When you change the edit effective date in a policy change, everything that existed on the policy prior to
that change will be on the policy after that change. In your customization, there may be cases where you need to
modify or remove what is on the policy. In particular, underwriting issues might have applied on the earlier
effective date but are no longer applicable on the new effective date. For an example, “Underwriting issues and
editing the effective date in policy change” on page 122.

Multi-version policy change

When you select Actions > Edit > Effective Date, the action applies to all versions of a multi-version policy change.
PolicyCenter warns you that all versions will have their effective date modified, and all quotes will be invalidated. If
any of the versions cannot have the effective date modified for any reason, then no version can have it modified.

New effective date in policy change must be within the same slice and policy
term
When editing the effective date of a policy change, the new effective date must not cross any slice boundaries. That is,
the new effective date must not cross over the effective date of any other transactions. It must also be within the same
policy term.
For more information about slices, see “Slice mode and window mode overview” on page 202.

120 Policy change transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

Example that does not cross slice boundaries

The following example of a change to the effective date does not cross slice boundaries.
1. The agent creates a new personal auto policy with one vehicle. The policy has a six month term from January 1
until July 1. The policy has one slice from January 1 until July 1.
2. On February 1, the policyholder calls to change the coverage levels on his vehicle. The effective date of the
policy change is February 1. The agent binds the policy change. The policy now has two slices. The first slice is
from January 1 to January 31. The second slice is from February 1 to July 1.
3. On March 1, the policyholder calls to say that he is buying a new vehicle. He expects to receive the vehicle on
March 15 (in the second slice). He wants to know the cost of adding the vehicle to his policy. The agent starts a
policy change with the expected delivery date. The agent gives the policyholder a quote. The agent tells the
policyholder to call with the vehicle identification number (VIN) once he has actually received the vehicle. The
VIN is required to bind the policy change. The policy change is quoted but not bound. The policy still has two
slices.
4. The policyholder calls on March 25, saying that he has received the vehicle. The agent adds the VIN and changes
the effective date of the policy change to March 25. This change to the effective date is allowed because the date
is within the second slice. The agent binds the change.
The following illustration shows the slice boundaries in this example.

Changing the effective date without crossing a slice boundary

01/01 07/01
effective time

01/01 02/01 03/15 03/25 07/01

On January 1, policyholder opens a policy

from January 1 to July 1.
The policy is bound and has one slice.
1 vehicle

On February 1, the policyholder changes

the coverage levels on his vehicle. The
change is bound. The policy has two 1 vehicle 1 vehicle, new coverage levels
slices.
On March 1, the policyholder adds a new
vehicle expected to arrive March 15 (in
the second slice). This policy change is
not bound, therefore, there are still two 1 vehicle coverage new vehicle + coverage
slices. slice 1 slice 2

On March 25, the policyholder reports

that the vehicle arrived today. The new
effective date of the policy change is
within the second slice. The change is 1 vehicle coverage new vehicle + coverage
bound. The policy has three slices.

Unbound policy transaction

Example that crosses slice boundaries

The following example crosses slice boundaries. Therefore, it is not allowed.
1. The agent creates a new personal auto policy with two vehicles. The policyholder is the primary driver of the first
vehicle, and his wife is the primary driver of the second. The policy has a six month term from January 1 until
July 1.
2. The policyholder calls on February 1 to report that the lease on the second vehicle expires on March 17. He is not
going to renew the lease. The agent starts and binds a policy change. The policy has two slices. The first slice is
from January 1 through March 16. The second slice extends from March 17 through July 01.

Policy change transaction 121

Guidewire PolicyCenter 10.2.3 Application Guide

3. On March 1, the policyholder calls and says that he is buying a new vehicle. He expects the vehicle to arrive on
March 15. He wants to know the cost of adding it to his policy. His wife will be the primary driver of the new
vehicle.
4. The agent starts a policy change with the expected delivery date. The agent gives the policyholder a quote. The
agent tells policyholder to call back with the VIN once he has actually received the car. The VIN is required to
bind the policy change. The policy change is within the first slice. The policy change is quoted but not bound.
Because the policy change is not bound, the policy still has two slices.
5. The policyholder calls on March 25, and says he has received the vehicle and has the VIN. The effective date of
the policy change is not within the first slice. Therefore, the effective date of the policy change cannot be changed
to that date. The agent must withdraw the current policy change and start a new one with the same information.
The following illustration shows the slice boundaries in this example.

Changing the effective date to cross a slice boundary is not allowed

01/01 07/01
effective time

01/01 03/15 03/17 03/25 07/01

On January 1, policyholder opens a policy

from January 1 to July 1.
The policy is bound and has one slice.
2 vehicles

On February 1, the policyholder calls to

remove the second vehicle effective
March 17. The policy change is bound. 2 vehicles remove 2nd vehicle
Therefore, there are two slices. slice 1 slice 2

On March 1, the policyholder calls to add

a new vehicle expected to arrive March
15 (in the first slice).
2 vehicles new Remove 2nd vehicle
slice 1 slice 2
On March 25, the policyholder reports
that the vehicle arrived today. The new
X
effective date of the policy change is not
within the first slice. Therefore, the 2 vehicles 1 old & 1 new vehicle
effective date of the policy change slice 1 slice 2
cannot be changed to that date.

Unbound policy transaction

Underwriting issues and editing the effective date in policy change

In general, when you edit the effective date of a policy change, PolicyCenter preserves existing underwriting issues and
approvals. There is some variance in that way that underwriting issues are handled when you edit the effective date of a
policy change.

Approvals valid for a specific amount of time

In an unbound policy change, a new underwriting issue may be approved for a specific amount of time. If the effective
date changes, PolicyCenter recalculates the expiration date of the approval based on the new effective date.
For example, an underwriter approves an issue for three years:
• Policy change effective date: 02/01/2010
• Approval expires: 02/01/2013
The agent changes the effective date, and PolicyCenter adjusts the underwriting approval expiration:

122 Policy change transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

• Policy change effective date: 03/01/2010

• Approval expires: 03/01/2013

Approvals with expiration dates

When the user changes the effective date of a policy change, PolicyCenter reevaluates approvals that have an
expiration date. For the approval to remain in effect, the new effective date must be before the expiration date of the
approval. An approval that had expired on the original date must be reevaluated to determine if it is valid on the new
date.
For example, an underwriting issue is approved because the policy change effective date is sooner than the approval
expiration date:
• Original policy change effective date: 02/01
• Approval expiration date: 02/05
After the effective date is changed, the approval is no longer in effect:
• New Policy change effective date: 02/08
• Approval expiration date: 02/05

Approvals invalid from next edit

Editing the effective date of a policy change expires an approval if the approval becomes invalid from the next edit.

Rule sets, Gosu code, and editing the effective date

In your custom rule sets and Gosu code for handling underwriting issues and approvals, editing the effective date of a
policy change might require special handling by that code.
For example, assume the code of an underwriting issue rule creates an underwriting issue if the effective date is before
June 1, 2010. An agent creates a policy change effective on May 1, 2010 that triggers that rule to create an
underwriting issue. Later, the agent changes the effective date to June 2, 2010. Because the effective date is after June
1, the underwriting issue is now invalid. PolicyCenter automatically keeps that underwriting issue. The rule set or Gosu
code needs to handle removing it.

Handling out-of-sequence policy transactions in a policy

change
Out-of-sequence policy transactions are policy transactions with an effective date is before the effective date of a
previous policy transaction on the same policy. Insurers sometimes call these situations out-of-sequence endorsements.
PolicyCenter uses the term out-of-sequence.
A policy can have changes with effective dates that are not sequential. Sometimes this is not an issue. However, there
are other times that multiple policy transactions can conflict with each other. PolicyCenter handles these conflicting
policy transactions by first recognizing them and second, by allowing you to reconcile any conflicts that result. Policy
transactions conflict when a policy change has a transaction date later than another policy transaction, but an effective
date earlier than that other policy transaction.
See also
• See “Out-of-sequence jobs” on page 213

Using preemption in a policy change

A preemption can occur if two policy transactions are open on a policy at the same time. The first policy transaction
that binds preempts the second one. PolicyCenter handles preemptions by merging the changes made in the preempting
policy transaction with the changes made in the preempted policy transaction. The user interface provides you with a

Policy change transaction 123

Guidewire PolicyCenter 10.2.3 Application Guide

way to merge these changes into the preempted policy transaction. Preemptions are not unique to policy changes; they
also occur in audits, cancellations, reinstatements, and renewals.
See also
• See “Preempted jobs” on page 215

Policy change general steps

The following flow diagram shows the basic steps to create a policy change. These steps are for the default
configuration of PolicyCenter. Your business requirements and even lines of business can alter the process. The steps
may differ slightly between personal and commercial lines and in how you access policy change screens.

124 Policy change transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

Policy Change General Steps

A policy needs to be
changed.

Find the policy, make your

modifications.

Review the policy.

Obtain a quote.

Edit and re-quote, if

necessary.

Bind the policy.

The steps are sequential:

1. A policy needs to be changed: An insured wants to change some information on the policy.
2. Find the policy, make your modifications: After locating the policy, start the policy change to make the requested
edits.
3. Review the policy: Review your changes on the Policy Review screen to verify that the changes are correct.
4. Obtain a quote: Like a submission, the policy change transaction must be quoted before you can bind it because
the changes may affect the price of the policy.

Policy change transaction 125

Guidewire PolicyCenter 10.2.3 Application Guide

5. Edit and re-quote, if necessary: If the insured requests quotes for multiple policy change scenarios, then repeat the
prior steps (using multiple versions). Review and compare the quotes to find the policy change that the insured
prefers.
6. Bind the policy: Finish the policy change transaction by binding it.

Working with policy changes

IMPORTANT: Since the policy change process for any insurer can be configured based on business
requirements, all discussions apply to the default application except as noted.

This topic explains, from a user’s point of view, how to modify a policy. The ways that you can start a policy change
transaction are:
• Manually through the user interface in PolicyCenter by selecting Change Policy from the Actions menu.
• Externally using the Policy Change API which allows you to set policy transactions to run manually or
automatically. A policy transaction can be started, quoted, and bound automatically. See the Configuration Guide
for more information.
With any policy change transaction, certain steps occur:
• Policy changes must be quoted before being bound and are subject to validation at the quotable level.
• Validation is run at the bindable validation level when attempting to bind the change. If validation fails with errors,
the process stops and stays in the previously quoted status. If validation fails with warnings, then PolicyCenter
stops the first time, but you can override the warnings by clicking Bind again.
• If the policy can be bound, then billing instructions are sent to an external billing system through the
IBillingSystemPlugin.
See also
• “Tools menu in policy file” on page 178

Create policy change

Procedure
1. Navigate to a policy and select Change Policy from the Actions menu.
2. Specify an effective date and optionally enter a description for the policy change.
Although optional, it is useful to provide a description for the policy change. Otherwise, the policy change can
only be identified by its effective date. If a policy has more than one policy change, it can be difficult to find a
particular policy change if effective date is the only way to distinguish them. This situation is particularly a
problem when multiple policy changes have the same effective date.
3. Make changes to the policy contract by using the policy change wizard links on the left of the screen.
4. Review changes made to the policy by selecting Policy Review.
This review identifies any additions, removals, or changes to the policy.
5. Since a change typically involves modifications to the exposures or coverages, you must select Quote to requote
the policy.
The tabs on the Quote screen provide different views of the financial impact of the policy change. View the
different cards on the Quote screen to see the financial impact of the policy change. The purpose of these cards is
to answer various questions an insured might ask when exploring the financial impact of a policy change. The
insured might ask, “How much will this cost me right now?” and “What is the total cost for this policy going to
be?”

126 Policy change transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

• Viewing the Policy Premium card itemizes the entire policy as it stands after the change. This information does
not distinguish between exposures and coverages previously on the policy and those just being added to (or
removed from) the policy.
• The Cost Change Detail card shows the transaction cost (offset and onset) resulting from the policy change.
6. After the policy change has been successfully quoted, you can:
• Edit and requote. To edit policy changes, you must have the viewpolchange and editpolchange system
permissions.
• Create a new version.
• Save the draft.
• Select close options.
7. Click Issue Policy to bind and issue the policy.
This action is similar to binding a submission. After binding, the change becomes a legal part of the contract as of
the change’s effective date.

Edit the policy change effective date

About this task
You can edit the policy change effective date in an unbound policy.

Procedure
1. Find a policy change that has not been bound and issued.
2. Select Actions > Edit > Effective Date.
The Policy Change Summary screen appears.
3. Modify the Effective Date and, optionally, the Description.
The effective date must be:
• Different that the current effective date.
• Within the current slice. See “New effective date in policy change must be within the same slice and policy
term” on page 120.
4. Click Next to advance to other screens in the policy change wizard. You can make other changes to the policy.
5. Click Quote or Save Draft.
6. Click Issue Policy if you wish to bind and issue the policy change. After you issue the policy, you are no longer
able to edit the effective date of the policy change.

Change the policy expiration date in a policy change

About this task

Follow these instructions if you need to change the policy expiration date in a policy change transaction.

Procedure
1. Navigate to the Policy Info screen.
2. In Policy Details, select Other from the Term Type drop-down menu to make the Expiration Date field editable.

Policy change transaction 127

Guidewire PolicyCenter 10.2.3 Application Guide

128 Policy change transaction

chapter 18

Reinstatement policy transactions

Reinstatements are a type of policy change that returns a canceled policy to in force status. The policy becomes in force
again as of the reinstatement date. The reinstatement removes the cancellation from the policy period. Hence, the
policy expiration date remains the same.
In a reinstatement policy transaction, you cannot reinstate with a lapse in coverage or change the policy expiration date.
To reinstate with a lapse in coverage, you must do a rewrite policy transaction. For more information, see “Rewrite
policy transactions” on page 133.
Note: In PolicyCenter, the user interface uses the term policy transaction to refer to submissions, policy
changes, and other policy transactions. Policy transactions are implemented as jobs in the data model, and
referred to as jobs in PCF files, Gosu classes, and other configuration files. Therefore, the configuration
documentation refers to policy transactions as jobs.
A reinstatement policy transaction can be started either manually in the PolicyCenter Policy File or programmatically.
From the policyholder’s perspective, a reinstated policy is no different than the original policy. However, PolicyCenter
tracks the reinstatement as a policy transaction.
Reinstatement has the following features:
• You can reinstate a canceled policy.
• The reinstated policy cannot have a lapse in coverage.
• You cannot make changes to the policy in a reinstatement.
• You cannot reinstate a canceled policy with a new expiration date.
See also
• Configuration Guide

Reinstatement general steps

The following diagram shows the basic steps in a reinstatement. These steps are for the default configuration of
PolicyCenter. You business requirements and even lines of business can alter the process. Steps may also differ slightly
between personal and commercial lines and in how you access the reinstatement screens.

Reinstatement policy transactions 129

Guidewire PolicyCenter 10.2.3 Application Guide

Reinstatement General Steps

The carrier wants to

reinstate a canceled policy

Begin reinstatement.

Enter reinstatement
information.

Obtain a quote.

Reinstate the policy.

The steps are sequential:

1. The insurer wants to reinstate a canceled policy: A previously insured party contacts the insurer and asks them to
reinstate a canceled policy.
2. Begin reinstatement: The user locates the canceled policy and selects Reinstate Policy in the user interface.
3. Enter reinstatement information: The user enters the reason and optional description, then selects Quote. The
reinstatement date is set to the cancellation date. The expiration date remains the same. The user cannot change
these dates.
4. Obtain a quote: The user obtains a quote for the reinstatement, then selects Reinstate.
5. Reinstate the policy: The policy is reinstated.

130 Reinstatement policy transactions

 Guidewire PolicyCenter 10.2.3 Application Guide

Working with reinstatements

Reinstate a policy
About this task
You can start a reinstatement from a canceled policy.

Procedure
1. Find a canceled policy and select Reinstate Policy.
The Reinstatement wizard displays the Start Reinstatement screen with the Effective Date of the reinstatement set
to the Cancellation Effective Date.
2. Enter a Reason, an optional Reason Description, and select Quote.
The Reinstatement wizard begins, and the Quote screen appears.
3. From the Quote screen, you can either edit, reinstate, withdraw, or print a quote.
a) Select Edit to edit the Reason Description field. You must select Quote to return the policy to quoted status.
However, the amount in the quote does not change.
b) Select Reinstate to reinstate the policy.
c) Select Withdraw Transaction to stop the process. The policy remains in canceled status. You can decide at a
later date to reinstate the policy.
d) Select Print Quote to print the quote.

Reinstatement policy transactions 131

Guidewire PolicyCenter 10.2.3 Application Guide

132 Reinstatement policy transactions

chapter 19

Rewrite policy transactions

Insurers must do a rewrite if they need to change the effective date of the policy or producer of record. Insurers cannot
change these in a policy change transaction.
Note: In a policy change, you can change the producer of service but not the producer of record. In a policy
change, you can modify policy information but the effective date must remain the same.
Insurers may choose to rewrite a policy when the policy has errors or significant changes. For example, the producer
reviews the policy documentation before it is sent out and notices that the name of the insured is misspelled. The
insurer can use a policy change to correct the name, however the name will be corrected in an addendum to the policy
but not in the policy itself. The insurer decides to do a full-term rewrite of the policy, which reissues the documentation
with the insured’s name spelled correctly. The policy rewrite is transparent to the insured because the insured never
receives the original policy and documentation.
Although significant changes to a policy can be done as a policy change, it may be preferable to do these as a rewrite.
For example, the insured calls and asks that the billing method be changed from agency to direct. The insurer makes
this change as a mid-term rewrite to simplify tracking of this change for both the insurer and the insured. Rewrite
reissues the policy documentation rather than sending an addendum, and the insurer creates a completely new policy.
Rewrite makes it easy to keep track of when the change occurred.
Note: In PolicyCenter, the user interface uses the term policy transaction to refer to submissions, policy
changes, and other policy transactions. Policy transactions are implemented as jobs in the data model, and
referred to as jobs in PCF files, Gosu classes, and other configuration files. Therefore, the configuration
documentation refers to policy transactions as jobs.
In the base configuration, the rewrite policy transaction allows a user to completely rewrite a policy. It creates a new
policy version that can still be tracked to the original submission. Rewrite does not appear as a menu option until a
policy has been canceled. The user must first manually cancel the policy.
Rewrite policy transactions are similar to submission policy transactions. However, rewrite can be configured
independently of submission, so they have separate user interface screens, wizard flow, permissions, and rules.
There are a few differences between the Policy Info screen in the rewrite wizard and the submission wizard. You can
change any or all of the policy information details. However, rewrite has a Boolean radio button which allows you to
assign a new policy number. If selected, then PolicyCenter assigns a new policy number when binding the rewrite;
otherwise the policy number remains the same. So from the policy holder’s perspective, they have received a
completely new policy, and both the newly rewritten policy and the original policy version still exist in PolicyCenter.

Change any policy information in a rewrite

In a rewrite you can change anything in a policy. In particular, rewrite allows you to change the producer of record and
the policy effective and expiration dates.
Rewrite policy transactions 133
Guidewire PolicyCenter 10.2.3 Application Guide

Full-term rewrite
A full-term rewrite replaces the original policy for the complete policy term. A full-term rewrite can have a lapse in
coverage.
Mid-term rewrite
A mid-term rewrite replaces a portion of the original term and allows you to rewrite the policy to the original policy
end date or to a new end date. A mid-term rewrite can create a lapse in coverage.
See also
• Configuration Guide

Rewrite general steps

The following flow diagram shows the basic steps in a rewrite. These steps are for the base configuration of
PolicyCenter. Your business requirements and even lines of business can alter the process. For example, the steps may
differ slightly between personal and commercial lines and in how you access rewrite screens.

Rewrite General Steps

The insurer or insured

wants to change an existing
policy.

Cancel existing policy

Rewrite canceled policy.

Generate a quote.

Bind the policy

134 Rewrite policy transactions

 Guidewire PolicyCenter 10.2.3 Application Guide

The steps are sequential:

1. The insurer or insured wants to change an existing policy: The insurer may have misspelled the insured’s name
(full term rewrite) or need to change the producer of record (mid-term rewrite).
2. Cancel existing policy: The user locates the policy and cancels it. If the user knows that the policy will be
rewritten, then they choose Policy rewritten (mid-term) or Policy rewritten or replaced (flat cancel) for the reason.
3. Rewrite canceled policy: The user makes changes to the policy. The user can move the effective date to a later
date, thus creating a lapse in coverage. The user can also change the expiration date.
4. Generate a quote: The user generates a quote for the rewritten policy.
5. Bind the policy: The user binds the newly rewritten policy.

Working with rewrites

Rewrite a policy
About this task
The rewrite process starts from a canceled policy.

Procedure
1. Navigate to a canceled policy.
The policy Summary screen appears.
2. From Actions menu, select Rewrite Full Term, Rewrite Remainder of Term, or Rewrite New Term.
If the cancellation reason was Policy rewritten or replaced (flat cancel), only Rewrite Full Term is available. For
other cancellations Rewrite Remainder of Term and Rewrite New Term are available.
If you select Rewrite Remainder of Term, you can make changes to the policy including the Effective Date and
Expiration Date. By default, Effective Date is set to the cancellation date. You can change Effective Date to a later
date but not an earlier date.
If you select Rewrite New Term, you can make changes to the policy including Term Type and Effective Date. By
default, Effective Date is set to the cancellation date and Expiration Date is set to Effective Date plus the term. You
can change Effective Date to a later date but not an earlier date.
Note: To create a lapse in coverage, change the Effective Date to a later date.
3. Make your changes to the policy, and then select Quote.
4. Select Issue Policy to issue the policy.

Approve, request changes, or decline a rewrite

About this task
An underwriter may choose to approve, request changes, or decline (by withdrawing) a rewrite. A user first cancels a
policy with the intent to rewrite it. Based on business rules, the user does not have the authority to complete the rewrite
because it needs underwriting approval. PolicyCenter sends the rewrite to the underwriter, and alerts the underwriter by
an activity.

Procedure
The underwriter reviews the rewrite and may choose to approve it or edit it then requote the policy.
• The underwriter selects Approve Options on the rewrite toolbar.
• The underwriter can also decline the rewrite by withdrawing the rewrite policy transaction.

Rewrite policy transactions 135

Guidewire PolicyCenter 10.2.3 Application Guide

PolicyCenter notifies the user of the underwriter’s action. The user can contact the policyholder and send the
appropriate documentation.

View rewritten policies

About this task
Rewriting a policy creates a new version of the policy.

Procedure
You can view all versions of the policy by going to the Account and viewing the Account File Summary screen.
The Policy Terms listview shows the original policy that was canceled, and the full-term rewrite of the policy that is
currently in force.

136 Rewrite policy transactions

chapter 20

Rewrite new account policy

transaction

In PolicyCenter, you can move a policy going forward to a new target account. The previous policy terms remain on
the initial account. For example, a young adult has a policy in his parent’s personal auto account. He graduates from
college, and wants to move his policy to his own account. The insurer cancels his policy, and rewrites it to his new
account.
When you rewrite policies to a new account, PolicyCenter creates a rewrite new account policy transaction for each
policy. This policy transaction takes data from an existing policy and creates a new policy with a new policy number in
the new account. You can only rewrite canceled or expired policies to a new account.
Note: In PolicyCenter, the user interface uses the term policy transaction to refer to submissions, policy
changes, and other policy transactions. Policy transactions are implemented as jobs in the data model, and
referred to as jobs in PCF files, Gosu classes, and other configuration files. Therefore, the configuration
documentation refers to policy transactions as jobs.
The rewrite new account policy transaction creates a completely new policy, but PolicyCenter treats the source policy
and the new policy functionally as one policy. Therefore, this policy transaction enforces the business requirement that,
even though the source and rewritten policy are on different accounts, the active policy periods may not overlap. This
business requirement is enforced throughout the life of both policies. If necessary, the active policy periods can have a
gap between them.
The rewrite new account policy transaction has similarities to both submission and a rewrite policy transactions.

Similarities to submission
• Results in a new policy with a new policy number.
• Provides a qualification step.
• Provides billing similar to a submission.

Similarities to rewrite
• Is based on an existing policy period.
• Effective dates cannot overlap with the policy period it is based on.
• May result in out-of-sequence conflicts. If the based-on policy has future slices, they are rewritten to the new
policy. The start of the rewrite new account policy transaction may be out of sequence in relation to these future
slices.
Rewrite new account policy transaction 137
Guidewire PolicyCenter 10.2.3 Application Guide

See also
• “Moving and rewriting policies between accounts” on page 386
• “Rewrite policies from one account to an existing account” on page 396
• “Split and spin-off policies” on page 172
• Configuration Guide

Restrictions to rewrite new account started on source policy

The rewrite new account policy transaction rewrites a source policy to a target policy. There are a number of
restrictions that apply to a rewrite new account policy transaction. Primarily, the restrictions prevent the target policy
from having an active term that overlaps with the source policy.
Note: While the rewrite new account policy transaction is open, no policy transactions other than audit can be
started on the source policy.

Rewrite to new account on or after expiration date

When you rewrite a policy to a new account, the effective date of the policy can occur on or after the expiration date of
the source policy. Policy transactions on the source policy have some restrictions.
In the illustration below, Account #1 is the source policy with an expiration date of January 1, 2020. Account #2 is the
rewritten policy with an effective date of January 1, 2020. The effective date of Account #2 can be a date on or after
January 1, 2020.

Rewrite to new account on expiration date

Account #1

January 1, 2018 January 1, 2019 January 1, 2020

Term A Term B

Account #2
January 1, 2021

Term C

The following table shows restrictions for policy transactions on the source policy.

Policy transaction Restriction

Submission Not applicable.

Policy Change Not allowed on and after the expiration date of the source policy.

Cancellation Not allowed on and after the expiration date of the source policy. Does not differ from the usual behavior.

Reinstatement The end of the term being reinstated cannot be after the cancellation date of the source policy.

138 Rewrite new account policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

Policy transaction Restriction

Rewrite Not allowed on and after the expiration date of the source policy. Therefore, you cannot rewrite this policy.

Renewal Not allowed on or after the expiration date of the source policy.

Audit Allowed.

Rewrite New Account Not allowed.

Rewrite to new account on cancellation date

When you rewrite a policy to a new account, the effective date of the policy can be the cancellation date of the source
policy. Policy transactions on the source policy have some restrictions.
In the illustration below, Account #1 is the source policy with a one year policy term starting on January 1. Account #1
is canceled, and has a cancellation date of July 1. Account #2 is the rewritten policy with an effective date of July 1 of
that same year.

Rewrite to new account on cancellation date

Account #1

January 1, /2018 January 1, 2019 January 1, 2020 January 1, 2021

Term A Term B Term C

July 1, 2019

Account #2
July 1, 2020

Term D

The following table shows restrictions for policy transactions on the source policy.

Policy transaction Restriction

Submission Not applicable.

Policy Change Not allowed on and after the cancellation date of the source policy.

Cancellation Not allowed on and after the cancellation date of the source policy. Does not differ from the usual behavior.

Reinstatement The end of the term being reinstated cannot be after the cancellation date of the source policy.

Rewrite Not allowed on and after the cancellation date of the source policy. Therefore, you cannot rewrite this
policy.

Renewal Not allowed on or after the cancellation date of the source policy.

Audit Allowed.

Rewrite New Account Not allowed.

Rewrite new account policy transaction 139

Guidewire PolicyCenter 10.2.3 Application Guide

Rewrite to new account on future date within the policy term

When you rewrite a policy to a new account, the effective date of the policy can be a future date within the canceled
policy term. Policy transactions on the source policy have some restrictions.
In the illustration below, Account #1 is the source policy with a cancellation date of July 1, 2020. Account #2 is the
rewritten policy with an effective date of October 1, 2020.

Rewrite to new account on future date within the policy term

Account #1

January 1, 2019 January 1, 2020 January 1, 2021 January 1, 2022

Term A Term B Term C

July 1, 2020

Account #2
October 1, 2020 October 1, 2021

Term D

The following table shows restrictions for policy transactions on the source policy.

Policy transaction Restriction

Submission Not applicable.

Policy Change Not allowed on and after the effective date of the rewritten policy (Term D).

Cancellation Not allowed on and after the cancellation date of the source policy. Does not differ from the usual behavior.

Reinstatement Not allowed on and after the cancellation date of the source policy because the reinstated period would
overlap the rewritten policy (Term D).
To reinstate the gap from 07/01/2011 until 10/01/2011:
1. Do a policy change on term B, and set the period end date to 10/01/2011, the effective date of the
rewritten policy.
2. Reinstate the policy.

Rewrite Not allowed on and after the cancellation date of the source policy because the rewritten policy overlaps
Term D or its successors.
To rewrite the gap from 07/01/2011 until 10/01/2011:
1. Do a policy change. Change the end date of Term B to 10/01/2011, the effective date of the rewritten
policy.
2. Rewrite the remainder of the term.

Renewal Not allowed on or after the effective date of the rewritten policy (Term D). Therefore, Term C cannot be
renewed.

Audit Allowed.

140 Rewrite new account policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

Policy transaction Restriction

Rewrite New Account Not allowed.

Rewrite to new account on a future date beyond the policy term

When you rewrite a policy to a new account, the effective date of the policy can be a future date beyond the policy
term and any pending renewals. Policy transactions on the source policy have some restrictions.
In the illustration below, Account #1 is the source policy with a cancellation date of July 1, 2020. Account #2 is the
rewritten policy with an effective date of March 1, 2025.

Rewrite to new account on future date beyond the policy term

Account #1

January 1, 2019 January 1, 2020 January 1, 2021 January 1, 2022

Term A Term B Term C

July 1, 2020

Account #2

Term D

March 1, 2025

The following table shows restrictions for policy transactions on the source policy.

Policy transaction Restriction

Submission Not applicable.

Policy Change Not allowed on and after the effective date of the rewritten policy (Term D).

Cancellation Not allowed on and after the cancellation date of the source policy. Does not differ from the usual behavior.

Reinstatement Not allowed on and after the start date of the rewritten policy (Term D), because the reinstated period
would overlap the rewritten policy. In addition, a canceled period that overlaps the start date of the
rewritten policy cannot be reinstated.

Rewrite Not allowed on and after the start date of the rewritten policy because the rewritten policy overlaps Term D
or its successors.
Rewrite is allowed if the expiration date does not overlap term D.

Renewal Not allowed on or after the effective date of the rewritten policy (Term D).
Term C can be renewed as long as the expiration date does not overlap the effective date of Term D.

Audit Allowed.

Rewrite New Account Not allowed.

Rewrite new account policy transaction 141

Guidewire PolicyCenter 10.2.3 Application Guide

Restrictions to rewrite new account started on target policy

A rewrite new account policy transaction on the target policy cannot set an effective date that overlaps with the
expiration or cancellation date of the source policy.
Other policy transactions do not allow you to move the effective date of a policy to an earlier date. Therefore, this
restriction does not affect these policy transactions.

Rewrite new account and the Policy Renewal Start batch

process
The Policy Renewal Start batch process does not process an expired policy that has been rewritten to a new account.
The expired policy is not processed because the renewed source policy could create an active period that overlaps the
effective dates of the rewritten policy.

Working with rewrite new account

Rewrite policy to new account
Before you begin
“Rewrite policies from one account to an existing account” on page 396

About this task

When you rewrite policies from one account to another, PolicyCenter does the following:
• Starts a rewrite new account policy transaction for each policy.
• Creates an activity for each new rewrite new account policy transaction and assigns it to the current user.
• Creates a history event on the policy term of the source period for each rewrite new account policy transaction.

Procedure
1. As the same user who rewrote the policy from one account to another, go to the Account Summary screen.
2. In Current Activities, click the Rewrite to new account activity generated by rewriting from one account to another.
PolicyCenter jumps to the Rewrite New Account policy transaction. The bottom part of the window displays the
Activity Detail tab.
3. Click through the wizard steps making changes as necessary.
On the Policy Info screen, the default Effective Date is the cancellation or expiration date of the source policy. You
can change the Effective Date as long as the policy period does not overlap with the source policy period.
4. Quote and issue the policy.
5. In the Activity tab at the bottom of the screen, click Complete to complete the activity.

142 Rewrite new account policy transaction

chapter 21

Premium audit policy transaction

In the base configuration, PolicyCenter provides two types of premium audits: final audit and premium report policy
transactions. You can configure these audit types to meet your requirements or add new configurable audit types. For
information about configuration, see the Configuration Guide.
A final audit policy transaction covers the entire policy term. Only one final audit applies for each policy term. The
final audit begins on the policy effective date and ends on the policy expiration or cancellation date. Premium report
policy transactions, on the other hand, are a series of non-overlapping periodic audits that are scheduled and billed
within the coverage period. They are also know as interim reports. For example, you can choose to schedule premium
reports by calendar months. Then a separate audit is conducted for each calendar month of the policy term.
A final audit contains the verified and ultimate cost for a variable basis policy. When the policy is issued, the estimated
annual premium (EAP) is based on the policyholder’s best guess at the basis, such as payroll, for the entire policy year.
The final audit is conducted at expiration or cancellation. A premium auditor reviews the policyholder’s records, or the
policyholder officially reports the actual payroll amounts for the past policy term. The cost of the policy is recalculated
using this actual basis amount, and the policyholder is billed or returned the difference.
With premium report policy transactions, the policyholder is billed for premium based on periodic requests for actual
basis amounts, such as payroll. A deposit, usually a percentage of the EAP, is billed at the beginning of the policy. As
each reporting period ends, the policyholder is billed based on the actual basis reported by them. Take a policy which
runs from January 1 of this year to January 1 of the following year with monthly premium reporting. The policyholder
will be billed a deposit and up to 12 monthly reports will be scheduled. At the end of January, PolicyCenter initiates the
first monthly report which covers the month of January. By mid-February, the policyholder sends back the basis detail.
The application calculates the premium for the month of January and bills the insured. These reports continue on a
specified schedule until the policy ends. A final audit is also conducted. The final audit verifies and adjusts the
premium for the entire policy term. It also prompts the return of the initial deposit.
In PolicyCenter, final audit policy transactions are available for both workers’ compensation and general liability lines
of business. Premium report policy transactions are available for the workers’ compensation line of business only.
Note: PolicyCenter contains an integration with Guidewire BillingCenter. This topic describes PolicyCenter
when this integration is not enabled. For details on how PolicyCenter integrates with BillingCenter see “Billing
system integration” on page 787.

Final audit overview

Note: In the base application, the workers’ compensation and general liability lines of business are set as
auditable.

Premium audit policy transaction 143

Guidewire PolicyCenter 10.2.3 Application Guide

Some lines of business will require final audit; other lines may offer an optional audit. When the final audit is optional,
the underwriter can set the Requires Final Audit field on the Payment page to Yes, No, or Determined By Business Rules.
Various criteria determine whether a final audit is required, the audit method, and the audit assignment. These criteria
vary by insurer. Among other things, the criteria may include the type of exposures that the policy contains, the
premium size of the policy, the jurisdiction of the policy coverage.

Audit schedules
Audit schedules offer the user choices about the audits to be scheduled. For example, final audit schedules determine
the audit method, the process start date, and the due date, of the audit method.

Process start date

An expiration final audit ends on the normal expiration date of the policy. The audit schedule for an expiration final
audit which will be completed by a physical audit may be set to start 30 days prior to the policy expiration.
A cancellation final audit ends on the policy cancellation date. The audit schedule, which will be completed by a
physical audit, may be set to start as soon as the policy is canceled.
On the process start date, the Audit Task batch process starts the audit policy transaction. The status of the audit
changes from scheduled to in progress, and you can begin collecting the audit information. After the information is
received and entered, the rating engine uses these actual values to calculate the premiums for the prior policy term.
PolicyCenter adjusts the amount billed for the policy. Final audits are always completed after the policy term ends
through expiration or cancellation. For expiration final audits, the audit process starts shortly before the renewal policy
term begins and the prior policy term concludes.
Note: Since a final audit policy transaction changes the billing, but not the policy contract, the audit policy
transaction is not bound but is considered complete.
If the final audit is scheduled, but it is later determined that it is not required, it may be waived. If a final audit is
completed and then the audited values need to be adjusted, the final audit may be revised. When policy changes are
made after a final audit has been completed, PolicyCenter reverses the final audit. PolicyCenter schedules a new audit
based on the changed policy so that the policy changes may be incorporated into the new audit.

Due date examples

It is likely that a physical audit will take a longer time to complete than a phone audit. Therefore, the physical audit
schedule may set the due date to 45 days from the period end date. The phone audit may set the due date to only 15
days from the period end date.

Audit method examples

The default application provides the following audit methods:
• Physical – A representative (such as a premium auditor) makes an in person visit to the policyholder to review the
business records and verify and obtain required audit information.
• Phone – The premium auditor contacts the policyholder by phone to obtain all audit information.
• Estimated – This method is used only when the other methods are not available. For example, the policyholder
went out of business, and the records were lost.
• Voluntary – The insurer sends a document to the policyholder requesting the required information. The
policyholder adds the information and returns the document to the insurer for processing. This document contains
instructions for the policy holder to provide actual exposures for the reporting period. Generally, this includes class
codes and other rating information.

Where does the insurer send premium audit information?

Final audits are important to determine actual policy premium. The insurer must also report final audit information to
regulatory agencies. For example, worker’s compensation unit statistical reports (unit stat reports) are sent to
jurisdictional bureaus or a council that handles multiple jurisdictions (NCCI, for example). The jurisdiction uses unit

144 Premium audit policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

stat reports to calculate policyholder experience modifications and to calculate suggested or mandatory rates obtained
by the insurer. PolicyCenter does not create or send unit stat reports. However, you can configure PolicyCenter to
export final audit data for statistical reporting. This data can be imported to another system such as the unit stat
software application used by a particular jurisdiction.

Reversing and revising final audits

If you need to make changes to a final audit, you can reverse or revise it.

Reverse a final audit

The goal of a reversal is to undo the original audit so that a new audit can incorporate changes made by another policy
transaction. In addition, PolicyCenter notifies the billing system that the first audit is reversed and will likely be
replaced by an entirely new audit. Reversal occurs as a result of another policy transaction becoming effective within
the final audit period after the final audit has been completed. In the base configuration, reversal occurs when
PolicyCenter processes a cancellation, policy change, or reinstatement on a policy that has a completed final audit.
There is no explicit user action. When an audit is reversed, PolicyCenter calls the billing system to reverse charges
related to the final audit and sets the reversal date to the current date. In addition to reversing the final audit,
PolicyCenter schedules a new audit that replaces the reversed one. After the audit task initiates the new scheduled
audit, users can begin processing the new audit.

Revise a final audit

You can use an audit revision to change a completed audit. The existing completed audit is the basis for the revision.
The revision allows a user to amend the audit details and recalculate the premiums. PolicyCenter forwards the revised
audit value or the change in premium to the billing system. This audit becomes the most current representation of the
policy premiums.
Click Revise in the user interface to begin revising an audit. This action creates a new audit with an audit type of Final
Audit (revised).
When might you revise an audit? A premium auditor completes a final audit with an audited payroll. At some later
date, the premium auditor realizes that someone entered the amount incorrectly. The premium auditor revises the
original final audit and enters the correct amount.

Final audits do not alter the policy contract

PolicyCenter policy transactions, such as submissions, policy changes, or rewrites, are bound when completed. Unlike
those policy transactions, a final audit policy transaction is locked when completed. The final audit policy transaction
does not change the policy contract.

Adding a final audit

Usually, PolicyCenter schedules final audits automatically for policies that need them. PolicyCenter allows the user to
add a final audit in the following cases:
• If the user waived the final audit, then later decide that they need one.
• The application did not schedule a final audit, but the user decides that one is needed.
• If the final audit was reversed without scheduling a new one.
A period can only have one final audit scheduled, in progress, or completed. This limit does not include reversed or
revised audits.
See also
• “Add a new audit” on page 154 for instructions on adding a final audit

Premium audit policy transaction 145

Guidewire PolicyCenter 10.2.3 Application Guide

Final audit general steps

The following flow diagram shows the main steps that are necessary to conduct a final audit. These steps are for the
base configuration of PolicyCenter. Your business requirements can alter the process.

Final Audit General Steps

PolicyCenter initially schedules a final
audit when a submission, rewrite, or
renewal job is issued. The line of business
and choices on the Payment page
A final audit is scheduled. determine whether a final audit is required
and the choice of audit schedules.
Other jobs, such as policy change,
reinstatement, or cancellation can amend
the audit.

A batch process starts the audit The batch process uses the process start
process usually before policy date to determine when to start the audit.
expiration.

Audit policy?

You can process the audit

Request audit basis and by the following methods:
Waives audit. phone, physical,
enter it into PolicyCenter.
voluntary, or by
estimation.
Audit process is complete.
However, an audit can be
manually re-added to the
schedule. Premium is calculated and
sent when audit is
complete.

Billing system is notified to

make any premium
adjustments.

Premium report overview

Note: In the base application, premium report are configured for the workers’ compensation line of business.

Premium report policy transactions allow the insurer to bill the premium at regular intervals throughout the policy term
based on reported values. These billings attempt to ensure that the premium billed is close to the final audit amount. In

146 Premium audit policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

most cases, the billings are more accurate than an estimate. For direct bill policies, the insured sends payment along
with the report. If the insured does not submit reports in a timely fashion, the insurer can cancel the policy.
The insured may choose premium reporting because they are not able to accurately predict their payroll in advance or
they have variable bases, such as seasonal variations in their payroll. Others may choose premium reporting because
they end up paying only for the premiums that they actually owe. They may prefer this to paying for everything up
front or agreeing to an estimated amount.
On binding a new policy period, the insured is billed a collateral amount called a deposit. The application schedules
premium reports based on the audit schedule selected. As each report comes in, the user enters the reported amounts
and the rating engine calculates the premium. When the user submits the report, PolicyCenter sends the transactions to
the billing system. If a payment is received with the report, then the billing system reconciles the premium amount with
the amount that the policyholder sent. Since the insured is doing their own calculation of premium outside the system
and sending in a payment, there may be discrepancies that the billing department must resolve.
Within a submission, the premium report policy transaction is a payment plan choice on the Payment page. If you select
premium reporting, then you can select one of the audit schedules configured for premium reporting. The audit
schedule determines the frequency and number of premium reports. The Payment page includes another field for
scheduling a final audit. The choices are Yes (schedule a final audit), No (no final audit is required), or Determined By
Business Rule. When a final audit is selected or required, the application determines which final audit schedule to use.

When the policy is issued, PolicyCenter adds audit scheduled items to the policy. You can see these audits by clicking
the Audit Schedule link of the policy file. Initially these are not audit policy transactions, rather they are a list of all the
audit policy transactions anticipated but not yet initialized for the policy period. They are listed according to their start
and end dates and their status is Scheduled. When a policy is canceled or reinstated, PolicyCenter revises the number of
audits scheduled according to the coverage dates.
Each of the scheduled items includes a process start date, an audit method and a due date. Users with the proper
permissions can edit these fields before the premium audit policy transaction is initialized. For example, you can
change a final audit with an audit method of voluntary to physical. You can also waive a premium audit. However, the
final audit may not be waived on a premium reporting policy because it is the mechanism to return the initial deposit.
A regularly scheduled batch process called Audit Task starts the audit policy transactions on their process start date.
The audit status changes from scheduled to in progress. The audit becomes a draft policy transaction and the scheduled
item becomes a link to the audit wizard. You can begin entering the audit information.
After receiving the audit details, you can enter them into the Audit Summary and Audit Details screens. Determine the
premiums by selecting the Calculate Premiums button. Finalize the calculations by selecting the Submit button. At that
time, the audit becomes uneditable, the status becomes Completed, and the audit schedule displays the resulting
premiums.
You can change completed audits. Premium reports can be manually reversed and rebilled. Final audits are
automatically reversed and rescheduled by policy changes completed after the final audit. Final audits can also be
manually revised. A revised audit displays current and previous premium values.

Premium report audit schedules

Premium report audit schedules include settings that allow for a wide variety of audit schedules. Just like final audit,
there are schedule settings for process start date, due dates, and audit methods. In addition, premium reporting audit
schedules contain settings for the following:
• The frequency of reports
• Whether the report dates match calendar dates or policy dates
• The minimum period length
• Whether to include or exclude the last period
The premium report items scheduled for a particular policy may be amended by changes to the policy such as a
cancellation or change to the effective or expiration date.

Premium audit policy transaction 147

Guidewire PolicyCenter 10.2.3 Application Guide

Premium report trend analysis

In a policy with premium reports, reporting trend analysis is a way to track how far apart the reported premiums are
from the estimated premiums. Reporting trend analysis tracks the total estimated premium, total reported premium, the
ratio between the premiums, and number of days reported. PolicyCenter displays these values on the policy Summary
page and premium report Premiums page. These values are also stored in the database when the audit is submitted or
after a premium report reversal. The database is also updated after a policy change, cancellation or reinstatement. You
may use out-of-range ratios to indicate that the underwriter needs to review the policy for accuracy.
See also
• “Enter premium report data” on page 157 to view the trend analysis information in the application
• Configuration Guide

Adding a premium report

PolicyCenter allows you to add a premium report to a policy for any unreported portion of a policy period. For
example, you may add a premium report to a policy in the following cases:
• The policy originally had 11 monthly reports plus a final audit. The underwriter wants to add a 12th report rather
than waiting for the final audit to collect the premium for the last month.
• A user submits a policy change on a policy with one or more completed reports. These reports need to be reversed
and added back.
See also
• “Add a new premium report” on page 157

Premium reports general steps

The following diagram shows the main steps that are necessary to conduct premium reports. These steps are for the
default configuration of PolicyCenter. Your business requirements can alter the process.

148 Premium audit policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

Premium Reports General Steps

If the payment type is premium reporting,

then PolicyCenter schedules premium
reports when a workers’ compensation
Schedule premium reports. submission, rewrite, or renewal job is
issued.
Other jobs, such as policy change,
reinstatement, or cancellation can amend
the reporting schedule.

A batch process starts each The batch process uses the process start
premium report. date to determine when to start each
premium report.

Conduct
premium
report?

Waive premium report. Send report to insured to obtain the audit basis.

The selected premium

report is waived. However,
a new premium report may Enter report data received from insured in
be scheduled manually for PolicyCenter. Premium is calculated.
the waived period.

Premium amount is sent to the billing system

along with a message regarding the payment
received with the report.

Billing system reconciles amount received with

PolicyCenter amount and makes any necessary
billing adjustments.

Premium audit policy transaction 149

Guidewire PolicyCenter 10.2.3 Application Guide

Premium audit roles

Many regular users of PolicyCenter are underwriting personnel or producers. Although premium audits interest these
users, the actual initiation and processing of premium audits is typically done by a separate premium audit department.
The premium audit department might include in-office premium audit examiners, and outside premium auditors who
travel to the policyholder’s location.
The default application contains audit roles as described in the following topics.

Premium auditor
PolicyCenter assigns an audit with a method of physical to a premium auditor. The premium auditor is a person who
travels to the policyholder’s location to conduct the audit. The premium auditor returns that information to the insurer’s
office. The premium auditor role can vary by insurer. For example, the auditor may be allowed to edit the audit
summary and audit details. However, the auditor may not be allowed to complete the audit because a premium audit
examiner needs to check it for accuracy.
Note: In the default configuration when the audit method is physical, PolicyCenter assigns the audit to a user
with the premium auditor role.

Premium audit examiner

The premium audit examiner is located at the office of the insurer. The premium audit examiner enters the audit details
for premium reports and final audits. The premium audit examiner checks physical audits for accuracy, calculates the
premiums, and completes the audit.
If the final audit method is:
• Physical – The premium audit examiner receives the physical audit from the premium auditor and checks it for
completeness and accuracy. The examiner also checks it for adherence to manual rules and guidelines of the
insurance company. For example, does it include all the locations and entities? Does it split exposures for the
anniversary rating date (ARD)?
• Voluntary – The premium audit examiner receives a completed report document from the policyholder. The
examiner reviews the document prior to billing to ensure that the policyholder completed it properly. If necessary,
the premium audit examiner calls the policyholder to clarify or amend the totals received.
• By phone – The premium audit examiner calls the policyholder to obtain audit exposures and ask questions
appropriate to the audit or renewal.

Premium audit supervisor

The premium audit supervisor is a supervisor in the premium audit department. Premium audit supervisors have all the
audit permissions. In addition the supervisor has access to team screens where outstanding audits and audit activities
can be tracked.

Premium audit and other policy transactions

The following table describes the interaction between final audit and premium report and other policy transactions.

Policy Description
transaction

Audit Premium Report Policy Transactions

If you have an open report and final audit is already billed, then the report cannot be billed because the final
audit already finalized the premium for this period. This situation occurs if the auditor does the final audit early
and completes it before receiving the last report.

Submission Final Audit and Premium Report Policy Transactions

150 Premium audit policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

Policy Description
transaction

According to the configuration settings, PolicyCenter schedules final audit and appropriate premium reports
when you issue the policy.

Issuance Final Audit and Premium Report Policy Transactions

If changes are made to the policy term, then PolicyCenter schedules final audit and appropriate premium
reports when issuing the policy.

Renewal Final Audit and Premium Report Policy Transactions

PolicyCenter schedules a final audit and appropriate premium reports when renewing the policy.

Policy Change Final Audit Policy Transaction

Policy changes impact final audits as follows:
• Scheduled audits – If the policy change amends the policy term, PolicyCenter replaces the scheduled audit
with an audit for the new policy term.
• In Progress audits – PolicyCenter preempts and updates the In Progress audit. The updated audit includes the
policy changes, such as classification or policy term changes.
• Completed audits – PolicyCenter reverses the Completed audit and schedules an audit for the full policy term
or cancellation period. If the Completed audit has an In Progress revision, PolicyCenter withdraws the
revision.
Premium Report Policy Transaction
• Scheduled premium reports – if the policy change amends the policy term, PolicyCenter replaces the audit
schedule with the appropriate premium report periods.
• In Progress premium reports – If there is an open premium report, a policy change preempts the report and
adds in the changes.
• Completed premium reports – A policy change does not impact a Completed premium report.

Cancellation Audits are affected when the policy reaches a Canceled status. Cancellations may be completed with a scheduled
future effective date or canceled immediately. Policies canceled immediately are given a Canceled status. Policies
with Scheduled cancellations reach a Canceled status on the cancellation date.
Final Audit Policy Transaction
When the policy changes from a Canceling to a Canceled status, audits are impacted as follows:
• If the policy is canceled flat, no audit is required. PolicyCenter removes any scheduled final audit or
withdraws any open final audit.
• If the cancellation is midterm:
◦ Scheduled audits – PolicyCenter replaces the full term audit in the schedule with an audit for the
cancellation period, including assigning the configured audit schedule. The cancellation calculates the
cancellation amount and sends this amount to the billing system.The cancellation also sends a message
to hold these funds until final audit completes.
◦ In Progress audits – PolicyCenter preempts the In Progress audit. PolicyCenter amends the dates and
displays only classifications that apply to the cancellation term.
◦ Completed audits – PolicyCenter reverses the Completed audit and schedules an audit for the cancellation
period. If the Completed audit has an In Progress revision, then PolicyCenter withdraws the revision.
Premium Report Policy Transaction
When the policy changes from a Canceling status to a Canceled status, premium reports are impacted as follows:
• Scheduled audits past the cancellation date are removed.
• Completed reports remain completed regardless of the period they cover.
• In Progress reports
◦ Any reports Scheduled or In Progress with dates prior to a completed report remain regardless of the
cancellation date.

Premium audit policy transaction 151

Guidewire PolicyCenter 10.2.3 Application Guide

Policy Description
transaction

◦ An In Progress period that includes the cancellation date is Withdrawn.

◦ In Progress periods later than the cancellation date are Withdrawn.
◦ In Progress reports covering the period prior to the report that includes the cancellation date are
Withdrawn if both of the following are true. 1) If the premium report schedule excludes the last month.
2) The number of days from the end of the prior period to the cancellation date is less than the
minimum audit period length.

Reinstatement Final Audit Policy Transaction

Reinstatement policy transactions impact audits as follows:
• Scheduled audits – PolicyCenter replaces the cancellation period audit with an audit for the full policy period.
• In progress audits – PolicyCenter withdraws the in progress cancellation audit and schedules a new audit for
the full policy term.
• Completed audits – PolicyCenter reverses a completed audit and schedules an audit for the full policy term.
Premium Report Policy Transaction
Reports are reinstated as follows:
• Periods that were Withdrawn, Waived, or removed are added again as new Scheduled items
• The Waived and Withdrawn scheduled items remain in the list as Waived and Withdrawn.
• Completed periods that were reversed are also Scheduled as new scheduled items.

Rewrite Final Audit Policy Transaction

When the rewrite finishes, PolicyCenter schedules a final audit for the new period.
Premium Report Policy Transaction
.According to the configuration settings, PolicyCenter schedules premium reports when you issue the rewritten
policy.

Note: Final audits cannot be out of sequence with other policy transactions. However, final audits can be
preempted.

Working with final audits

You can schedule a final audit upon issuance of a workers’ compensation or general liability submission. Or you can
manually schedule an audit later in the policy term. Close to policy expiration, PolicyCenter creates the final audit
policy transaction according to the process start date. You can configure when the final audit policy transaction starts
by configuring final audit schedule patterns. For more information on configuring audit, see the Configuration Guide.
If you have the appropriate audit permissions, you can edit, calculate, complete, or revise a final audit. By default, a
producer or underwriter can view some details of the final audit but cannot edit it.
The included topic provide step-by-step instructions.
See also
• “Tools menu in policy file” on page 178

View final audit schedule

About this task
You can view basic details about a final audit, such as the period start and end dates, the method of the audit, and its
status.

152 Premium audit policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

Procedure
1. Navigate to a policy that can be audited.
2. Select Audit Schedule in the Tools menu. The Audit Schedule screen displays a summary of audits and audit
scheduled items (future audits).
Note: Without sufficient permissions, you can only view summary information.
3. Select the pull-down menu to filter the list of audits. The menu displays the following options:
• Scheduled/in-progress – Default. Display open audit policy transactions or audits that are scheduled for the
future.
• In progress – Display only open policy transactions.
• Closed within last 12 months – Display any item that has a closed date within the last 12 months.
• Due date within last 12 months – Display any item with a due date within the last 12 months or due in the
future.
• End date within last 12 months – Display any item that has an end date in the last 12 months or a future end
date.
• All – Full history of audit policy transactions excluding deleted policy transactions.

View audit activities

About this task
The Audit Task batch process changes the status of an audit to open and assigns the audit. For each audit, the batch
process creates an activity with the subject A new audit has been assigned. You can find these activities by selecting
Activities from the Search tab.

Procedure
1. To find audit activities that are assigned to you, navigate to the Desktop tab and click My Activities in the left
sidebar. Look for activities with the subject A new audit has been assigned.
2. Click the Subject of an audit activity. The audit appears at the top of the screen, and the activity appears at the
bottom.

Edit, start, or waive a final audit

Before you begin
“View final audit schedule” on page 152

About this task

If a final audit is scheduled (but has not started yet) you can edit details of how it is scheduled, or waive it. Follow
these steps when you need to waive an audit or change any of the dates or methods for an upcoming final audit.
Note: To edit an audit, you must have the Edit audit (editaudit) permission. To start an audit, you must have
the Start audit job (startaudit) permission. To waive an audit, you must have the Waive audit permission
(waiveaudit).

Procedure
1. Navigate to the Audit Schedule screen for a policy.
2. Under the Actions column, select one of the following choices:

Edit Change the Process Start date, Due Date, or planned Audit Method.

Premium audit policy transaction 153

Guidewire PolicyCenter 10.2.3 Application Guide

Start Send the audit for processing by the Audit Task batch process.
Waive Bypass the audit procedure. PolicyCenter will not perform an audit on that audit period. If you later decide that you
need the audit, you can add it back in. See “Add a new audit” on page 154.

When an audit is in progress, the Edit and Waive buttons are not available. Changes or waives must be done
within the audit. See “Enter audit data and complete final audit” on page 154.

Add a new audit

About this task
In certain cases, you can add an new audit or premium report. “Adding a final audit” on page 145 describes when you
can add a new audit. “Adding a premium report” on page 148 describes when you can add a new premium report.

Procedure
1. Navigate to a policy that has an audit or premium reports.
2. Click Audit Schedule in the left sidebar.
3. Click New Audit.
4. Select appropriate values and click OK.
The screen for final audit allows you to enter Process Start Date, Due Date, and Audit Method. Audit Period Start
Date and Audit Period End Date are set automatically to the start and end of the audit period.

The screen for premium report allows you to enter Audit Period Start Date, Audit Period End Date, Process Start
Date, Due Date, and Audit Method.

Enter audit data and complete final audit

About this task
If a final audit has a status of In Progress, you can enter the audit data. The following steps describe how to edit and
complete an audit.
Note: To edit an audit, you must have the Edit audit (editaudit) and Quote (quote) permissions. To complete
an audit, you must have the Complete audit (completeaudit) permission.

Procedure
1. Perform the steps in “View final audit schedule” on page 152 or “View audit activities” on page 153. Then click
the link of the Final Audit you wish to complete.
2. Enter information in the Summary screen.
The Audit Summary screen allows you to enter the following:
Field Description

Due Date Modify the due date, if necessary.

Received Date Enter the date that the audit information was received.

Method (actual) Change the audit method to the type of audit that actually occurred. In most cases this is the same value as
Method (planned), however, sometimes it is not. If a physical audit was attempted but did not succeed, then
this audit policy transaction may need to be completed with Estimated values.

Audit Fee Enter an audit fee when a vendor conducts the audit.

Instructions Enter instructions for the premium auditor or premium audit examiner.

3. Click Next.

154 Premium audit policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

4. In the audit Details screen, all the exposure class codes for the period appear by jurisdiction. Enter the actual
audited payroll amounts for each location and class code. Click Save Draft.
Because of your permissions, the screen displays Calculate Premiums next to the Save Draft button.
5. Click Calculate Premiums. The rating engine calculates the amounts and displays the results on the Summary tab
of the audit Premiums screen.
The Summary tab displays the audit premium and the difference between the audited costs and the costs on the
policy. Use the Comments field to add an explanation for the difference.
6. To see the calculation of the total premium for the audit term, select the PremiumDetails tab.
The Premium Details tab shows the calculation for each audit cost and compares it to the policy contract values.
You can see the difference between these costs in the Change column.
7. If you need to change the class code exposures, click Edit Audit.
8. When the amounts are accurate, click Submit. The audit status is now Completed.

Revise a final audit

About this task
If a final audit has a status of Completed, you can revise the audit through a policy transaction called a revised final
audit.
You must have the Revise audit (reviseaudit) permission.

IMPORTANT: Starting a revision policy transaction does not submit a change to the billing system. It is only
upon completion of the audit revision that the billing system is notified of the change in final audited premiums.

To revise a final audit:

Procedure
1. Perform the steps in “View final audit schedule” on page 152, and click Revise under the Actions column.
PolicyCenter starts the audit policy transaction. This action also changes the original audit to a status of Revised.
2. Enter revised information as you would in the “Enter audit data and complete final audit” on page 154.
The revised final audit policy transaction displays Close Options > Withdraw Transaction instead of a Close
Options > Waive. If you select Withdraw Transaction, the policy transaction goes to a Withdrawn status. When a
revision is withdrawn, PolicyCenter changes the status of the revision policy transaction to Withdrawn and
returns the status of the original audit to Completed.
3. Click Calculate Premiums.
The Audit Premiums > Summary tab displays the difference between the original audit and the revised audit. To
see a breakdown of the amounts, select the Premium Details tab.
4. Click Submit to complete the audit.

Working with premium reports

You can choose premium reports on the Payments screen in the workers’ compensation line of business. This topic
describes how to work with premium reports in PolicyCenter.
See also
• “Tools menu in policy file” on page 178

View a premium report

You can view basic details about a premium report, such as the period start and end dates, the method of the audit, and
status. Viewing a premium report is the same as viewing a final audit. See “View final audit schedule” on page 152.

Premium audit policy transaction 155

Guidewire PolicyCenter 10.2.3 Application Guide

View premium report activities

The AuditTask batch process changes the status of a premium report to open and assigns it. For each premium report,
the batch process creates an activity with the subject A new audit has been assigned.
The Overdue Premium Report batch process creates an activity for overdue premium reports. PolicyCenter displays the
activity on the policy Summary page under Current Activities or on the underwriter’s Desktop under My Activities.
The display of activities is the same as for final audit. See “View audit activities” on page 153.
See also
• “Start a premium report” on page 156 for more information about the AuditTask batch process.
• “Create activities for overdue premium reports” on page 156 for more information about the Overdue Premium
Report batch process.

Select premium reports

About this task
You can select premium reports on the Payment screen of a workers’ compensation submission, rewrite, or renewal
policy transaction.
To select premium reports:

Procedure
1. Start a submission, rewrite, or renewal policy transaction and navigate to the Payment screen.
2. In Payment Method, select Reporting Plan.
3. Under Premium Report Plans, select one of the plans. In this example, select the first plan, Monthly Reports by
calendar months, excl. last month.
In the base application, PolicyCenter displays the following Premium Report Plans:
• Monthly reports by calendar month, excl. last month
• Monthly reports by policy month, excl. last month
• Quarterly reports by calendar quarters
• Quarterly reports by calendar quarters, excl. last quarter
• Quarterly reports by policy quarters, excl. last quarter
After you choose a report plan, PolicyCenter displays fields for the deposit percentage and amount. Deposit
percentage is configured in the audit schedule. You can override the percentage in the Deposit override % field.
All report plans in the base application require final audit. The final audit notifies the billing system to release the
deposit.
4. After you issue the policy, you can view the audit schedule. In the Tools sidebar, click Audit Schedule.

Start a premium report

The AuditTask batch process starts premium reports. In the base configuration, PolicyCenter launches the Audit Task
batch process at a predefined interval. The batch process activates premium reports that have passed their process start
date. These reports have an In progress status in the Audit Schedule.
For more information on batch processes and how to configure them, see the Administration Guide.

Create activities for overdue premium reports

Premium reports have a process start date, which is the date when the audit task batch process can start processing the
report. If the user does not make the payment by due date then the premium report goes into delinquency. The Overdue

156 Premium audit policy transaction

 Guidewire PolicyCenter 10.2.3 Application Guide

Premium Report batch process finds overdue premium reports. For each overdue premium report, the batch process
creates a Premium report overdue activity for the underwriter.

Enter premium report data

About this task
The insured completes the premium report and returns it to the insurer. The user enters the report data into
PolicyCenter.
To enter premium report data:

Procedure
1. Navigate to a policy with premium reports.
2. Click Audit Schedule in the left sidebar.
If the batch process has started a premium report, Premium Report is a link in the Type column.
3. Click a Premium Report link.
4. In the Summary screen, enter the Received Date and Payment Received. Then click Next.
5. In the Details screen, enter the payroll amounts reported by the customer.
6. Click Calculate Premiums.
The Premiums screen displays the calculated cost along with the payment received from the insured.
The Reporting Trend Analysis displays the following fields. The Reporting Trend Analysis also appears on the
policy Summary screen.

Field Description

Total Estimated Premium The pro rata premium based on the number of days reported to date and the Total Estimated
Premium for the policy. (Until final audit, there is no total premium on a reporting policy. Until final
audit, it is only an estimated premium.)

Total Reported Premium The total premium from completed premium reports.

Ratio The ratio between the total estimated premium and total reported premium.

Days Reported The number of days for which the total reported premium applies.

For more information about reporting trend analysis, see “Premium report trend analysis” on page 148.

Edit or waive a premium report

You can choose to edit or waive a premium report. The steps are the same as for final audit. See “Edit, start, or waive a
final audit” on page 153.

Add a new premium report

In certain cases, you can add a new premium report. The section “Adding a premium report” on page 148 describes
when you can add a new premium report. The steps are similar to the steps for final audit. See “Add a new audit” on
page 154.

Premium audit policy transaction 157

Guidewire PolicyCenter 10.2.3 Application Guide

158 Premium audit policy transaction

chapter 22

Side-by-side quoting

With side-by-side quoting, you can view multiple versions of a policy transaction on one screen. You can modify the
coverages and terms of each version in the side-by-side screen, and see the side-by-side comparison of the costs and
benefits of each version. You can use side-by-side quoting with quick quote. In the default configuration, the personal
auto line of business provides side-by-side quoting. You can configure side-by-side quoting for other lines of business.

Side-by-side quoting versus multi-version quoting

PolicyCenter provides two ways to generate alternate versions of a policy quote: side-by-side quoting and multi-
version quoting. The two options are mutually exclusive.
The following table compares and contrasts some of the features of side-by-side quoting and multi-version quoting.

Side-by-Side Quoting Multi-Version Quoting

Side-by-Side Quoting screen enables you to view and modify Select version from drop-down menu under Actions. No side-by-
multiple quotes in one place. side comparison view.

Copies changes to base data to other side-by-side versions. All policy data can differ. Provides more flexibility than side-by-
side quoting.

When you switch to side-by-side quoting, PolicyCenter quotes When you create a new version, PolicyCenter does not quote
each version. either version of the policy.

Use the Quote All button to quote all versions. Quotes each version of the policy independently.

Available in the personal auto line of business in the default Available in all lines of business in the default configuration.
configuration.

See also
• “Multi-version quoting” on page 167

Side-by-side availability overview

PolicyCenter supports side-by-side quoting for the following policy transaction types:
• Submission
• Policy change
• Renewal
Side-by-side quoting 159
Guidewire PolicyCenter 10.2.3 Application Guide

• Rewrite
The policy transaction must have a status of:
• New
• Draft
• Quoting
• Quoted
You cannot enter side-by-side quoting in a policy change or renewal that has out-of-sequence conflicts or unhandled
preemptions. PolicyCenter will display a warning message after you click the Side-by-Side button to enter side-by-side
mode.

Base data overview in side-by-side quoting

Each line of business which implements side-by-side quoting defines base data, which data that is common across all
versions. Making a change to the base data in one side-by-side version triggers a change to the base data in all side-by-
side versions. You can change the base data in any policy transaction wizard step, such as on the Policy Info screen in a
submission. However, you cannot edit the base data in side-by-side view.

IMPORTANT: To conform to Guidewire configuration requirements, base data entities or fields on the Side-by-
Side Quoting screen must not be editable in more than one place on a given screen. For example, placing an
editable widget for a base data field in the columns replicated for each version is a violation of this requirement.
This requirement applies to fields that are implicitly base data, such as contact or location information that can
be synchronized.

Typical types of base data on the policy period include:

• Account associated with this policy
• Policy
• Effective dates
• Answers to pre-qualification questions
• Address and contact information
In the personal auto line of business, the base data also includes line-level modifiers.

Side-by-side data overview

A change to side-by-side data affects only a single version. PolicyCenter does not propagate the change to other side-
by-side versions.

Typical side-by-side data

Typically side-by-side data includes:
• Coverages, exclusions, and conditions
• Forms
• Underwriting issues and approvals
• Costs and transactions
• Other financial data
• Numbering of coverables
• Reinsurance-related information

160 Side-by-side quoting

 Guidewire PolicyCenter 10.2.3 Application Guide

• Grandfathering-related dates
• Internal status information
• Denormalized data
• Archiving- and purging-related information
Personal auto side-by-side data
In the personal auto line of business, the side-by-side data includes:
• The selected offering code
• Line-level coverages, such as liability coverage
• Vehicles, along with their coverages
• Vehicle drivers
• Personal auto vehicle additional interest
• Quick quote numbering

Side-by-side quoting process flow

The following flow diagram shows the process flow of side-by-side quoting.

Side-by-Side Process Flow

Enter base data

for the policy 1

7
2
Autofill policy
data Edit Side-by-
Side versions

3 4 5 6 9

View Side- Select version

Click Side- Generate Quote all
by-Side and issue
by-Side versions versions
versions policy

Edit single
version
8

The steps are sequential up to step 6.

1. Enter base data for the policy: In PolicyCenter, the user enters base data for the policy such as the primary named
insured and contacts on the policy.
2. Autofill policy data: PolicyCenter automatically fills in territory codes and similar data.
3. Click Side-by-Side: The user selects Versions > Start Side-by-Side to enter side-by-side mode.
4. Generate versions: PolicyCenter generates multiple versions of the policy by using business logic configured for
the line of business. The number of versions is also configurable.

Side-by-side quoting 161

Guidewire PolicyCenter 10.2.3 Application Guide

5. Quote all versions: PolicyCenter generates quotes for all versions.

6. View Side-by-Side versions: The user views a screen showing side-by-side versions of the policy. From step 6
you can progress directly to step 9. If you need to make edits, go to “step 7” or “step 8”, which return you to
“step 5”.
7. Edit Side-by-Side versions: The user makes modification to the side-by-side data, such as making changes to
coverages. Then to compare the costs of the different versions, the user quotes the policy (“step 5”).
8. Edit single version: Alternately, the user can edit a single version and change the base data or side-by-side data.
PolicyCenter copies changes to base data to the other side-by-side versions. Then to compare the costs of the
different versions, the user quotes the policy (“step 5”).
9. Select version and issue policy: The user selects a version and issues the policy.

Side-by-side quoting in the user interface

Tools menu items for side-by-side quoting
If you are in a policy transaction in which you have selected side-by-side quoting, two additional menu items appear in
the Tools menu in the left sidebar:
• Side-by-Side Quoting – Displays the Side-by-Side Quoting screen.
• Policy Versions – Displays the Policy Versions screen which contains brief information about each side-by-side
version. This screen also appears for multi-version quoting policy transactions.

Side-by-Side Quoting screen

On the Side-by-Side Quoting screen, you can view and modify multiple versions of a policy and compare quotes for
each version. For each version, this screen displays side-by-side data fields which you can modify. You can configure
this screen to display base data as long as the user can edit it in only one place. Do not repeat base data in the side-by-
side columns.

Side-by-side versions locked

In some circumstances, certain users cannot modify any versions in a side-by-side policy transaction. If there are one or
more locked versions, and you do not have the Edit Lock Override (editlockoverride) permission, you cannot make
modifications until there are no locked versions. For Gosu code, you can use the UWLockedAndNoOverride property on
a PolicyPeriod to determine if this lock applies to a user. Locking across versions prevents inconsistencies in sharing
base data across versions in side-by-side mode. The UWLockedAndNoOverride property is defined in
gw.policy.PolicyPeriodBaseEnhancement.

For example, if you select Request Approval for one or more versions on the Risk Analysis tab, those versions are
locked awaiting underwriter approval. Consequently, all versions in the side-by-side policy transaction are also locked.
If you do not have the Edit Lock Override permission, you cannot make modifications until underwriting approves all
versions. If PolicyCenter did not lock all versions, you could modify base data in an unlocked version, but
PolicyCenter could not copy those changes to the locked versions. If you have the Edit Lock Override permission, you
have permission to modify all versions, including locked versions. Therefore, if you make a change, base data copy
copies your change to the other versions.

Buttons at top of screen

Some of the buttons at the top of the Side-by-Side Quoting screen are:
• Add Side-by-Side Version – Adds a new side-by-side period up to a configurable limit. If you click Select next to a
version to jump to the single version wizard for that period, this button appears in the Versions drop-down menu. On
the Side-by-Side Quoting screen, the selected policy period is the basis of the new version. In the single version
wizard, the current policy period is the basis of the new version.
See also the Configuration Guide.

162 Side-by-side quoting

 Guidewire PolicyCenter 10.2.3 Application Guide

• Rate All – Generates rates for all versions.

• Validate All – Generates validation errors and underwriting issues for all versions.
• Save All – Saves all versions.

Quote comparison
Each version has the following fields:
• Name – A text box for editing the version name.
• Offering Selection – Has a drop-down menu to select an offering.
• Reset – Applies the selected offering to the policy period, setting all coverages to default values in the product
model.
When you click Reset, PolicyCenter synchronizes the product model with the currently selected offering. Simply
changing the offering selection does not synchronize the product model for the current version.
• Validation errors and underwriting issues – Appear in the final row under the version. You cannot Rate All if a
version has validation errors or underwriting issues that block quote. In many cases, a wizard step is selected based
on the condition needing resolution.
• Select – Select this version. When you click Select, PolicyCenter takes you to the Policy Review screen for that
version. PolicyCenter marks the selected version with an asterisk in the drop-down list underneath the Actions
menu. You can navigate backwards in the policy transaction wizard to make changes to other screens, including
changes to base data and side-by-side data.
Clicking Select marks the selected policy period for the policy transaction. Reporting and other PolicyCenter
processes may access this status. Changes to base data are copied to the other versions. For example, in personal
auto, you can go back to the Policy Info screen and change the Effective Date. This change to base data is copied to
all side-by-side versions. From a version, select Versions > View Side-by-Side Versions to return to the Side-by-Side
Quoting screen.

• View Period Details – Jumps to the Policy Review screen.

• Duplicate Period – Creates a new version based on this version.

• Delete Period – Deletes that version and only that version.

• Resolve – Forwards you to a step in the policy transaction wizard for the version based on the type of validation
errors or underwriting issues. You can edit the policy and make changes in that step. If errors are present,
PolicyCenter displays a worksheet with error or warning messages and, in many cases, links to the step in the
wizard. This behavior is similar the display of errors and warnings when attempting to quote.

Coverages
The Side-By-Side Quoting screen displays coverages for each version. You can make coverage selections for each
version.

Entering the Side-by-Side Quote screen for the first time

You enter side-by-side for the first time by selecting Versions > Start Side-by-Side. If you select Start Side-by-Side in the
base configuration, PolicyCenter creates two additional periods for a total of three side-by-side periods. If the initial
period has an offering, the side-by-side periods are the same as the initial period. If there is no offering on the original
period, PolicyCenter applies the basic, standard, and premium offerings to each side-by-side version, respectively.
In policy periods that have the Standard Program offering, PolicyCenter removes collision and comprehensive
coverages on vehicles over 10 years old.
If an underwriter locked the policy, then Policy Transaction Under UW review appears in the info bar and the agent
cannot view quotes for the versions. An underwriter might lock the policy so that the agent cannot make changes while
the policy is under review.

Side-by-side quoting 163

Guidewire PolicyCenter 10.2.3 Application Guide

Resolving out-of-sequence conflicts and unhandled preemptions in side-by-side quoting

If there are out-of-sequence conflicts or unhandled preemptions, the Side-by-Side Quoting screen displays a warning
message and does not create multiple versions. If the policy transaction is already in side-by-side mode, then
PolicyCenter prevents you from editing the side-by-side data.
If there are unhandled preemptions, you can apply all the preemptions or withdraw the changes. If you apply
preemptions in a side-by-side policy transaction, PolicyCenter applies preemptions against the current policy period.
PolicyCenter then copies base data from the current policy period to the other side-by-side periods. If you choose to
withdraw the changes, the policy transaction is marked for withdrawal.
In the HandlePreemptionPopup PCF file, the Apply All Changes button handles preemption in side-by-side policy
periods. You can view the HandlePreemptionPopup in Studio.
If there are out-of-sequence conflicts, you resolve these conflicts in the single wizard view. When you resolve out-of-
sequence conflicts for a particular policy period, PolicyCenter copies base data product model changes to the other
side-by-side periods. In some cases the copy does not fix out-of-sequence conflicts for other side-by-side periods. If so,
PolicyCenter forwards you to the out-of-sequence conflict resolution page of a period that still has conflicts.
The handleConflict method in the OOSConflictPanelSet PCF file handles out-of-sequence conflicts in a side-by-
side policy.

Policy Versions screen

The Policy Versions screen displays brief information about each version. In side-by-side quoting policy transactions, a
link to this screen is available under Tools.

Buttons at top of screen

The following buttons appear at the top of the screen:
• Select – To make a version the selected version, select a Version Name and click this button.
• Rename – To rename a version, select a Version Name and click this button.
• Withdraw – To withdraw one or more versions, select a Version Name and click this button.
If all but one period is withdrawn, the policy transaction is taken out of side-by-side mode, and the Side-by-Side
Quoting screen is no longer available. The Versions > Start Side-by-Side menu item is enabled.

If you select all versions and click Withdraw, PolicyCenter displays a message in the Validation Results and does not
remove any versions.
• Diff – To see the differences between two versions, select two versions and click this button.

Each version
For each version in a side-by-side quote, the Policy Versions screen displays:
• Selected Version – The currently selected version is marked Selected.
• Create Time – The day and time that the version was created. The time stamp on version #1 is the time when the
original policy period was created. The time stamps on version #2 and #3 are the times when the Side-by-Side
button was clicked. There is a small possibility that the time stamps for version #2 and #3 have different minute
values because PolicyCenter creates the side-by-side periods sequentially.
• Version Status – The status of the version. For example, Draft or Quoted.
• Premium Totals – The value of the premium if the policy has been quoted.

164 Side-by-side quoting

 Guidewire PolicyCenter 10.2.3 Application Guide

Working with side-by-side quoting

Select side-by-side quoting in a submission
About this task
Follow these steps to convert a submission policy transaction to side-by-side quoting and make changes in the side-by-
side data.
Note: These instructions walk you through the steps in a Quick Quote. You can also select Full Application as
the Quote Type.

Procedure
1. Start a submission for personal auto. In the sample data, you can use the Ray Newton account.
2. On the New Submissions screen, select Quick Quote for Quote Type.
3. Add a driver and a vehicle.
4. Select Versions > Start Side-by-Side.
PolicyCenter displays the Side-by-Side Quoting screen. Because you did not select an offering, PolicyCenter
applies the Basic Program, Standard Program, and Premium Program offerings to each side-by-side version,
respectively. Each side-by-side period has been rated. Policy Premium displays the rate.
5. Compare the values for each Policy Premium.
6. Make changes to the coverages for one or more versions.
The coverages are side-by-side data that apply to each version. After you make changes, the value for Policy
Premium disappears in the changed versions.
7. Click Quote All to regenerate the Policy Premium for this version and to generate rates for all versions.

Edit a version in a policy transaction with side-by-side quoting

About this task
Follow these steps to make changes to a version in a policy transaction with side-by-side quoting. If you change the
base data, that change is copied to the other side-by-side versions. If you change side-by-side data, that change applies
to the selected version only. These instructions assume that you are in a quick quote for a personal auto submission.
Note: In some circumstances, certain users cannot modify any versions in a side-by-side policy transaction. For
more information, see “Side-by-Side Quoting screen” on page 162.

Procedure
1. In a policy transaction with side-by-side quoting, click Tools > Side-by-Side Quoting to jump to that screen.
2. Under Version #2, click Select to select this version.
3. Click Quick Quote Information in the left sidebar. PolicyCenter displays this screen.
4. Click Edit Policy Transaction to make the policy editable.
5. In Policy Info, make a change to the Term Type. Term Type is a base data field.
6. Click Vehicles > New Vehicle.
7. Add a vehicle. A vehicle is side-by-side data. Therefore, the vehicle is only on Version #2 the policy.
8. Click Save Draft.
9. Click Tools > Side-by-Side Quoting.
Notice that all versions no longer have a Policy Premium value. The premium for the versions must be updated to
reflect the new term type.

Side-by-side quoting 165

Guidewire PolicyCenter 10.2.3 Application Guide

The vehicle that you added is not on other versions of the policy.
10. Under Version #1, click Select to select this version.
11. In the left sidebar, click Policy Contract to go to the Quick Quote Information screen for Version #1.
Notice that the Term Type has the new value that you set for Version #2. Because term type is base data,
PolicyCenter copies the value to the other versions.
Notice that the vehicle that you added to the other version does not appear. Because the vehicle is side-by-side
data, PolicyCenter does not copy it to the other versions.
12. Click Versions > View Side-by-Side Versions.
13. Click Rate All to generate rates for all versions.

Bind and issue a side-by-side submission

About this task
Follow these steps to bind and issue a submission with side-by-side quoting. These instructions assume that you are in
a personal auto submission.

Procedure
1. In a policy transaction with side-by-side quoting, click Tools > Side-by-Side Quoting to jump to that screen.
2. Click Select in the version that you want to bind and issue.
PolicyCenter displays the Quote page for the selected version.
3. If you are in Quick Quote, click Full App. You cannot bind and issue a quick quote submission. You may have to
add additional information required for quoting. When you make the change to Full App, PolicyCenter invalidates
the quotes and sets the policy periods back to draft status.
4. Click Quote.
5. Select Bind Only or Issue Policy from the Bind Options menu.

166 Side-by-side quoting

chapter 23

Multi-version quoting

With multi-version quoting, you can generate multiple versions of a policy for comparison in a submission, renewal,
and policy change policy transaction. You can select to view each version of the policy, and modify the coverages,
terms and other parts of the policy. You can compare the status and premiums for all versions. In the default
configuration, multi-version quoting is available in all line of business.

Multi-version quoting versus side-by-side quoting

Multi-version quoting is similar to side-by-side quoting. In the default configuration, multi-version quoting is available
in all lines of business. In the default configuration, side-by-side quoting is only available in the personal auto line of
business. With multi-version quoting, you view and modify each version individually. In side-by-side quoting, you
view and make changes to multiple versions in a screen that displays the versions next to each other.
See also
• “Side-by-side quoting” on page 159
• “Side-by-side quoting versus multi-version quoting” on page 159

Working with multi-version quoting

Create and compare multi-version quotes
About this task
You can create alternate versions that better reflect an applicant’s requirements, and then compare them. You can create
multiple versions in submission, renewal, and policy change policy transactions. You can create multiple versions after
the policy is quoted.

Procedure
1. In the Quote screen, click Versions > Start Multi-Version.
PolicyCenter creates a new version of the policy transaction that contains the previously entered data. Below the
Actions menu, drop-down menu displays the name of the current version.
2. Make desired changes and click Quote.
3. If you want to compare the submissions, click Policy Versions under the Tools menu.
The Policy Versions screen appears with a message indicating that you are viewing multiple parallel versions and
not side-by-side versions. You can:
Multi-version quoting 167
Guidewire PolicyCenter 10.2.3 Application Guide

• Select a version and make it the selected version.

• Select a version and rename it.
• Select a version and withdraw it.
• Select two versions and click Diff to compare the differences.

Setting the maximum number of multi-version quotes

In the default configuration, you can create three versions by using multi-version quoting. In config.xml in Studio, the
maximum number of quotes is 3. To change the maximum number of multi-version quotes, change the parameter
values. The parameters are:
• RenewalMaxQuotes
• RewriteMaxQuotes
• SubmissionMaxQuotes
• PolicyChangeMaxQuotes
See also
• Configuration Guide

168 Multi-version quoting

part 4

Policies

In PolicyCenter, you can work on policies within the Policy tab. The policy file is the electronic file in which
PolicyCenter stores policy information that is part of the legal contract. You use policy transactions to work with the
policy file. For example, policy transactions allow you to create, modify, cancel, and perform other actions on policies.
See also
• “PolicyCenter policy transactions” on page 83

Policies 169
Guidewire PolicyCenter 10.2.3 Application Guide

170 Policies
chapter 24

Policy basics

Copying data between policies

PolicyCenter allows you to copy data from an existing policy or policy transaction to an open policy transaction. In the
base configuration, this functionality is available in the personal auto line of business. By configuring PolicyCenter,
you can add this functionality to other lines of business.
In personal auto, you may want to copy data between policies for one of the following reasons:
• An agent added a car to the wrong personal auto policy. The agent can copy the car over to the correct policy
without needing to reenter the information.
• A family has a personal auto policy that covers several vehicles. A daughter moves out of the house, and her
parents give her one of the vehicles. The daughter gets her own account and personal auto policy. The agent copies
the vehicle from the parents’ policy to the daughter’s policy. The agent does not need to reenter the vehicle
information in the daughter’s policy.
• The daughter buy a new vehicle and returns the old vehicle to her parents. The agent reinstates the old vehicle by
copying the vehicle from an earlier version of the parents’ or daughter’s policy onto a policy change for the parents’
policy.
Searching for policies and policy transactions from which to copy data
You can copy data if you are in one of the following types of policy transactions:
• Submission
• Policy change
• Rewrite
• Rewrite new account
• Renewal
From within one of these policy transactions, you can search for both bound policies and policy transactions to copy
data from. The search finds bound policies and policy transactions with the same product type as the current policy
transaction. You can copy data from other policy terms or other policy transactions on the current policy.
When searching for policies or policy transactions to copy from, each search result represents a slice of the policy at a
particular time. The slice contains the entities available from that slice of the policy.
For policy transactions, PolicyCenter displays the slice on the edit effective date of the policy transaction. For policy
terms, PolicyCenter displays the last slice of the policy period.
Policy basics 171
Guidewire PolicyCenter 10.2.3 Application Guide

When you select a policy transaction to copy from, PolicyCenter displays the slice on the edit effective date of the
policy transaction. For policy terms, PolicyCenter displays the last slice of the policy period. For policy terms, you
have an option to specify a date which represents the slice of the policy at that particular time. PolicyCenter displays
the entities available from that slice of the policy.

Copy data and multi-version quoting policy transactions

You can copy data to and from multi-version quoting policy transactions.
• Copy data to – When working in a multi-version quoting policy transaction, you can copy data to any version of
that multi-version quoting policy transaction. PolicyCenter copies the data to the version that you are currently
working in.
You cannot copy data to all versions of a multi-version quoting policy transaction in one copy data action.
• Copy data from – You can copy data from any single version of a multi-version quoting policy transaction.

Copy data and side-by-side quoting policy transactions

In one copy data action, you can copy data to a single version side-by-side quoting policy transaction. However, if you
use copy data on a side-by-side quoting policy transaction, any base data you copy to the version you are working with
gets copied to the other versions. This behavior is the same as making a change to the base data in the PolicyCenter
user interface: PolicyCenter copies that change to the other versions.

Including child entities when copying data

In some cases, you can include the children of an entity when copying data. For example, when copying a vehicle, you
can choose to copy all or selected coverages. The vehicle details, except for assigned drivers, are copied by default.
Copy data always includes certain child entities when copying the entity. For example, copy data always includes the
following:
• Personal vehicle modifiers – specify features of the vehicle such as whether the vehicle has a passive restraint
system or anti-lock brakes. Copy data always copies vehicle modifiers because they are part of the vehicle.
• Coverage terms – Are always copied when copying a coverage.

Configuring copy data for a line of business

In the base configuration, copy data is available in the personal auto line of business. You can modify the personal auto
line to meet your business needs. You can also configure copy data in other lines of business.
Copy data enables you, the user, to quickly and accurately take information from one policy and copy it to a policy
transaction for another policy. In addition, you can copy data from prior versions or policy transactions of a policy to
the current policy transaction. Copy data enables copying information from a source period into a target period by
providing the following:
• A mechanism for searching and selecting the source period.
• A user interface that controls which items to copy from the source period.
• Copier and CompositeCopier classes that copy the information from the source period data into the target period.
These classes are in the gw.api.copy namespace.
See also
• Product Model Guide

Split and spin-off policies

PolicyCenter allows you to split an existing policy into two policies. PolicyCenter also allows you to spin-off a single
policy from an existing policy.
In the base configuration, this functionality is available in the personal auto line of business. By configuring
PolicyCenter, you can add this functionality to other lines of business.

172 Policy basics

 Guidewire PolicyCenter 10.2.3 Application Guide

Note: The ability to split and spin-off policies from an existing policy requires that copy data is configured for
that line of business.
In personal auto, you may want to split or spin-off a policy for one of the following reasons:
• Split – A couple gets divorced. Both spouses wish to remain with the insurer. The insurer creates two new
accounts, and splits the coverables on the existing policy into coverables on policies in the new accounts. The split
creates two submission policy transactions. The insurer cancels the original policy.
• Spin-off – A son moves out of the house, and takes a car covered on his parents’ policy. The insurer creates a new
account for the son, and moves the car from the parents’ policy to a new policy on the son’s account. Spin-off
creates a single submission. The insurer does not cancel the original policy after spinning-off part of the policy.
Splitting or spinning-off a policy has the following features:
• The data available to include on the split or spun-off submissions comes from the last slice of the bound policy.
• PolicyCenter creates a link between the source policy and any submissions or policies split or spun-off.
• The account that contains the split or spun-off policies can be the current account, a related account, or an arbitrary
account.
• The producer of record and the producer of service on the submission are both set to the current producer of service
on the policy. You can change both of these during completion of the submission.
• You can select the primary named insured from all named insureds on the account.
• The new submissions are of the same product as the source policy.
• You cannot create new submissions with a company contact as the primary named insured if the product does not
support company contacts.

Configuring split and spin-off policies

This topic describes how to configure split and spin-off policies. A line of business that provides the ability to split and
spin-off policies requires that copy data be configured for that line of business.

Object model
A source policy and the policies split or spun-off from it are connected by fields in the object model. The
DividedPolicies array on the source policy provides access to policies split or spun-off from the source policy. The
DividedSourcePolicy foreign key points from a split or spun-off policy back to the source policy. A split or spun-off
policy can have only a single source policy as shown in the following diagram.

Policy Split Object Model

Policy
DividedPolicies

Legend

* A B A has 0 or more Bs
Policy *
DividedSourcePolicy

Policy basics 173

Guidewire PolicyCenter 10.2.3 Application Guide

Gosu classes
The gw.product.DividePolicySelection Gosu class collects basic information for creating the submission for a
split policy. The basic information includes a ProducerSelection object, the QuoteType, and an AccountContact to
create the PrimaryNamedInsured.
After collecting the basic policy information, the createSubmission method creates a new submission. Next in the
initializeSubmission method, a PolicyPeriodCopier object copies policy data to the submission. Split policies
have two DividePoliciesSelection objects, one for each submission. These objects are independent and are not
directly connected.

Earned premium
The Earned Premium is the portion of premium that applies to the expired part of the policy period. In other words, the
amount of premium that has been earned as of the current date. For reporting policies, prior to final audit, the
calculation includes the earned-but-unreported (EBUR) amount. For package policies, earned premium is shown for
each line of business. You cannot edit the value of this field.
Click Calculate Earned Amount as of different date to see the earned premium on a different date. This does not affect
the calculation on the Summary screen.
See also
• Configuration Guide.

Loss ratio
The Loss Ratio represents the total loss incurred for claims divided by the current earned premium. The claim system
provides the claims amount. If enabled, the built-in integration with ClaimCenter provides the total loss incurred. If
you are not integrated with a claim system, the loss ratio is always 0.
The loss ratio fields are not automatically updated each time you display the Summary screen. Click Recalculate Loss
Ratio to update these fields.

The equation for loss ratio, expressed as a percentage, is:

Loss Ratio = 100 * Total Loss Incurred / Earned Premium

Policy object model overview

The following object model diagram shows some of the basic relationships of policy objects. This diagram focuses on
the entities that interact with the Policy entity.
Note: See the Data Dictionary to see a complete list of all properties in the entities. The diagram and entity
descriptions contain a partial list, highlighting those that may be of interest to you.

174 Policy basics

 Guidewire PolicyCenter 10.2.3 Application Guide

Policy Object Model

Legend PriorPolicy Policy LossHistoryEntry

A has a one-to-one
A B
relationship to B LossHistoryType
A has a one-to-many PackageRisk
A B
relationship to B CreateUser
PriorTotalIncurred
A B A is a subtype of B

A B A delegates to B
Note
A B A has a foreign key to B

ProducerCodeOfService

Document Account

ProducerCode
Job

Subtype

PolicyPeriod

PeriodStart
ProducerCodeOfRecord
PeriodEnd
PaymentPlanID
PolicyNumber

Policy entity
A policy is a contract of insurance that describes the term, coverage, premiums, and deductible. A policy protects the
insured from accidental loss. A policy also lists the people or properties being insured against loss. If an insurer offers a
policy and an insured accepts the terms in the policy, it becomes bound and is an enforceable legal document. Policies
are defined by dates or periods of time. For example, your auto policy is in force from January 1st to June 30th. These
are called policy periods.
The Policy has access to individual note types through derived properties such as creditworthyNotes and
generalNotes.

The main foreign keys to Policy are:

• Document • NoteSearchCriteria
• DocumentSearchCriteria • PolicyPeriod
• Job • PriorPolicy
• LossHistoryEntry • UserRoleAssignment
• Note

Job entity
The Job entity contains these subtypes: Audit, Cancellation, Issuance, PolicyChange, Reinstatement, Renewal,
Rewrite, and Submission. Each policy transaction processes a policy in a different way. The Submission, Rewrite,
and Renewal jobs (policy transactions) create new policy periods and new policy terms. You can access all the jobs for
a policy from the Jobs array.

Policy basics 175

Guidewire PolicyCenter 10.2.3 Application Guide

Other entities associated with policies

The Note and Document entities have foreign keys to Account, Policy, Job, and PolicyPeriod. The Message entity
has foreign keys to Account, Policy, PolicyPeriod.
Entities such as Note, Message, and Document have foreign key references to Policy because they span the life of the
policy, not just a time period.
The PriorPolicy entity contains information about the prior policy.
The LossHistoryEntry entity contains information about prior policy losses.
The ProducerCode entity identifies the producer of service and has fields such as ProducerStatus and Description.
It also has a foreign key to PreferredUnderwriter.

Policy term and policy period entities

The following illustration shows some of the entity relationships for the PolicyTerm and PolicyPeriod entities. The
PolicyTerm and PolicyPeriod entities represent different information about the contractual period of a policy.

PolicyTerm and PolicyPeriod Object Model

PolicyLine Legend
Job
Subtype A has a one-to-one
A B
Subtype relationship to B
EffectiveDate
PolicyID Lines A has a one-to-many
ExpirationDate A B
relationship to B

A B A is a subtype of B
UWIssue
Policy PolicyPeriod A B A delegates to B
IssueType
LossHistoryType PeriodStart IssueKey A B A has a foreign key to B
PackageRisk PeriodEnd EffectiveDate
CreateUser PaymentPlanID ExpirationDate
PriorTotalIncurred PolicyNumber

PolicyContactRole

EffectiveDate
PolicyTerm ExpirationDate
DepositAmount
TotalEstimatedPremium PolicyLocation
TotalReportedPremium
PrimaryLoc
EffectiveDate
PolicyPeriodWorkflow ExpirationDate

Form

EffectiveDate
ExpirationDate

Policy term entity

The PolicyTerm entity represents a policy term, or one contractual period for the policy. The contractual period
extends from the date the policy goes into effect (the effective date) to the date it expires (the expiration date). For
example, if a homeowners policy has a year long period starting on January 1, calendar year 2013 is one policy term.
There is only one PolicyTerm entity for each contractual period. The fields on the PolicyTerm entity apply to the
whole contractual period. Unlike the PolicyPeriod entity, the PolicyTerm entity and its subentities are not revisioned.
PolicyCenter creates a new PolicyTerm whenever PolicyCenter completely recreates the policy contract. PolicyCenter
completely recreates the policy contract with a new policy submission, a renewal, or a rewrite of an existing contract.
PolicyCenter does not create a new PolicyTerm when you amend a policy contract with a policy change job. The
PolicyTerm has a foreign key to the Policy. The PolicyTerm and Policy entities have arrays of PolicyPeriod
entities.

176 Policy basics

 Guidewire PolicyCenter 10.2.3 Application Guide

Policy period entity

The PolicyPeriod entity stores information for a specific revision of the contractual period of a policy. A revision
occurs anytime a job occurs on a policy. A submission creates the first revision. Each additional transaction on the
policy (such as a policy change) creates a new revision. Therefore, a policy almost always has multiple revisions, with
one PolicyPeriod entity for each revision. During the contractual period, only one PolicyPeriod entity is in effect at
a time. The PeriodStart and PeriodEnd properties contain the start and end dates of the contractual period.
Each PolicyPeriod entity is the root of a complex graph of subentities such as policy lines, vehicles, coverages, and
many others. These subentities have EffectiveDate and ExpirationDate fields which specify when the entity
becomes effective and when it expires. The EffectiveDate and ExpirationDate are bounded by the contractual
period (represented by the PeriodStart and PeriodEnd fields on the PolicyPeriod entity).
PolicyCenter creates a new revision when you process a policy change that adds a car to the policy. The
EffectiveDate for the car is several months into contractual period, and the ExpirationDate extends to the end of
the period. PolicyCenter clones a new PolicyPeriod entity and its subentities and adds an entity for the new car. The
contractual period now has two PolicyPeriod entities. The new PolicyPeriod entity is in effect. PolicyCenter
preserves the old PolicyPeriod entity as a historical record of the policy.
Each PolicyPeriod has a Status which is a typekey to PolicyPeriodStatus. The PolicyPeriodStatus typecodes
include values such as Binding, Canceling, Quoted, and Withdrawn. See the Data Dictionary for the complete list of
typecodes.
When you start a new policy transaction (job) or create a new revision, PolicyCenter creates a PolicyPeriod. For a
short amount of time during initialization, the policy period is in Temporary status. However, if an error occurs during
initialization of the job or policy period, the policy period can remain in Temporary status. This policy period may
persist in the database. Because the initialization did not complete, a policy period that is in Temporary status may
contain invalid data. In your code, be sure to check for the Temporary status on PolicyPeriod and to avoid using data
from policy periods with this status.
See also
• “Policy revisioning” on page 193

Policy line entity

A policy can be monoline or multi-line. A monoline policy contains a single type of insurance, such as personal auto.
A multi-line policy contains more than one type of insurance, such as a commercial package policy with property and
general liability. PolicyLine contains subtypes which include: BusinessOwnersLine, PersonalAutoLine, and
WorkersCompLine.

The PolicyPeriod entity has boolean fields (such as BOPLineExists or CPLineExists) for each policy line. The
boolean field indicates whether or not that policy line exists on the policy period. If the policy line exists, then the
BOPLine or CPLine field, for example, allows you to access the policy line.

Workflow entity
The Workflow entity has more than one subtype, but the one that pertains to PolicyPeriod is PolicyPeriodWorkflow.
PolicyPeriodWorkflow has a foreign key to the policy period associated with this workflow.

Job entity
The Job entity has subtypes of Audit, Cancellation, Issuance, PolicyChange, Reinstatement, Renewal, Rewrite,
and Submission. It contains foreign key references to Policy and other entities.

Policy file user interface

Info bar in policy file
In the policy file, use the Info bar at the top of the screen to quickly view main information about the policy.

Policy basics 177

Guidewire PolicyCenter 10.2.3 Application Guide

The first item indicates where you are. In this example, you are in the policy file. The second item displays the policy
type. The third item displays the primary named insured for the policy. The fourth item displays the account number. If
you click that link, PolicyCenter takes you to the Account File for the insured. The next item is the policy number.
Depending on where you are in the policy file, this too can be a link. The final item displays the policy status. In this
example, you can see that the policy is in force and when it is due to expire. Other status messages include information
on whether a submission needs approval, or who the underwriter is.

Actions menu in policy file

When viewing the policy file, use the Actions menu to start an action to the policy. Actions on the policy include
starting contextually appropriate policy transactions on the policy. The Actions menu is contextual and displays only
the actions that apply to the policy at that time. For example, if a policy is scheduled for cancellation, then one of the
options available to you would be to rescind the scheduled cancellation.

Policy contract in policy file

The Policy Info screen in the policy file contains policy information that is part of the legally bound policy contract.
The links in this section vary by line of business although all share certain steps, such as Policy Info, Forms, and
Payment.

Tools menu in policy file

The Tools menu contains links to supporting information that apply to the policy. This menu is context-sensitive.
Items in the Tools menu can include:
• Summary – View the contents of the policy file summarized on one screen. The screen also includes information
regarding current activities, policy transactions, and policy transactions in progress.
• Billing – View overall balance and balances for individual policy periods. You can also view the payment schedule.
• Contacts – View contacts that have a role on the policy. For each contact, you can view basic contact information
and the roles the contact plays on the policy.
• Participants – This screen lists the users that interact with the policy by the role that they perform on the policy. The
screen also shows the assigned group that the user belongs to. You can add or remove participants. For existing
roles, you can change the user who performs that role.
• Notes – Search and view notes related to the policy transaction or policy.
• Documents – Search and view any attached documents related to the policy transaction or policy.
• Policy Transactions – View summary information about all policy transactions that have occurred on the policy. The
list includes policy transactions that have modified the policy and policy transactions that are in-progress,
withdrawn, not taken, or non-renewed. You can also compare policy transactions.
• Risk Analysis – View any issues that may affect the policy. This section includes underwriting referral reasons,
underwriting issues, claims, prior policies, or prior losses. You can also add, close, or reopen underwriting referral
reasons.
• History – Search and view historical events that pertain to the policy. You can filter history events by the following:
◦ User
◦ Timestamp – Specify From and Until dates.
◦ Related To – This drop-down list allows you to filter events for a specific policy transaction or to show all
events.
The History screen displays the following information for history events: Type, User, Event Timestamp, Description,
Job, Original Value, and New Value. In the base configuration, submission, renewal and other policy transactions log
history events. For more information, see the Configuration Guide.

178 Policy basics

 Guidewire PolicyCenter 10.2.3 Application Guide

Policy Summary in policy file

General use
The screen summarizes information about a policy, providing useful information for underwriters and other people who
make decisions about policies. For example, it provides all the information you need when deciding to renew a policy.
In this screen, you can:
• Change, cancel, or renew a policy
• Review the financials of this policy
• Check the loss ratio on this account
• Review or add notes about the account
• Check latest policy terms, transactions and claims
See also
• Configuration Guide

How to access
This summary screen is available:
• In the Policy tab
• From any screen that contains the reference to a policy, for example Account Holder Summary, or Account Summary
• Through search results

Panels in this screen

Details
Displays information about the policy, so that you can make sure you are looking at the right one. You can:
• Go to the Account Holder Summary window by clicking the link in the Primary Named Insured field.
• Depending on the status of this policy, you can perform different actions in the New Transaction menu. For
example, you can change, cancel, or renew the policy.

Term Financials

Displays financial information related to this policy term only, such as total premium for this term. You can check
the loss ratio for this policy. To get the latest information, click Recalculate Loss Ratio.
In final audit of a workers compensation policy, there is more info in this panel about what the earned premium will
be. Seeing the estimated premium, the underwriter can better determine the value of this policy.
If the policy is a commercial package there is no earned premium in each policy, but earned premium exists in the
package.

Current Activities
Displays the last five activities for this policy. It displays open activities first, starting with the highest priority and
latest. You can open an activity by clicking its subject. If there are more than five activities, you can view them all
by clicking View more.
Pending Policy Transactions
Displays the last five policy transactions which are still open. You can:
• Open a transaction by clicking its number.
• If there are more than five policy transactions, you can view them all by clicking View more.

Claims

Policy basics 179

Guidewire PolicyCenter 10.2.3 Application Guide

If PolicyCenter is integrated with a claim system, displays the status of the latest five open claims for this account
holder. (For example, if integrated with Guidewire ClaimCenter, PolicyCenter will get the information from
ClaimCenter.) You can use this panel to answer questions or decide what to do about a request from your customer.
You can view more details about the claim by clicking its number. This action redirects you to your claim system.
If there are more than five claims, you can view them all by clicking View more.

Completed Policy Transactions

Displays the last five policy transactions which are completed. You can:
• Open a transaction by clicking its number.
• If there are more than five policy transactions, you can view them all by clicking View more.

Account

Displays information about the account that holds this policy. You can:
• Go to the account page by clicking the account name
• See how many in-force policies this account has
• See how many open claims this account has

Billing
If PolicyCenter is integrated with a billing system, displays a summary of billing information—how much they
owe, and how much they have paid. You can use this to let the customer know when their next invoice is due, or if
you received their last payment. If integrated with Guidewire BillingCenter, PolicyCenter will get the information
from BillingCenter.
Contacts
Displays the contacts for this policy. You can open a contact by clicking their name. You can also see their roles in
the policy, so that you know who to call about a claim, or to complete an activity. If there are more than three
contacts, you can view them all by clicking View more.
Producer

Displays the names and codes of producers related to this policy.

If there are more than five producers, you can view them all by clicking View more.

Notes
Displays three latest notes. You can review past notes and add new ones by clicking New Note. If there are more
than three notes, you can view them by clicking View more.

Working with policies

Copy data from one policy to another
About this task
You can copy data from other policy periods or other policy transactions on the current policy. To copy policy data, you
must have the Copy policy data permission. The code for this permission is copypolicydata.

Procedure
1. Start or navigate to a policy transaction and line of business that supports copy data. For example, in a personal
auto submission policy transaction you can copy data from another policy.
2. Select Actions > Copy Data.
PolicyCenter displays the Copy Policy Search Policies screen. This screen allows you to search for policies or
policy transactions to copy data from. By default, the Account Number field is set to the account number of the
target policy.

180 Policy basics

 Guidewire PolicyCenter 10.2.3 Application Guide

3. Make a selection from the Search For drop-down list.

Select Search For > Policy to search for a policy. Enter information about the primary insured. You can also search
on the account and policy numbers. You can specify an As of Date to constrain the search results to policy terms
in effect on that date.
Select Search For > Policy Change, Renewal, Rewrite, Rewrite New Account, or Submission to search for a policy
transaction. Enter information about the primary insured. You can also search on the account, policy, and policy
transaction numbers.
PolicyCenter retrieves both open and completed policy transactions. Completed policy transactions include
expired and withdrawn policy transactions. You can optionally select whether to search by effective date or
creation date. You must specify whether you want to retrieve all works orders, or policy transactions within a date
range. PolicyCenter returns a list of matching policy transactions in the specified date range.
Note: You can copy data from other policy periods or other policy transactions on the current policy.
4. Click Search to display the list of Search Results.
5. Click Select to select data to copy from the Search Results.
PolicyCenter displays the Select data to copy from screen. This screen allows you to choose which data to copy
from the selected policy or policy transaction.
For policy transactions, PolicyCenter displays the slice on the edit effective date. For policy terms, PolicyCenter
displays the last slice of the policy period. For policy terms, you can specify an As of Date on this screen. If you
enter an As of Date, the screen displays the entities available to copy as of that date, or slice.
6. Select data. In the Personal Auto Line tab, you can select the following types of data to copy:
• Drivers
• Vehicles – The copy includes modifiers. You can choose to copy all or selected vehicle coverages. You can
choose to copy additional interests.
• PA Coverages
• Exclusions
• Conditions
7. Click the Notes tab to copy all or selected notes.

Split an existing policy into two policies

About this task
These instructions are for splitting a policy. The steps for spinning-off a policy are similar but create a single
submission instead of two.
You must have the Split or Spin Policies permission to view Split Policy into Two and Spin-off Policy from this One from
the Actions menu. The code for this permission is splitpolicy.

Procedure
1. Navigate to an existing policy in a line of business that supports split or spin-off policies. In the base
configuration, the personal auto line of business support split and spin-off policies.
2. Select Actions > Split Policy into Two.
PolicyCenter displays the Split Policy screen with Submission #1 on the left and Submission #2 on the right. Each
submission has the following fields:
Field Description

Account Number Required. Click the account picker icon to choose an account by using the Search Accounts screen.

Policy basics 181

Guidewire PolicyCenter 10.2.3 Application Guide

Field Description

Name After you select an Account Number, this field displays the name of the account holder on the
selected account.

Quote Type Required. Select Quick Quote or Full Application. Default value is Full Application.

Default Effective Date Required. Default value is the current date.

Primary Named Insured Required. Select the primary named insured for the policy. The selection lists all named insureds
on the account. Default value is the account holder.

Select data to include on This section displays the policy data configured for copy data in the current line of business.
new submission (Notes are not available to copy when splitting or spinning-off policies.)
In personal auto, you can select to include drivers, vehicles, coverages, exclusions, and conditions
in the new submission.

3. Make your selections in each submission, and click Create Submissions.

PolicyCenter displays the Split Policies Complete screen. This screen has links to original policy and to the two
submissions split off from it.

182 Policy basics

chapter 25

Policy forms

For the insured customer, the physical representation of an insurance policy is a collection of policy forms. Policy
forms define aspects of the policy such as coverages, exposures, exclusions, and government regulations.
Use policy forms for the information that comprises the policy contract. For generating and tracking information that is
not part of the policy contract, use documents.

Overview
PolicyCenter supports viewing a list of forms in the user interface. You can also integrate with a forms printing system
hosted separately from PolicyCenter. Although printing forms is primarily associated with issuance in a submission
policy transaction, forms can be printed as part of any policy transaction. For example, a policy change might trigger
reprinting a changed form, or printing additional forms that are now necessary because of newly-added vehicles or
other changes.
Note: For what Guidewire calls policy forms, the insurance industry sometimes calls endorsements on a policy.
Guidewire avoids the term endorsements due to its ambiguity in the industry, since endorsements sometimes
refer to policy changes.
All PolicyCenter forms are automatically inferred forms, not manually added forms. In PolicyCenter, forms are not
added explicitly by the user. Instead, PolicyCenter users add coverages, exclusions, and other policy data. Then
PolicyCenter generates forms automatically by using forms inference logic and configuration settings. In addition, the
form itself never contains variable information that is not already encoded in the data model or product model for that
policy.
If a user submits a new auto policy, the forms to print when issuing the policy can be inferred by the coverages,
vehicles, and other fields. If the insured later adds another vehicle to a policy, PolicyCenter determines which forms to
reprint and whether to print entirely new forms for the new vehicle.
In the user interface, forms are listed on the Forms screen after the policy is quoted. The user interface displays a list of
forms not the actual representation of the forms. After quoting, the list of forms is just a preview, not the final list of
forms that will be attached to the policy. After the policy is bound (or after the policy is issued in a submission), the list
of forms may be different. The list may be different because the information to accurately infer some forms is available
only at binding or issuance. When the policy is bound or issued, your integration code sends XML data describing the
form to an external system which prints the forms to paper or electronic format.
The forms feature of PolicyCenter has the following components:

Policy forms 183

Guidewire PolicyCenter 10.2.3 Application Guide

What Where to configure Description

Forms basic In PolicyCenter, go to View or add policy form patterns that can be inferred for policies created in
definition Administration > Business Settings PolicyCenter.
> Policy Form Patterns.

Custom inference Custom Gosu classes defined in You can define custom inference classes to get more advanced behavior
classes Studio. than is possible with the basic forms definitions. These custom classes
define the conditions that determine when to add the form to the policy.

Forms preview No configuration needed. The job (policy transaction) wizard user interface displays a preview of the
list of forms for the current policy.

Form printing Event Fired rules. Custom Event Fired rules intercept forms issuance events and generate messages.
integration messaging plugins. Custom messaging plugins (destinations) that you register must send the
XML payload to the forms printing system. Typically, this occurs only prior
to binding a policy transaction.

If your forms printing system integrates with a document management system (DMS), the printing system can generate
a visual representation of the form and add it to the DMS. After it does this, the integration code can also connect with
PolicyCenter to let it know there is a new document associated with the policy. You can then view the policy from the
Documents screen in the policy file.
See also
• “Policy form pattern administration” on page 725 for more information about how to administer forms.
• The Integration Guide for more information about inference classes, forms printing integration and document
management.

184 Policy forms

chapter 26

Policy data spreadsheet import/export

In PolicyCenter, policy data spreadsheet import/export enables you to export policy data to and from a spreadsheet.
You can review and revise the exported data in a spreadsheet editor. You can import data from a spreadsheet into
PolicyCenter.
You can use policy data spreadsheet import/export to review or enter large amounts of data for commercial policies.
You can review existing policy data in a spreadsheet, add or update the data, then import that data into PolicyCenter.
Policy data spreadsheet import/export uses the Office Open XML Workbook (.xlsx) spreadsheet format.
With policy data spreadsheet import/export you can:
• Export a template to a spreadsheet. The template provides just the column headings and typelists for fields needed
in new submission policy transactions.
• Export policy data to a spreadsheet. The spreadsheet provides a snapshot of a current policy transaction. You can
use this snapshot for review purposes or to make modifications for most policy transactions, including submission,
change, renewal, and rewrite.
• Import updated or newly added policy data from a spreadsheet into PolicyCenter. Prior to committing the import,
you can preview the changes that the import operation will make to the policy, and then accept or reject the entire
import operation.
• Configure export formats that specify the fields to export within each supported coverable.
• Extend this functionality to handle spreadsheet import/export for additional coverables and other lines of business.
In the base configuration, policy data import/export is implemented for buildings and locations in the commercial
property line of business.
See also
• “Importing and exporting policy data spreadsheets” on page 752
• Configuration Guide

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
Policy data spreadsheet import/export 185
Guidewire PolicyCenter 10.2.3 Application Guide

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.

Policy data spreadsheet import/export in commercial

property
With policy data spreadsheet import/export, you can export to and import coverables from PolicyCenter to the Office
Open XML Workbook (.xlsx) spreadsheet format. Assuming you have the necessary permissions, you can perform
the following operations within a submission, change, renewal, or rewrite policy transaction:
• Export a locations template or a buildings template to a spreadsheet. The exported template spreadsheet
contains column headings only and is used to capture data for new submissions. Using a spreadsheet program, you
can enter new data, one row per location or building.
• Export locations or buildings to a spreadsheet. Locations and Buildings spreadsheets are pre-filled with data
describing all existing coverables of a given policy. You can use exported spreadsheets to review policy data or can
be edit to add, remove, or change coverables within a policy transaction.
• Import locations or buildings from a spreadsheet. Coverables can be imported into the same policy transaction
from which they are exported, or into a related policy transaction. A related policy transaction is one whose
basedOn property leads back to the policy transaction that was actually exported. PolicyCenter attempts to find the
matching entities in the graph and change those entities using the data in the spreadsheet you are importing. Before
making any changes, PolicyCenter displays a warning message. By matching policy transactions using the property,
you can export a submission policy transaction and import the result into a policy change based on the exported
submission.
For ease of matching a spreadsheet with a policy transaction, the transaction number is part of the file name that
PolicyCenter proposes when saving the exported spreadsheet. During import operations, you can preview changes
before accepting them. After importing, you can correct any validation errors just as if the data had been entered
interactively into PolicyCenter.
• Use custom export formats. When exporting either a template or a coverables spreadsheet, you can select an
export format that exports only the specific data columns to capture the needed details. Administrators can define
new export formats.

186 Policy data spreadsheet import/export

 Guidewire PolicyCenter 10.2.3 Application Guide

You can extend commercial property policy data spreadsheet import/export in the following ways:
• Customize column headings, including translating headings into other languages.
• Include additional coverage details within the commercial property line of business
You can extend policy data spreadsheet import/export using Guidewire Studio, Gosu code, and an XML editor. You
define the fields to export from each coverable in an XML file, along with the column headings that appear in the
spreadsheet. Spreadsheet column headings are defined as separate attributes. Therefore, they need not match the field
names they represent and can be translated as needed for various locales.

Using spreadsheets generated by policy data spreadsheet

import/export
This topic provides step-by-step instructions for working with spreadsheets exported by the policy data spreadsheet
import/export. The examples demonstrate this feature in the commercial property line of business.
Note: Policy data spreadsheet import/export uses the Office Open XML Workbook (.xlsx) spreadsheet format.
You can use spreadsheet import/export with a legacy version of Microsoft Excel (Microsoft Office 2003 or
prior version). Install a free compatibility pack from Microsoft that enables you to read and write .xlsx files.

Export buildings and locations to a spreadsheet

About this task
To export buildings and locations from a policy in PolicyCenter to a spreadsheet:

Procedure
1. Start a policy transaction in the commercial property line. You can export a spreadsheet during a submission,
change, or renewal. Advance to the Buildings and Locations screen.
2. In the Buildings and Locations wizard step, click Spreadsheet and select Export from the drop-down list. The
Export to Spreadsheet screen appears.
3. Make selections as described in the following table.

Export • Commercial Property Locations – Exports a spreadsheet that enables you to add new locations.
• Commercial Property Buildings – Exports a spreadsheet that enables you to add buildings, If needed,
you can also specify new locations for the new buildings.
The Commercial Property Buildings spreadsheet is useful because you can add both buildings and their
locations in a single operation. PolicyCenter validation requires that each location have at least one
building.

All from this Exports a spreadsheet that contains all existing coverables, enabling you to make changes to existing
version policy data and add new coverables.
You can only import this spreadsheet can into the same policy transaction from which it was exported.

Template for any Exports a template spreadsheet that contains only column headings, enabling you to add new coverables
policy transaction only.
You can use this spreadsheet to import new policy data into any policy transaction.

Format Lists the export formats that have been defined by an administrator. Each export format defines a subset
of fields to export. To export all available fields, select All Available. To export a subset of fields, select the
corresponding format from this list.
Consult the person who designed the export formats to determine the appropriate formats to use for
various situations.

Language Lists available languages. Select the language that appears in the exported spreadsheet column headings.

Policy data spreadsheet import/export 187

Guidewire PolicyCenter 10.2.3 Application Guide

Locale Lists available locales.

4. Click Export to Spreadsheet to export the specified spreadsheet. Specify a location and file name for the
spreadsheet. PolicyCenter provides recommendations for file names to help identify the transaction number and
date for future reference.
5. Use a compatible spreadsheet program to open the exported spreadsheet and fill in the fields.
If you exported a Template for any policy transaction, you can now add rows to the spreadsheet for new
coverables. If you exported All from this version, you can perform either of the following operations:
• Add new buildings or locations
• Make changes to existing buildings or locations

Using exported spreadsheets

You can send exported spreadsheets to agents or customers who then use any compatible spreadsheet application to fill
in the needed details, adding one row per coverable. After you receive a filled-in spreadsheet, you can open it in your
spreadsheet application to visually check the information. Then you can import the spreadsheet into PolicyCenter.
Unless you are importing a template spreadsheet, import the spreadsheet into the same policy transaction (job) from
which it was exported or a policy transaction (job.basedOn) the exported policy transaction. PolicyCenter displays an
error message and aborts the import if the spreadsheet does not match the current policy transaction.
The exported spreadsheets have the following characteristics:
• The individual worksheets of the spreadsheet are protected and designed to be used while protected. If special use
cases require a worksheet to be unprotected, the protection password is 1234. This password can be changed as
explained in the Configuration Guide.
• Some columns of the spreadsheet are read-only so that you do not change their contents. These columns correspond
to read-only fields in the PolicyCenter database. Read-only cells have a light gray background and an italic font.
• Capitalization of data in the spreadsheet is significant. For example, you attempt to add two buildings to the same
location, but spell the city name with different capitalization in each of the two rows. The import operation displays
an error because it assumes you are attempting to change the city name during an Add operation. Only the first
building is added if you complete the import operation.
• Some columns contain lists that have been populated with the contents of a PolicyCenter typelist. In these columns,
you must either select a value from the list or type the value exactly as it is listed, including capitalization.
• Numbers are exported as text to preserve their formatting. For example, class codes must be preserved with leading
zeros, because 0034 is not equivalent to 34. Numbers are converted back to their appropriate types during the
import operation.
• Policy data import ignores columns with headings that it does not recognize. Therefore, you can add notes or other
information to the spreadsheet in unused columns, provided the column heading does not conflict with column
headings used by policy data import/export. Any data you enter in such columns is not imported.
• You can import a spreadsheet only when the imported spreadsheet is basedOn the exported spreadsheet. You cannot
import a spreadsheet that was exported from a different policy or from a different policy transaction in the same
policy. To help you match spreadsheets to policies and transaction numbers, PolicyCenter suggests file names when
saving exported spreadsheets. The pattern of the file name varies depending on the type of spreadsheet.
Policy_PolicyNumber appears at the beginning of the file name only when the policy transaction is not a
submission policy transaction. PolicyCenter does not assign a policy number until a submission policy transaction
is quoted and bound.

Examples of export file names

The following list contains example file names of exported spreadsheets:
• Template_Commercial_Property_Locations_20120514_1432.xlsx

• Template_Commercial_Property_Buildings_20120516_0954.xlsx

188 Policy data spreadsheet import/export

 Guidewire PolicyCenter 10.2.3 Application Guide

• Submission_16004467_Commerical_Property_Buildings_20120601_1014.xlsx

• Policy_5246715349_Policy_Change_16185124_Commercial_Property_Buildings_20120527_1602.xlsx

The string portions of file names are exported in the selected language and are provided only as a convenience to users.
PolicyCenter does not use the file name to match export policy transactions to import policy transactions. Instead it
uses hidden data in the spreadsheet to match the policy transactions. If the policy transactions are not an exact match
but can be linked through the basedOn property, PolicyCenter displays a message that the policy transactions do not
exactly match. If the export and import policy transactions do not match, PolicyCenter displays an error message and
does not complete the import operation.
Use care when choosing localized names containing prohibited characters in such items as file names and spreadsheets,
or that are potentially dangerous when evaluated by operating systems. For example, Microsoft Windows (en_US)
prohibits the use of the following characters in file names:

\ / : * ? " < > |

PolicyCenter converts spaces in the file names to the underscore characters.

Adding buildings and locations

When using the Commercial Property Buildings spreadsheet to add buildings, you can do any of the following:
• Add buildings to existing locations
• Add buildings to new locations
• Add multiple buildings to the same new location
In the Commercial Property line, buildings cannot exist on their own—they are child entities of locations. When a new
building is created, it must be attached to a location, either an existing or newly-created location. In the base
configuration, importing a building that has the LocationID of an existing location creates the new building in the
existing location.
Importing a building that has a blank or unused LocationID creates the new building in a new location. Importing
multiple buildings with identical invalid LocationID fields creates a new location containing all of the new buildings.
PolicyCenter converts the invalid Loc ID columns from the spreadsheet into valid LocationID field values when the
imported spreadsheet is accepted.
Note: The LocationID field is key. If the LocationID does not exist in the PolicyCenter database, the import
operation creates a new location, even if all of the address fields exactly match an existing location. To
determine the LocationID of all of the locations defined within a policy, export a Commercial Property
Locations spreadsheet and find the location IDs in the Loc ID column.

Add buildings to an existing location in the spreadsheet

Procedure
1. In the spreadsheet editor, set the Action column to Add.
2. Leave the Bldg ID column blank, then fill in the other building data columns as needed. Stop when you reach the
Loc ID column.
3. Switch to the worksheet tab named unpopulated entity.CPLocation. This worksheet contains a row for each
location that has no buildings.
4. Locate the row representing the location to which you want to add the building. Select the individual cells that
contain all of the location data and copy them to the clipboard.
Because the worksheets are protected, you cannot copy and paste entire rows. Therefore, you must select and
copy only the needed set of individual cells.
5. Switch back to the Commercial Property Buildings worksheet tab and select the Loc ID cell of the building you are
adding.

Policy data spreadsheet import/export 189

Guidewire PolicyCenter 10.2.3 Application Guide

6. Paste the clipboard contents to fill in the remaining cells with the exact data that defines the location.
7. Repeat these steps for additional buildings.
To add multiple buildings to the same location, paste the same set of location data to as many rows as needed
first. Then fill in the remaining building data for each building. If multiple buildings share duplicate values, copy
and paste those cells between rows. Remember that you can copy and paste only cell ranges, not entire rows.
8. Save and import the spreadsheet.

Add buildings to new locations in the spreadsheet

Procedure
1. In the spreadsheet editor, set the Action column to Add.
2. Leave the Bldg ID column blank, then fill in the other building data columns as needed, until you reach the Loc ID
column.
3. Leave the Loc ID column blank to create a new location for the building.
4. Fill in the remaining location data columns as needed. Note that to successfully import the location, you must
supply a territory code in the Terr Code column that is valid for the specified location. The spreadsheet does not
provide a list of territory codes.
5. Repeat this steps to add more buildings, each at a new location. Upon import, PolicyCenter creates a new location
each time it imports a building that has a blank Loc ID field.
6. Import the spreadsheet.

Add multiple buildings to the same new location in the spreadsheet

Procedure
1. In the spreadsheet editor, set the Action column to Add.
2. Leave the Bldg ID column blank, then fill in the other building data columns as needed, until you reach the Loc ID
column.
3. Type any non-blank value in the Loc ID column. For example, type HomeOffice.
4. Fill in the remaining location data columns as needed.
5. For additional buildings at the same location, repeat steps 1 and 2. Then copy the remaining range of cells
beginning with Loc ID, to the corresponding range in each subsequent row. Note that each building with an
identical Loc ID value is added to the same location.
6. Save and import the spreadsheet.

Make changes to buildings or locations in a policy change

About this task
You can make changes to buildings and locations in either a submission or change policy transaction. In a submission
policy transaction, you can change buildings and locations that have been previously entered or imported but not yet
bound or issued. In a renewal policy transaction, you can add or change existing buildings or locations.
To make changes to buildings or locations in a policy change:

Procedure
1. In a PolicyCenter submission or change policy transaction, export a buildings or locations spreadsheet.
PolicyCenter does not allow you to change location information in a buildings spreadsheet. PolicyCenter displays
an error upon importing the spreadsheet. Change only building information in a buildings spreadsheet; change
location information in a locations spreadsheet.

190 Policy data spreadsheet import/export

 Guidewire PolicyCenter 10.2.3 Application Guide

2. In the spreadsheet editor, select the appropriate action in the Action column for the coverable:
• Blank – Change building or location data. Make the necessary changes within the spreadsheet row.
• Add – Add new buildings or locations. Make the appropriate additions by following the same steps as
described in the previous section.
3. Repeat “step 2” for each building or location that must be changed.
4. Save and import the spreadsheet to PolicyCenter.

Import spreadsheet into policy transaction

Procedure
1. In PolicyCenter open the policy transaction that matches the exported spreadsheet. You can determine which
policy transaction to open by examining the file name of the exported spreadsheet. File naming conventions are
described in “Using exported spreadsheets” on page 188.
2. Go to the Buildings and Locations screen, then click Spreadsheet > Import.
The Import option only appears if the policy transaction is in edit mode. If the Import option is not present when
you click Spreadsheet, make sure the policy transaction is in edit mode by clicking Edit Policy Transaction.

IMPORTANT: A large import operation can overwhelm the PolicyCenter server by creating a very large
bundle file. The exact number of spreadsheet rows that can be imported without problems depends on
system configuration, available memory, system load, and other factors. When the limit is reached, the
PolicyCenter application server stops responding. To ensure satisfactory import performance, Guidewire
recommends limiting the number of rows imported in a single operation to 1000. To import more rows,
you can split the spreadsheet into multiple spreadsheets by cutting and pasting rows. You can cut data
without un-protecting the spreadsheet by selecting the range of cells rather than selecting entire rows.

3. In the Import From Spreadsheet screen, click Import, then navigate to and select the spreadsheet to import. Click
Import to proceed with the import operation.

On import, PolicyCenter detects the language of the spreadsheet. The spreadsheet can be in any language
supported by the PolicyCenter instance, without regard to the language preference of the user importing the data.
For example, PolicyCenter is configured for English, French, and German. In PolicyCenter, an English-speaking
user exports a spreadsheet in French. The French-speaking insured edits the spreadsheet and returns it to the
insurer. A German-speaking user then imports the spreadsheet into PolicyCenter.
4. After the import operation completes, review the Import From Spreadsheet screen to view the results. At this
point, the import operation is not complete and can be abandoned if needed. You can now do any of the
following:
• View the Import Summary to assess the quality of the import operation. You can view the number of locations
or buildings read, edited, added, and removed, and the number of rows that had errors. Any rows with errors
are not imported.
• Click Show Changes to view a comparison that shows the changes that will be made if you accept the changes
and complete the import operation.
When importing a spreadsheet that contains a large number of changes, using Show Changes can potentially
take a long time.
After you have exported a policy transaction, it is possible that a user can make preemptions that affect some
of the exported data. When the spreadsheet is later imported, PolicyCenter handles such preemptions in the
same way as if the preemptions occurred during data entry in PolicyCenter. For information about how
PolicyCenter handles preemptions, see “Preempted jobs” on page 215.
• Click Save Log to save a log file containing the import summary and error information.

Policy data spreadsheet import/export 191

Guidewire PolicyCenter 10.2.3 Application Guide

• Click Cancel to cancel the entire import operation. If your import operation caused errors, consider whether to
resolve these interactively in PolicyCenter or cancel and repeat the import operation after making the changes
in the spreadsheet.
5. Click Accept Changes to complete the import operation and update the policy with the imported changes,
additions, and deletions.

192 Policy data spreadsheet import/export

chapter 27

Policy revisioning

An insurance policy may change one or more times during its lifetime within PolicyCenter.
Policies may change in the middle of a period due to:
• Adding a driver to a policy
• Changing coverage amounts
• Adding a vehicle
• Canceling the policy
• Reinstating the policy
The complete history of all policy changes in legally-binding policies must be carefully tracked, not merely stored in
the latest version of the policy. The policy history might be needed for legal auditing, customer service, financial
reports, or tracking how much to charge customers for a change.
PolicyCenter stores the policy history as a series of policy revisions. Policy revisions are like snapshots of the policy on
date the revision was bound (when it became legally binding). When a revision is bound, that revision represents the
legally-enforced truth of that policy for all effective dates within a single policy period. However, PolicyCenter
preserves older versions of the truth for that policy as historical records. Both the enforced versions and the historical
versions persist and can be used or compared as needed.
In PolicyCenter, policy revisions are often referred to as branches. You can think of a branch as a graph of objects with
PolicyPeriod at the root. The branch collectively represents a policy for one contractual period as of one moment in
real-world time.
To track policy changes over time, a policy must be considered in two different time dimensions:

Dimension How PolicyCenter uses this dimension

model time– The actual real-world time When a branch is bound, PolicyCenter sets its branch model date to match the real-
when policies are created or jobs (policy world date it was bound. Additionally, PolicyCenter increments the policy revision’s
transactions) are bound. This is like model number, which is an integer value that indicates the relative order of multiple
tracking the history of previous changes in versions of the same contractual policy revision. The bound revision with the latest
any online system that has an audit trail. model number is always the currently-active legally-enforced policy revision for that
effective time range. Changes that happen later supersede earlier versions of the
policy for the policy period’s effective time range. However, PolicyCenter keeps older
branches in the database. Older branches are required to view the policy history. Use
this to generate reports of the legally-binding state of the policy at a model date earlier
than today.

Policy revisioning 193

Guidewire PolicyCenter 10.2.3 Application Guide

Dimension How PolicyCenter uses this dimension

effective time – The time dimension of the If the policy period is one year, each PolicyCenter policy period records the policy
policy itself within the policy period. For information for one year of effective time. Some objects on the policy may only exist
example, what time range does the policy for some range of effective time, or have different property values for different ranges
cover? This dimension of time is unique to of effective time.
a policy system.

To contrast the two dimensions of time, suppose a customer calls on March 1. The customer wants to add a car to the
policy as of the beginning of the next month, April 1st:
Model date
March 1
Effective date
April 1, effective until the end of the period

IMPORTANT: Be sure you understand the differences between effective time and model time before proceeding
through this topic. These concepts are extremely critical for understanding the complex sequencing issues
discussed later.

Model time examples

The following are example of model time:
• A customer takes out a policy on a red car. Later the customer calls and apologizes and says it is a blue car. Yet
again the customer calls and says the car really is green. The policy covers the same policy period with the same
effective time but there are three different model dates with changes.
• Policy reports run every quarter must reflect the state of policies on the last day of each quarter, which is the model
date. However, you may not run the report until several weeks later. It is important that the system can query the
policy as of a specific model date and ignore all changes made later (in actual time) after the model date.

Effective time examples

The following are examples of effective time:
• A policy covers one car for an entire calendar year. Halfway through the year, the insured individual buys a used
car. The policy covers the first car for the whole year of effective time. The policy covers the added car for the
second half of effective time.
• A change to an effective date in the future: a customer calls to say they will add a car to the policy as of the
beginning of the next month.
• A change to an effective date in the past: canceling a policy effective last month.

Policy in model time versus effective time

The following diagram shows a policy across model time and effective time.

194 Policy revisioning

 Guidewire PolicyCenter 10.2.3 Application Guide

Comparing Effective Time and Model Time

January effective time December

1 31
March 1 April 1

On March 1, customer opens policy from

March to year end. At this model time, the 1 car
policy across effective time looks like:

model time

On March 2, customer adds another car

effective April 1 through year end. At this
1 car 2 cars
model time, the policy across effective
time looks like:

On March 3, the customer removes the

new car coverage added the day before. 1 car
At this model time, the policy across
effective time looks like:

Key

After multiple changes, only the most recently updated PolicyPeriod is legally enforced. PolicyCenter
Enforced PolicyPeriod
keeps older versions for historical reasons, such as reports with model date earlier than today.

Historical PolicyPeriod

Basic revisioning structure of a policy

Think of a policy as a container of contractual periods, each with a specific range of effective time. A contractual
period is a single policy term from the date the policy goes into effect (the effective date) to the date it expires (the
expiration date). For example, if a homeowners policy has a year long period, calendar year 2008 is one contractual
period. If that 2008 policy is modified, then PolicyCenter saves each version. Each version represents the same policy
in the same period.
The period can be any length and start on any day of the year. A period can be six months, three months, or any
arbitrary length. The main rule is that one policy cannot have contractual periods that overlap in effective time, not
including sections of contractual periods where a policy was canceled or rewritten.
Note: The contractual periods might overlap if there was a cancellation and a new contractual period was
created after the cancellation date. However, their effective time (the non-canceled time range) for the periods
must never overlap.
When a policy renews, the renewal job (policy transaction) creates another contractual period with a different range of
effective time. For example, a renewal job for a 2008 policy period would clone the data for that policy for a new
contractual period with different effective dates for 2009.
Each one of these snapshots of the policy for one period is a branch. PolicyCenter represents each branch in the
contractual period as a PolicyPeriod entity instance. This entity instance is a container for the rest of the objects on

Policy revisioning 195

Guidewire PolicyCenter 10.2.3 Application Guide

the policy, for example vehicles, coverages, and policy contacts. PolicyCenter assigns each period a unique period ID,
which is stored in a PolicyPeriod in its PeriodID property. That value identifies and links all branches for that
contractual period.
As part of making a branch legally enforced, PolicyCenter performs a process called binding. This process is also
called binding a branch or promoting a branch. The result is a promoted branch or a bound branch. When binding a
branch, PolicyCenter sets the ModelDate property in the PolicyPeriod to the real-world date it was bound.
Additionally, if there are earlier versions of this PolicyPeriod entity instance in the contractual period, PolicyCenter
increments the PolicyPeriod model number (the ModelNumber property). It sets it to one greater number than the
most recently bound earlier revision in this contractual period. These model time properties let PolicyCenter track what
is the legally-enforced version of the policy for that period.
Each PolicyPeriod also includes a MostRecentModel property that is true if this PolicyPeriod is the most recently
bound branch for this contractual period. When a branch is bound, if there was another branch in that contractual
period, PolicyCenter sets two things. First PolicyCenter sets this property to false on the previous branch and sets it to
true on the newest branch in the same database transaction. Technically, this is redundant with checking for the
highest model number (ModelNumber) for all PolicyPeriod entities in this contractual period (those that share the
same PeriodID). However, this property is provided to simplify queries that work only with the latest bound branch in
any given period. The MostRecentModel property is very useful for writing reporting queries.
If a PolicyPeriod cannot be modified because the branch is bound, withdrawn, or discarded, PolicyCenter sets its
Locked property to true. This locking prevents accidental changing of that PolicyPeriod or any of its subobjects.
PolicyCenter enforces this locking at the application level.
Note: You can customize application logic before promoting a branch. For more on this topic, see the
Integration Guide.

Subobjects
Every policy revision branch is represented by a PolicyPeriod entity instance at the root of a complex graph of
subobjects such as policy lines, vehicles, coverages, and many others. The entire hierarchy of Guidewire entities are
cloned in the database into new rows during policy changes, renewals, or other jobs that result in cloning everything in
a branch. In contrast, a submission job’s branch is not cloned from another branch.
PolicyCenter must identify that some rows in the database represent the same real-world thing. This is true for the
following cases:
• Across model time – PolicyCenter typically represents one object (such as a driver or a vehicle) more than once
across model time. PolicyCenter creates one instance each time it copies the branch due to a policy change job or
other job. To understand differences between two historical periods, PolicyCenter needs to know they represent the
same object not multiple different objects.
• Multiple periods – One object (such as a driver or a vehicle) might exist in multiple contractual periods. To
understand differences between two periods, PolicyCenter needs to know they represent the same object not
multiple different objects.
• Across effective time – Some objects change across effective time within one branch. To understand that these are
the same object across effective time, PolicyCenter must know these represent the same object, not different
objects. For example, suppose you have a car on a policy and then need to change the license plate number. The
database contains two rows for the car: one with the original license plate number, one with the new license plate
number. This topic discussed further in “Structure of revisioning across effective time” on page 200.
For these reasons, PolicyCenter knows which rows represent the same object because they share an ID called a
fixed ID, stored in its FixedID property. If the fixed IDs for two vehicles match, they are versions of the same vehicle,
not two different vehicles. If the fixed IDs do not match, they represent different vehicles.
Note: In previous releases of PolicyCenter, the fixed ID was called a revision-independent ID (RIID).

Each subobject also contains a foreign key to the PolicyPeriod entity instance that contains it. This foreign key is
called a branch ID and is stored in the subobject’s BranchValue property. This foreign key always matches the
PolicyPeriod entity instance’s Id property. Remember that this foreign key references the PolicyPeriod unique Id
property, not the PeriodID property that identifies related PolicyPeriod entities in one contractual period.

196 Policy revisioning

 Guidewire PolicyCenter 10.2.3 Application Guide

The following diagram shows the structural relationship of simple policy with two contractual periods. Note in the
diagram:
• Within one contractual period, each PolicyPeriod entity instance shares the same period ID.
• Each PolicyPeriod entity instance has a model number that increments for each revision in the contractual period
each time a change is made in model time (real-world time).
• Each subobject contains a branch ID that identifies its root PolicyPeriod entity instance, and it matches the
PolicyPeriod.Id property
• Each subobject has the same fixed ID when the subobject exists in multiple branches and even across contractual
periods. For example, a car’s data that was modified has the same fixed ID in each branch that references it. The
fixed ID is also the same in renewal periods if that car is still covered in the renewal period.

Revisioning Structure and IDs

Policy

Contractual Period for Year 2008 Contractual Period for Year 2009
PeriodID 123 PeriodID 456
Effective Time Jan-Dec 2008 Effective Time Jan-Dec 2009

ModelNumber 1
2008 submission
ID 500, PeriodID 123

sub-object BranchID 500, FixedID 123456

Model
Time

ModelNumber 2
2008 policy change
ID 501, PeriodID 123
sub-object BranchID 501, FixedID 123456

ModelNumber 3
2008 policy change #2 ID 502, PeriodID 123

sub-object BranchID 502, FixedID 123456

ModelNumber 1
2009 renewal
ID 503, PeriodID 456

subobject BranchID 503, FixedID 123456

Key

In Force PolicyPeriod

Historical PolicyPeriod

Sub-object of PolicyPeriod

The policy period and effective date fields

The PolicyPeriod entity is the root of the graph of revisioned objects. The PolicyPeriod is the branch that all
EffDated objects in the graph point to. The PolicyPeriod defines the PeriodStart and PeriodEnd.

Although the PolicyPeriod entity is the root of the revisioned graph, it does not behave like other revisioned objects.
The PolicyPeriod entity delegates to the EffDatedBranch interface, but not to EffDated. Because the PolicyPeriod

Policy revisioning 197

Guidewire PolicyCenter 10.2.3 Application Guide

is not EffDated, the PolicyPeriod is handled differently than everything else in the policy period graph and does not
have behaviors like splitting on slice mode edit. Therefore, any property, such as one containing data, a typekey, or
foreign key, placed directly on PolicyPeriod behaves differently than one placed on EffDated objects such as
PolicyLine or PolicyLocation.

A property added directly to PolicyPeriod is for the full term. These properties always have the same value from
PeriodStart to PeriodEnd. You can still edit a property value on PolicyPeriod in a policy change, but that value
replaces the former full term value. The value is not effective as of the effective date of the policy change job.
For example, the PolicyPeriod has unrevisioned properties that apply to the full term. Some of these properties are:
• TermNumber – An integer
• CreateUser and UpdateUser – Foreign key to User
• Job – Foreign key to Job
Revisioned properties related to the PolicyPeriod are off of the EffectiveDatedFields object. Some of these
revisioned properties are:
• OfferingCode – A patterncode
• ProducerCode – Foreign key to ProducerCode
• PrimaryLocation – Foreign key to PolicyLocation
• PrimaryNamedInsured – Foreign key to PolicyPriNamedInsured
• BillingContact – Foreign key to PolicyBillingContact
• PolicyAddress – Foreign key to PolicyAddress
These properties are all items that are revisioned but not tied to a PolicyLine. For convenience, the PolicyPeriod
object defines derived properties that enable you to access these revisioned properties. For example, you can access
EffectiveDatedFields.BillingContact through the derived property PolicyPeriod.BillingContact.

The following diagram shows PolicyPeriod and EffectiveDatedFields entities.

198 Policy revisioning

 Guidewire PolicyCenter 10.2.3 Application Guide

PolicyPeriod and EffectiveDatedFields entities

PolicyPeriod
TermNumber EffectiveDatedFields
UpdateTime OfferingCode
WrittenDate

User PolicyLocation
PrimaryLocation

Job ProducerCode

ProducerCode PolicyPriNamedInsured

Legend
PolicyBillingContact
A B A has a B

A delegates to
A
EffDated
PolicyAddress
A delegates to
A Retireable and
EventAware

Arrays and one-to-one relationships of EffDated objects behave the same whether placed on the PolicyPeriod or an
EffDated object. All array or one-to-one relationships have a foreign key back to the object to which they are attached.
Arrays of EffDated objects attached to a PolicyPeriod vary across effective time. For example, the PolicyPeriod
has an array of PolicyContactRole objects that are EffDated. You can determine array membership by the
EffectiveDate and ExpirationDate. For example, on 1/1/2019, the array contains one PolicyContactRole object.
On 3/1/2019, a policy change adds two PolicyContactRole objects. On 5/1/2019, another policy change removes the
first PolicyContactRole.

Deciding whether to add a property to policyperiod or effectivedatedfields

A property defined on the PolicyPeriod object behaves differently than a property defined on the
EffectiveDatedFields object.

The PolicyPeriod has a ProducerCodeOfRecord foreign key which points to a ProducerCode. However, if you move
the ProducerCodeOfRecord foreign key from PolicyPeriod to EffectiveDatedFields, there could be more than one
ProducerCodeOfRecord for the period. The ProducerCodeOfRecord could vary over effective time.

Suppose you have a submission with the policy period extending from 1/1/2019 to 1/1/2020. The
ProducerCodeOfRecord is Alpha:

• Foreign key on PolicyPeriod – The producer code of record for the submission is Alpha.
• Foreign key on EffectiveDatedFields – The producer code of record for the submission from 1/1/2019 to
1/1/2020 is Alpha.
On the submission, both ways of representing the producer code of record are effectively the same. Now you do a
policy change effective 7/1/2019 and change the ProducerCodeOfRecord to Beta:
• Foreign key on PolicyPeriod – The producer code of record for the policy change is Beta. The producer code of
record is effective for the full policy period.
• Foreign key on EffectiveDatedFields – The producer code of record is Alpha from 1/1/2019 to 7/1/2019, and
then it is Beta from 7/1/2019 to 1/1/2020.

Policy revisioning 199

Guidewire PolicyCenter 10.2.3 Application Guide

With the foreign key on an EffDated entity, you have a split in effective time when you change the policy period. The
foreign key was one value, and at some date it changes to another value. When the foreign key is on the
PolicyPeriod, any change is for the full period. For the policy change it is Beta for the full term—there is no concept
that is was Alpha for some dates and then Beta for other dates. You can still go back in history and see that the
submission had a different value. This is the key difference between the two models.

Structure of revisioning across effective time

Every policy revision (a PolicyPeriod entity instance) is the root of a complex graph of subobjects such as policy
lines, vehicles, coverages, and many other objects. If one object such as a vehicle does not change across
effective time, the database contains only one row for that object at that model time. However, if the object changes
across effective time, the object is cloned into a new row in the database, differing in effective time begin and end
dates. The insurance industry calls these begin and end dates the effective date and expiration date.
For example, suppose on March 1 a customer requests an auto policy for a red car, effective from March 1 through the
end of the year. On August 1, the customer calls and says the car was painted today and is now blue.
PolicyCenter represents these changes across effective time for the vehicle as two rows:
• A red car with effective date March 1 and expiration date August 1 (typically at 12:00am)
• A blue car with effective date August 1 and expiration January 1 of the next year
Note that the expiration date of the first row is the same as the effective date of the second row. This means the first
row is effective up until the exact date and time of expiration, but not including that exact date and time. A row is
effective at date specified_date if the following equation is true:

effective_date <= specified_date < expiration_date

Effective dates are stored in the EffectiveDate property of each PolicyPeriod subobject. If the EffectiveDate
property is null, implicitly the effective date of the subobject is the effective date of the PolicyPeriod that contains
the object. The effective date of the PolicyPeriod object is in the PolicyPeriod.PeriodStart property.
Expiration dates are stored in the ExpirationDate property of each PolicyPeriod subobject. If the ExpirationDate
property is null, implicitly the expiration date of the subobject is the expiration date of the PolicyPeriod that
contains the object. The expiration date of the PolicyPeriod object is in the PolicyPeriod.PeriodEnd property.
The following diagram represents the structure of revisioning across effective time, showing a single vehicle subobject
in an auto policy. Notice that a policy change of an existing object can sometimes split an object into two objects. Each
object has different effective time ranges. These objects have the same FixedID values since they represent the same
object. However, when adding an entirely new object such as a vehicle, the new entity instance has a different FixedID
value. The new fixed ID shows that it represents a new vehicle, not a change to an existing vehicle.

200 Policy revisioning

 Guidewire PolicyCenter 10.2.3 Application Guide

Subobjects Across Effective Time

Contractual Period
For the year 2008

New auto policy for a red car, effective for all days in 2008
PolicyPeriod for submission ModelNumber 1

Subobject

VEHICLE A PolicyPeriod entity’s subobject has an EffectiveDate or

Color: RED ExpirationDate field to indicate the effective date range. If
EffectiveDate: null they are null, they implicitly use the start date and end date
ExpirationDate: null of the containing PolicyPeriod. In this case, both are null,
FixedID: 12345 which means the effective date range is the entire year.

Change the car’s color to blue, effective August 1 through year end

PolicyPeriod for policy change ModelNumber 2

Policy changes can split entities. One has

VEHICLE VEHICLE effective time range before the change’s
Color: RED
Color: BLUE effective date, and another has changes
EffectiveDate: null
EffectiveDate: August 1, 2008 after that date. Also note the same FixedID
ExpirationDate: August 1,
ExpirationDate: null
2008 values means they are the same car, with
FixedID: 12345
FixedID: 12345 different effective date ranges.

Add additional (new) car to policy, effective September 1 through year end

PolicyPeriod for policy change #2 ModelNumber 3

VEHICLE VEHICLE VEHICLE

Color: RED Color: BLUE Color: GREEN
EffectiveDate: null EffectiveDate: August 1, 2008 EffectiveDate: Sept 1, 2008
ExpirationDate: August 1, 2008 ExpirationDate: null ExpirationDate: null
FixedID: 12345 FixedID: 12345 FixedID: 67890

The different FixedID means it

represents a different car.

Key
Enforced PolicyPeriod Historical PolicyPeriod Subobject of PolicyPeriod

Policy revisioning 201

Guidewire PolicyCenter 10.2.3 Application Guide

Unbound policy revisions

All legally-binding versions of a policy are kept as a series of ordered revisions in the database. However, PolicyCenter
also stores revisions that are not part of the official legally-binding history of the policy.
Examples of unbound branches include:
• Branches for unfinished jobs, such as in-process policy changes. These are sometimes called draft revisions or in-
progress revisions.
• Withdrawn policy changes, withdrawn by selecting Withdraw Policy Transaction before changes were bound.
• Rescinded cancellations (before changes were bound)
• Unbound versions (unselected versions) of a multi-version quoting job. At most one version can be bound for a job.
Non-bound revisions are stored in the same database tables as bound revisions, differing only in their Promoted
property. If the Promoted property value is true, it was made legally binding. However, it may not be the only one in
that period. The branch with the highest model number is the enforced branch for that contractual period, which is
found most easily by using the Boolean property MostRecentModel.

Slice mode and window mode overview

There are two ways to access a branch’s subobjects: slice mode and window mode.
In most cases, a job changes its policy data effective as of a specific date in effective time. This date is stored on a
PolicyPeriod as the EditEffectiveDate. Most changes for a job (and sometimes all changes for that job) will
happen in effective time as of that date. Because this is the typical way to edit a PolicyPeriod and its subobjects,
PolicyCenter includes a special way to view the branch as of that effective date. PolicyCenter can hide subobjects that
are not effective at the desired date. This way to view the branch is called slice mode, and is the most common way
PolicyCenter accesses policy data. Most edits are made at this date, called the slice date.
When working with a PolicyPeriod, the PolicyPeriod is typically already in slice mode. For example, if you access
a PolicyPeriod as a reference for a job, the PolicyCenter job has probably set the slice date to the job’s effective date.
This is true for almost all code that you will work with. You typically do not need to do anything special to setup the
PolicyPeriod slice date if you want to work with the branch at the effective date. Simply access the properties on
objects referenced from the PolicyPeriod in a job and work with it as a graph of objects. The slice date does not
persist. PolicyCenter stores this only on the in-memory PolicyPeriod entity instance accessed by Gosu. PolicyCenter
never stores this in the database row with the PolicyPeriod.
Note: The slice date (and more generally, the slice mode or window mode status) is stored on each in-memory
copy of effective dated entities. This information is not persistent in the database row.
In contrast, sometimes you must view all versions of an object across all dates in effective time. This view is called
window mode. For example, suppose a policy covered one car on an annual policy that starts at the beginning of the
year. On March 1, the insured buys a new car and adds it to the policy. On March 10, she sells the old car and removes
it from the policy.
• In slice mode viewed as of February 15, the policy contains only the first car.
• In slice mode viewed as of March 5, the policy contains two cars.
• In slice mode viewed as of April 1, the policy contains only the newer car.
Note: When you view a policy in slice mode at any given effective date, you might not see all cars that exist at
some point in that policy period.
Instead, suppose you want to display a page that lists all cars that exist on the policy for any amount of time. For each
car, you want to list the effective date ranges for each car. To do this effectively:
1. Get a list of all cars that were ever on the policy. There is one entry for each car, regardless of whether it changed
over effective time.
2. For each car, iterate across all changes to that particular car across effective time. There is exactly one row in the
database for each version of that car. For example, if the car has had three different colors, there are three rows in

202 Policy revisioning

 Guidewire PolicyCenter 10.2.3 Application Guide

the database that represent that car. The set of three rows that represent this one car is called a version list. From
the version list, you can access every version of the car in the period. In this case, the version list contains three
versions of the car, each with a different color.
When you request all cars on the policy in slice mode, PolicyCenter automatically gets the correct version of each car
as of the slice date. Also, PolicyCenter only returns the cars that are effective at the slice date.
In contrast, you ask for all the cars on the policy in window mode, there is no implicit slice date. PolicyCenter gets a
version list for each car.
For more details about window mode, see, “Window mode API overview” on page 204.

Exposures in general liability and workers’ compensation and getSlice

In the base configuration of general liability and workers’ compensation, exposures appear in the user interface in
window mode because of the special way that they are rated. The line-specific implementation, including rating and
sample code, handle these exposures in window mode. If you get exposures on a policy period in slice mode, all
exposures on the policy period are returned regardless of effective date.
You can use the following methods in the sample code as a model for how to handle these exposures in window mode.
These methods do not use the generic getSlice method to get the exposures. For sample code, see:
General liability
GLExposuresWM and AllGLExposuresWM methods in GeneralLiabilityLineEnhancement
Workers’ compensation
AllWCExposuresWM method in WorkersCompLineEnhancement

If you use the generic getSlice method on a PolicyPeriod or other object to access general liability and workers’
compensation exposures, you only get the exposures effective in the current slice, not all exposures in window mode.
There are times where getSlice is appropriate, such as if you need to create a split in the exposure.
Avoid getSlice for viewing data on general liability and workers’ compensation exposures. For editing, you need to
know what your intent is. You can use getSlice if you are getting a slice and making a split. Avoid getSlice for
editing exposures in window mode.

Slice mode APIs

In most cases, you access a PolicyPeriod related to a job. In standard application contexts, PolicyCenter sets up the
PolicyPeriod and sets the slice date to the effective date for the job. Typically you do not need to do anything special
to set a slice date if you want to work with the branch at the effective date. Simply access the properties on entities
referenced from the PolicyPeriod and work with it as a graph of objects.
To ensure you access a PolicyPeriod entity instance in slice mode, you can call its getSlice method:

// get a handle to the PolicyPeriod in slice mode with a specific date and SAVE the return value
slicedPolicyPeriod = aPolicyPeriod.getSlice(sliceDate)

The returned object represents the same PolicyPeriod entity instance, but it is a different object in local memory that
Gosu specially marks as in slice mode. Remember to use the return value from the getSlice, not your original
reference to the PolicyPeriod. The original in-memory copy of the entity instance is unchanged.
If you get properties on a slice mode object to access other objects, those objects are also automatically in slice mode.
In typical code, you can navigate up or down the object graph hierarchy without worrying about the revisioning details.
At any time you can get the object.SliceDate property to get the slice date.
In most cases, it is best to call getSlice on the root PolicyPeriod and navigate down the object graph from there.
However, you can call getSlice on an individual revisioned subobject of PolicyPeriod if necessary.
For example:

autoLineExpiration = vehicle.getSlice(sliceDate).PolicyLine.PolicyPeriod.ExpirationDate

Policy revisioning 203

Guidewire PolicyCenter 10.2.3 Application Guide

The foreign key links after the getSlice method implicitly use the slice date to find the right version of the
PolicyLine.

Note: If a policy period is in slice mode and you get any subobjects, they are in slice mode automatically. it is
redundant to call getSlice with the same slice date.
Be sure that the slice date that you pass to getSlice is in the effective date range for that object. If you try to pass a
date outside the required range, then Gosu throws an exception.
For example, if you removed an auto from an auto policy before the slice date, Gosu throws an exception because that
auto is not effective at that date. However, if you call getSlice on the PolicyPeriod and navigate down the object
graph for that slice, you do not need to worry about unavailable effective dates for subobjects. This is why it is
typically best to call getSlice on the PolicyPeriod and navigate down the object graph from there.
Note: For many use cases, it is best to slice the root PolicyPeriod with a specific slice date. In other words,
call getSlice on the root PolicyPeriod entity instance and then navigate down the object graph from there.

Automatic changes for slice mode edits

When editing objects in slice mode, certain changes happen automatically:
• If in slice mode and you change an existing subobject of the PolicyPeriod, the changed entity instance
automatically splits into two entities. One entity instance represents the change before the slice date and one entity
instance represents after the slice date. The split does not occur if the split date is already the effective date of the
entity instance. If a split is needed, it happens immediately in the in-memory version of the entity instance. Even if
a property is reverted after a split, the entity instance remains split.
• If in slice mode and you add a subobject of the PolicyPeriod, the new entity instance automatically has an
effective date of the slice date.
• If in slice mode and you delete a subobject of the PolicyPeriod, the entity instance automatically has an expiration
date the day of the slice date. However, if the split date is already the effective date of the entity instance, the entity
instance is simply deleted.
• To handle situations like out-of-sequence jobs and preempted jobs, merging changes forward to future effective
dates is not handled automatically in Gosu at the time the change is made. The job process and workflow files
detect this issue at quote time. The job files and PCF files offer the user a chance to apply changes to later effective
dates and resolve any conflicts. For more information, see “Out-of-sequence jobs” on page 213, “Preempted jobs”
on page 215, and “Applying changes to future renewals” on page 218.

Slice mode notes

• You can mark an entity instance in the data model to not automatically split on an edit. For example, PolicyCenter
uses this feature for objects that never split, such as transactions and forms. Other objects can be split but only split
explicitly, for example costs and Workers’ Compensation Jurisdictions. To mark an entity instance to not
automatically split on editing, set the data model attribute autoSplit to false.
• A scalable field that scales as a result of a split shows up in the PolicyCenter list of differences as a window edit.

Window mode API overview

To view objects across all effective time, you can view the policy objects (or a whole branch) in window mode.
Typically you do this with a version list for an object. A version list represents all versions of that one object within one
policy period. For example, a version list for a car represents all versions of that car during the entire policy period.

IMPORTANT: For important overview information about window mode and version lists, see “Slice mode and
window mode overview” on page 202.

In general, you get a version list from a revisioned object by getting its VersionList property. The result has the type
specific to that object with the VersionList suffix, for example a Building version list has type
BuildingVersionList. In the unusual case that you write general purpose code that operates on multiple revisioned

204 Policy revisioning

 Guidewire PolicyCenter 10.2.3 Application Guide

entity types, declare variables as the base type EffDated or EffDatedBase. For those types, instead of getting the
VersionList property, get the property VersionListUntyped.

If you have a version list, you can get various information about the object. For example, get all versions of the object,
or navigate up or down the hierarchy to other entity instances or version lists.
The most important APIs on a version list are as follows. All results are in window mode unless otherwise noted.
• The versionList.AllVersions property gets all versions of this object. All results are in window mode. The
order in the list (the sort order) is the effective date for each version.
• The versionList.asOf(date) method gets the one version of this object on that date, or null if none were
effective on that date.
• If an entity property contains an array of entity instances, Gosu generates two version list properties related to that
original entity property:
◦ Gosu generates a version list property whose name exactly matches the property name on the original object. It
contains a list of all unique objects that are ever in that array at any effective time in the period. For example, a
personal vehicle object contains its drivers in the vehicle.Drivers property. Thus, a vehicle’s version list also
has a Drivers property. It contains a list that contains one version list for each unique driver for that vehicle.
The items in this list have no defined order. Do not rely on the order.
◦ Gosu generates a version list method whose name matches the property name on the original object but with the
suffix AsOf. This method takes a date argument, which is an effective date. The AsOf method returns a snapshot
of that array property as of that effective date. The AsOf method converts and returns the results to a list, which
is typically easier to code with than arrays. For example, a personal vehicle object contains its drivers in the
vehicle.Drivers property. Thus, a vehicle version list has a DriverAsOf(date) method. This method returns
a list of that vehicle’s drivers on that date. The entities are returned in window mode. The items in this list have
no defined order. Do not rely on the order.
Note: Generated methods like DriverAsOf are a rare exemption to the normal Gosu coding rule that method
names always begin with a lowercase character. PolicyCenter capitalizes the first character in this case to
improve Gosu code readability because these methods mirror the original property names with an initial
capital letter.
The following subtopics describe real-world tasks with a version list by using as an example a car (a
PersonalVehicle) and its version list. For code examples, assume that the variable vehicleVL contains a version list
for the car (vehicle.VersionList). There are three versions of this car in this period, each with a different color. The
car’s version list represents exactly three versions of this car.

Get all versions of a particular car

To get all versions of this particular car in the policy period, use the following Gosu code:

var val = vehicleVL.AllVersions

If the car changed twice during the period, such as a color change, the result is a list with three entity instances. Each
represents a different version of this car.

Get the car version that is effective at specified date in window mode
To determine which version of this car (if any) was effective at a specific effective date, and return it in window mode,
use the following Gosu code:

var vehOnDate = vehicleVL.asOf(date)

The result is a single car object returned in window mode, or null if no version of the car is effective at that date.

Policy revisioning 205

Guidewire PolicyCenter 10.2.3 Application Guide

Get the car version that is effective at specified date in slice mode
To get this car’s version that was effective at a specific effective date, and return it ready to make slice mode changes at
that date, use the following Gosu code:

var vehSlicedOnDate = vehicleVL.asOf(date).getSlice(date)

The result is a single car object returned in slice mode, assuming a car is effective at that date. If no car is effective at
that date, it throws a null pointer exception, since asOf returns null. Because the code calls the getSlice method of
the result of asOf, that is a method invocation on a null value.
Note: For more information about null-safety of properties but not methods, see the Gosu Reference Guide.

Get the set of all drivers who were ever drivers of this car
To get the list of all drivers who were ever drivers of this car during this period, use the following Gosu code:

var drivers = vehicleVL.Drivers

The result is a list. The list contains one version list for each unique driver of this particular car. Each version list
represents a single driver. From each version list, you can get all entity instance versions of that unique driver by
getting the version list’s AllVersions property.

Get the set of all drivers who were ever drivers of this car at specified date
To get the list of all drivers who were drivers at a specific date, use the following Gosu code:

var theDate = new Date() // a date object, in this case "today"

var drivers = vehicleVL.DriversAsOf(theDate)

The result is a list containing one or more VehicleDriver objects in window mode. Think of this as a snapshot of the
entity array on that effective date, with all other entities hidden. The type of the result is
java.util.List<VehicleDriver>.

Get the drivers of this car at specified date and return their contact public IDs
To get the list of all drivers who were drivers at a specific date, then get the public IDs for their contacts, use the
following Gosu code:

var arrayOfPID = vehicleVL.DriversAsOf(date)*.PolicyDriver*.PublicID

The DriversAsOf method returns a list of VehicleDriver objects. Each one of those objects links to the actual contact
for that driver through its vehicleDriver.PolicyDriver property. That is the object that contains the driver name and
drivers license number. The Gosu array expansion operator *. extracts data from each item in an array or list, then
returns results in a single-dimension array. Similarly, if you pass it a list, it return returns a list. For details, see the
Gosu Reference Guide.

Safely accessing foreign keys with slice mode

It is important to understand that a window mode entity instance has no slice date. It represents the car over a range of
dates. With a reference to a window-mode entity instance, you can access simple properties such as a String or a
number.
Generally speaking, with a window mode entity instance, do not access links to other entities by using standard foreign
key properties on the object. For example, for a vehicle entity instance in window mode, do not access its PolicyLine
property. In window mode, this property is unclear with respect to the policy line as-of date.
If you access foreign key fields on a window-mode entity instance, Gosu returns the value of that property as of the last
second of the window mode object’s effective time. This is sometimes what you want, but in typical code it is not.
For example, suppose you have a window mode version of a car in a variable called vehicleUnsliced. The
vehicleUnsliced.GarageLocation property returns the garage location as of one second before the expiration date of
the vehicleUnsliced object.

206 Policy revisioning

 Guidewire PolicyCenter 10.2.3 Application Guide

Note: That date might not be the last moment before the expiration date of the car on the policy. It is only the
last moment for this particular window mode object. There may be a version of this object with a later
expiration date.
For typical code, do not rely on this feature to navigate to related objects since the return result is not typically what
you want. Instead, it is typically best to convert the window mode entity instance to a slice mode entity instance and
then access its related objects at that slice date.
Any objects that you access from it are now automatically in slice mode because you accessed them from a slice mode
object.
Compare the following two code examples.
The following code slices a window mode vehicle and then gets its policy line at that date:

unslicedVehicle.getSlice(date).PolicyLine

The following code gets the PolicyLine property from an unsliced (window mode) version of a vehicle, and then
slices that result. This result is potentially different from the previous example. That is because this relies on the
window feature discussed earlier in the topic. Although it looks similar, this code may return a different result from the
first example. This code gets the policy line as of the last moment of this car’s effective date range. Then, the code
slices that policy line at the desired date.

unslicedVehicle.PolicyLine.getSlice(date)

The important thing to notice is that the two lines of code may access different policy lines entirely. The first one
accesses the PolicyLine property as of an explicit date. The second one accesses the policy line as of an implicit date
(one second before the expiration of that window mode entity instance).
Secondly, when you use the getSlice method, the date must be within the effective date range of that individual
version of the object. With that in mind, notice that in the first example, the date must be within the effective date range
of the unsliced car object. In the second example, the date must be within the effective date range of the policy line.
It is important to keep track of which entity instance is most appropriate to call getSlice on. If you do not know
whether the current version is the correct one, get the version list and call its asOf method:

unslicedVehicle.VersionList.asOf(date).getSlice(date).PolicyLine

IMPORTANT: Generally speaking, on a window mode object be careful with directly accessing any foreign key
references or array references. If you access a foreign key or array property on a window mode entity instance,
Gosu returns the value as of one second before the expiration date of that object. In typical code, this is not
what you want. Instead, get the version list, then get the correct window mode version of the object, and then
slice it at an explicit date. Carefully review the Gosu code examples in this topic.

Version list API

The version list API provides methods to access to all versions of an effective dated object across all dates in effective
time for the duration of a policy period.

Version list API methods that query an effective dated object

The following methods on the version list act upon an effective dated object (entity instance). Every version list has
properties and methods that are common to all version lists. The version list also has properties that mirror property
names on the source object.
The version list name includes the entity instance for which it is a version list appended with the suffix VersionList.
For example, a version list for a PersonalAutoLine entity instance has type PersonalAutoLineVersionList.
Examples assume an entity instance of type PersonalVehicle with a property called Drivers. Each Driver is of the
type PolicyDriver.

Policy revisioning 207

Guidewire PolicyCenter 10.2.3 Application Guide

AllVersions
Gets all versions of this entity instance in this period.
Returns a list of entity instances of the entity type. Each entity instance has a unique effective date range that does not
overlap. For PersonalVehicle, this property returns List<PersonalVehicle>.
This property gets all versions of this entity instance across effective time in this policy period. Each entity instance
reference is set to edit in window mode.
This property can access properties on an entity instance where the properties are not array properties. You use this to
iterate across all versions and get the desired property from each one.
You can use this method in rating code to iterate across all effective time versions of an object that you need to send to
the rating engine.
Note: When getting this property on a version list for a PolicyPeriod (the graph root), this property contains
only one version since this root entity instance is not revisioned.

asOf(date)
Gets the version of this entity instance that is effective at the specified date, if such version exists.
Returns one entity instance as of the specified date, if such instance exists. The entity instance is in window mode. If
the entity instance does not exist on the specified date, returns null. This can occur if the entity instance has been
removed, canceled, or not yet added to the policy. For PersonalVehicle, this property returns a PersonalVehicle.
Use this method to access properties on an entity instance where the property is not an array. This is because you can
choose a date to pass to this method, and get the desired property from the result.

hasGaps
Check if an entity instance has effective-date gaps.
Returns boolean.
If true, the entity instance has at least some amount of non-effective time between two ranges of effective time in that
contractual period.

hasOverlaps
Check if an entity instance has overlapping duplicates across effective time.
Returns boolean.
If true, some code created invalid data. This is most likely due to incorrect manipulation of entities in window mode.
PolicyCenter has built-in validation routines that use this method to detect certain types of problems before binding the
branch. You can choose to use this method in your own validation code or other Gosu code.

getAllVersionsUntyped
Get all versions of this object, but typed to the root of all revisioned entities.
Returns a list of effective dated entities: List<EffDatedBean>. The type for each item is the root class of all revisioned
entities, which is EffDatedBean. Typically, you need to cast each item to the specific entity subtype.
This method is similar to the AllVersions property, but with a different return type declaration.

getVersionAsOf(date)
Gets the entity instance as of a date, but typed to the root of all revisioned entities, EffDatedBean.
Returns an entity instance typed as the root of all revisioned entities (EffDatedBean).
This method is the same as the asOf method, but with a slightly different return type.

208 Policy revisioning

 Guidewire PolicyCenter 10.2.3 Application Guide

Version list API methods that query an array of entities

The following are methods on the version list that query an array of entities. There is one of each of these members for
every property on a policy entity that contains arrays of other entities. This commonly represents navigating down a
hierarchy, but that is not always the case. For example, a policy object contains an array of policy lines, a vehicle object
contains an array of drivers. This applies only to directly database-backed properties, not to enhancement properties or
to any methods.
Examples assume an entity instance of type PersonalVehicle with a property called Drivers. Each Driver is of the
type PolicyDriver.

property

Use property where property is the name of the property in source entity instance returns a list of all version lists for
this property. The version lists are typed to the property type on the source entity with a suffix of VersionList. Each
version list in the result represents the source entity instance and all its versions for this period. The source entity
instance and its versions have the same fixed ID.
There is a method for each property on the source entity instance that contains an array. For PersonalVehicle, the
Drivers property returns List<VehicleDriverVersionList>.

propertyAsOf(date)

There is an AsOf(date) method for each property on the original entity instance that contains an array.
This method gets the contents of this property as of a particular date. Add the AsOf suffix to the name of the property in
the source entity instance. This is a method even though its first character is capitalized. Pass the date as an argument.
For PersonalVehicle.Drivers, the DriversAsOf method returns List<VehicleDriver>.
Returns a list, not an array, of the type contained in the array property. This could be an empty list if no child entity
instances in that array are effective at that date due to being removed or canceled. The return value can be an empty
array. This method does not return null nor throw an exception.

addToProperty(obj)
There is an addTo method for each property on the original entity instance that contains an array.
Add an entity instance to the version list that represents the property that is array of entity instances of that type.
This method returns void.
The method is addTo appended with the source property name. This method takes an entity instance of the type of the
original property (in this example, VehicleDriver). This change always happens in window mode to preserve the
effective and expiration dates on the entity instance. In contrast, when adding entities in slice mode, PolicyCenter
overrides the effective date with the slice date.

Version list API methods that are not type-safe

The following version list methods use type reflection (dynamic access) and are rare in typical code. In general, avoid
using these methods because reflection APIs prevent Gosu from checking the correctness of arguments at compile
time.

IMPORTANT: Use these methods only for algorithms that are impossible with type-safe APIs. This can occur if
you do not know property names at compile time.

These methods are similar to property in “Version list API methods that query an array of entities” on page 209.
However, these methods uses type system reflection to get the property. Pass the property as an argument.

getArray(propName)
Get all version lists for this property using reflection to specify the property name.

Policy revisioning 209

Guidewire PolicyCenter 10.2.3 Application Guide

Returns a list of version lists. Each version list in the result represents a unique entity instance (a shared fixed ID) and
all its versions for this period. The result type is List<EffDatedBean>, not a more specific subtype. At compile time,
Gosu does not know the type of the results. Your code must cast each list member to your desired subtype.
To get the version lists for all unique drivers of a vehicle, but specify the property name by using reflection (dynamic
access at run time):
var driversProp = PersonalVehicle.Type.TypeInfo.getProperty("Drivers") as gw.entity.IArrayPropertyInfo
var driversArray = vehicleVL.getArray(driversProp)

getArrayAsOf(propName, date)
Get a list of the objects in the array that are effective at the particular date using reflection to specify the property name.
Returns a list of the objects that are effective at the particular date. The result type at compile time is
List<EffDatedBean>, not a more specific subtype. At compile time, Gosu does not know the type of the results. Your
code must cast each list member to your desired subtype. For example, cast the version list to a more specific subclass
such as List<VehicleDriverVersionList> .
Returns an empty list if there no child objects in the array are effective at that date due to being removed or canceled.
If you pass an invalid date for this method, it returns an empty array. This method does not return null and does not
throw an exception for this condition.

Advanced version list examples

The following examples use a variety of PolicyCenter objects and includes some more advanced VersionList APIs.
For version list APIs that return lists or lists of version lists, you can use the powerful Gosu enhancements for
collections to make Gosu code as concise as possible. For example, you can use code such as

vehicle.VersionList.AllVersions.first()

Many collection enhancements have arguments that are Gosu blocks, which are in-line functions that make powerful
Gosu code easy to read.
For more information about collection enhancements, see the Gosu Reference Guide. For more information about
blocks, see the Gosu Reference Guide.

Get all costs from an auto policy line

For example, suppose you have a PersonalAutoLine. If you want to get all its personal auto costs (in its PACosts
property) in the contractual period, use the Gosu code:

myCostVersionLists = autoPolicyLine.VersionList.PACosts

This returns a list of version lists. Each of these version lists represent one cost and all its costs across effective time.
It is an extremely common mistake to use code that looks like

notAllCosts = autoPolicyLine.PACosts // generally NOT what you want to do

This code does not get all the costs. It gets only the costs associated only at the slice date (which typically is
meaningless). You usually want all the costs for the policy period, which represents the total price of the policy.

Extract all costs from an auto policy line and return them in a 1-dimensional array
To extract all cost entities across effective time, use the flatMap collection enhancement method. As an argument it
takes a Gosu block. In this case, the block takes a cost version list as an argument. Then the code gets all versions of
this cost. Then finally the flatMap enhancement method combines them into a single list.

var allCosts = autoPolicyLine.VersionList.PACosts.flatMap( \ costVL -> costVL.AllVersions )

The result is a list that contains all auto costs as one flattened list.

210 Policy revisioning

 Guidewire PolicyCenter 10.2.3 Application Guide

Some cost objects have the same fixed IDs as other costs (they are the same cost) but vary in effective dates.

Original drivers of a vehicle

Get the drivers of the vehicle as of the earliest effective date on the policy for this vehicle:

var firstVersionUnsliced = vehicleVL.AllVersions.First()

var origDrivers = firstVersion.getSlice(firstVersion.EffectiveDate).Drivers

The list that vehicle.AllVersions returns is ordered by effective date. Getting the first item from the list (as this
example does) gets the item with the earliest effective date.

Get all coverages on a vehicle and print data from each version, segregated by each unique coverage
Display all the coverages that any time were on the vehicle along with display name and the date range covered by that
version:

for (covVL in vehicleVL.Coverages) {

for (cov in covVL.AllVersions) {
print("${cov.Pattern.DisplayName}: effdate ${cov.EffectiveDate}, expdate ${cov.ExpirationDate}")
}
}

Get a vehicle’s garage location at a specific date

Suppose you want to get a vehicle’s garage location. Since the location might have changed, you often just want to
show one location, usually the last one or perhaps the one as of a particular date. This example assumes you have a
vehicle version list in a variable called vehicleVL.

// find out which version of this object was effective on that date
var vehicleUnsliced = vehicleVL.AsOf(asOfDate)
if (vehicleUnsliced == null) throw "No vehicle effective on that date"

// get the version of the garage at that date

// Get the Garage in slice mode, just before the end of its active time
Var vehicleSliced = vehicleVersion.getSlice(vehicleUnsliced.ExpirationDate – 1 sec)
var g = vehicleSliced.garageLocation

// print the location (in real world code, display in PCF files instead)
print("garage ${g.AddressLine1} / ${g.AddressLine2} / ${g.City} / ${g.State} ")

See “Safely accessing foreign keys with slice mode” on page 206 for related discussion.

Get all available drivers for a vehicle at a specific date

This example assumes you have a vehicle version list in a variable called vehicleVL.

var vv = vehicleVL.AsOf(asOfDate).AvailableDrivers

Although PersonalVehicle.AvailableDrivers returns an array of driver objects, it is an enhancement property not a

database-backed property. The version list properties that Gosu creates for array properties (such as
vehicle.DriversAsOf(date)) only exist for database-backed properties. Thus, it might seem like the following Gosu
code works, but it results in a compile error:

var v2 = vehicleVL.AvailableDriversAsOf(asOfDate) // compile error!

Working with window mode (unsliced) objects

If you have reference to any revisioned subobject of PolicyPeriod, simply get its Unsliced property to get a
reference to that entity instance in unsliced mode. Remember to save the return result. The original reference is
unchanged.
Note: The PolicyPeriod entity instance is not a revisioned entity instance. It is the root of the graph of
revisioned objects and it does not have an Unsliced property.

Policy revisioning 211

Guidewire PolicyCenter 10.2.3 Application Guide

Version lists always return entities in window mode (‘unsliced’ mode)

If you get a version of an entity instance from a version list, Gosu always returns that entity instance as a window mode
entity instance. In other words, you have the entity reference but no implicit slice date. This means that the entity
instance represents the car over a range of dates.
With an unsliced entity instance, you can access simple properties on the object but you cannot access links to other
entities (foreign keys and arrays of entity instances).

Window mode entities from database queries

The typical way to get window mode versions of entities is to use version lists. However, there are other ways to get a
window-mode reference to an entity instance if you have a slice mode reference to an entity instance.
The most common other way to reference an entity instance in window mode is an entity instance that you retrieve
through a database query. See the Integration Guide for related information.
Database query results do not have any inherent context from which to determine a slice date. Thus, by default any
objects from a database query return in window mode (and in a read-only bundle). It is usually correct to then convert
the item into slice mode as of a certain date with the version list getSlice method:

var sliceModeVehicle = myVehicle.getSlice(sliceDate)

However, it depends on the context. In some cases, you might want to work with the object in window mode.

Naming conventions
When reading code, you may get confused as to whether you are working with sliced or unsliced objects. One
approach to improving code readability (and reducing coding errors) is to consistently name variables. For variables
that contain unsliced objects, include the suffix Unsliced. For example, policyLineUnsliced.
The convention is that variables that do not have the Unsliced suffix contain a sliced version (the more common case).
For example:

var firstVersionUnsliced = vehicleVL.AllVersions.First()

var drivers = firstVersion.getSlice(firstVersion.EffectiveDate).Drivers

Comparing window mode edits to slice edits

If you directly edit an entity instance in window mode, the changes affect the full effective period only of that one
entity instance.
In contrast, a slice mode edit using the default split-on-edit approach, in which changes affect the entity instance from
the edit date forward. Unlike slice editing, window mode changes do not merge changes forward when the object is
edited in window mode. For example, when an out-of-sequence policy change is merged forward, the window mode
edits do not merge forward in effective time. For more information about out-of-sequence changes, see “Out-of-
sequence jobs” on page 213.
For example, Workers’ Compensation line of business includes Workers’ Compensation payroll amounts that do not
change across effective time. A change to these amounts applies to the entire contractual period. People need to
provide the amount of payroll that they had for a class of workers within a couple of separate date ranges. They need to
edit these numbers directly, not partway through the period. They need to see all date ranges at once, not just the ones
effective as of a given date. It would make no sense to merge a change made to the first date range forward to a later
one. You must edit each one separately.
Also note that editing in window mode disables automatic scaling and splitting behaviors that would normally happen
in slice mode.
Other objects that PolicyCenter edits in window mode include RatingPeriodStartDates and WCCoveredEmployees.

212 Policy revisioning

 Guidewire PolicyCenter 10.2.3 Application Guide

Out-of-sequence jobs
Many policy jobs have effective dates later than the effective date of any existing bound revisions for that contractual
period. The change implicitly applies from the job’s effective date until the end of the contractual policy period. For
example, increasing coverage on an effective date applies for the rest of the contractual period, or canceling a policy is
effective for the rest of the policy period.
However, if a change is bound to take effect before a previous change (that is, earlier in effective time), there are
additional implications for completing this change. Depending on what changes already happened to the policy,
sometimes PolicyCenter requests that you review how to apply changes for the rest of the contractual policy period.
For example, suppose the following standard order of changes:
1. On January 1, the customer adds new auto policy effective all year for a red car, covered for $10,000. The
effective date of this change is January 1.
2. On March 1, customer increases a specific coverage on the car to $20,000, effective from that day to year end.
The effective date of this change is February 1.
3. On March 2, the customer calls to say that the original car was painted blue on February 1. The effective date of
this change is March 1. This effective date is later than the effective date of the previous change.
This is a regular change because effective dates of the changes are later than effective dates of previous changes.
However, if you reverse the last two effective dates, the order or changes would be:
1. On January 1, the customer adds new auto policy effective all year for a red car, covered for $10,000. The
effective date of the change is January 1.
2. On March 1, the customer increases a specific coverage on the car to $20,000, effective from that day to year end.
The effective date of the change is March 1.
3. On March 2, the customer calls to say that the original car was painted blue on February 1. The effective date of
the change is February 1. This effective date is earlier than the effective date of the previous change.
The last change in that example is an out-of-sequence change because February 1 is earlier than March 1. For effective
time after February 1, there are two date ranges:
• From February 1 to February 28 in effective time, the PolicyPeriod must represent the newly painted blue car
with the original coverage.
• From March 1 to year end in effective time, the PolicyPeriod must represent the updated increased coverage.
However, PolicyCenter considered this a red car for this time range before the latest change. Was the car blue for
the rest of the year or did it change only from February 1 to March 1?
Any change with effective date ordering like this is called an out-of-sequence job. Any PolicyCenter job, such as
cancellation and reinstatement, not just policy change jobs can be out of sequence. A job is out of sequence if its
effective date is earlier than other jobs bound on the policy for that contractual period.
PolicyCenter automatically detects out of sequence jobs. Some changes may not need user intervention. In other cases,
you must review out-of-sequence conflicts in the Policy Review > Out-of-Sequence Conflicts tab before binding the job.

Out-of-sequence job user interface

When PolicyCenter detects a job as out of sequence, PolicyCenter warns you when you start the job.
If you continue with the out-of-sequence transaction, there might be changes you need to review to determine whether
to merge that change forward for the rest of the contractual period.
If there are out-of-sequence conflicts, the Policy Review page for the job contains an Out-of Sequence tab. PolicyCenter
alerts you to out-of-sequence conflicts when you try to bind the job.

Policy revisioning 213

Guidewire PolicyCenter 10.2.3 Application Guide

Create an out-of-sequence policy transaction

About this task

This task uses the Ray Newton personal auto policy from the small sample data set. The policy is in force, and the
policy number is 3316157326.

Procedure
1. Open any personal auto policy that is currently active. Note the dates of the period. If necessary, create a new
policy that is effective right now and extends a few months in the future.
2. Select Actions > Change Policy.
3. In the Start Policy Change screen, enter an effective date in the middle of the period (2 months from the start
date), and a short description. Click Next.
4. In the left sidebar, click PA Coverages.
5. In Uninsured Motorist - Bodily Injury, change Uninsured Motorist - BI Limits to 250/500. Click Quote.
6. Click Issue Policy.
7. On the Policy Change Bound screen, click View your policy.
Create the out-of-sequence policy change
8. Navigate to the policy and select Actions > Change Policy.
9. Enter an Effective Date that is in the period but before the effective date of the last change you made (1 month
from the start date). Enter out-of-sequence in the Description. Click Next.
A dialog appears warning you of the out-of-sequence transaction. click OK to continue.
10. In the left sidebar, click PA Coverages.
11. In Liability - Bodily Injury and Property Damage, change the value of Auto Liability Package to 15/30/5. This is the
out-of-sequence change.
12. Click Quote.
PolicyCenter warns you that there are out-of-sequence conflicts that must be resolved prior to quoting.
13. As suggested, go to the Policy Review screen, and select the Change Conflicts tab.
This screen displays all conflicts and lets you decide whether to override the future conflict.
14. Choose your override method.
• Override all conflicts or none by using the Override All or Override None buttons.
• Override (merge) individual conflicts with your recent change by selecting Yes in the Override Future
Conflicts column. Overriding later-effective-date jobs has the effect of merging forward your change for the
rest of the contractual policy period.
15. Click Submit to finish overriding.
16. Quote and bind the policy as usual.

Back-dated versus out-of-sequence job

Not all out of sequence changes are back-dated, and not all back-dated changes are out-of-sequence. These are really
two separate issues, which in some cases may both be true, but neither one necessitates the other.
Compare these two definitions:
• A job is back-dated if the change has an effective date earlier than today.
• A job is out-of-sequence if the change’s effective date is earlier than the effective date of another job in that
contractual period.

214 Policy revisioning

 Guidewire PolicyCenter 10.2.3 Application Guide

Validation issues and out-of-sequence jobs

If there are validation issues with a job, PolicyCenter requires you to handle validation issues before it displays the out-
of-sequence user interface. In most cases, fixing the validation issues at the effective date of this job is sufficient to
prevent validation issues when applying (merging forward) changes in the Out-of-Sequence Conflicts tab.
In very rare cases, even after handling out-of-sequence conflicts there can be validation errors in the same contractual
period with later effective dates. For example, suppose you changed driver usage time percentages and caused out-of-
sequence conflicts and applied some driver usage values forward but not others. This would mean you could
temporarily cause the driver percentages to be less than 100% or greater than 100%. If validation errors at future
effective dates occur due to handling out-of-sequence conflicts, PolicyCenter displays a special user interface to handle
this case.
PolicyCenter alerts you to the validation errors and displays a picker in the left navigation bar so you can select future
effective dates at which there are validation errors. After selecting a future effective date that contains the validation
error, you can update the values that cause the validation errors.

Preempted jobs
Although some PolicyCenter jobs start and finish quickly, other job take a long time to complete the entire lifecycle.
Sometimes this delay is due to technical reasons such as contacting external systems. There may also be legal reasons
such as legally-enforced delays during cancellation.
When jobs take a long time to complete, chances increase that multiple jobs started on the same branch and are in
process at the same time. For instance, two jobs are based on exactly the same PolicyPeriod entity instance and its
subobjects. When the first job finishes there is no problem. When later jobs started at the same time complete, there
may be challenges binding the new changes. The job that finishes second does not have the changes recently made and
bound by the job that finished first.
When two jobs run concurrently like this, this situation is called preemption when the second job to finish attempts to
bind. When PolicyCenter tries to bind a preempted branch, initially the branch does not contain preempted changes.
PolicyCenter must incorporate the changes from the preempting branch. Preemption applies to any PolicyCenter job,
such as cancellation and reinstatement, not just policy change jobs. After the first job to finish is bound, any unfinished
jobs are preempted. PolicyCenter attempts to fix these problems early, as soon as you view a preempted job rather than
just waiting until the preempted job tries to bind.
For example, suppose on a personal auto policy, two users start policy change jobs at the same time:
• One policy change adds an additional vehicle, effective March 1, keeping coverage amounts the same
• One policy change increases the coverage amount on the original car, effective April 1. Remember that this policy
was based on the original legally-enforced policy when the policy change started. PolicyCenter represents this
policy change as a branch (a PolicyPeriod entity instance and its subobjects) that is a clone of the original branch
before any of the recent changes.
PolicyCenter detects potential preemption when starting a job if it appears that another job is in progress. The second
concurrent job displays a warning to the user.
This warning does not indicate that a preemption will necessarily occur, or that it already occurred. However, if both
branches eventually bind, one of the two jobs will be preempted.
Despite this warning, PolicyCenter lets the user start the policy change job or another job anyway. The complexity of
preemption really takes place when the jobs finish or you try to handle the preempted job. The first change to finish
preempts (takes precedence over) any concurrent changes not yet finalized.
Note: The complexity of preemption occurs after the first branch is bound and the user tries to work with the
preempted non-bound job. This can happen in any phase of the preempted job, not just in the bind phase. The
finish time determines which branch needs special handling, not the start time of the two jobs.
For example, if the policy change that adds the additional vehicle finalizes first, PolicyCenter makes that branch the
legally enforced branch for this period. Nothing very unusual happens from a database or user interface perspective as
part of binding this job.

Policy revisioning 215

Guidewire PolicyCenter 10.2.3 Application Guide

However, after the user binds this change, if there are open jobs on this policy, PolicyCenter displays a warning this job
preempted another transaction. It offers a link to view that policy transaction immediately.
At this point in the application, it is possible that the user might withdraw or ignore other non-bound branches.
However, if any user attempts to bind the second change (the coverage increase change), that change was preempted.
That change was originally based on a branch that is no longer the most recently bound branch. PolicyCenter displays
special options to handle the preemption.
Let us first consider the case in which the job that you bound first in real-world time had an earlier effective date than
the second-to-bind change. This is a standard preemption. Before binding the coverage increase change, PolicyCenter
must add the additional vehicle to the draft branch containing the coverage increase before attempting to bind the
increased coverage.
Note: PolicyCenter must merge changes like this during preemption. Otherwise, when you bind the coverage
change, the additional vehicle would be missing. It would appear as if you removed the vehicle from the policy
as of April 1 as part of the recent change even though that was not your intention.
If you later view the preempted job, PolicyCenter warns you with a message at the top of the window. Also, the Handle
Preemption button appears if you have preemptions to handle on this job.

You must choose to do one of the following:

• Click Handle Preemption to merge changes as appropriate from recently-bound jobs into the active job that is about
to be bound.
• Click Withdraw to withdraw (abort) the current job.
If you click Handle Preemption to handle the preemption, PolicyCenter displays a tree showing the preemptions.
You can use the tree navigation (clicking on - and + signs) to hide or show parts of items in the hierarchy.
Use the buttons the screen to choose among the following actions:
• Click the Apply All Changes button to apply all changes.
• Click the Withdraw button to withdraw the job.
• Click the Decide Later button to save the draft and return to the policy review screen.

Effective date later

If you apply changes and the effective date of your draft branch is later than effective dates of other bound jobs for that
period, PolicyCenter simply applies the changes. This is a standard preemption.

Effective date earlier

However, if the effective date of your draft branch is earlier than effective dates of any bound jobs for that period, this
preempted job is also out of sequence. Because it is out of sequence, there might be out-of-sequence merge conflicts. If
there are merge conflicts, they appear in the Change Conflicts tab. You can review each conflict and determine whether
to merge each change forward. For more information about the meaning of out-of-sequence in PolicyCenter, see “Out-
of-sequence jobs” on page 213.

IMPORTANT: A job can be both preempted and out-of-sequence, depending on the effective date of the current
branch compared to the effective date of other bound branches. If you apply changes to handle the preemption,
there might be merge conflicts. If this happens, PolicyCenter displays the same change conflicts user interface
(the Change Conflicts tab) as a standard out-of-sequence job.

How PolicyCenter actually handles preemptions

In the PolicyCenter interface for preemption handling, it appears as if PolicyCenter simply merges changes into the
latest selected (draft) branch. However, from a database perspective, PolicyCenter actually creates a new branch to
handle the preemption.
The changes happen in the following order:

216 Policy revisioning

 Guidewire PolicyCenter 10.2.3 Application Guide

1. PolicyCenter creates a new branch that is a copy of the most recently bound PolicyPeriod in that contractual
period. By definition, this includes all changes from any preempting branch (or branches for multiple
preemptions). This is the safest way to preserve consistency with a legally enforced branch.
2. PolicyCenter then merges the changes you attempted to make in the preempted branch to this new branch.

IMPORTANT: In rare cases, PolicyCenter cannot automatically reapply the changes. This can happen if
you make a change to a vehicle that has been removed in a preempting branch. Because of the preempting
branch, there is no longer a vehicle in the newly merged branch. If such rare cases occur, after
PolicyCenter reapplies changes, PolicyCenter opens a worksheet to notify you about change conflicts.
This is just a notification. It requires no action.

3. PolicyCenter discards the branch that the user was actively working on (the preempted branch) after handling the
preemption. PolicyCenter replaces it with the new merged branch in the user interface and in the database.
4. You can customize application logic that occurs after handling a preemption but before discarding the draft
branch and binding the new PolicyPeriod. For more on this topic, see the Integration Guide.

Create a preempted job

About this task

Procedure
1. Open a policy that is currently active. Notice the dates of the policy period. If necessary, create a new policy that
is effective right now and extends a few months in the future.
This example uses a personal auto policy.
2. Select Actions > Change Policy.
3. Enter an effective date in the middle of the policy period and a short description.
For example, select an Effective Date two months from the original effective date. Enter Change 1 in the
Description.
4. Make a change to a coverage.
For example, select PA Coverages and change Uninsured Motorist - Bodily Injury > Uninsured Motorist - BI limits
to 250/500.
5. Click Quote to quote the policy change.
6. In the Info Bar, click the policy number to go to the Policy Summary screen.
The policy change is not completed. It has been quoted but not bound.
7. Select Actions > Change Policy.
PolicyCenter displays a warning that there is another open policy change and that you might want to wait.
8. Enter an effective date later than the first policy change but still in the policy period. Add a short description.
This will be the preempted policy change.
For example, select an Effective Date three months from the original effective date. Enter Change 2 in the
Description.

Note:

If you select a date is between the original effective date and the start of the first policy change, the
preemption will also be out-of-sequence.
9. Click Next.
10. In the Info Bar, click the policy number to go to the Policy Summary screen.

Policy revisioning 217

Guidewire PolicyCenter 10.2.3 Application Guide

11. In Pending Policy Transactions, click to open the first policy change, with Status of Quoted.
12. Click the Transaction # to open the quoted policy change.
13. Click Issue Policy.
The Policy Change Bound screen displays a link Your policy change preempted Policy Change.... This preempted
policy change is the second policy change.
14. Click the Your policy change preempted Policy Change... link to jump to the second policy change.
15. The screen displays a message that this policy change was preempted and that you need to handle preemptions
before continuing.
16. Click Handle Preemption or Withdraw Transaction.
If you choose Handle Preemption, you have three choices:
• Apply All Changes from the first policy change to the current (second) policy change.
• Withdraw the current (second) policy change.
• Decide Later how to handle the preemptions. You cannot quote the policy change until you handle
preemptions.

Applying changes to future renewals

If a user changes a policy in the current period but a future renewal revision already exists, PolicyCenter displays a
special screen. That screen asks the user whether to apply (merge) changes forward to the renewal period.
If you do not apply the changes from the current job to the renewal period, you can apply changes later when you
revisit the policy change job. PolicyCenter asks again whether to apply these changes to the renewal period.
If the user says yes, PolicyCenter reapplies the changes to the future renewal branch. However, the behavior is slightly
different depending on whether the future renewal contractual period is bound or unbound:
• If the future renewal period is bound, a new job is started in the renewal period to apply the changes. The new job
in the renewal period always is a policy change job based on the most recently bound branch in the renewal period.
The changes only include the ones you made in the prior period. If multiple jobs in the prior period are bound and
the user requests to apply these changes to the renewal period, multiple jobs are created in the renewal branch. The
new jobs are independent of each other (some might be bound, some might be withdrawn, as desired).
• If the future renewal period is unbound, changes are made directly to the draft renewal branch. No new job is
created to handle this case. If multiple jobs in the current (pre-renewal) period are bound and you request to apply
changes to the renewal period, all changes are applied to that same draft renewal branch.

IMPORTANT: In rare cases, PolicyCenter cannot automatically reapply the changes. For example, if you make a
change to a vehicle removed in a preempting branch. There is no longer a vehicle PolicyCenter can modify in
the new merged branch. If such rare cases occur, after PolicyCenter reapplies changes, PolicyCenter opens a
worksheet to notify you about change conflicts. This is just a notification requires no action.

Revisioning rewrite jobs

A rewrite job starts from a copy of the canceled policy. In most cases, the rewrite gets a copy of the policy at the
cancellation date. When there is a lapse in coverage, the copy comes from the canceled portion.
There are several special different conditions to keep in mind:
• If a rewrite starts after the cancellation date, it gets a duplicate of the canceled policy as of the start date of the
rewrite. In this case, the copy of the policy as of the cancellation date can have multiple slices, such as if the rewrite
is out of sequence to other policy changes.

218 Policy revisioning

 Guidewire PolicyCenter 10.2.3 Application Guide

• If the start date is after the original end date, PolicyCenter duplicates the rewritten policy from the last day of the
canceled policy. In this case, there is a single slice. Everything on the rewrite job has the same effective and
expiration dates. This is, however, a rare case.
If the start date of a PolicyPeriod moves forward to a later date, PolicyCenter moves the effective date of all objects
on the policy graphs forward to that date. All information about the original start date of the PolicyPeriod and its
subobjects start date no longer appears as data in the PolicyPeriod graph. This is the intended and defined behavior.
However, in some edge cases the result can be difficult to understand and can look strange or incorrect, so keep in mind
how it works.
For example, suppose the following sequence occurs:
• You create personal auto policy, one vehicle, one driver, 9/1/09 through 3/1/10.
• You change the policy, effective 12/1/09, adding a second vehicle.
• You start a midterm rewrite, with the effective date initially set to the cancellation date (the default), 11/5/09.
• You bind this policy as is then in the policy term that resulted. Vehicle 1 has an effective date of 11/5, and vehicle 2
has an effective date of 12/1 (correctly). However, you might expect a one month lapse in coverage, so you change
the effective date of the rewrite to 12/5/09, and save the draft.
• If you bind the policy at this point, on the policy term that results, both vehicle 1 and vehicle 2 have an effective
date of 12/5 (correctly).
• However, you decide there was not supposed to be a lapse in coverage, so you change the effective date of the
rewrite back to 11/5. This is unusual but possible. That branch in PolicyCenter no longer has the information about