You email a contract as a PDF attachment, and then what. You wait. You check your inbox more often than you should. Three days later you send a polite "just following up" message, and the client says they meant to sign it but got busy, and now you are starting the project anyway because you need the work to begin, with a signature that may or may not ever actually arrive. This is not a rare failure, it is the default outcome of sending a document that has no built-in way to tell either of you where things stand.
Here is why email-attachment contracts create this exact stall, and why a signing link the client completes directly in the browser removes most of the friction that causes clients to set a contract aside in the first place.
A PDF attachment adds five steps between "sent" and "signed"
Once you attach a contract to an email, the client has to download it, open it, find a way to sign it (print and scan, or hunt for a PDF annotation tool they may not have used before), and email the signed copy back. Every one of those steps is a place the process can stall, and on a phone, several of them are genuinely awkward to do at all. None of this requires the client to be careless, the format itself is simply heavier than it needs to be for something as routine as putting a signature on a document.
This is what actually causes the "meant to sign it but got busy" response: not indifference, but a task that takes more effort to complete than it looks like it should, so it keeps losing to whatever is more urgent that day.
A signing link removes most of those steps at once
When a contract is sent as a link the client opens and signs directly in the browser, there is no attachment to download, no printer or scanner needed, and no separate app or account to set up first, the client reviews the agreement and signs right there on whatever device they already have open. Fewer steps between opening the link and finishing it means fewer places for the client to set it aside and forget, which is most of what actually causes the stall in the first place.
See the free freelance contract template generator for a starting point if you are still sending a static PDF today, and the guide on the freelance contract guide for India for the baseline clauses a contract needs before it ever gets to the signing step.
A polite follow-up still works better than silence
Removing friction from the signing process does not remove the need to follow up entirely, some clients need a nudge regardless of how easy the document is to sign. A short, direct message a few days after sending, "just checking you got the contract, happy to answer anything before you sign," reads as helpful rather than pushy, and works better than a vague "any update?" that puts the burden back on the client to remember what you are even asking about.
Give a specific, reasonable window before following up, a couple of business days for a straightforward contract, longer if you know the client is traveling or mid-launch, so the nudge lands as a normal check-in rather than an anxious one.
Starting work before a signature is a bet you don't need to make
The real cost of the "chasing a signature" problem is not the awkwardness of following up, it is the freelancers who start work anyway because the client is eager and the deadline is real, with no signed agreement covering scope, payment terms, or what happens if the relationship goes wrong. Removing the friction that causes contracts to stall in the first place, and following up promptly when one still does, is what makes it realistic to hold the line on waiting for a signature rather than starting unprotected.
How Rinto handles the signing step
Rinto lets you send contracts for e-signature directly, the client reviews and signs in the browser with no separate app or DocuSign account needed. Signing a contract can also create the linked project automatically with the client's details, scope, and dates already pre-filled from what was agreed, so the signature is not just a formality, it is the step that actually kicks the project off.
Frequently Asked Questions
Why do clients take so long to sign a freelance contract?
Often it is not reluctance, it is friction: a PDF attachment has to be downloaded, printed or digitally annotated, signed, scanned, and emailed back, and that multi-step process is easy to set aside for "later" and then forget. A signing link the client opens and completes directly in the browser removes most of these steps, which is frequently enough on its own to get a contract signed faster without any change in how eager the client actually is.
How do I know if a client has actually opened a contract I sent?
You generally cannot tell with a PDF email attachment, since email read-receipts are unreliable and easy to ignore. A signing link removes most of the ambiguity indirectly: since there is nothing to download or print, a client who intends to sign usually does so in one sitting rather than opening it once and setting it aside, so a follow-up after a couple of business days is a reasonable, low-stakes check-in rather than a guess about whether they even opened it.
Is it risky to start freelance work before the contract is signed?
Yes. Without a signed contract, you have no agreed record of scope, payment terms, or what happens if the client disputes the work or delays payment, which matters most exactly when something does go wrong. The pressure to start early usually comes from the deadline feeling more real than the missing signature, but a deadline does not change what happens if a dispute arises with nothing signed to point to.
How long should I wait before following up on an unsigned contract?
A couple of business days is reasonable for a straightforward contract, longer if you know the client is traveling, mid-launch, or otherwise genuinely busy. Send a short, specific message, "just checking you got the contract, happy to answer anything before you sign," rather than a vague "any update?" which puts the burden back on the client to remember what you are asking about.
Is an e-signature legally valid for a freelance contract in India?
Yes. A standard e-signature is legally valid for ordinary freelance contracts in India, a contract is not unenforceable simply because it was formed and signed electronically. What actually determines whether a contract holds up is its content, clear scope, payment terms, and the other baseline clauses, not the specific method used to sign it.