Portal Worx Logo
The record

This is what comes back.

A real record from a real approval, made on the demo project: the client opened a link, marked a spot on the drawing, approved and signed. Nothing here is a mock-up and nothing is redacted, because every name is a test person. Read it the way your client's solicitor would.

Page one of a real Portal Worx approval record: Approved, who answered, their email, when, from where, the drawn signature, who asked, the verified address, the version and the fingerprint of the file
Page one of the record, as the PDF prints it.

Seven things on it, and what each one proves.

  1. Who answered

    The name they typed and the email address the link was sent to. The name is claimed, not verified, and the record says so in its own words at the foot. The address is where the request went, and only whoever held that inbox had the link.

  2. When

    The moment the answer was recorded, in the sender's time zone, to the minute. The request time sits below it, so the record shows how long the decision took.

  3. From where

    The network address the answer came from. On this sample it's the local address, because the sample was produced on our own machine. On yours it's the signer's.

  4. The signature they drew

    Drawn with a finger or a mouse on the page, stored with the answer, and stamped with the name and the time it was drawn.

  5. Verified

    This request asked for it, so before they could sign we emailed them a one-time code and they typed it in. That's written on the record: whoever answered could read that mailbox at that moment. It proves control of the inbox, not identity.

  6. The fingerprint of the file

    The SHA-256 of the exact file they saw, 64 characters that change if a single byte of the file changes. The file itself is embedded inside the record PDF, so the fingerprint can be checked against it by anyone, at any time, without us.

  7. The version

    The version they signed, v1 here, and whether it's still the current one. When version C replaces version B, this record still says B, adds "since replaced by C", and carries B's own file inside it. The argument about which drawing was approved is over before it starts.

The answer block of the record: answered by Yusuf Rahman, the email address, the date and time, the network address, and the signature drawn on the page
The answer: who, when, from where, and the signature they drew.
The request block of the record: asked by Daniel Whitfield, asked on, asked of, the address it was sent to marked Verified, the version, and the 64-character fingerprint of the file
The request: the verified address, the version and the fingerprint of the exact file.

They drew a box on the drawing. The record kept the drawing.

The client marked an area of page one and wrote a note against it. The record doesn't just quote the note: it embeds a crop of that exact spot on the page, at print resolution, beside their words. Eighteen months later nobody has to find the drawing to know which spot they meant.

The note on the record: a crop of the area the client marked on the drawing, with their words beneath it
The crop of the marked area, embedded in the record beside the note.

And it stays on the project.

A signing tool would email you this and be done. Here the record sits on the document it's about, at the version it's about, next to the photos and the thread, findable when the invoice is disputed. That's the difference between a signature and proof of sign-off.

Take the sample with you.

The PDF below is the record itself, original file embedded, exactly as the signer could have downloaded it. Open it, check the fingerprint against the attached file, hand it to whoever you like.

Download the sample record (PDF)

Send your first one today.

Free for 14 days, no card. Sign-off isn't counted on any plan.