Core concepts (Q1-Q8)
1. What does PolicyCenter do, in one sentence?
PolicyCenter is the InsuranceSuite policy administration system: it manages the full policy lifecycle, quoting, binding, issuing, changing, renewing, cancelling, for every line of business the insurer sells.
2. What is an Account vs a Policy vs a PolicyPeriod?
An Account represents the customer and can hold many policies. A Policy is the ongoing contract across terms. A PolicyPeriod is one effective-dated term (or a branch of it being edited by a job), the root entity of the policy graph holding lines, coverages, and costs. Interviewers frequently ask this hierarchy first; get it crisp.
3. What is effective dating and why does PolicyCenter need it?
Policy data varies within a term: a mid-term change makes a vehicle's coverage differ before and after the change date. PolicyCenter models this with effective-dated entities that carry effective/expiration dates inside the period, so any date's view of the policy can be reconstructed exactly, essential for premium calculation, claims coverage verification (ClaimCenter asks "what was in force on the loss date?"), and audits.
4. What is a policy line?
A line of business within a policy, e.g., Personal Auto, Homeowners, Commercial Property. Each line has its own coverages, exposures (vehicles, dwellings, locations), and rating logic. A PolicyPeriod contains one or more lines.
5. What is the difference between a coverage and a coverage term?
A coverage is a promise of protection (e.g., Collision). A coverage term is a parameter of that promise (e.g., a ₹50,000 deductible, a limit). The product model defines which terms each coverage carries and their allowed values.
6. What is a quote in PolicyCenter terms?
Quoting runs validation at quote level, executes rating to produce cost entities, and moves the job branch to Quoted status with a priced premium. A quote is always attached to a specific branch, re-editing invalidates it back to Draft.
7. What entities store premium?
Rating produces Cost entities (per coverage/line, effective-dated); binding transforms costs into Transaction entities representing the premium amounts booked for the term. Costs answer "what would it cost"; transactions answer "what was charged."
8. How does PolicyCenter integrate with the rest of the suite?
Outbound to BillingCenter (bound premiums create billing items), to ClaimCenter (policy search/verification on the loss date via policy retrieval integration), plus ratings, documents, and reinsurance systems. Knowing the direction of each integration matters: ClaimCenter pulls policy data; PolicyCenter pushes billing instructions.
Job model & lifecycle (Q9-Q15)
9. List the job types in PolicyCenter.
Submission (new business), Policy Change, Renewal, Cancellation, Reinstatement, Rewrite, Issuance, and Audit (premium audit for workers' comp/commercial). Each job type has its own lifecycle and wizard flow.
10. Walk through the submission lifecycle.
Create submission on an account → capture policy data through the line wizard (Draft) → quote (validation + rating → Quoted) → resolve underwriting issues / obtain approvals → bind (Bound) → issue documents and commit the term. Bonus points for mentioning that bind and issuance can be separate steps and that the bound branch becomes the in-force PolicyPeriod.
11. What is a branch in PolicyCenter?
Each job edits its own copy, branch, of the PolicyPeriod, isolated from the bound version and from other jobs' branches. Multi-version quoting creates several branches within one job (e.g., quote with different deductibles) so the insured can compare options.
12. What is preemption and how is it resolved?
When two jobs are open on the same term and one binds, the other is preempted, its branch is now based on stale data. The preempted job must merge the newly bound changes into its branch (automatic where possible, manual review otherwise) before it can quote/bind. This is the most reliably asked mid-level PolicyCenter question.
13. What is out-of-sequence transaction handling?
A change effective earlier than an already-bound later change (e.g., add a driver from March when an April change is already bound). PolicyCenter must re-apply the later change on top of the new earlier one, out-of-sequence conflict handling decides what merges automatically vs needs review.
14. How do renewals get started automatically?
The renewal batch process finds terms approaching expiration and starts Renewal jobs per configured lead time; renewal flows then run through automated rules (rate, issue if clean) or route to underwriters based on renewal direction rules (non-renew indicators, risk changes).
15. Cancellation: what are the key concepts?
Cancellation source (insured-requested, carrier-initiated, non-payment from BillingCenter), effective date rules (flat/pro-rata/short-rate refund calculation methods), notice periods per jurisdiction, and reinstatement afterwards. Non-payment cancellation arriving from BillingCenter as an integration is a favorite cross-suite follow-up.
Product model & rating (Q16-Q21)
16. What is the product model?
The metadata layer defining what the insurer sells: products → policy lines → coverages → coverage terms → options/packages, plus availability rules (by jurisdiction, date, or answer to qualification questions). It's maintained in cloud releases with Advanced Product Designer (APD).
17. What is APD and why does it matter in 2026?
Advanced Product Designer lets product owners define/modify insurance products visually (mind-map style), generating the product model and even line configuration. It shifts product build from pure code toward metadata, interviewers use it to check whether your knowledge is cloud-current. See our GWCP overview.
18. How does availability logic work?
Availability scripts/rules determine whether a product, coverage, or coverage term value can be offered for a given policy context, driven by jurisdiction, effective date, and prior answers. The senior-level point: availability lives in the product model, not scattered in PCF visibility conditions.
19. Explain the rating framework at interview depth.
Quoting invokes the rating engine per line: rate routines (parameterized calculation steps) read rate tables (versioned lookup data), compute per-coverage costs, and write Cost entities onto the branch. Carriers with complex pricing may instead call an external rater through an integration point. Know one concrete flow: e.g., base rate × territory factor × driver factor → coverage premium.
20. What are rate books and rate tables?
A rate book is a versioned, effective-dated collection of rate tables (factor lookups) and routines. Versioning lets filed rate changes apply by policy effective date, quoting picks the rate book valid for the period, which is why two identical risks with different effective dates can price differently.
21. How would you debug a wrong premium?
Method answer: reproduce with the same effective date → check which rate book version was selected → trace the rate routine execution/worksheet for the affected coverage → verify input factors on the branch (territory, class codes) → compare cost entities against expected worksheet output → only then suspect code. Mentioning rating worksheets (step-by-step calculation traces) signals real project exposure.
Underwriting & scenario questions (Q22-Q25)
22. What are underwriting issues and authority profiles?
Underwriting rules raise UW issues when risk thresholds trip (high limits, prior losses). Each issue type requires approval authority; users hold authority profiles granting approval power up to thresholds. A job with unapproved blocking issues cannot bind, escalation routes it to someone with sufficient authority.
23. Difference between validation error and UW issue?
Validation = data quality gate (blocks save/quote outright until fixed). UW issue = business risk gate (data is fine; a human with authority must accept the risk). They fire from different rule sets and resolve differently, this contrast question appears constantly.
24. Scenario: a mid-term change must not re-rate untouched coverages. How do you approach it?
Discuss effective-dated rating: only date-sliced costs affected by the change window should recalculate; pro-rating handles the changed slice. The expected shape of the answer is (a) understand which costs are effective-dated across the change date, (b) let the rating framework re-rate the changed slice, (c) verify with a worksheet comparison, not hand-patching premiums.
25. Scenario: business wants a new auto coverage with a new rating factor, live in one sprint. Outline your plan.
Product model: add coverage + terms with availability → rating: extend rate routine/table with the new factor → data model: extension fields if the factor needs new inputs → PCF: surface inputs on the line wizard → rules: validation/defaulting → integrations: expose in Cloud API payloads and downstream (billing categories, documents) → test: rating worksheet cases per jurisdiction. Closing with sequencing and risk (filed-rate dependencies, regression on existing quotes) is what separates senior candidates.
Preparing for a PolicyCenter round?
Cross-check yourself against the full 150+ question bank, then review Gosu and ClaimCenter sets.
Open the Question BankRelated reading: Top 50 Guidewire Interview Questions · ClaimCenter Interview Questions · Gosu Interview Questions