Define the product in Guidewire PolicyCenter by creating or extending a Product Definition including line of business, policy type, and jurisdiction availability
Model coverages, coverage terms, and coverage groups using the PolicyCenter product model configuration (Gosu or configuration XML depending on version)
Configure underwriting rules and validation rules that fire at each policy transaction step (quote, bind, issue)
Set up rating integration by connecting the product to a rating worksheet or external rating engine call within the PolicyCenter rating framework
Configure the policy lifecycle workflows (submission, policy issuance, endorsement, renewal, cancellation) for the new product
Test the product configuration end-to-end in a lower environment by submitting a test quote through to policy issuance and verifying generated documents
Known gotchas
PolicyCenter product model changes typically require a code deployment — configuration is not purely data-driven in all versions; confirm whether your version supports hot-deployed configuration changes
Jurisdiction-specific coverage availability and mandatory coverage rules must be configured per state; missing jurisdiction rules can allow non-compliant quotes to bind
Rating worksheet logic and external rating engine integrations must be kept in sync with the product model; a mismatch between coverage terms defined in the product model and those expected by the rater causes runtime errors
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp