How-to

How to Tell If a Client Actually Read Your Proposal

Short of asking, the most reliable way to tell if a client actually read your proposal is to send it through a tool that tracks opens, total time spent, and which pages got attention — a single 5-second open is a glance, not a read, while several opens with real time on the pricing page is someone seriously considering it. Without that, you're reading silence, which is a weak signal either way.

The soft signals, if you're not tracking opens

Even without a tracking tool, a few things are worth watching before assuming silence means "no": a reply with a specific question about something in the document is a strong signal they read it closely; a request to hop on a call shortly after you sent it usually means they got far enough to want to talk; and a client who's normally responsive going quiet for longer than their usual pattern is worth a check-in, not necessarily a bad sign on its own. None of these are as reliable as actually knowing whether the document was opened, though — they're inference, not evidence.

The reliable way: read the actual open data

1. Send it through a tool that tracks opens. A PDF attached to an email gives you nothing once it leaves your outbox — no confirmation it was opened, let alone read. Sending it as a link through an e-signature or proposal tool is what makes any of the rest of this possible.
2. Check status before assuming anything. Before reading three days of silence as disinterest, check whether the document has even been opened — a surprising number of "ignored" proposals are actually just an unread email.
3. Look at open count and total time, not just "viewed." "Viewed" alone doesn't distinguish a 5-second glance from a real read. A single short open often means someone confirmed it arrived and meant to come back to it; multiple opens adding up to several minutes is a much stronger sign they're actually evaluating it.
4. Check which pages actually got attention. Page-level time is the most useful detail here — a client who spent most of their time on the pricing page is thinking about cost, not scope, and that should shape what you say in a follow-up far more than a generic "just checking in."
5. Time your follow-up off what you actually saw. Once you can see it's been read, a specific follow-up ("wanted to check if the pricing on page 2 works, happy to talk through options") lands better than a reminder sent on a guess, and it beats waiting on silence you can't actually interpret.

What this looks like in DocuAgree

Every document you send shows each signer's status — sent, viewed, or signed — and, once they've opened it, an Engagement panel with how many times they opened it, when they first (and last) opened it, total time spent, and a page-by-page breakdown of where that time went. It's automatic — nothing to turn on, no separate tracking pixel to configure.

Common mistakes

• Reading one quick open as a bad sign. A short first open is often just someone confirming it landed, intending to sit down with it properly later — don't write off a deal after a single 5-second view.
• Following up before checking status at all. A "just checking in" sent to someone who hasn't even opened the document yet is a wasted message — check first.
• Ignoring page-level detail. Total time tells you whether they read it; per-page time tells you what to say next. Skipping the second part means a generic follow-up when a specific one would land better.