Feature
Documented Signatures
Prepare supported PDFs for signature and retain selected workflow, consent, and completion records to support your own record-keeping.
Understand the supporting record
Orbis Sign records selected evidence about the signing workflow. These records can assist a review, but do not independently prove a person's civil identity, authority, or the legal effectiveness of a document.
- Completion Records: Keep a time-stamped record of signing activity.
- Recipient records: Tie signing activity to a specific destination email and recipient token.
- Event metadata: Timestamps and reported network or browser details where the relevant event captures them.
Match the signing method to the document
Before sending, confirm the approved PDF, the legal names of the parties, each signer's authority, and whether order matters. Orbis Sign supports sequential routing when one recipient should act before another and parallel routing when they may act independently. Neither choice resolves witnessing, deed, registry, notarisation, or agreed delivery requirements.
At completion, inspect the PDF and supporting record rather than relying on status alone. Event coverage varies, and reported browser or network details do not capture every interaction or independently identify a person. Where completed PDF bytes are available, completion can record a hash of those bytes; a separately labelled fallback event hash is not the same thing.
Use the practical audit-trail guide to interpret evidence and the contract signing checklist when authority and execution constraints matter. General information is not legal advice.