LifeX · New Business Onboarding

From Quotation to Policy, explained for people who know Medical, not Life

You already understand insurance — claims, coverage, premiums. This guide bridges the specific gap: how a Life insurance sale actually works in LifeX, why it looks different from a Medical policy, and exactly what you'll click through when you test it. Every screenshot below is a real screen from the running system, not a mockup.

For: BA & Testing team Assumes: Medical insurance background Covers: Individual, Group & Credit Life

Medical vs. Life insurance — same idea, different shape

Your Medical background gets you further than you'd think. The claim/approval/network machinery is conceptually similar. What's genuinely new is what the product actually promises.

M Medical insurance (what you know)

Pays for treatment as it happens — a hospital visit, a prescription.
Coverage resets every policy year; nothing is "saved up."
Claims go through a network of approved hospitals/clinics.
Underwriting mostly checks pre-existing conditions at renewal.
The policy has almost no value if nobody gets sick that year.

L Life insurance (what this guide covers)

Pays a lump sum on death or a specific event (disability, critical illness) — or on maturity.
A slice of every contribution can be invested into funds — it grows over the life of the policy, like a savings plan bolted onto protection.
No treatment network — instead there's a beneficiary (who gets paid) and, in Saudi practice, a Zakat calculation on the invested portion.
Underwriting happens once, up front, before the policy is even issued — a "Yes" to a health question can pause the whole sale for manual review.
The policy has real value even if nothing bad ever happens — that's the savings component.

The one-sentence version

Medical insurance reimburses you when something happens this year. Life insurance is a long-term promise — plus, for these products, a savings pot — that someone else (a beneficiary) collects on, or that you collect on at maturity.

Glossary — the words you'll see everywhere

Skim this once. You'll recognize every one of these terms in the screenshots further down.

Quotation: A draft — not yet a real contract. The customer's chosen product, plan, contribution and coverage, still editable, still needs approval.
Policy: A real, in-force contract. Created automatically the moment an approved Quotation is "issued" — you never create a Policy directly.
Product / Plan: Product = the type ("Personal Protection & Savings Plan"). Plan = one configured version of it (its rates, its benefits) — a Product can have more than one Plan over time.
Underwriting: The manual health-risk review. Triggered only when a customer answers "Yes" to a medical question that's flagged as risky.
Sum Assured / Coverage: The lump sum paid out on the insured event. Separate from the "Contribution" (what the customer pays in).
Contribution: Life insurance's word for "premium" — what the customer pays, on a schedule they choose (Monthly, Yearly, etc.).
Fund Allocation: How the savings portion of each contribution is split across investment funds (Growth, Balanced, Conservative...). This is what makes Life different from Medical — there's money actually growing inside the policy.
Beneficiary: Who gets paid if the insured event happens. A concept Medical insurance simply doesn't have.
MCA (Maker–Checker–Approver): Nothing in LifeX goes live from a single click. A named sequence of people (roles) has to sign off in order first — see The approval chain.
Individual Life: One customer, one policy. The default, and the one you'll test most.
Group Life: One employer or association ("the scheme") buys one master policy that covers many employees ("members") at once.
Credit Life: A special case of Group Life sold by a bank: the "members" are borrowers, and the coverage amount automatically shrinks as each loan gets paid down.
Service Request: Anything a customer asks for after the policy already exists — a top-up, a withdrawal, a beneficiary change, a claim.
Reinsurance / Cession: The insurer shares part of the risk (and the premium) with a reinsurer, automatically, the moment a policy is issued — happens behind the scenes, nothing the front-office team does by hand.

The big picture — one Quotation's life story

Every Quotation, Individual or Group, moves through the same set of states. This is the map to keep in your head while you test.

stateDiagram-v2
    [*] --> Draft: Sales creates the Quotation
    Draft --> MedicalReferred: A risky "Yes" answer
    Draft --> MedicalCleared: All answers clear
    MedicalReferred --> MedicalCleared: Underwriter clears the case
    MedicalCleared --> PendingApproval: Submitted for approval
    PendingApproval --> PendingApproval: Maker approves, hands to Checker
    PendingApproval --> Accepted: Final Approver signs off
    PendingApproval --> Rejected: Any stage rejects
    Accepted --> Converted: "Issue Policy" clicked
    Converted --> [*]: A real Policy now exists
    Rejected --> [*]

Group Quotations skip the Medical states entirely — see What's different.

Why this matters for testing

A Quotation's on-screen "Save & Continue" never means "this is now real." It only becomes a real, billable Policy at the very last step, after every approval stage has said yes. Test both the happy path (all "No" answers, clean approval) and the branch paths (a "Yes" answer that forces Underwriting, a rejection at any approval stage).

The approval chain — Maker, Checker, Approver

This is the same idea as a Medical claim needing a supervisor's sign-off, just formalized into three named stages LifeX calls MCA. A Quotation cannot become a Policy until all three have said yes, in order.

