Core concepts (Q1-Q8)
1. What does ClaimCenter do, in one sentence?
ClaimCenter is the InsuranceSuite claims management system: it handles the entire claim lifecycle from First Notice of Loss through investigation, evaluation, payment, recovery, and closure across all P&C lines of business.
2. What is FNOL and what happens during intake?
First Notice of Loss, the initial loss report. The FNOL wizard: verifies the policy in force on the loss date (via policy retrieval from PolicyCenter or a policy system of record), captures loss details, parties, and damage; creates the claim; then segmentation and assignment rules classify and route it. The policy-verification-on-loss-date detail is what interviewers listen for.
3. What is an exposure? Why not track everything at claim level?
An exposure is one claimant's demand under one coverage, the claimant × coverage intersection. A two-car accident claim may have exposures for the insured's vehicle (collision), the third party's vehicle (property damage liability), and the third party's injury (bodily injury). Financials attach to exposures so each demand is reserved, paid, and closed independently, claim-level-only tracking couldn't answer "how much is reserved for the injury vs the vehicle."
4. What is the claim/exposure relationship to the policy?
The claim references a snapshot of the policy as of the loss date (a frozen copy, the "policy in ClaimCenter" is not live PolicyCenter data). Exposures link to specific coverages from that snapshot. Follow-up to expect: why a snapshot? Because the policy may change or renew after the loss; the claim must adjudicate against what was in force at loss time.
5. What are claim contacts?
All people/companies on the claim, insured, claimants, witnesses, adjusters, vendors (body shops, doctors, lawyers), modeled as contacts with roles. Contact roles drive screen behavior, permissions, and integrations (e.g., vendor payments need address/tax data).
6. What is a matter?
A litigation record: when a claim goes legal, a matter tracks the lawsuit, attorneys, court dates, and legal spend, linked to the affected exposures.
7. What is the LOB (line of business) model in ClaimCenter?
The typelist-driven mapping that defines, per policy type: which loss causes exist, which coverage types map to which exposure types, and which claim screens apply. Adding a new line of business is largely LOB-model configuration, a strong senior-level talking point.
8. How does ClaimCenter get policy data if the insurer doesn't run PolicyCenter?
Through the policy retrieval integration point, a plugin queries the external policy admin system and maps results into ClaimCenter's policy snapshot entities. This is one of the most common real-world integrations in Indian SI projects, since many carriers phase their Guidewire adoption starting with ClaimCenter.
The financial model (Q9-Q16)
9. Name the transaction types in ClaimCenter's financial model.
Reserves (money set aside for expected future payments), Payments (money out, drawn against reserves), Recoveries (money in, subrogation, salvage, deductible), and Recovery Reserves (expected recoveries). All are transactions against an exposure, categorized by cost type and cost category.
10. How is Total Incurred calculated?
Total Incurred = remaining (open) reserves + total payments − recoveries (recovery treatment varies by carrier configuration). It answers: "what do we currently expect this claim to ultimately cost?" Interviewers ask this formula verbatim, say it precisely.
11. What are cost type and cost category?
Two-level classification of every financial transaction: cost type separates claim cost vs expenses (e.g., claim cost, adjusting expense, legal expense, mapping to accounting buckets); cost category refines it (e.g., auto body repair, medical, rental). These feed reserving granularity and downstream finance/reinsurance reporting.
12. Walk through what happens when an adjuster writes a check.
Payment created against an exposure's reserve line → validation (sufficient reserves? authority limits?) → approval if above the adjuster's authority → transaction lifecycle: pending → submitted → the check instruction flows through the financial integration (check writing/ERP system) → acknowledgment sets status issued/cleared. Mentioning the transaction lifecycle states and the async integration acknowledgment is what marks a real practitioner.
13. What happens if a payment exceeds remaining reserves?
Depending on configuration: automatic reserve increase with the payment (if permitted and within authority), or the payment is blocked pending a reserve change approval. This tests understanding that reserves gate payments.
14. What are authority limits in the financial context?
Per-user/role caps on reserve changes and payment amounts. Transactions above authority spawn approval activities routed up the supervisor chain. Expect the follow-up: "how do you configure a new authority level?", authority limit profiles assigned via the org model.
15. Explain subrogation and salvage as recovery flows.
Subrogation: recovering paid amounts from the at-fault third party (or their insurer); ClaimCenter tracks liability assessment, demand, negotiation, and recovery transactions. Salvage: recovering value from damaged property (totaled vehicle sold for parts). Both post recovery transactions that reduce net incurred.
16. What is a bulk invoice?
A single vendor invoice covering items across multiple claims (e.g., a law firm billing 20 claims monthly), split into per-claim, per-exposure line items that post as individual payments while being settled as one instrument.
Process: segmentation, assignment, workplans (Q17-Q21)
17. What is segmentation and when does it run?
Rule-driven classification of claims (and exposures) by complexity/severity shortly after creation, e.g., fast-track windshield vs complex bodily injury. The segment then drives assignment, workplan selection, and oversight level. Re-segmentation can occur when facts change (minor claim becomes litigation).
18. How does assignment work in ClaimCenter?
Assignment rules route claims/exposures/activities to groups and users using methods like round-robin or load-balanced selection, filtered by segment, location, and adjuster skill/workload. Both claim-level and exposure-level assignment exist, a multi-exposure claim can have different handlers per exposure.
19. What are workplans and activities?
A workplan is the generated checklist of activities (tasks with owners, due dates, priorities, escalation) appropriate to the claim's segment, e.g., "contact insured within 24h," "inspect vehicle within 3 days." Activity patterns define reusable templates; rules generate them onto claims.
20. What is SIU referral?
Special Investigation Unit, fraud handling. Rules score fraud indicators; above threshold, an SIU referral routes the claim for investigation, with restricted access and its own activity patterns. Fraud-detection integration (including ML-based scoring via Guidewire's analytics products) is an increasingly common 2026 question.
21. What are claim validation levels used for?
Same staged-validation concept as the suite generally: a claim can be saved with partial data at FNOL but must satisfy stricter levels before payments or closure. It lets intake be fast while keeping financial actions safe.
Scenario questions (Q22-Q25)
22. Scenario: narrate a two-car accident claim end-to-end with money.
FNOL (policy verified on loss date) → segmentation: moderate → assignment to auto adjuster → exposures: insured collision, TP property damage, TP bodily injury → reserves: ₹80k / ₹1.2L / ₹5L → payments: body shop ₹75k, TP vehicle ₹1.1L, medical + settlement ₹4.5L → liability investigation shows other driver 60% at fault → subrogation recovers ₹3.5L → net incurred adjusts down → exposures close, claim closes. Practice saying this aloud, it's the single most common ClaimCenter scenario prompt.
23. Scenario: a closed claim needs a new payment. What happens?
Reopen flow: claim (or just the exposure) is reopened with a reopen reason, reserves re-established, payment made, then re-closed. Tests knowledge that closure is reversible and audited, and that exposure-level reopen avoids reopening the whole claim.
24. Scenario: adjusters complain the claim screen is slow. Your investigation plan?
Profile the page load → common culprits: expensive Gosu in PCF visibility expressions, unindexed queries in screen list views (activities/history panels), oversized policy snapshots, or synchronous integration calls (document/vendor lookups) on page render. Fix pattern: move logic to enhancements, add indexes on extension columns, make integrations async. The method matters more than the specific guess.
25. Scenario: business wants automatic fast-track settlement for glass claims under ₹25,000. Design it.
Segmentation rule identifies glass loss cause + estimate under threshold → auto-create exposure with default reserve → straight-through payment to approved vendor via integration → validation guardrails (policy in force, no fraud indicators, one prior glass claim limit) → auto-close with audit trail → exceptions route to human review. This tests straight-through processing design, the direction most Indian ClaimCenter programs are heading.
Preparing for a ClaimCenter round?
Drill the full question bank and the PolicyCenter and Gosu sets, most interviews mix all three.
Open the Question BankRelated reading: Top 50 Guidewire Interview Questions · PolicyCenter Interview Questions · Gosu Interview Questions