The client said yes. The mandate never came back.
Every unsigned mandate, disclosure or debit-order form is a policy that hasn't actually started — and a client with time to go quiet. Send it from your desk, let them sign from whatever device is in their hand, and get it back sealed, fingerprinted and timestamped the same day.
No credit card to start — Personal plan included.
Close the "client went quiet" gap
The days between "send me the forms" and a signed return are where deals die. A link they can sign on their phone, plus automatic reminders, shortens that gap to hours.
Provable at claim time
Claims get contested on wording. Every completed document is sealed and fingerprinted, so the version your client signed is provably the version everyone is relying on.
A record of how it was signed
Every signature carries an audit trail — the link it came from, the device, the timestamp, each event hash-chained. It doesn't tell you the signer's ID was checked; it tells you exactly what happened, and can't be rewritten afterwards.
The paperwork that stands between a quote and a policy
-
Broker mandates & letters of appointmentThe document that makes you the broker of record — signed before anyone can act on it.
-
FSP disclosure noticesThe disclosures you're required to give — with a signed, dated acknowledgement on file instead of a verbal "yes, I saw it".
-
Records of adviceThe client confirms what was recommended and why, in writing, at the time — not reconstructed later.
-
Policy schedules & endorsementsAcceptance of the schedule, and of every mid-term change, each one sealed as its own record.
-
Debit-order mandatesPremium collection starts with a mandate the bank and the client can both point to.
-
Claim forms & declarationsSigned claim submissions with a timestamp nobody has to argue about afterwards.
-
Group scheme member formsEmployee-benefit and group-life membership forms, sent in volume, chased automatically.
1. Appointment of Intermediary
The Client hereby appoints the Broker as intermediary of record in respect of the policies listed in Schedule A, and authorises the Broker to obtain quotations, place cover and attend to claims administration on the Client's behalf, with effect from the date of the last signature below.
Mid-flow: the client has signed from her own device; KuduDoc is holding the document open for the broker's counter-signature and will chase it automatically.
Signed today, defensible in three years
Sealed documents
At claim time, the version signed is the version relied on — provably.
Every completed document gets a tamper-evident certification signature, a SHA-256 fingerprint and an independent timestamp, Bitcoin-anchored within hours. When a claim turns on what the schedule said, anyone — client, insurer, ombud — can check the exact file for free, without trusting KuduDoc's word for it.
See how verification worksVerification result
Audit trail
What the record shows about the signing itself.
A signature proves someone signed. KuduDoc records the circumstances: which link was opened, from what device, at what time, with every event hash-chained so the sequence can't be rearranged later. What it does not do — yet — is check that the signer is who they say they are. ID-document and liveness checks* are in build and not live, so where the sum assured makes "are you sure that was the client?" an expensive question, keep doing that check the way you do now.
Where identity verification is headedAudit trail — L. Mokoena
* On our roadmap — in build, not live yet.
Before you send the next mandate
For an ordinary broker mandate, yes — electronic signatures are legally recognised in South Africa under the ECT Act, and a mandate is not among the instruments its Schedule 2 excludes. Two things to hold in mind. Where a statute itself demands a signature, only an advanced electronic signature from an accredited provider satisfies section 13(1), and we are not accredited. And your own FSP compliance framework, or an insurer's scheme rules, can prescribe how a particular mandate has to be captured — that's contractual rather than statutory, and worth checking with your compliance officer before you switch. What changes with KuduDoc is what you can prove afterwards: every completed document carries a certification signature, a SHA-256 fingerprint and an independent timestamp, not just a scribble on a scan.
The sealed file settles it. Any edit after completion breaks the certification signature, and the SHA-256 fingerprint identifies the exact version that was signed. Anyone involved in the claim can check the document at /verify, free, without a KuduDoc account — so "which version did the client actually sign?" stops being an argument.
Yes. The client gets a link, opens the document in their browser, and signs where you placed the fields — phone, tablet or laptop, no app to install and nothing to print or scan. If they stall, KuduDoc sends the reminders so you don't have to make the awkward follow-up call.
Not through KuduDoc yet. ID-document capture, liveness detection and a Home Affairs lookup are in build and not live, so nothing on a KuduDoc document today tells you the signer's identity was checked. What you get is the signing record — link, device, times, hash-chained — and a sealed document whose contents can be proved. On a large sum assured, do the identity check the way your compliance framework already requires. Where identity verification is headed.
5 documents a month are free, forever, no credit card — enough for the occasional mandate. Writing business every week? Personal raises that to 10 a month and costs R79/month including VAT for a household of five — that is the annual rate, and month-to-month costs more. Professional adds team seats and unlimited sends; its seat rate is on the full pricing page. Either way, documents you've already sent are never affected by a plan change.
The next policy shouldn't wait for the post.
Personal plan available · South Africa · POPIA-minded
Also see: Suretyships · Compliance certificates · Accountants & tax practitioners