How to Run a Claims Assessment Workflow That Closes Fraud Gaps and Satisfies the IRA
Who This Is For
You manage claims at an insurance company — motor, property, or medical. Assessors visit sites, submit assessment reports, and recommend settlements. Approvals happen informally — sometimes over WhatsApp, sometimes by email, rarely with a structured sign-off chain. An IRA examination is coming, or one has recently flagged your claims documentation as inconsistent. You know the current process has gaps. The question is what to do about it before the next examination.
The Problem
A claims approval that happens over WhatsApp, without a documented site visit record, an uploaded assessment report, and a structured senior approver sign-off, isn't a claims process — it's an open fraud channel. When KES millions are paid out based on an assessor's word rather than documented evidence, the question isn't whether a fraudulent claim will eventually succeed. It's how long before it becomes a regulatory finding or a litigated dispute. IRA examinations of claims records have become more detailed. Examiners want to see the site visit evidence, the full assessment report, the approver's documented decision, and the basis for the settlement amount — for every file in the sample they pull. When that documentation is scattered across email threads, WhatsApp conversations, and shared drives, the finding is straightforward: the claims process is not documented to the required standard. This isn't classified as an administrative observation — it's a governance and capital adequacy finding.
What You Can Achieve
- Every claim requires a documented site visit with photo evidence before any assessment data can be entered — assessors who skip visits create a visible, immediate workflow gap
- The complete assessment record — site photos, police abstract, full assessment report, approver decision — is captured in one structured, sequential workflow rather than scattered across inboxes
- IRA examiners reviewing your claims records find complete, sequential documentation for every settled claim — organized by assessor, approver role, and settlement amount
- Senior approver review is a documented, timestamped step attributed to a named individual — not a WhatsApp message that may or may not still exist
- Claims processing time drops when the workflow is clear and sequential — assessors know exactly what's required, and nothing gets stuck waiting for missing documentation to be chased
- Fraud patterns surface through the audit trail: assessors who consistently approve without complete site evidence, or who show unusual settlement amount patterns, become visible
The Hakiki Workflow
- 1Claim Reference & Policy Number Text
Enter claim reference number and policy number — ties the assessment to the policy record
- 2Site Visit Conducted Boolean
Confirm physical site visit has been conducted — MANDATORY. This step must be YES before any assessment data can be entered
- 3Damage / Loss Photos File Upload
Upload minimum 4 photos of damage or loss at the site — taken during the physical visit. Required
- 4Police Abstract File Upload
Upload police abstract — required for motor accident, theft, and burglary claims
- 5Estimated Repair / Replacement Cost Text
Enter assessor's estimated cost (KES) — supported by quotes or valuation evidence
- 6Pre-Existing Damage Noted Boolean
Record whether any pre-existing damage was observed at the site that is unrelated to the claimed incident
- 7Pre-Existing Damage Notes Text
Describe pre-existing damage in detail — required if previous step is YES, used in settlement calculation
- 8Assessment Report Upload File Upload
Upload completed assessment report — required before assessor recommendation is recorded
- 9Assessor Recommendation Single Select
Select: Approve / Decline / Investigate Further — with assessor ID and timestamp
- 10Senior Approver Review Boolean
Senior approver confirms they have reviewed the assessment record and recommendation
- 11Senior Approver Concurrence Boolean
Senior approver concurs with assessor recommendation — or documents the basis for override
- 12Final Decision Single Select
Select: Approved / Declined / Referred to Legal — recorded by senior approver with role ID
- 13Settlement Amount Text
Enter approved settlement amount (KES) — matches the authorized decision
- 14Payment Authorized Boolean
Finance confirms payment is authorized against the approved settlement — final gate before disbursement
HAKIKI Features Used
See Hakiki in action
Build your first auditable workflow in minutes — no credit card required.
Get Started FreeMore in Heavy-Procedure Industries
Private Hospital
How to Run the WHO Surgical Safety Checklist Digitally — and Make It Count for Accreditation
Pharmaceutical Manufacturer
How to Run GMP Batch Release Documentation That Passes WHO and KEBS Audits
Regional Airline
How to Run Pre-Flight Inspections With a Digital Audit Trail That Satisfies KCAA