# E-signature
Contracts get signed. The platform integrates with an e-signature surface so the signing flow lives inside your operations: request, send, track, store, and retrieve signed documents without exchanging PDFs outside the console.
## What e-signature covers
The e-signature flow handles four signature scenarios:
* **Supplier contracts** — signed between you and a property, chain or bedbank supplier.
* **Distribution contracts** — signed between you and a partner agency, B2B distributor or channel.
* **Organization agreements** — signed between you and a organization in your group (subsidiary onboarding, partner agency contracts, terms of service).
* **Operational addenda** — signed amendments to existing contracts (rate updates, allotment changes, scope expansions).
Each scenario uses the same flow; what differs is the counterparty and the document.
## How it appears in the contract flow
The four-step e-signature loop. The counterparty signs without needing a platform account.
You drive the first three steps from the contract page. The counterparty receives an email with a link to a signing surface; they sign without needing a platform account. Once their signature lands, your organization signs to complete the contract.
## What gets stored
For each signed contract, the platform stores:
* **The original document** — the version that was signed, immutable.
* **The signature events** — who signed, when, from where (IP region, signing surface).
* **The verification proof** — the proof that the signature is authentic and bound to the document.
* **Any amendments** — separate documents, each with its own signature chain, linked to the original contract.
You can retrieve any of these from the contract page; legal and finance can find them from contract history.
## What the counterparty experiences
From the counterparty's side:
* They receive a signed-link email that does not require a platform account.
* They open the document on a signing surface, can review every clause, and sign in line.
* They get a copy of the signed document automatically.
* They are notified when you counter-sign and the contract becomes active.
This is the standard e-signature experience travellers see across the industry; nothing about the Adrasis side requires them to learn a new tool.
## Legal review
For a legal review:
* **The signature event** is verifiable — the proof that signature N on document M happened at time T from a recognized signing flow.
* **The document at signing time** is the immutable version stored on the contract page; no later edit changes what was signed.
* **The signature chain** for amendments lets you trace every change to the contract through every counter-party agreement.
* **Retention** follows the contract setup for your organization.
## Status visibility
The contract page shows you, at a glance:
* Pending signatures — who has not yet signed, when the signature was requested, when it expires.
* Completed signatures — who signed, when, in what order.
* Failed deliveries — if a signing-link email bounced, the platform surfaces it.
* Amendments in flight — same surface, scoped to the amendment.
Concrete view: on Monday morning your contract dashboard shows 14 supplier contracts sent for signature in the last 30 days — 9 signed, 3 pending past 7 days, 1 with a bounced delivery to the supplier's billing address, and 1 amendment to Hotel Sunrise's allotment in flight. You re-send the bounced one to a new contact, send a single nudge to the 3 stale ones, and move on. This is what makes "*chase the contract*" a console action, not a separate team-chat thread.
## Adragent and e-signature
Common phrases that map to Adragent e-signature operations:
* *"Send the supplier contract draft for Hotel Sunrise to their authorized signer for e-signature."*
* *"Show me every contract waiting for counterparty signature for more than 7 days."*
* *"Resend the signing link for the Marina amendment to the supplier contact."*
* *"Pull the signed document for the Hotel X bedbank contract."*
Read operations return immediately; writes preview before applying.
## Where to next
* **The contract layer e-signature closes** → [Contracts](/console/contracts-and-onboarding/contracts.md)
* **The onboarding flow e-signature is part of** → [Onboarding flow](/console/contracts-and-onboarding/onboarding-flow.md)
* **Signature event history** → [Activity log](/console/notifications-and-ops/audit-log.md)
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://adrasis.gitbook.io/console/contracts-and-onboarding/e-signature.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.