6/13/25, 5:02 AM Guidewire Policycenter Professional Exam | Policy Administration, Data Model Management, Product Model Setup, User Interface …
Guidewire Policy center Professional Exam | Policy
Administration, Data Model Management, Product
Model Setup, User Interface Customization | Latest
Version 2025-2026
1. Producer of Record - Created the submission,
receives commision based on the premium
Types of Producers (2) 2. Producer of service - services the policy (usually
the same as the producer of record if a new policy -
if different, they only get commission after the policy
is renewed)
A unique ID assigned by the insurer to track which
What is a producer code
agent/agency is responsible for which policies and
accounts
Use the "User admin role"
How to delegate role
management to external The can have access to ao build groups, org and
users permissions for their own orgs but not others
1. Role based security - a role is a named collection of
permissions that typically map to a jo function or title
Security in PC (2)
2. Date based security - defines what data can be
access and typically managed through producer
codes
1. fully restricted - only access to their own org
3 levels of assignment for 2. protect internal - can be assigned producer codes from any
external users external org
3. allow internal - allow access to internal or external orgs
… 1/17
,6/13/25, 5:02 AM Guidewire Policycenter Professional Exam | Policy Administration, Data Model Management, Product Model Setup, User Interface …
1. declaration sheets - a summary of all exposures and coverages
2. Base forms - attached regardless of what
coverages or exposure units are selected
3. Additional coverage forms - add additional coverage
4. Exclusion forms - limit forms
5. Manuscript forms - blank forms with space for free text
Samples of forms (5) (4)
High level:
1. Policy forms form PC
2. Invoices from BC
3. Delinquency Letters from BC
4. Notification letters of new claims from CC
Form Inference - PC generates forms based on policy
details (this logic is defined by Form Patterns)
Form Pattern - defines metadata about a form and the
How are forms created? inference logic (the define valid forms the system can
infer on a policy)
The actual Form content is created by a Document
Production System (DPS) The created form
content is stored in a Document Management
System
1. Forms contain legal info, documents contain relevant account,
Forms vs Documents
policy, or job info
2. Forms are part of the policy contract, documents are not
Indicates the order that a form was added to the policy
Endorsement numbers
(apply to a specific policy period (sequential starting
at 1)
UW Issue - a specific occurance on a policy transaction
where an UW condition was true. Created when a
condition gives undesirable results based on data on the
policy or account. These can stop jobs until approved
Components of UW
authority UW Rule - Describes how the policy transaction is
affected by the UW issues and how issues can be
approved. Rules include conditions which will raise an
UW issue Authority Grant - The ability to approve UW
… 2/17
, 6/13/25, 5:02 AM Guidewire Policycenter Professional Exam | Policy Administration, Data Model Management, Product Model Setup, User Interface …
issues and to what degree
Authority profile - a group of authorities that can be
given to a user, allowing the user to approve UW
issues
1. Rule conditions can be created in the UW Rule UI,
more complex conditions can be written in gosu
How can UW issues be
created? (2) 2. UW issues can also be created manually on the UW
Issues screen (can not be removed automatically
Checking set A point in the job where issues can be raised (Pre-quote, Bind,
Pre-issuance)
Stops the progress of a job until an issue is approved
Blocking point
(some issues can be informational (non-blocking)
1. Fields related to defining the UW Rule (Name, Code,
Description, Checking Set, Blocking Point, Enabled,
Start/End Date)
Types of fields in the UW 2. Fields related to evaluating the UW Issue (applicability
Rules Screen (3) section, Rule Contect, Rule Condition, UW Details)
3. Fields related to approving the UW Issue (Auto-
Approvable, Default Edit before Bind, Default Approval
Blocking Point, Default Duration, Value Comparator,
Value Formatter Type, Default Value Assignment
Type, Default Value Offset Amount)
Dev:
1. Draft (rules have been created but not complete or tested)
2. Staged (tested and ready for deployment)
Deploying UW Rules (Dev vs
Prod server) Prod:
1. Approved (Rule is ready for Deployment)
2. Deployed (Rule executes)
1. Product Type
2. Product Name
3. LOB
Requirements to designing a
4. Product Account Types
product (required fields) 5. Available Jurisdictions
(7) 6. Policy Terms
7. Default Policy Term
… 3/17
Guidewire Policy center Professional Exam | Policy
Administration, Data Model Management, Product
Model Setup, User Interface Customization | Latest
Version 2025-2026
1. Producer of Record - Created the submission,
receives commision based on the premium
Types of Producers (2) 2. Producer of service - services the policy (usually
the same as the producer of record if a new policy -
if different, they only get commission after the policy
is renewed)
A unique ID assigned by the insurer to track which
What is a producer code
agent/agency is responsible for which policies and
accounts
Use the "User admin role"
How to delegate role
management to external The can have access to ao build groups, org and
users permissions for their own orgs but not others
1. Role based security - a role is a named collection of
permissions that typically map to a jo function or title
Security in PC (2)
2. Date based security - defines what data can be
access and typically managed through producer
codes
1. fully restricted - only access to their own org
3 levels of assignment for 2. protect internal - can be assigned producer codes from any
external users external org
3. allow internal - allow access to internal or external orgs
… 1/17
,6/13/25, 5:02 AM Guidewire Policycenter Professional Exam | Policy Administration, Data Model Management, Product Model Setup, User Interface …
1. declaration sheets - a summary of all exposures and coverages
2. Base forms - attached regardless of what
coverages or exposure units are selected
3. Additional coverage forms - add additional coverage
4. Exclusion forms - limit forms
5. Manuscript forms - blank forms with space for free text
Samples of forms (5) (4)
High level:
1. Policy forms form PC
2. Invoices from BC
3. Delinquency Letters from BC
4. Notification letters of new claims from CC
Form Inference - PC generates forms based on policy
details (this logic is defined by Form Patterns)
Form Pattern - defines metadata about a form and the
How are forms created? inference logic (the define valid forms the system can
infer on a policy)
The actual Form content is created by a Document
Production System (DPS) The created form
content is stored in a Document Management
System
1. Forms contain legal info, documents contain relevant account,
Forms vs Documents
policy, or job info
2. Forms are part of the policy contract, documents are not
Indicates the order that a form was added to the policy
Endorsement numbers
(apply to a specific policy period (sequential starting
at 1)
UW Issue - a specific occurance on a policy transaction
where an UW condition was true. Created when a
condition gives undesirable results based on data on the
policy or account. These can stop jobs until approved
Components of UW
authority UW Rule - Describes how the policy transaction is
affected by the UW issues and how issues can be
approved. Rules include conditions which will raise an
UW issue Authority Grant - The ability to approve UW
… 2/17
, 6/13/25, 5:02 AM Guidewire Policycenter Professional Exam | Policy Administration, Data Model Management, Product Model Setup, User Interface …
issues and to what degree
Authority profile - a group of authorities that can be
given to a user, allowing the user to approve UW
issues
1. Rule conditions can be created in the UW Rule UI,
more complex conditions can be written in gosu
How can UW issues be
created? (2) 2. UW issues can also be created manually on the UW
Issues screen (can not be removed automatically
Checking set A point in the job where issues can be raised (Pre-quote, Bind,
Pre-issuance)
Stops the progress of a job until an issue is approved
Blocking point
(some issues can be informational (non-blocking)
1. Fields related to defining the UW Rule (Name, Code,
Description, Checking Set, Blocking Point, Enabled,
Start/End Date)
Types of fields in the UW 2. Fields related to evaluating the UW Issue (applicability
Rules Screen (3) section, Rule Contect, Rule Condition, UW Details)
3. Fields related to approving the UW Issue (Auto-
Approvable, Default Edit before Bind, Default Approval
Blocking Point, Default Duration, Value Comparator,
Value Formatter Type, Default Value Assignment
Type, Default Value Offset Amount)
Dev:
1. Draft (rules have been created but not complete or tested)
2. Staged (tested and ready for deployment)
Deploying UW Rules (Dev vs
Prod server) Prod:
1. Approved (Rule is ready for Deployment)
2. Deployed (Rule executes)
1. Product Type
2. Product Name
3. LOB
Requirements to designing a
4. Product Account Types
product (required fields) 5. Available Jurisdictions
(7) 6. Policy Terms
7. Default Policy Term
… 3/17
