eSign flows with multiple documents face 3 issues:
- Lack of visibility for the customer - which leads to compliance risk
- Additional tech costs
- Forces you into manual reconciliation - adding operational costs and slowing down TAT
Let’s take an example of a home loan journey
A home loan kit consists of multiple documents - a Sanction Letter, Key Facts Statement (KFS), Loan Agreement, Mortgage Deed, DPN and an Insurance Consent.
With eSign tools, you are forced into:
Option 1Merge all documents into one PDF
The customer gets one eSign link with all the documents merged into a single PDF - with eStamps for each document lumped together at the top of the kit.
This creates 4 issues:
- Customers get a poor experience - which creates legal risk. They get confused and don’t realise they’re eSigning multiple documents. This is also a legal risk: a customer can later say they didn’t know they signed, for example, the Insurance Consent.
- Your KFS isn’t separately acknowledged. RBI’s KFS circular (April 2024) requires the customer to acknowledge the KFS before the Loan Agreement is signed. In a merged PDF, the customer signs once at the end, so there is no separate KFS acknowledgement.
- Manual reconciliation of eStamps. Since eStamps are not tied to the specific document, your team has to spend extra time and effort in checking that the right eStamp is on the right document.
- Sharing one document takes manual work. If you need to send specific pages to a different team, for example the Insurance Consent to the insurance team, you have to extract those pages manually and send them.
The only workaround for this right now is:
Option 2Create multiple workflows, one for each document
In this option you create a unique workflow for each document in the kit. But this creates additional issues:
- Customers get multiple eSign links - which adds to confusion. They may miss links
- You need to spend more time and effort on integrations: Your team needs to build and maintain multiple workflows, adding costs and complexity
Neither setup is how the kit should work. Both cost you: in customer drop-off, in tech effort, in ops time.
Leegality 4.0With Leegality 4.0, you can create a DocPack instead
With DocPacks, you can send multiple separate documents together as a pack — in a single eSign link. Each document still gets its own eSign type, own eStamp, and own configurations.
Signers eSign each document separately, but do it in the same session without leaving the window.
Here’s how it works - for our home loan example above:
With DocPacks you get the best of both worlds, without the issues of either the merged or individual workflow approach:





.avif)
.avif)
