What is click-to-sign, and is clickwrap binding?

The two questions a court asks about a click

First, was the person given reasonable notice of the terms. Second, did the act they performed unambiguously signal agreement to those terms. Both are about design rather than law. A page that puts the terms behind a link directly beside the button, in ordinary sized type, with the button labelled to say what pressing it means, passes both comfortably. A page that hides the link in grey text at the bottom, or labels the button continue and mentions agreement nowhere near it, fails the first and often the second. Nothing about the technology decides this. The same click, on two differently laid out pages, produces a binding agreement on one and an argument on the other, which is why the interface is the legal document as much as the terms are.

Clickwrap against browsewrap

Clickwrap requires an act: a box to tick, a button that says agree, a step that cannot be skipped. Browsewrap requires nothing, resting on a link somewhere on the page and the theory that using the site means accepting whatever it says. Courts have been consistently unimpressed by the second, because the person never did anything from which agreement can be inferred and often had no reason to look. There is a middle case, sometimes called sign in wrap, where a button says that continuing means accepting the terms linked beside it. That usually holds, and it holds because the notice is next to the act rather than because of the label anybody has given the pattern.

What the record has to contain

A click is worth exactly as much as the log behind it. The useful record captures who, in the sense of the account or verified address; when, to the second; what, meaning the exact version of the terms served at that moment, kept somewhere retrievable rather than overwritten at the next release; and how, meaning a copy or a faithful reconstruction of the screen the person saw. That last item is the one most often missing. Terms change, pages are redesigned, and two years later the business can show that somebody clicked without being able to show what they were clicking on. Versioning the terms and keeping the rendered page is dull work and is the whole value of the record.

When a click is not enough

Some documents need more, either because the law says so or because the counterparty will not accept less. Deeds have execution formalities that a button does not satisfy. Land dealings, wills and certain statutory declarations sit outside the ordinary electronic transactions rules in most jurisdictions. Employment and finance documents often need identified signatures because a later dispute is likely and the record has to name a person rather than a session. And any negotiated agreement, where the terms were amended back and forth, needs a fixed file that both sides can point to. A click gives agreement to whatever was on screen; it does not give you an agreed artefact.

Where document signing takes over

The dividing line is whether the terms are the same for everybody. Standard terms served to a whole customer base suit a click, because the document is the page and the page can be versioned. Terms negotiated with one counterparty suit a signed file, because the document is the thing that changed and it has to be pinned. Sending a document for signature produces exactly that pinning: one file, recipients named individually, an identity check chosen per recipient, and a certificate afterwards naming who signed what. Clickwrap acceptance is a different pattern and is not what a document signing flow produces, so a business that needs both usually runs them separately. A practical split is to keep clickwrap for anything served to a whole customer base and to route everything with a named counterparty through a file, so nobody has to decide case by case under time pressure. Write the rule down once, put it beside the terms in the same folder, and the question stops coming up in every deal.

Questions people ask