Checklist · core platform evaluation

The PAS RFP checklist: 14 areas that decide the choice

Feature lists converge — evaluations are won and lost on upgrade economics, AI placement, implementation risk, and deployment control. Here is the full checklist we see working in real core-platform RFPs.

How to use

Score each vendor 1–5 per area, weight the areas that matter most to your operation, and use your top 5–10 real use cases as the spine of the RFP — every vendor answers the same buyer-relevant problems. Scorecards before RFP, demos on your products, references on implementations your size.

The checklist

14 evaluation areas for a core platform RFP

01 · Policy lifecycle administration

Issue, renewals, amendments, cancellation, reinstatement — can business users run the full lifecycle without IT tickets?

02 · Product building & rating

How long from product idea to live? Configuration or code? Can rates change without a release?

03 · Claims management & automation

Intake to settlement, reserves, experts, fraud signals — and what share can run straight-through?

04 · Billing & payment processing

Recurring collection, e-invoicing, bank gateways, automatic payment recognition, dunning.

05 · Accounting & reserves

UPR, DAC, RBNS calculations, GL export, multi-branch and multi-currency books.

06 · Reinsurance

Native or partner add-on? Treaty and facultative, period reports, reinsurance billing.

07 · Taxes & compliance

Per-jurisdiction tax configuration on policies, claims, invoices; declarations and reporting.

08 · Data, analytics & AI

Where does AI live — core data model or marketplace add-ons? Claims AI, fraud, Client 360 included or extra?

09 · Integrations & APIs

REST/web services, broker systems, aggregators, registers, banks, clinics — and who builds them.

10 · Upgrade economics

Continuous releases or version projects every 3–5 years? Who pays for upgrades? Ask for the 10-year TCO.

11 · Deployment & sovereignty

SaaS-only or your infrastructure? Data residency, audit access, exit strategy, database choice.

12 · Implementation approach

Realistic timeline with references; parallel running; standard-config-first vs big-bang.

13 · Security & access

Roles, multi-level access, detailed audit of data and operations, ISO certifications.

14 · Vendor partnership

Who actually does the work — vendor or SI chain? Sprint cadence, demo access, escalation paths.

Common questions

FAQ

What do buyers most often forget to ask?

Upgrade economics. Continuous releases vs a version project every 3–5 years changes 10-year TCO dramatically — analyst reviews repeatedly flag "profitable upgrades" as a vendor revenue line. Ask who pays for staying current.

How many vendors should be in the RFP?

Three to five. Use a top-10 longlist (see our guide), score against weighted criteria, then deep-dive demos with 2–3 finalists on your own products and data.

Where does PINS stand on these 14 areas?

Full marks on full-cycle scope, native reinsurance, embedded AI, evergreen releases, deployment freedom, and 6–12 month implementations — that is exactly why we publish this checklist. Ask us the hard questions on a demo.

Related

Where to go next

Want the scorecard version?

We will share the weighted scorecard template and walk your team through it — no strings attached.

Ask our AI

Ask about your PAS RFP

RFP scope

What should a policy administration system RFP include?

Help

Can you help us shape our PAS RFP?

Fit

How does PINS meet these RFP requirements?