Stage 1

Maker (Sales Executive)

Reviews the Quotation was filled in correctly and submits it forward.

→

Stage 2

Checker (Sales Supervisor)

A second set of eyes — catches mistakes the Maker might have missed.

→

Stage 3

Approver (Sales Manager)

Final sign-off. Only after this does the Quotation become Accepted and eligible to be issued as a Policy.

What you'll actually see on screen

One shared panel handles all of this — it shows Not yet submitted, then Awaiting [Stage Name], then either Fully approved or Rejected. A reject at ANY stage stops the whole thing — it does not skip ahead. The exact same panel design is reused for approving Product changes, Pricing changes, and Underwriting question changes elsewhere in the system, so once you've learned this once, you've learned it everywhere.

Individual Life — step by step, real screens

One customer, buying one policy for themselves. This is the flow you'll test most often. Every screenshot below was captured from a live run of the exact steps described.

Start here

The Quotations list

Every Quotation ever created, with its current status badge. This is where Sales lands to start a new sale or check on one in progress.

Test tip: confirm status badges match what's actually happening — a Quotation stuck in MedicalReferred should never silently show as Accepted.

Step 1

New Quotation — Individual vs. Group

Every Quotation starts here with one choice: Individual or Group. This one toggle changes almost everything downstream — which sections appear, what gets validated, and how the price is calculated.

Step 2

Plan & Cover

Pick the customer, then the Product and Plan, then set the Contribution (what they pay), Coverage Amount (the lump sum promised), how often they pay, and for how many years. The right-hand "Plan Summary" panel recalculates live as you type.

Test tip: try a contribution just under and just over 36,000 SAR/year on a "Customer Choice" product — it should silently switch the charge structure between Front-Loaded and Level-Loaded.

Step 2 → saved

Saved, not yet real

A green "Plan & cover details saved" toast appears, and the Quotation now has a real ID in the database — but it's still just a Draft. Nothing has been sold yet.

Medical and disclosure questions, unanswered

Step 3

Medical & Disclosure Questions

This section has no equivalent on a Medical policy's sale — Medical insurance underwrites at claim time, Life insurance underwrites before the sale completes. Every question needs a Yes/No answer.

Step 3 → answered

The happy path: all "No"

Answer every question "No" and the case sails straight through — no manual referral needed. Answer even one flagged question "Yes" and a warning banner appears: the case gets routed to Underwriting instead, and the Quotation's status becomes MedicalReferred until a human clears it.

Test tip: deliberately answer a flagged question "Yes" in a separate run — confirm the referral banner appears and the status actually changes to MedicalReferred, not just visually but in the list view too.

Step 4

Funds & Beneficiaries — the Life-only step

This is the section with no Medical-insurance equivalent at all. Split the savings portion across funds with the sliders (the donut chart updates live), then either default beneficiaries to the legal inheritors or name specific people and their share.

Test tip: the fund split must total exactly 100% and beneficiary shares must total exactly 100% — try submitting at 99% and 101% and confirm both are rejected with a clear message, not a silent failure.

Review and Issue section, not yet submitted

Step 5

Review & Issue

A final summary, and the "Submit for Approval" button that kicks off the MCA chain described above. Nothing before this point required anyone else's sign-off.

Steps 6–8

Submitted → approved

The same panel walks through Awaiting Maker Review → Awaiting Checker Review → Awaiting Approver Sign-off → Fully approved. In test environments one user can hold all three roles and clear the whole chain solo — in production these are three different people.

Step 9

Issue Policy — the moment it becomes real

Only now does "Issue Policy" become clickable. This is the single moment a real, numbered Policy is created — everything before it was reversible; this generally isn't.

Step 10

The Policy itself

A real contract with its own number, start/expiry dates, and status. From here, tabs expose everything else — Fund Allocation (the live investment split), Zakat (the compliance calculation on fund value), Beneficiaries, Endorsements, and Documents.

Bonus

Fund Allocation tab

The split you set during Step 4, now attached to the live Policy — this is the number that actually grows (or shrinks) as fund performance is published, and what a "Fund Switch" service request would change later.

Group & Credit Life — what's actually different

Same overall lifecycle (Draft → Approval → Issued), but the unit being insured changes from "one person" to "a whole roster of people at once." Read this before the walkthrough — it explains why several screens look different.

