Skip to content
TR Contact

Agencies

Renewal week should not be the week you learn the surprise.

In a portfolio, risk accumulates in the policy text, not in the policy count. A coverage that was included last year and has narrowed this year never shows up as a row in a table — only someone comparing the two documents sees it.

What you can do

  • Portfolio analysis
  • Renewal analysis and coverage drift
  • Need versus opportunity
  • Customer matching and data readiness
  • Case queue and intervention log

The table is accurate, and incomplete.

A portfolio table tells you premium, expiry and line of business. It does not tell you scope. What the customer lost at renewal, which clause was dropped, which limit fell back — all of it lives in the text. POLİÇEK reads the portfolio at clause level, not row level.

Agencies

What you can do

See the coverage drift in your portfolio before renewal week, not during it.

  • Portfolio analysis

    Policies in the portfolio are analysed against a shared rule catalogue, so coverage gaps and repeating patterns become visible at portfolio level.

  • Renewal analysis and coverage drift

    Two periods of the same customer are chained together. Changed coverages, dropped clauses and reduced limits are surfaced separately. “Absent” and “excluded” are never conflated — they are different facts.

  • Need versus opportunity

    A compliance gap and a sales opportunity do not get mixed into one list. A shortfall is called by whichever of the two it actually is; the product never substitutes one for the other.

  • Customer matching and data readiness

    Records of the same person across different policies are matched, and how confident the match is stays visible. Where the data is insufficient the screen says so rather than guessing.

  • Case queue and intervention log

    A finding is queued, owned and closed. Who did what and when is recorded — it leaves an auditable trail.

Real output

One card the engine produces for this segment.

Taken from a real analysis, anonymised. The quote stands exactly as it appears in the document; the engine does not rewrite it.

Coverage drift
A coverage included last period is excluded at renewal
Previous period: coverage included. New period: the same coverage listed among the exclusions — no corresponding premium difference is stated.

The chain compares the two periods and reports the difference as a fact. “No such coverage” and “coverage excluded” are recorded separately; the second is the result of a choice, and the customer needs to be told.

Source: the policy documents of both periods

What POLİÇEK is not

Some parts of an agency workflow are deliberately outside this product.

  • It does not rate premiums, produce quotes or bind policies.
  • It does not tell you whose product to sell and favours no insurer.
  • It does not manage commissions, accounting or collections.

If you already have an account, pick up where you left off.

POLİÇEK accounts are created by invitation. If you need access for your organisation, speak to the administrator who opens accounts for you.

Cookie preferences

Strictly necessary records cannot be switched off, because the page will not work safely without them and the cookieless counter stores no personal data. The only optional item is your raw IP address and browser signature; while it is off, neither field is ever written.

Strictly necessary

The form's bot protection and remembering your choice in this panel. Cannot be disabled.

Always on

Detailed visit record

Turn this on and your visit record will also carry your raw IP address and browser signature. Page counting is independent of this switch and works without cookies; with it off you are still counted, but your identity is only a digest that changes daily.

NO cookies in this category — a server-side record only