Skip to content

Corporates

“The coverage exists” may not be true for everyone.

In group policies, coverage is often attached to individual insured persons rather than to the policy as a whole. It is entirely ordinary for the same guarantee to exist for some insured persons and not for others — and a reading collapsed into a single value cannot see it.

What you can do

  • Person-level coverage view
  • Portfolio and renewal calendar
  • Cross-evidence
  • Executive summary

Aggregation destroys information.

Summarising a group policy as “covered / not covered” can drop the employee who needs it most into the wrong bucket. Seeing the person-level truth requires building the person ↔ coverage link in the document; POLİÇEK builds it at read time.

Corporates

What you can do

See person by person who is actually covered under your group and fleet policies.

  • Person-level coverage view

    Insured persons in the document are separated out, so who holds a guarantee and who does not becomes visible per person. No single aggregated flag is produced.

  • Portfolio and renewal calendar

    All corporate policies gather into one view; documents approaching expiry and scope changes between periods surface ahead of time.

  • Cross-evidence

    Before a finding is shown, the engine asks whether anything else in the same document modifies or limits it. Causation is never invented: related evidence is presented as related, nothing more.

  • Executive summary

    The summary that reaches a decision-maker stays attached to the evidence beneath it. A figure appears only on a line that has evidence; a line without evidence carries no figure.

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.

Cross-evidence
Lifetime renewal guarantee held by only one of three insured persons
As extracted from the document: insured 1 YES; insured 2 NO; insured 3 NO — same policy, same period.

A reading that reduces this line to one true/false value says “no guarantee” and drops the insured person who does have it into the wrong bucket. Without the person ↔ guarantee link, this policy has not been read correctly.

Source: the special terms of your policy · person-level extraction

What POLİÇEK is not

The limits a corporate buyer should know about.

  • It is not a broker: it does not bind policies, intermediate or negotiate premiums.
  • It recommends no insurer and no insurance product.
  • It is not an HR or employee-records system.

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