Proposal Tracking: Know When Clients Open It

Send a proposal and know when it was opened

Do not treat a proposal as a file that disappears into an inbox. Send it as a tracked browser link, a link that records each visit. The client gets a normal page. You get access and engagement data that an attachment cannot give you, for example who opened the proposal and what they read.

Instead of the question “Did they see it?”, you can ask better questions:

• Access: Did someone open the proposal?
• Identity: Which verified visitor opened it?
• Interest: What did that person view, and for how long?
• Timing: Is this a sensible time to follow up?

This guide covers these topics:

• Which tools to use
• How to set up access so that the data means something
• How to read a “proposal viewed” notification
• How to turn activity into a useful follow-up

Why a tracking link beats an attachment

After a PDF attachment arrives, you learn almost nothing. Email open tracking is also unreliable. For example, Apple’s Mail Privacy Protection prevents senders from seeing whether you opened their email. A visit to a document link is different, because someone must reach the page.

Approach	What you can learn	Main limitation
PDF attachment	Delivery or bounce status	No dependable reading activity
Email open tracking	Sometimes an “opened” flag	Privacy features in mail apps can hide real opens
Public document link	Visits and time on pages	You cannot say who visited
Password-protected link	Activity behind a gate	A shared password does not identify a person
Email-verified link	Who entered, when, and what they viewed	Adds a small step for the client

Choose a proposal tracking tool

Tool	What it records	Notes
DocSend	Each visit, the percentage of the document viewed and time spent	Email verification is on the Advanced, Advanced Data Rooms and Enterprise plans
Papermark	Viewer email, country, time spent and seconds on each page	Link settings include email verification, allow lists and view notifications
PandaDoc	Per recipient: views, last view, total time, PDF downloads and link clicks	Built for proposals and e-signature. An edit to a sent document removes its old analytics
Cloudflare Pages with Cloudflare Access	Who signed in, when and from which country	A self-hosted option. It logs sign-ins, not pages read

For most freelancers and small teams, a document-sharing tool (DocSend or Papermark) is the quickest start. If you also need pricing tables and signatures in the same document, choose PandaDoc or similar proposal software. If the proposal includes a live demo or must be on your own domain, choose the self-hosted route. Our Cloudflare Pages access guide shows the setup.

Choose access that matches the claim you want to make

“Someone opened it” and “Morgan at Acme opened it” are different claims. The access rule decides which one you can make.

Access rule	Best use	What you know	Identity limit
Public link	Low-risk decks and broad sharing	The link received visits	You cannot say who visited
Password	Confidential work for a known group	Someone with the password entered	Someone can share the password
Email required	Light identification	The email address the visitor typed	Anyone can type any address
Email verified	Proposals that need named engagement	The verified email and its activity	It proves inbox access, not who is at the keyboard

If you want named activity, use email verification. Add the address of each stakeholder (or the domain of the client) to an allow list. An allow list is the list of addresses that can enter. For four buyers, four identified visitor records are better than one shared password.

Be honest in the notes in your CRM, the system that holds your customer records. A public visit is traffic. A password visit is protected traffic. A verified-email visit is identified activity.

How to send a tracked proposal, step by step

This walkthrough uses DocSend. Papermark has equivalent settings.

1. Prepare the client package. Export the proposal as a PDF with a clear file name. Remove drafts, comments, hidden pricing tabs, and private notes. Make sure that every link inside works.
2. Upload the PDF to your DocSend Content library.
3. Create the link. If your plan includes it, choose Verify email to view under Viewing requirements. If not, choose Require an email to view (DocSend link settings).
4. Limit who can enter. Use Allow or block viewers by email to allow the addresses or the company domain of the client. If you want a second factor (a second proof of access) for the whole group, add password protection. If not, leave it off.
5. Decide on downloads and expiry. If you need page-level data, turn off Allow downloads. If the offer has a deadline, use Set an expiration date.
6. Turn on visit alerts. Open Settings > Notifications. Turn on As Visits Occur. If you prefer one summary a day, choose Daily Digest instead (DocSend notification settings).
7. Test the link. Open it in a private window. Examine the email step, the title, the mobile layout, and every link.
8. Send a short email. Say what the proposal covers, which decision you need, and when you will talk next. Mention the link calmly: I shared this through a secure link. The link will ask you to confirm your email.

In Papermark, the same setup is a link with email verification, an allow list, downloads off, and notifications on (Papermark link settings). In PandaDoc, open the sent document. Open the menu next to a recipient. Select Recipient analytics to see the activity of that recipient.

What a proposal viewed notification actually tells you

A proposal viewed notification tells you that the tool recorded a visit. It does not prove agreement or budget approval. It also does not prove that the client read the full proposal. Treat it as a reason to look at the evidence before you write.

For example, a DocSend “As Visits Occur” alert includes the device and the approximate location of the visitor. It also includes the percentage of the document viewed and the time spent. The visit can still be in progress when the email arrives. So read the final numbers in the Content section of the document.

Review the activity in layers:

