How do I collect an ID copy or insurance certificate alongside a signed form instead of chasing a second email?

This page may contain affiliate links from which Blur Studio earns commissions.

Splitting a signature and a required attachment into two separate requests is how businesses end up with half their contractors or vendors signed but missing proof of insurance, a licence copy, or whatever supporting document the signature was supposed to come with. The signing feels complete because the document got signed, and the missing attachment quietly becomes someone's problem to chase down later, usually right when it actually matters.

The no-tool way first

For a one-off, low-stakes request, asking someone to reply to an email with the document attached is fine, and it's not worth setting anything up for something that happens once. The volume problem shows up when you're regularly onboarding contractors, vendors, or tenants who each need to provide the same handful of supporting documents alongside a signature, and tracking who's sent what becomes its own spreadsheet, with columns for "agreement sent," "agreement signed," "certificate requested," and "certificate received," each one a separate thing someone has to remember to update. The same gap shows up with staff paperwork, covered in stopping employees sending incomplete onboarding forms.

Options, from least to most effort

Paper, by hand. Fine if you're meeting the person and can physically photocopy their licence or certificate on the spot.

Signeasy. Signeasy is an e-signature and contract platform built with mobile-first signing in mind. Confirmed live on its pricing page: Personal runs $10 a month ($120 a year annually) for 5 documents a month with 1 user, Business runs $20 a user per month ($240 a year annually) for unlimited sends with team templates.

Jotform Sign. Jotform Sign is part of Jotform's broader form-building platform, which makes it a natural fit here since Jotform's core product is already built around collecting file uploads alongside form fields. Confirmed live on Jotform's pricing page: Starter is free for 10 signed documents a month, Bronze runs $39 a month for 100, Silver runs $49 a month for 250, and Gold runs $129 a month for 1,000. A longer comparison is in Jotform Sign vs DocuSign.

DocuSeal. DocuSeal is an open-source e-signature platform, self-hosted free or hosted in the cloud. Confirmed live on its pricing page: Basic is free for 10 signature request emails a month, Pro runs $20 a user per month ($200 a year annually).

QuickSigner. QuickSigner, an e-signature platform for signing PDFs and Word documents from any device, supports an attachment field alongside signature, date, text, checkbox and stamp fields, confirmed live on its site, with fields pre-assignable to each signer. Its Free plan, confirmed on its pricing page, includes signature and stamp fields; text and date fields require a paid plan, and Business runs $5 a month per user (or $48 a year annually) with unlimited documents and 10 MB files.

The actual steps

1. List the papers needed with each form. Licence, insurance certificate, ID copy, whatever's actually required for that specific document type.
2. Add an upload field next to the signature. Same request, same step, not a follow-up email.
3. Send a test. Confirm the upload field actually works and that the file type you expect (usually a photo or PDF) is accepted.
4. Check the upload by eye. The tool collects the file, it doesn't verify it's genuine or current, so someone on your end still needs to actually look at it.

When to skip the tool

An upload field is not identity or document verification. It collects whatever file the signer chooses to attach, it doesn't check that a licence is real, unexpired, or actually belongs to the person signing. If you need genuine identity verification, confirming the person signing is who they claim to be, that's a different capability, and it's worth checking directly whether your chosen tool offers it as a distinct feature (QuickSigner's Professional plan adds OTP phone verification, for example, which is a step up but still not full identity verification) rather than assuming an upload field covers that need. For most small businesses, a human actually looking at the uploaded document and comparing it against what's expected, a licence number, an expiration date, a named insured matching the actual contractor, is still the real verification step, software or not.

A worked example

Say you're a property manager onboarding a new maintenance contractor who needs to provide a signed service agreement plus a current certificate of insurance before they can be dispatched to any property. If these go out as two separate requests, the agreement comes back signed within a day, and the insurance certificate request sits unanswered because, from the contractor's side, the urgent-feeling part (the agreement, tied to getting paid work) is already done. Weeks later you discover the contractor's been dispatched to three jobs without ever actually sending the certificate, because nobody cross-checked the two separate threads against each other. Combining both into one form, with the attachment field required before the signature can even be completed, closes this gap structurally: there's no way to finish signing without the certificate already attached, so the contractor can't be marked "done" until both pieces are actually there. If the contractor is standing on site, signing on a phone without an app keeps it quick.

The part everyone glosses over

I see businesses treat "they uploaded a certificate" as equivalent to "they have active insurance," when all that's actually confirmed is that a file was attached. Insurance certificates expire, and a certificate uploaded once at onboarding can be months or years out of date by the time it actually matters, on the day of a claim or an incident. If this is a real risk for your business, set a calendar reminder to request a fresh certificate periodically, rather than treating a document collected once as permanently valid. The signing tool solves the collection problem. It does nothing for the expiration problem, and conflating the two is a genuinely common and costly mistake. I'd build this as a simple recurring habit tied to your existing contractor or vendor list, a quarterly or annual pass checking expiration dates, rather than trusting it to come up naturally whenever someone happens to think of it.

Who this matters most for

This pattern shows up hardest for businesses managing recurring relationships with outside vendors: property managers with contractors, agencies with freelance subcontractors, any business that hires out specialized work regularly. A one-off purchase rarely needs this level of document discipline. A standing relationship where someone's going to be back on your property or in your systems repeatedly absolutely does, because the cost of a lapsed insurance certificate or an expired licence isn't theoretical, it's the exact situation that turns an ordinary incident into a real liability problem for you specifically.

How I'd approach this

Combining the signature and the required attachment into one step fixes the most common failure, a signed document with a missing follow-up document nobody tracked down. The part worth building real process around is making sure time-sensitive documents, insurance certificates especially, get refreshed on a schedule rather than collected once and forgotten. Get in touch if you want a system that actually flags expiring documents rather than relying on someone remembering to check.