A link is the most fragile part of any message you send. It breaks quietly, and the person on the other end almost never tells you.
"See attached" is the smallest sentence in business writing and one of the least reliable.
Everything you care about is inside the file. Whether that file opens and gets read is decided by a handful of things you never checked.
The request-access screen eats your thread
A link that opens for you is not automatically a link that opens for them, and they will not tell you when it fails.
Picture their side of it. They click and land on a screen asking them to request access. Now they have a small decision: ask you for permission and look like they are making a fuss about a document, or close the tab and get on with their morning.
Plenty of people close the tab. Your thread goes quiet, and you conclude they were not interested, which is the wrong lesson drawn from the wrong evidence.
Asking costs them more than it looks like from your side. They have to admit they could not open it and imply you made a mistake. Two small social debts for one document, payable to someone who is probably senior to them.
Three checks before you paste anything:
- Open the link in a private window and look at what a stranger sees.
- Confirm it works for people outside your company, if any of them are on the thread.
- Confirm it does not expire before the thread does.
Ten seconds of work, and it prevents more silent failures than anything else here.
To someone outside your company, a link into your drive is a locked door with your name on it, and their access request lands in a queue nobody watches.
Expiring links are the quiet version of the same failure. They work perfectly on the day you send them and fail three weeks later, which is exactly when a busy person finally reaches your message. If the document still matters next month, do not send something that will not survive the wait.
Name it so a broken link is recoverable
Say what the document is, in the reader's own words, so they can find it when the URL fails them.
A bare URL carries no information. Once it breaks, the reader is left with nothing: no title to search and no owner to ask.
"The migration doc, tab two, owned by Priya" survives a dead link completely. They can search for it, or they can ask her.
Name it the way the reader would name it. "Q3-final-FINAL-v2" is your filing system talking.
Two words about length
Two words about length remove the main reason people put a document off.
The thing behind a link has an unknown size, and unknown sizes get deferred to a calmer moment that never arrives. Nobody can tell from a URL whether they are opening one page or forty.
"Two pages" fixes that. So does "only the first section matters", which is better still, because it converts an open-ended commitment into a small one.
Deep-link to the section while you are at it, so they land on the paragraph instead of the front door of a forty-page file. And put the link after your ask, since a link placed early is an exit from the message you just spent time writing.
What survives a forward
Text survives a forward. Attachments frequently do not.
This is the part people underestimate. Your message gets forwarded, quoted into a channel, pasted into a ticket, read by people you have never met. The words travel through all of that intact. The file does not, and it fails in three ordinary ways:
- Stripped by a mail rule before it ever reaches the second reader.
- Renamed by a phone into something nobody recognizes.
- Left behind entirely when somebody copies out the useful paragraph and pastes it elsewhere.
So anything a reader would be annoyed to have missed belongs in the body, where it can travel: the number, the date, the owner's name. If it exists only in the file, it exists conditionally.
Quote the paragraph, link the rest
Pull the one passage the reader needs into the message, and put the source underneath it.
This is how long documents become usable. The reader gets the substance immediately and the depth on request, so your ask stops depending on their curiosity or their calendar.
That turns the link into a receipt: proof that the thing you just quoted is real and checkable by anyone who cares to look, rather than a homework assignment.
The support version of the same lesson
When somebody asks a question, the answer goes in the reply, even when a perfectly good page already exists.
People ask what happens to the text they type when they use Unvent. There is a page that answers it properly. The link alone leaves the question open. Writing "your draft is not stored anywhere" in the reply closes it, and the link sits underneath as the checkable version for anyone who wants to verify me.
A link on its own reads as a brush-off even when you meant it helpfully. You know the page answers them. They see a busy person handing them a task.
I once answered a question with a link to the page instead of the sentence written on it. The thread stopped there. I do not think they were annoyed. I think they were finished with me.
What you are actually deciding
Every time you attach instead of write, you are choosing your convenience over theirs.
Sometimes that is correct. You have twelve of these to send and they have one to read, and summarizing twelve documents is real work you may genuinely not have time for. Make the trade knowingly rather than by habit, because the cost lands on the reply you were hoping for.
One test before you send. Mail the thing to yourself, open it, and delete the attachment. Read what is left. If a colleague could still act on it, the message is doing its own work. If it collapses into a covering note, the document was carrying the message rather than supporting it, and you will not find that out from the silence.
Make the message carry itself
Unvent rewrites what you are typing, in place, in the tone you pick, so the few lines that have to work without an attachment come out clear the first time. The document then supports the point instead of hiding it.
Add Unvent to Chrome