GitLaw How-To guides
How to get a document signed
GitLaw includes free built-in e-signatures, so you can send a finalised document for signing without leaving the platform or paying extra.
Steps
- Open the document and trigger signing: From the document view, click the Send for signature button (also available from the file drawer or by asking the Agent - "Send this for signature").
- Confirm signers: GitLaw automatically detects contract parties from signature blocks and Smart Fields in your document (e.g.
party_1.name,party_2.email). In the party assignment step you can review, edit, add, or remove signers, and reposition signature blocks before sending.
- Set the signing order (optional): Choose whether signers must sign sequentially - for example, the drafting party first - or whether any order is acceptable. You can also decide whether a recipient may reassign their signing responsibility to someone else.
- Send: Once you confirm, each signer receives an email from
[email protected]containing the document name, their role, and a button to sign in their browser. No GitLaw account is required to sign.
- Track status: The document moves through three states - Draft → Awaiting Signatures → Fully Signed. You can monitor who has signed and who has not from the document view. GitLaw sends automated reminders for pending signatures; you may also configure a signing deadline.
- Receive the signed PDF: Once every party has signed, GitLaw generates a final, tamper-sealed PDF and attaches it to the document. All participants receive a copy by email. The document is then locked against further edits.
Audit trail
Every signing event produces a secure audit file stored alongside the signed PDF. It captures:
| Data point | Purpose |
|---|---|
| Timestamp of each signature | Legal audit trail |
| Signer IP address | Identity evidence |
| Device / browser fingerprint | Dispute resolution |
| Email address used | Authentication match |
| Hash of the signed PDF | Integrity verification |
| Full transaction log | Sent → Viewed → Signed → Completed |
This meets industry standards (equivalent to DocuSign / HelloSign audit certificates) and is legally enforceable under the ESIGN Act / UETA (US), Electronic Communications Act 2000 (UK), and eIDAS Regulation (EU).
Notes
- Collaboration history is excluded. The version sent for signature contains only the finalised document - chat, comments, and drafting history are not shared with signers.
- Free, always. E-signature is included in GitLaw at no extra cost and is not metered.
- Signing from the Agent. If you prefer, simply tell the Agent to send the document for signature. It will detect the parties and guide you through the same flow.