Skip to content
Nucleus One

Signatures

Signed, and filed against the thing it belongs to

Most signing tools hand the document back to you. This one already knows which record it is part of, because the document never left.

A wax seal press and pen resting on a signed page

What is behind the signature

A certificate, not a picture of a name

Each link is issued by the one above it, which is what makes the finished document something you can verify rather than something that looks signed.

  1. 01Root CAThe anchor the rest of the chain is trusted from
  2. 02Intermediate CAIssues the certificates that do the signing
  3. 03Subscriber certificateThe certificate a given signature is made with
  4. 04The signed PDFCarries the signature, verifiable afterwards

Root authority, intermediate authority, subscriber certificate, signed document.

What goes on the page

Six things you can ask for

Placed where they belong on the document, filled by the person signing it.

  • SignatureThe signature itself
  • InitialInitialled pages and clauses
  • NamePrinted, as it should read
  • TitleThe capacity they sign in
  • DateFilled when it is signed, not before
  • EmailCaptured with the signature

Who is in the session

Not everyone has to sign

A session separates the people who act from the people who only need the result.

  • SignerActs

    Has fields to complete and has to act before the session can finish.

  • RecipientReceives

    Receives the finished document without being asked to sign anything.

The session keeps its own record

Five things it writes down

So what happened is a record rather than a memory of an inbox.

  1. 01

    Sent out

    SessionStart

    The session opens and the signers are invited

  2. 02

    Signed

    RecipientSigning

    Recorded per signer, as each one completes their fields

  3. 03

    Rendered

    RenderCompletion

    The signed document is produced

  4. 04

    Finished

    SessionCompletion

    Everyone who had to sign has signed

  5. 05

    Stopped

    SessionStop

    Ended early, and the record says so

FAQ

Signature questions

A real one. Nucleus One runs its own public key infrastructure, with a root certificate authority, an intermediate authority and subscriber certificates, and the PDF is digitally signed rather than having an image of a name placed on it.

Yes. A session separates signers, who have fields to complete, from recipients, who receive the finished document without being asked to act.

The session keeps its own events: when it started, each signer signing, the signed document being rendered, and the session completing or being stopped early.

No. Signing is part of Nucleus One, and the signed document is filed against the record it belongs to rather than living in another vendor’s system.

Send one for signature

Create a free account, place the fields, and watch the signed copy file itself against the record.

Prefer to talk? Call (863) 937-0272

Create a free accountCall (863) 937-0272