Any tool can collect a signature. The question that matters later is whether you can prove what was signed, by whom, and that it has not changed since.
Everything in this piece happens automatically on every document. None of it is configured and none of it can be switched off.
The trust drawer
Open any signed document and there is a single panel holding everything the system recorded. It has four parts.
The trust strip
A one-line summary: whether the document is tamper-evident, whether it carries an independent timestamp, and whether it is locked.
This is the part to look at when you simply need to know that a document is sound.
Integrity
A live re-check rather than a stored verdict.
The document is re-hashed when you open the panel and compared against what was recorded at signing. A match means it is byte-for-byte what was signed. A mismatch means something changed, and you would want to know.
Re-checking rather than displaying a saved result is the whole point. A stored "verified" badge proves only that something was verified once. This proves it now.
The audit timeline
Every event in the document's life: created, sent, viewed, each signature, sealed.
The events are chained, each one referencing the last. That is what makes the trail tamper-evident rather than merely present: removing or altering an entry breaks the chain in a way that is detectable, so the history cannot be quietly edited afterwards.
The evidence bundle
A single download containing the executed document, its certificate, and the independent timestamp.
This is the thing to send a lawyer. It is self-contained, it does not require access to your NearSync account, and it can be checked by somebody with no relationship to your organisation.
Independent timestamping
A signature carries your system's word about when it happened, which is worth something and is not worth as much as an outside party's word.
Documents are timestamped against an external authority, so the time is attested by somebody with no interest in the outcome. In a dispute, that is the difference between your records saying a thing and a third party confirming it.
The verification log
Every completed document in one list, which is the archive.
Two uses. Finding a specific executed agreement, which is what people come for. And an audit, where somebody wants to see the whole set rather than one document.
Why it is automatic
None of this is a setting, and that is the point.
A tamper-evidence feature somebody has to remember to switch on is a feature that will be off on exactly the document that later matters. The same is true of timestamping and of the audit trail.
So it applies to every document, including drafts that go nowhere and routine acknowledgements nobody will ever dispute. The cost of doing it universally is negligible; the cost of discovering it was off is not.
What this actually protects against
Worth being concrete, because the technical vocabulary obscures the everyday cases.
A document altered after signing. The most obvious, and the least common. Detected by the integrity check.
A dispute about what was presented. Far more common. Somebody says the schedule they saw had different numbers. The record holds the document as shown.
A dispute about when. Resolved by the external timestamp rather than by your own logs.
A dispute about who. The record holds the name typed, the address it came from, and the consent given.
None of those are exotic. They are the ordinary shape of a commercial disagreement two years after the fact, when everybody involved has left.
What it does not do
It does not make an agreement enforceable. Enforceability is about what the document says and the law where it applies. This makes it provable, which is a different and narrower thing.
It does not verify identity beyond what was collected. A signing link sent to the right address and signed by somebody with access to that address is what the ordinary flow establishes. Where you need more than that, stronger identity checks can be required on a document.
It does not replace legal advice. The material elsewhere in this section on compliance frameworks is background for an assessment, not counsel for your situation.
What is recorded, plainly
Six things, on every document, without anybody asking for them.
What was signed, as a sealed copy of exactly what was shown. Who signed, by asserted name and email. When, attested externally. From where, by network address. What they agreed to, as recorded consent. Everything that happened, as a chained history.
That list is the answer to most questions a lawyer will ask, and it is worth knowing it exists before the first time somebody asks.
Reading the timeline
Most of the time the interesting information is not the signature, it is the pattern before it.
Long gap between sent and viewed is a delivery or attention problem.
Viewed several times over days, then signed usually means it went to somebody else for approval.
Viewed once and signed within a minute means it was not read, which is fine for a routine acknowledgement and worth noticing on a substantial contract.
Several views and no signature is the one to act on, and the action is a conversation.
Explaining it to a customer
Procurement and legal teams ask how signatures are handled, and a good answer shortens the conversation considerably.
The short version: signatures are captured with the signer's asserted identity and consent, the executed document is hashed and sealed, the time is attested by an independent authority, the full history is chained so alteration is detectable, and the whole package can be exported and verified without access to our systems.
The better answer is to send them a bundle from a test document and let them check it.
When to look at it
Almost never, day to day. That is the correct amount. It runs on every document without anybody thinking about it.
When a customer asks how signatures are handled, the evidence bundle is a better answer than a description.
When somebody disputes something, before you reply. Read the timeline first; a surprising proportion of disputes are resolved by discovering that the document was viewed four times before signing.
Did this answer your question?
No, ask a person