Should a Proposal Link Have an Expiry Date?

Two different things get called expiry and they should almost never be the same setting. One is a commercial term — this price is good until the end of the month. The other is a technical control — this URL stops working on a date. Confusing them is how a deal dies at an error page.

The failure mode, stated first

You send a proposal on the first of the month with a fourteen-day expiry, because fourteen days feels like a reasonable amount of time to make a decision.

What actually happens: your contact reads it, likes it, and sends it to their director, who is away. It comes back, goes to legal for a look at the terms, and reappears on someone’s desk five weeks later. That person clicks your link and gets an error. They do not email you about it, because from where they are sitting the supplier’s document is broken, which is a small data point about the supplier. They ask your contact, who has to come back to you, and the momentum you spent three weeks building is now a favour someone has to do.

The structural problem is that an expiry date does not choose who it stops. The reader it stops is disproportionately the one who arrived late through an internal chain — which is to say the most senior person, and the one with the authority to say yes. It is the same asymmetry that makes a view cap dangerous, and it is set out at length in what a forwarded link can and cannot tell you.

What the reader actually sees

Worth knowing precisely, because it is the experience you are choosing on their behalf. In Quixli, a reader who follows a link that has ended gets a short page headed “Link Expired”, telling them the link has expired or is no longer available, and inviting them to contact the person who shared it. A link that has hit its view cap gets its own page — “View Limit Reached” — rather than being folded into the same message, because those are different problems and the reader deserves to know which one they have.

Note what is not on either page: a way in. There is deliberately no request-access button, no “ask the owner” form, nothing that puts the reader into a queue. Ending access means ended, and the only route back is a human one. That is the right design — a self-service door into a withdrawn document is not a withdrawn document — and it is also the reason a mistimed expiry is expensive. The recovery path runs through your contact’s goodwill.

A reader who is already reading when access ends is treated more gently: the document stays on screen and an amber banner appears saying access has ended and what is shown is no longer being updated. Nobody has a document snatched out of their hands mid-sentence.

When an expiry date is the right call

It is not never. There are four situations where it clearly earns its place:

• The document contains something that should not outlive the deal. Named day rates, margins, third-party pricing, a client’s data used as an example. A URL is forever unless you make it not be, and “forever” includes after the relationship ends.

• It is going somewhere you do not control. A shared inbox, a distribution list, a portal, a consultant who will not be there next quarter. The link outlives the person you sent it to.

• You are under an obligation. An NDA, a data-processing agreement or a client policy that says material is available for a defined period. Then the date is not your choice and you set it exactly.

• The document is genuinely time-boxed. A tender response, an availability hold, a slot in a schedule that really does disappear. Here the expiry is honest, and it should also be written in the document so nobody meets it as a surprise.

When it is the wrong call

For an ordinary proposal to an ordinary client, with an ordinary decision cycle you cannot see into: leave it open, and close it deliberately when you know something.

That is the argument in one line. You are trading a small, speculative confidentiality benefit against a specific, plausible way of losing a deal you had already won, and the trade is bad.

If you do set one, three rules make it much less likely to hurt you:

1. Set it well past your decision cycle, not on it. Take the longest your last five deals took, and then choose something comfortably beyond it. The date exists to stop the document being readable years from now, not to create urgency.

2. Write the date inside the document. A reader who can see “available until 30 November” at the top has been told. A reader who meets a dead link has been rebuffed.

3. Check the activity before it lands. If the document is still being opened, the expiry is about to cut off a live conversation. That is precisely the information a tracked link gives you and a file on a disk never can.

Expiry as urgency is a bad trade

The temptation to use a short expiry as a deadline device is understandable and it is answering the right problem with the wrong instrument.

Urgency in a proposal has to be legible and it has to be true. A sentence — “we can hold this rate and a September start until the 12th” — is legible, true, and something the reader can act on or negotiate. A link that stops working is neither: it does not communicate a deadline, it enforces one nobody was told about, and it is indistinguishable from your website being broken.

A deadline the reader can read is a commercial device. A deadline the reader discovers by being locked out is an outage with a story attached.

The better instrument: ending access deliberately

An expiry date is a decision made in advance, in ignorance, by someone who does not know how the deal will go. Ending access is a decision made later, with information.

Every Quixli share link can carry a pincode, an end date or a cap on how many times it can be opened, and access to any of them can be ended at any point. The last of those is the one worth defaulting to. When the deal closes, when it is lost, when the engagement ends — those are the moments when the document should stop being reachable, and all three are moments you will know about.

You also have something an expiry date cannot use: whether anyone is still reading. A document nobody has opened in two months can be closed with no risk. A document that was opened yesterday should not be, whatever the calendar says.

The related control is the PIN, which has a similar shape of cost — whether to password-protect a document you send works through it. For the commercial version of expiry, where pricing goes in a proposal has where a validity date belongs. And the full set of controls a share link can carry is documented, including which kinds of share support which.