How to Know If a Client Read Your Proposal
Four methods, ranked by what actually works, and why an emailed PDF gives you nothing at all.
By Carlos Soto · Published 2026-09-10 · Updated 2026-09-14
Send the proposal as a tracked link instead of an email attachment. A tracking tool then shows when the client opened it, how long they spent, which pages they read, whether they reached pricing, and how many times they came back. An emailed PDF shows none of this: once sent, it is a file on someone else's computer.
Everything else is guesswork, and most of it is worse guesswork than people realize.
Four ways to know if a client read your proposal, ranked
1. Tracked proposal links
You upload the proposal and share a link instead of the file. When the client opens it, the page loads from your tracker, which records the session.
What you get: the moment it was opened, total time spent, time per page, return visits, and whether they reached pricing. Some tools notify you in real time.
What you do not get: certainty about who is behind the click if the link circulates. A tool can tell you a link was opened by a second distinct browser, a strong hint it was forwarded, but not who that second reader was. Good tools are upfront about that limit instead of dressing an inference up as a fact.
This is the only method that tells you what was actually read rather than what was received.
A tracked link shows what was read, page by page. Sample data.
2. Email open tracking
A pixel embedded in the email fires when the message renders. Mailtrack, Streak, HubSpot and Yesware all work this way.
The problem is that it tracks the email, not the proposal. A client can open your message, see the attachment, and never open it. You get a green tick and learn nothing about the document itself.
It also breaks constantly. Apple Mail Privacy Protection downloads remote content in the background whether or not the message is ever read, so it reports opens that never happened. Gmail and Outlook block remote images by default for many users, so real opens go unrecorded. Corporate security scanners open every message on arrival, hours before a person does.
Useful as a rough signal that your email did not bounce. Not a read receipt for a proposal. See proposal tracking vs email open tracking for the full case.
3. Read receipts
Outlook and some Gmail accounts can request a read receipt. The recipient gets a prompt asking whether to send one.
Most people decline. Many mail clients suppress the prompt before the recipient ever sees it. And even a returned receipt only confirms the email was opened, not the attachment.
4. Analytics built into a proposal builder
If you build the proposal inside Proposify, PandaDoc or Qwilr, tracking comes with it. This works well, and it is the right answer if you also want templates, an editor and e-signatures in one place. The Proposify alternative comparison covers that trade-off in full.
The catch is that you have to build the proposal in their editor. If your proposals live in Figma, Canva, Google Docs or a designed InDesign PDF, moving them is real work for a small answer.
Can you tell if someone read a PDF you emailed?
No. Once a PDF leaves your outbox as an attachment, it is a file on someone else's computer. There is no callback, no receipt, no open event. Nothing you embed in a standard PDF changes this reliably: a remote image meant to "phone home" on open is blocked by Adobe Reader and most modern viewers by default.
If you need to know whether a PDF was read, you have to change how you deliver it, not what is inside it: serve it as a link rather than an attachment.
What the signals mean once a client has read your proposal
Knowing it was opened is the boring part. The useful information is in the pattern.
Opened once, under 30 seconds. They skimmed for the price and stopped. Usually a budget mismatch, occasionally a bad first page.
Opened once, several minutes, reached the end. Genuine consideration. This is your best follow-up window and it closes fast.
Opened, then opened again a couple of days later. Someone is thinking about it, or has shown it to a colleague. A return visit is one of the strongest positive signals you get without the client saying anything, since nobody reopens a proposal they have mentally rejected. See what it means when a client opens your proposal multiple times.
A link you sent to one person turns into two or three distinct readers. Often the proposal is being circulated internally. Ask who else is involved in the decision, and you will usually be right, though the same person on a second device or a cleared browser looks identical, so treat it as a strong hint rather than a fact.
Long time on the pricing page. They are working out whether they can afford it or comparing you to a quote. Follow up with payment terms or scope options rather than more features. See what a long time on your pricing page means.
Never opened after four days. Not a rejection. Most commonly the email got buried. Resend with a different subject line before you assume anything. See how long to wait after sending a proposal for the fuller timing case.
Opened repeatedly but no reply. Interest without authority, usually. Your contact likes it and cannot approve it alone.
Should you tell the client you can see they read it?
It is your call, and Closewatch leaves it to you: the viewer shows the proposal and nothing else. If you want to be upfront, one sentence in the covering email does it, such as "I use a tool that lets me see when this has been opened."
The case for saying so holds whatever tool you use. Tracked document links are standard practice in sales and have been for a decade. Nothing about a view count is private to the recipient in the way message content would be. But recipients increasingly notice, and being upfront about it costs nothing. It also changes the conversation for the better: "let me know if the pricing page needs work" is a conversation you would have had anyway, just from the other end.
How Closewatch tells a real read from a scanner
Ask this of any tool before you trust its numbers, because it is the difference between real data and a dashboard that flatters you. Corporate email security gateways open links automatically to scan them for threats, and an unfiltered tool will report that scan as your client opening the proposal.
Closewatch filters two ways: known bots and link-preview fetchers are excluded outright, and a visit only counts once it has held three seconds of visible attention on the page, the line between something fetching a page and someone reading it. Everything on the dashboard is built from qualified reads only.
How to set this up with Closewatch
- Make the proposal however you already make it: Google Docs, Figma, Canva, Word, InDesign, whatever produces a PDF.
- Upload that PDF to Closewatch.
- Send the Closewatch link in place of the attachment.
- Get notified when it opens.
- Check page-level engagement before you follow up.
Closewatch is $19 a month, flat, with no per-seat pricing, and does not require rebuilding the proposal in a new editor. Two proposals can be live and read at once on the free plan, with all the tracking and an email on first open; Solo adds emails when a client comes back, a new reader opens it, or it turns hot. If you want the proposal builder as well as the tracking, Proposify or PandaDoc will suit you better, and both start around $19 per user per month. See pricing for the full breakdown.
Frequently asked questions
How long should I wait before following up on a proposal?
Three to five business days if it has been opened, sooner if you see a return visit, since that is when the client is actively thinking about it. If it has not been opened after four days, resend rather than chase: the most likely explanation is that the email got buried, not that the client isn't interested.
Does email open tracking tell me if they read the proposal?
No. It tells you the email was rendered, which is a different event. Apple Mail Privacy Protection reports opens that never happened, image blocking hides opens that did, and corporate scanners open everything automatically. It is a weak signal about the message and no signal at all about the document.
Can I track a proposal without the client creating an account?
Yes. On Closewatch the link opens like any other web page: no account, no plugin, no app on the recipient's side. As far as they are concerned, you sent them a document.
What if the client forwards my proposal to someone else?
Closewatch counts distinct readers on each link: a browser that has not opened it before, marked the first time it does. So the dashboard reports "opened by a second reader" rather than claiming a forward outright, because that is what was actually observed. You know who you sent the link to and the tool does not, so the inference is yours to make, but when one link turns into three readers in an afternoon, it usually went round the room. See how to tell if a client forwarded your proposal for how to read the pattern.
Is it worth paying for proposal tracking if I only send a few proposals a month?
If a single proposal is worth more than a few hundred dollars, knowing whether it was read changes when and how you follow up, and that changes close rates. Below that value, and at high volume with small deal sizes, the honest answer is probably not.
How do I ask a client about a proposal's status?
Ask a specific question instead of asking for a status. "Is the scope in section 2 roughly what you had in mind?" gets an answer, and "any update?" gets put off. If you know they have read it, ask about the decision instead: who else needs to see it, or when they expect to decide.
New to proposal tracking? Start with what proposal tracking is and how it works, or try the proposal tracking demo on yourself: read a sample proposal, then see the report your reading produced.