flowchart LR
    subgraph IND["Individual Life"]
        C1["One Customer"] --> P1["One Policy"]
    end
    subgraph GRP["Group Life"]
        S["One Scheme
(the employer)"] --> MP["One Master Policy"]
        M1["Member 1"] -.enrolled under.-> S
        M2["Member 2"] -.enrolled under.-> S
        M3["Member N..."] -.enrolled under.-> S
        MP --> CT1["Certificate 1"]
        MP --> CT2["Certificate 2"]
        MP --> CT3["Certificate N..."]
    end

Each Group member gets their own coverage Certificate, but there is still only ONE Policy and ONE bill for the whole scheme.

Concept	Individual Life	Group Life	Credit Life
Who is "the customer"?	One named person	An employer or association ("the Scheme")	A lending bank ("the Scheme"), members are its borrowers
Who is actually covered?	That one person	Every enrolled employee ("Member")	Every borrower with an active loan
Medical questions?	Yes, per person	Skipped — not applicable at master-policy level	Skipped, same reason
Funds & Beneficiaries?	Yes, per person	Skipped — no individual savings component at this level	Skipped, same reason
Coverage amount	Fixed, chosen at sale	Set per member (a scheme default, or a per-member override)	Decreases automatically as the loan balance is paid down
Extra input needed	—	Member Count ("lives"), often with a minimum group size rule	Loan amount, interest rate, term — per borrower
Billing	Per-policy contribution	ONE consolidated bill for the whole scheme per cycle	Same as Group
Reinsurance	Standard quota-share, invisible to the front office	Mandatory Surplus-Share treaty, calculated per member	Same as Group

The one thing to remember

A Group or Credit Life Quotation still becomes exactly one Policy — never one Policy per member. Members plug into that one Policy afterward as "Certificates." If you ever see the system create a separate Policy per employee, that's a bug, not a feature.

Group Life — step by step, real screens

The same underlying screens as Individual Life, with the Group-specific differences called out. This example uses a group scheme with 12 enrolled lives.

Start here

Group Schemes — the "employer" record

Before a Group Quotation can exist, the employer (or association, or lending bank for Credit Life) must exist as a Scheme, with its members already enrolled. This is a separate admin screen from Quotations.

Step 1

The same wizard, switched to Group

Same "New Quotation" screen as Individual Life — but flipping the toggle to Group swaps the Customer picker for a Group Scheme picker, and adds a Member Count field.

Group quotation filled with scheme, member count, product, plan

Step 2

Plan & Cover for a Group

Pick the Scheme, enter how many lives are being covered, then the Product and Plan as before. Some plans enforce a minimum group size — try a number below that minimum to see the rejection message.

Test tip: group rating is banded by size — the per-life rate for a 10-person group is different from a 60-person group on the same plan. Confirm the quoted premium actually changes as you cross a band boundary.

Steps 3–4

Straight to approval — no Medical or Funds steps

Because those two sections don't apply at scheme level, a Group Quotation goes from "Plan & Cover saved" directly into the same MCA approval chain used everywhere else in LifeX.

Step 5

Issue Policy — one Policy, many members

Exactly the same "Issue Policy" action as Individual Life. Behind the scenes, this single click also creates a coverage Certificate for every enrolled member and, if this product requires it, generates the mandatory reinsurance cession.

Group policy view details showing scheme header

Step 6

The Policy screen — now scheme-shaped

Notice the header now shows the Scheme's name and a "Group Policy" badge instead of a customer's name — and two tabs that only ever appear for Group policies: Members and Billing.

Members tab

The certificate roster

Every enrolled member, their coverage amount (either the scheme default or a personal override — for Credit Life this is the shrinking loan balance instead), and their certificate number. This is the closest Group Life equivalent to "who is insured."

Billing tab

One bill, not one per member

The employer gets billed once per cycle for the whole group — never a separate invoice per employee. This tab is where that consolidated schedule and payment history live.

Status cheat-sheet

Every status you can encounter on a Quotation, in the order you'll normally see them.

Status	Means	Who moves it forward
Draft	Just created, still being filled in.	Sales
MedicalReferred	A risky health answer paused it for manual review. (Individual only.)	Underwriter
MedicalCleared	No health concerns, or Underwriting cleared it.	—
PendingApproval	Inside the 3-stage Maker–Checker–Approver chain.	Sales Exec → Supervisor → Manager
Accepted	Fully approved. Ready to become a real Policy.	Sales
Rejected	Stopped at some approval stage. Needs rework or abandonment.	Sales
Converted	Issued. A real Policy now exists; this Quotation is now historical record.	—

A starting checklist

Not exhaustive — a sensible first pass covering both product lines.

Individual: full happy path, all medical answers "No," clean approval, real Policy issued.
Individual: a flagged "Yes" medical answer correctly routes to MedicalReferred and blocks conversion until cleared.
Individual: fund allocation and beneficiary share validation both reject anything ≠ 100%.
Individual: a Customer-Choice product's charge structure actually flips at the contribution threshold.
Group: a group size below a plan's minimum is rejected with a clear message, not a silent failure.
Group: the quoted per-life rate genuinely changes across a group-size band boundary.
Group: issuing the policy creates exactly one Certificate per enrolled member — count them.
Both: a rejection at ANY approval stage stops conversion — it should not be possible to "Issue Policy" on a Rejected or still-Pending Quotation.
Both: the resulting Policy's data (contribution, coverage, dates) exactly matches what was quoted — no silent rounding or drift.