ChekSign

Send it for signature, and prove it happened.

ChekSign is an electronic signature product for Australian businesses. Contracts, engagement letters, leases, authorities and employment paperwork, sent from your business, signed by whoever has to sign it, and certified with a record you can hand to anybody who asks.

  • No credit card
  • No watermark on what you send
  • Australian support
The ChekSign signing page: an engagement letter on the left, and on the right
                          the consent statement, a box for the signer's name and a signature pad.

One place, from the wording to the certificate

A document, the people who sign it, and the record

Most businesses send a contract out of a word processor, chase it by email, and file whatever comes back. ChekSign holds the wording, the sending, the signing and the evidence in one place, so what you can prove afterwards is not a matter of what somebody remembered to save.

Start from wording that already exists

Over three hundred starting points, written for this market

Employment contracts, supplier agreements, retail lease disclosure, company resolutions, engagement letters. Copy one into your workspace and it is yours to edit for ever. Nothing a later release does reaches a document you have made your own.

  • Start from a template, your own wording, or a PDF or Word file you upload
  • Write [Client.Signature] where a signature belongs and the box is placed exactly there
  • Or draw the boxes on the page yourself
  • Anything the document is still waiting on is named before it is sent, not after
Starting a request in ChekSign: the ChekSign library, with covers for the
                              shipped starting points and a blank document tile.

What a certificate actually says

Evidence bound into the document, not filed somewhere else

Every signed document carries a certificate of completion: who signed, when, from what address, and which identity check they actually passed. The transcript is numbered, so a reader can see the record is whole rather than take our word for it.

  • The document is stored, read back and hashed before anybody is asked to sign it
  • What the signer sees is those exact bytes, never a fresh render
  • Anybody holding a signed copy can check it against the original, with no account and no relationship with us
  • Where the order matters, the next person's link does not exist until the one before them has signed
A ChekSign certificate of completion: the document, its SHA-256 hash, and
                              each signatory with the times they were sent it, opened it and signed.

The parts a firm gets asked about

Built for the document being questioned later

Frozen before anybody signs

A document is stored, read back and hashed before it is sent, and what the certificate attests is what storage actually holds, not what we meant to store.

The check that was enforced

A certificate records the identity check a signer actually passed. Raising somebody's level afterwards does not change what their certificate says about them.

A transcript with no gaps

Events are numbered one to N for the document, and the count is printed. A gap would mean a record was missing, and a request with one will not send.

Signing order that is structural

A later signer's link is created at the moment their group is released and never before, so a forwarded link cannot sign early. There is nothing to present.

Witnessing, where a deed needs it

A witness is bound to a person rather than to a role, and their link is created by the signature they attest: in person, or over an audio-visual link, recorded.

One price per document sent

A request is one envelope however many documents are in it and however many people sign, so adding the guarantor who ought to be on the deed costs nothing.

How it works

Five steps, and the fifth one is automatic

  1. Start from a template, your own wording, or a file you upload.
  2. Say who is signing, in what order, and what each person is being asked to do.
  3. Prepare the document. Fill in what it is waiting on, and look at it before it is fixed.
  4. Send. Your client opens a link, reads the document, and signs.
  5. Everyone gets a copy, with the certificate bound into it.

Get started

Try it on a real document.

A fortnight, no card. Documents you send during the trial are recorded and certified exactly as any other. There is no watermark, and nothing on them says they were sent on a trial.

Reconnecting...

Still reconnecting. Trying again in seconds.

Could not reconnect.
Nothing you have typed or drawn is lost. Try again, or reload the page.

This page has been paused because it was left open for a while.

Could not pick up where you left off.
Nothing you have typed or drawn is lost. Try again, or reload the page.

Something went wrong on this page. Nothing you have typed or drawn is lost. It is kept in this browser and comes back with the page. Reload the page 🗙