• Entry: The visitor opened the link at a recorded time.
• Identity: With email verification, the record includes the verified address.
• Depth: Page data shows whether the visit stopped at the cover or reached scope and pricing.
• Action: A download or a click on a linked demo suggests a next step.
• Return: A second visit can mean review, internal discussion, or a recheck.
• Response: A reply or a question shows direct intent. It counts for more than any behavioral guess.

One visit shows awareness. A pricing-page view plus a download is stronger. A written question is stronger still.

Use engagement data for follow-up timing

No single response time fits every client. A notification is an opportunity, not a command to call. Match the follow-up to the strength of the signal and the relationship.

Signal	Sensible timing	Useful message
One brief visit	Next business day	“Did the link work? What can I clarify?”
Scope and pricing viewed	Same business day	“I can walk through the scope options if that helps.”
Proposal downloaded	Within a few business hours	“I am available for questions about the timeline or the terms.”
Several verified stakeholders visit	Same day, or before the planned decision meeting	“Can a 20-minute group Q&A help your review?”
Client sends a question	As soon as practical	Answer the question. Skip the generic check-in
No activity by the agreed date	On that date	Ask if the proposal arrived and if the review schedule changed

Keep the tone human. I wanted to make myself available while the proposal is under review works. I saw you spent 6 minutes on page 11 does not.

Before any follow-up, ask three questions:

1. Do you know who the visitor is? Anonymous public traffic or a shared password is weak evidence about a specific person.
2. Did the visitor take a meaningful action? A return visit, a pricing view, a download, or a question counts for more than the notification alone.
3. Does the activity fit the agreed timeline? If the client said that the team decides on Friday, a Tuesday visit rarely justifies an urgent call.

Then write the message around the proposal, not the tracking. Refer to the decision, the assumption, or the next step that helps the client move forward. Our guide on following up after sending a proposal has more wording examples.

Four examples: know when the client opens the proposal

These are composite examples (combined from several cases), not claims about named customers.

1. An independent consultant sends a 16-page strategy proposal. A visitor opens it through a verified work email. The visitor reaches pricing and downloads the scope. So the consultant follows up that afternoon with two meeting times. The consultant also offers to compare the two service options.
2. A design agency shares a proposal, and three allowed client addresses visit it over two days. One visitor spends time on the portfolio, and another visitor opens the timeline again. The procurement contact downloads the terms. This activity shows the buying group. So the agency offers one group Q&A instead of three separate nudges.
3. A startup founder sends a public deck link to one investor, and the link records 27 visits. Forwarding, link previews, and repeat visits can all add to this number. So the founder does not claim that the investor opened it. The next sensitive deck uses email verification.
4. A client of a freelance developer opens the proposal. The client replies and asks for a smaller first phase. The freelancer replaces the PDF behind the same link, so nobody reviews an old version. The freelancer also answers the real objection: project size.

Use identity, depth, action, and direct response together. Never turn a weak signal into a confident story.

Common pitfalls, privacy and identity limits

Tracking backfires when it creates false certainty or unease. Keep it transparent and restrained, and tie it to a business purpose.

Pitfall	Why it fails	Better practice
Naming a visitor from a public link	Public traffic is anonymous	Record the visit without assigning identity
Treating a password as identity	Shared credentials travel	Use email verification for each stakeholder
Calling after every alert	The client can feel watched	Look at the activity and the agreed timeline first
Counting every visit as interest	Previews and repeat visits inflate totals	Look at per-visitor records and actions
Hiding the tracking	Surprise damages trust	Say that the link is secure and that the tool records visits
Uploading internal notes	Shared files expose them	Review the file before you create the link

Collect only the data that you need. Limit who in your team can see it. Follow the privacy rules that apply to you and your client. For regulated or highly sensitive proposals, make sure that you know the contractual, security, and retention requirements before you share.

Keep one proposal link current

Keep the tracked proposal useful after the first visit. In DocSend, select Replace on the file in the Content library. Existing links then show the new version. But DocSend does not tell visitors that the file changed, so mention the change in your next message (update content in DocSend).

In PandaDoc, an edit to a sent document removes its old analytics. If you want to keep the history, duplicate the document. Then send the new version.

One current link and one place to respond are better than a chain of attachments named final, final-2, and final-revised.

Final thoughts

Send the proposal as a link, with an access rule that matches the claim that you need to make. Public and password-only links can show activity, but they cannot reliably name the person. Email verification gives a stronger identity signal.

Remember these points:

• Treat a proposal viewed notification as a clue, not a verdict.
• Combine identity with page data, downloads, return visits and direct replies.
• Follow up according to the strength of the signal and the schedule of the client.
• Keep revisions at the same link so that nobody reviews an old file.

If you do it well, proposal tracking removes guesswork, and the client does not feel watched. You know when the client opens the proposal, and you have a clear, useful reason to follow up.

Free email addresses
for your AI agents

Each agent gets an address like myagent.x7k2@revdokumail.com. It can receive emails, send replies and store files.

• 3 free mailboxes, each with its own address
• 3,000 incoming and 500 sent emails a month
• 3 GB of storage for attachments and files
• Virus, malware, spam and prompt-injection filter
• Read and reply through API, MCP or CLI

Create free mailbox

You do not need a card.