Automate IRDAI claim forms A and B in 5 steps.

Most Indian insurance brokers fill IRDAI claim form A and B the same way they did ten years ago. The customer emails a photo of the form. An ops person opens Adobe Reader, types in the values, prints, signs, scans, and sends it to the insurer. The next claim, they do it all over again.

This guide shows a simpler way in five steps. By the end, your customer fills the claim once on their phone, and a signed PDF lands in your inbox. No typing, no scanning, no copy-paste.

Why IRDAI claim forms eat your week

Two forms cause most of the work. Form A is filled by the customer with details of the loss. Form B is filled by the surveyor or hospital with the cause and the amount of the claim. Both forms have the same set of customer details repeated at the top, name, address, policy number, vehicle or property identifier, and contact number.

The pain is not the form itself. The pain is filling it five times for one claim. Once on the application, once on Form A, once on Form B, once on the surveyor note, and once when the insurer asks for a clean copy.

One customer name, typed five times in one claim. That is not a paperwork problem, it is a system problem.

The 5-step plan

Here is the simple version. You set this up once. After that, every claim follows the same flow.

Step 1, upload the IRDAI form once

Take the official IRDAI claim form A PDF that your insurer provided. Open Mezdoc, click New template, and drop the PDF on the editor. Mezdoc shows every page. Do the same for Form B in a second template.

You do this one time. Not once per customer. Once for your whole company.

Step 2, drop fields on the form

Drag a box on every place a value should go. Name, address, policy number, date of loss, IDV, claim amount, signature. Pick the right type for each box, name as a name field, date as a date field, claim amount as a currency field. Give each field a simple alias like customer_name, policy_no, claim_amount.

If the same value goes on two pages, link the fields. The customer types their name once, both pages get it.

Step 3, publish a version

Click Publish. Mezdoc saves a version of the template that can never change unless you publish a new version. Months later, when an auditor asks which version of the form was used for a claim from June, the answer is recorded in the claim itself.

Test the template on a staging copy first. If it looks right, promote it to production with one click.

Step 4, share a fill link with your customer

For every new claim, send a Mezdoc fill link to the customer over WhatsApp or email. The link opens on their phone. They see your branding, fill the boxes, sign on the screen with their finger, and submit.

On your side, you get a signed PDF in your dashboard within seconds. The PDF carries a full record of who signed it, when, from which IP address, and against which version of the template.

Step 5, send the signed PDF to the insurer

Download the signed PDF from your dashboard or set Mezdoc to email it straight to the insurer when the customer signs. Some teams also bundle Form A and Form B into one packet that goes out together. Pick the option that matches your team.

That is the whole flow. Five steps, set up in an afternoon. Every claim after that follows the same pattern with no manual typing.

What changes for your team

Four things change once this is in place.

• Your ops team stops typing. They handle exceptions, not transcription.
• Customers fill the form once. No back and forth over WhatsApp asking for missing details.
• Every claim has a full record. Signer, time, IP, and the version of the form that was used.
• Form updates from IRDAI are a 10-minute job. Edit the master template, publish v2, the next claim uses the new version.

What about the surveyor report

The same five steps work for the surveyor inspection report and the photo affidavit. Make each one a Mezdoc template, share a fill link with the surveyor, get the signed PDF back. Many brokers bundle the claim form A, Form B, and the surveyor report into one workflow so a single link drives all three documents.

A worked example

A two-wheeler claim comes in. The customer says their bike was hit. Here is what the day looks like under the old and new flow.

# Customer emails photos of the form filled by hand
# Ops opens Form A in Adobe Reader, types name, address, policy
# Ops opens Form B, types the same name, address, policy
# Ops prints both, scans the customer signature
# Ops emails the insurer
# Insurer keys the values into their system

# Ops opens the claim in their CRM
# Clicks Generate claim packet, Mezdoc fills Form A and Form B
# Customer gets a fill link, fills any extra fields, signs on phone
# Signed packet lands in the inbox
# Forwarded to insurer with one click

Twenty-two minutes saved per claim. At fifty claims a week, that is roughly two full working days back to your team every month.

What you need to start

Three things, none of them hard.

• The IRDAI claim form A and B PDFs from your insurer (you already have these).
• A Mezdoc account, the free plan covers a real test setup with no card.
• One afternoon to set up the two templates and run a test claim end to end.

If you want help, the team builds the first two templates with you on a call. Just ask. Most brokers we work with have their first claim packet running in production by the end of the week.

Common questions

Does this work for health claims too

Yes. The same five steps work for the hospital cashless claim form, the reimbursement claim form, and the pre-authorisation form. Each becomes a separate Mezdoc template.

Is the audit trail accepted in disputes

The audit trail records signer name, email, IP address, signed time, and a code that proves the PDF was not changed after signing. Many Indian insurers accept this as proof. If you operate in a court that needs Aadhaar eSign with a digital signature certificate, Mezdoc supports that too.

Can the customer fill on a feature phone

The fill link opens in any browser. A feature phone with internet access can open the link in its browser. The customer can also fill on a desktop if they prefer. Both arrive the same way on your side.

Where to go from here

Sign up on the free plan and build the first IRDAI claim form A template this week. The setup is 30 to 60 minutes. The first time a customer signs on their phone and the signed PDF appears in your inbox, you will know why your team will not go back to Adobe Reader.