Should You Send a Proposal as a PDF Attachment or a Link?

This looks like a question about convenience and is really a question about what you are willing to give up. Each option costs you something specific, and the costs are not symmetrical — which is why “whatever the client prefers” is not an answer, it is a way of not having decided.

What an attachment costs you

The moment a PDF leaves your outbox it becomes a file on somebody else’s disk, and four things follow from that.

• No signal, ever, by construction. Not a weak signal — none. It can be opened on a plane, forwarded to three colleagues, printed, annotated and argued over, and nothing about any of that reaches you. It is the only common way of sending work that generates no evidence at all.

• The version is frozen at the worst possible moment. The copy they have is the copy you sent, including the typo, the stale date and the number you changed your mind about an hour later. You cannot fix it; you can only send another file and hope they open the right one.

• It fragments. Three people at the client now have three copies, one of which is v2 and two of which are v1, and the meeting about your proposal is partly a meeting about which file is current.

• It can simply not arrive. Attachment size limits, mail gateways that strip or quarantine files, and spam scoring that treats an unsolicited attachment from a new sender less kindly than a plain message.

What a link costs you

The other side, stated as plainly, because a link is not free either.

• It asks for a click on a URL from someone the reader may not know. Every corporate security awareness programme in the world trains people not to do that. A recognisable sender, a plain-language message and a link that is obviously about the thing you discussed are what get past it.

• It needs connectivity at the moment they want to read. Trains, planes, sites, hospitals, factories. If your buyer reads on a commute, an attachment is genuinely more considerate.

• A process may simply refuse it. Portals want an uploaded file. Some organisations’ record-keeping requires an artefact they hold rather than one you host.

• It can be withdrawn — including by accident. The flip side of control is that an expiry date or a view cap you set and forgot can lock out a reader who was about to say yes.

The trap in sending both

The obvious resolution is to attach the PDF and include the link, and it is usually right. But it has a failure mode that nobody warns you about, and it is worth being deliberate rather than lucky.

If both are present, most readers open the attachment. It is one click closer, it needs no network, and it does not look like it came from the internet. So you have sent both and are now measuring almost nothing, while believing you are measuring something — which is worse than not measuring, because you will read the silence as “not opened” when it means “opened, as a file, invisibly”.

So if you send both, choose which one is the primary and make the message reflect it:

1. Link primary. The link is in the sentence that says what to do next; the PDF is mentioned once, further down, as “a copy for your records if you need one”. Most readers follow the sentence.

2. Attachment primary. Fine, when the situation demands it. But then treat your open data as absent rather than as negative, and go back to asking people — which is a legitimate method and always was.

What the link buys you, concretely

Not “insight” — four specific capabilities that an attachment cannot have, listed so you can decide whether you want them:

• Evidence that it was opened, and by how many people, and for how long. The difference between “they have not looked” and “they looked and are not convinced” is the difference between a nudge and a phone call — every method for answering that, compared.

• One current version. Fix something and the next reader sees the fix. This has a hazard of its own and needs a discipline around it, which is the versioning piece.

• Controls that can be changed after sending. A link can carry a PIN, an end date or a cap on how many times it can be opened, and access can be ended at any point. None of those exists once a file is on a disk.

• A record of who is reading it now. Useful mostly for timing — a document being read at 4pm on a Thursday is a different follow-up from one last opened a fortnight ago.

One thing a link does not buy you, and it is worth saying because it is widely assumed: it does not stop a copy being taken. A reader of a Quixli document can export it as a PDF from the document itself, and from that moment it is a file on a disk exactly like an attachment, with all the same invisibility. Sending a link is a choice about the primary path, not a lock.

When the attachment is simply the right answer

Four cases where you should not fight it:

• A procurement portal that accepts an upload and nothing else.

• A document that exists to be printed and physically signed.

• A reader you know reads offline — the commute, the site visit, the long flight.

• A client whose IT blocks unknown domains, which you find out about the first time and then never forget.

The formal-submission case is its own genre with its own rules, and a link plays a real but different role in it — sending to a procurement process rather than a person covers it.

If you go the link route, the two decisions that follow immediately are whether it should expire and whether it should carry a PIN. Both cost you readers, and both are worth it sometimes. What a Quixli link actually records — and what it deliberately does not — is set out in full.