Electronic Signatures manages the full lifecycle of an execution: preparing a document for signing, defining who signs and in what sequence, collecting each signature and finalising a sealed, verifiable result. Senders place fields directly onto a document, signature blocks, initials, dates, checkboxes, radio groups, attachments and free-text entries, and bind each field to a specific participant so no one can complete another party's obligations. Reusable templates capture recurring agreements once, with their fields, roles and routing preset, so a new send is a matter of naming the parties rather than rebuilding the layout.

Routing supports sequential, parallel and hybrid flows: signers in a strict order, groups who may act simultaneously, carbon-copy recipients who receive the finished copy, and approvers who authorise before the document reaches a signer. Both remote and in-person signing are first-class. A remote signer receives a secure link and completes the document from any device; an in-person host passes a single session between parties on one screen at a counter or in a meeting. Bulk sending issues the same template to hundreds or thousands of recipients at once, each as a private, individually tracked envelope. Reminders, expiry, resend, void and delegation are handled centrally, and every envelope carries a live status that senders and dashboards can watch from dispatch to completion.

The organising idea is the envelope: the unit of execution that gathers one or more documents, the people who must act on them and the rules governing how they act. An envelope moves through a clear lifecycle, from draft, to sent, to in progress as parties respond, to completed or, if abandoned, voided or declined. Everything the module knows about a transaction hangs from this single spine, which is what makes an execution auditable as one coherent event rather than a scatter of separate signatures.

Around the envelope sit its participants. Each is a named role with a defined capacity, signer, approver, in-person host or informed recipient, an identity to verify against and a position in the routing order. A participant is granted only the fields assigned to them, so authority is explicit and cannot be borrowed. The other central concept is the field: a typed placeholder anchored to a precise location on a page, owned by exactly one participant, and either required or optional. Fields are how intent is captured with precision, a signature here, an acknowledged clause there, a date that stamps itself on completion.

Binding the whole together is the audit trail, an append-only record of every event in the envelope's life: who opened it, when, from where, what they viewed, what they entered and how their identity was confirmed. Because the trail is sealed to the final document, the executed agreement and the evidence of how it was executed are inseparable. This small set of concepts, an envelope holding documents, routed to participants who complete fields, all witnessed by an audit trail, is enough to model everything from a one-signer consent form to a multi-party, counter-signed master agreement.

The common path begins with a sender preparing an envelope, either from a blank document or a template, adding participants, placing fields and setting the routing order. On sending, each participant is notified in turn according to the sequence. A signer authenticates, reviews the document, completes their assigned fields and adopts a signature; the envelope advances to the next party automatically. When the last required action is taken, the module seals the document, generates the completion certificate and distributes the finished copy to every party and to the connected systems of record.

Alongside this, senders run in-person signing sessions for face-to-face execution, dispatch bulk campaigns for high-volume agreements such as policy acknowledgements or renewals, and manage exceptions in flight: correcting a mistyped recipient, reassigning a signer who has left, extending an expiry, sending a reminder or voiding an envelope that is no longer needed. Approval steps let an internal reviewer authorise content before it reaches an external signer, so nothing binding leaves the organisation without the required sign-off. Throughout, a monitoring view shows exactly where each envelope stands and which party is holding it up, turning chase-and-hope follow-up into a precise, actionable queue.

The evidentiary strength of an execution is the point of the module, and it is built to the standards that make an electronic signature enforceable. It supports both the simple, familiar electronic signature and stronger forms where the setting demands it, with layered identity verification, from email and access-code challenges to knowledge-based questions, one-time passcodes and document-based identity checks, applied per participant according to the risk of the agreement. Signing intent is captured explicitly, so consent to transact electronically is recorded rather than assumed.

Every completed envelope produces a tamper-evident completion certificate: a self-contained record listing each participant, their verified identity, the timestamps and network origin of every action, the consent given and a cryptographic seal over the final document. The seal is what makes tampering detectable, any alteration after execution breaks it, so a party cannot later swap a page or amend a figure without the change being provable. Sealed documents carry embedded validation so their integrity can be confirmed independently, long after the transaction, without access to the platform that produced them. Trusted timestamps fix when each signature occurred, and full retention of the audit trail means the who, what and when of an agreement remains reconstructable for the life of the record. These controls align the module with the recognised legal frameworks for electronic and digital signatures, and they make the resulting agreements defensible in dispute, in audit and in regulatory review.

Electronic Signatures is the execution engine the rest of the suite calls on whenever a commitment must be made binding. Its closest partners are Contract Lifecycle and Document Management: a negotiated contract is dispatched for signature directly from Contract Lifecycle, and on completion the sealed agreement and its certificate return there as the authoritative executed version, while Document Management archives the record under retention and access controls. Sales-side agreements originate in the quoting and CPQ flows, so an approved quote becomes a signed order without rekeying, and Customer and Vendor records supply verified signer identities so the person who signs is provably the counterparty on file.

Human Resources routes offers, policy acknowledgements and consent forms through the same execution path, and Finance draws on executed agreements as the trigger for billing and revenue recognition. Because the module writes back to a single record of the transaction, downstream reporting, renewals and obligations all reference one canonical executed document. Workflow and notification services carry reminders and status across the suite, so an execution in progress is visible wherever the originating work lives rather than trapped in a separate signing tool.

AI Workers act as full participants in the module, not an overlay on it. Staff query execution data conversationally, asking which envelopes are awaiting a particular customer, what is stalled beyond its target turnaround, or how a specific agreement was signed and verified, and receive grounded answers drawn from the live audit trail. Workers execute actions on request: preparing an envelope from a template, populating fields from a linked record, sending reminders, extending expiries, reassigning a departed signer or voiding a superseded document, each action recorded under the Worker's own identity.

They monitor for anomalies and exceptions, flagging envelopes that stall, signer identities that fail verification, routing that deviates from a template, or a document altered before dispatch, and they raise these to the right owner before they become problems. On inbound signed documents they extract signatories, effective dates, key terms and completed field values, reconciling them against the originating record and surfacing mismatches. Workers provide decision support to senders, recommending the identity assurance level appropriate to an agreement's value and risk, or highlighting a clause a counterparty has left unacknowledged. Most consequentially, an AI Worker serves as an approval or review node in the routing itself: positioned as an approver, it checks an envelope against policy, confirms the correct template and parties, and either authorises it to proceed or returns it with a reason, so routine executions clear without waiting on a person while every decision remains logged and accountable.