Signing engine
The default signing engine is Winnerr’s own internal legal-grade provider. It requires no external account or API key and is included on all plans. For organizations whose brokerage already uses DocuSign, SkySlope, or Authentisign, those providers can be configured to handle signature routing instead—see External providers below.What “legal-grade” means
The internal provider is built to satisfy the substantive requirements of the US Electronic Signatures in Global and National Commerce Act (ESIGN), the Uniform Electronic Transactions Act (UETA), and Ontario’s Electronic Commerce Act, 2000 (ECA-2000):The internal engine is engineered to be defensible, but counsel review of the ECA-2000 mapping is recommended before relying on it for a binding Agreement of Purchase and Sale. This review is non-blocking—the engine ships for all forms today.
Sending a document for signature
A document must be inGENERATED status before you can send it for signature.
From the document detail page, click Send for signature. A dialog lets you:
- Confirm the signers (pre-filled from the document’s canonical parties for OREA packs).
- Set the signing order: parallel (everyone signs at once) or sequential (each signer receives their link only after the previous person signs).
- Set an optional expiry window (days until the signing links expire).
The signer experience
Signers receive a link via email or SMS (depending on the delivery channel configured). The link opens a distraction-free, mobile-friendly signing page that does not require a Winnerr account. The signer page walks through four steps in order:- Open — the document is displayed; the
openedevent is recorded. - Authenticate — the signer confirms their identity via the configured auth method (email link possession by default). The
authenticatedevent is recorded. - Consent — the signer explicitly agrees to transact electronically. The
consentedevent is recorded. This step is required by ESIGN/UETA/ECA-2000 and cannot be skipped. - Sign — the signer applies their signature. The
signedevent is recorded.
Expired or voided links
Signing links that are unknown, expired, or belong to a voided envelope respond with a uniform “gone” state—no information is disclosed about why the link is unavailable.Signature status rail
The document detail page shows a per-signer status rail. Each signer chip displays their current status:
The envelope status rolls up from the signer statuses:
Voiding an envelope
To void an in-progress envelope, use the void action on the document detail (or the API). Voiding records avoided event with the reason and moves the envelope to terminal status. Already-completed envelopes cannot be voided.
Audit trail and completion certificate
The full audit trail is available from the document detail. Each event in the chain shows the type, timestamp, IP address, and user agent. The chain integrity can be verified by re-computingsha256(prevHash + payloadHash) for each event.
The completion certificate is a PDF appended to the signed document. It is downloadable from the document detail once the envelope reaches completed status.
External providers
For organizations whose brokerage is already contracted with DocuSign, SkySlope, or Authentisign, Winnerr can route signature requests through that provider instead of the internal engine. External providers require your brokerage’s own credentials. You must configure the provider credentials in Settings before signature requests can be sent through them. When an external provider is active, Winnerr maps the document’s canonical fields to the provider’s template tabs and hands off the signing flow to that provider’s platform. Completed external envelopes are synced back into Winnerr’s document repository (Locker) so your signed documents are searchable and their obligations are tracked in one place. To configure an external provider, go to Settings → Integrations and select the e-signature provider section.Related
- Generate — a document must be generated before it can be sent for signature.
- Locker — signed documents are automatically added to the searchable repository.
- Documents API — signature endpoints — programmatic access to send, status, and void.