How to share a contract as a link

A link is the best way to let someone read an agreement and the wrong way to record that they agreed to it. Knowing which half you are doing keeps you out of trouble.

A contract link is an agreement published at an address so both parties read the same text, which helps enormously during negotiation and does not by itself record that anyone agreed.

That split is the whole subject. Get it right and links make contracts less painful. Get it wrong and you have an agreement nobody can prove the wording of.

A contract open in a browser. Numbered clauses with a contents list down the side.
A contract open in a browser. Numbered clauses with a contents list down the side.

This guide covers what a link is genuinely good for, how to make long terms readable, and where the fixed signed file has to take over.

Contract negotiation by attachment is miserable in specific ways, and a link removes most of them.

Problem With attachments With a link
Which draft is current Filenames ending in v4-final One address
Reading on a phone Paper-sized, so unreadable Fits the screen
Pointing at clause 7.2 "Page 4, about halfway down" A link straight to it
Both sides looking at once Two copies, maybe different Same page
A clause changes mid-call Resend and reopen Refresh

The third row saves more time than people expect. A clause with an id can be linked directly, so "see 7.2" becomes something the other side can click rather than hunt for.

<section id="c-7-2">
  <h3>7.2 Termination for convenience</h3>
  <p>Either party may terminate on thirty days' written notice.</p>
</section>

Now the address ends in #c-7-2 and lands on that clause. On a long agreement this is the difference between a five-minute call and a twenty-minute one.

A page can be edited. That is its advantage everywhere else in this site and its disqualifying flaw here.

If the only artefact is a page, then a month after signing there is no way to establish what the text said on the day of agreement. Not because anyone acted badly, but because nothing recorded it. The other side's screenshot and yours are equally weak evidence.

So the rule is simple. Negotiate on the link. Sign a file.

Produce the final text as a fixed document, have it signed by whatever method suits the value of the deal, and keep that document. The page carries on being the readable copy, with a line at the top naming the signed version and its date.

Make long terms actually readable

Nobody reads terms that arrive as a wall. Structure is what turns a document people skip into one they skim correctly.

Number every clause and give each a heading in plain words. "Termination for convenience" tells the reader what the clause is for; "Clause 7.2" tells them nothing.

Put a contents list at the top and link it to the clauses. On a phone, make it collapsible so it does not push the actual terms below the fold.

<details open>
  <summary>Contents</summary>
  <ol>
    <li><a href="#c-1">Definitions</a></li>
    <li><a href="#c-2">Scope of work</a></li>
    <li><a href="#c-7">Termination</a></li>
  </ol>
</details>

A details element does this with no JavaScript, which means it still works when the page is printed or saved.

A phone screen opened directly at clause 7.2, the heading at the top of the view.
A phone screen opened directly at clause 7.2, the heading at the top of the view.

Printing and signing

Whatever you agree, someone will print it. A print stylesheet decides whether that copy is usable.

@media print {
  nav, details { display: none; }
  @page { size: A4; margin: 20mm; }
  section { break-inside: avoid; }
  a[href^="#"]::after { content: ""; }
}

Stop clauses breaking across pages, hide the navigation, and suppress the URL that browsers otherwise print after every link. Details in export HTML to PDF and keeping links in the PDF if cross-references matter.

Access, in proportion

Not every agreement needs the same care.

Standard terms you would publish on your own site can sit at an ordinary address. A negotiated agreement with commercial terms should sit at an address nobody can guess, and should not be indexed. Anything containing personal data belongs behind access control, not behind obscurity.

If the page needs a barrier, understand what browser-side approaches do and do not give you before relying on one: password protecting an HTML page is a deterrent, not security.

The short version

Use a link so the other side reads the terms. Use a signed file so both sides can prove what the terms were. The page says which file governs, and the file is the one that counts.

Done that way, links make contracts easier to negotiate without making them harder to enforce.

Questions people ask

Is a contract shared as a link legally binding?

The link is a delivery method, not the agreement. What binds is offer, acceptance, and the intention to be bound, and those can be established by email, by signature, or by conduct. The practical problem with a link is not validity, it is evidence: you need a fixed record of exactly what text was agreed, and a page you can edit is the opposite of fixed.

So when is a link the right tool for a contract?

For reading and negotiating. Draft terms, a redline under discussion, standard terms you want the other side to actually read before signing. All of those benefit from opening in one tap on a phone. The moment the terms are final, produce a fixed file and sign that.

How do I stop the page changing after agreement?

Freeze it. Export the final text to a file, sign that file, and keep it. Leave the link up as the readable copy but state on it which signed version governs and on what date. If the two ever disagree, the signed file wins and the page says so.

What about e-signature services?

They exist precisely to solve the evidence problem: identity, timestamps, an audit trail, and a document that cannot be quietly edited afterwards. If the agreement matters, use one. A link complements that by making the terms pleasant to read beforehand; it does not replace it.

Is it safe to put contract terms at a public address?

Use an address nobody can guess and keep it out of any public index. Beyond that, judge by content. Standard terms are usually fine. Anything with personal data, pricing you would not want a competitor to see, or a confidentiality clause covering the document itself should go through a channel with access control.

Keep reading