Get the Contract Signed Without Leaving Your Data
Collect legally binding electronic signatures on documents that already live on your records.
The agreement, the signature, and the work it authorises stay on one record instead of scattering across a signing tool, an inbox, and a folder.
Why this matters
Getting something signed usually means leaving your system. You export the contract, upload it to a signing tool, chase the signature, download the result, and paste it back onto the record. The agreement lives in one place and the work it authorises lives in another, so nothing downstream can react to it.
InfoLobby has a Signature field that signs a rich text document on a record. The signer types their name, confirms they intend it as their signature, and the field locks. From then on the record holds a permanent account of who signed, when, and exactly what the document said at that moment, plus a certificate of completion you can produce years later.
A hash proves a document changed. It cannot show what was signed.
That distinction is the whole job. InfoLobby keeps a complete copy of the document at the moment of signing, not just a fingerprint of it, because reproducing the signed agreement is what the law actually asks for. Edit the document afterwards and the signature says so in red, with the original still intact underneath.
- Consent and intent are recorded, never assumed
- Server time, not the signer's device clock
- The signed copy is retained, so it can be produced later
What changes for the team
- Signatures sit on the record beside the amount, status, and due date
- Send a document out for signing with a private link, no login needed
- Every signature carries a full audit trail, not just a name
- Automations can act the moment a document is signed
- Two parties can sign the same document independently
Feature details
- Sign in the app or send a signature form to someone outside your team
- Record consent and intent separately, with the exact wording shown
- Timestamp from our servers, so a signature cannot be backdated
- Retain a complete copy of the document as it stood at signing
- Flag the signature if the document is edited afterwards
- Record a refusal as firmly as a signature, with the reason
- Download a certificate of completion from the record at any time
- Attach that certificate to an automated email without any extra setup
How teams usually start
- Add a Text Area field set to HTML Rich Text to hold the agreement, then add a Signature field pointing at it.
- Write or generate the document per record, by hand or from an automation.
- Create a signature form, then share the record's link, or have an automation email it when the record reaches the right status.
FAQ
Are these signatures legally binding?
They are designed to meet the US ESIGN Act and UETA, the laws that make an electronic signature as binding as a handwritten one. That means recording intent and consent separately, keeping the exact wording the signer agreed to, and retaining a reproducible copy of the signed document.
What happens if someone edits the document after it is signed?
The signature immediately shows a red warning on the record, and the copy taken at signing is still there. Nothing is silently overwritten. Freezing the document outright would strand records with no way out, so we make the change loud instead.
Can two people sign the same document?
Yes. A table can hold as many signature fields as you need, all pointing at the same document, each signed independently and in any order. Give each party their own signature form so the link you send one cannot be used to sign for the other.
What does the signer get?
A certificate of completion: the document exactly as it stood when they signed it, followed by the audit trail. Their link stays live so they can come back for it, and an automation can email it to them the moment they sign.
Does this cost extra?
No. Signatures are included on every plan and there is no per-signature or per-envelope charge. Each signature form counts toward your plan's web form allowance, the same as any other form.
Do you verify who the signer is?
No. The signature proves that whoever was at the keyboard typed that name and agreed to be bound by it. It does not prove they are the person that name belongs to. Higher-value agreements that need identity checks should use a product built for that.
Want this feature in a system your team can actually run?
Start with the workflow this feature supports, then add the records, views, tasks, comments, and automations around it.