Skip to main content
Document OS is the document-lifecycle layer of Winnerr. It treats documents as structured data, not static files, and connects every stage of a document’s life—generation, signature, consent, and storage—back to the contacts, deals, and deadlines that already live in the CRM.

​
The four modules

Gen — Generate

Produce documents from OREA/TRREB form packs (APS, leases, listings, rental applications) or from any uploaded fillable PDF template. A human-gated draft → generate flow means AI only ever proposes; you decide what gets rendered.

Sign — E-signature

Send any generated document for signature. The default engine is Winnerr’s own legal-grade signing (intent capture, SHA-256 integrity hash, tamper-evident audit trail, completion certificate). DocuSign, SkySlope, and Authentisign can be configured to use your brokerage’s own account.

Locker — Obligations & search

Every executed document becomes structured and searchable. Deadlines—closing dates, condition waivers, deposit due dates—are surfaced as obligations in the command center. Semantic search (natural language over your document repository) requires the AI gateway to be configured.

Click — Consent

Lightweight clickwrap capture for buyer-rep acknowledgments, CASL marketing consent, disclosure acknowledgments, and similar low-friction consents. Every acceptance is stored with an immutable timestamp, IP address, and the exact version of the text accepted.

​
How it fits in the CRM

A signed Agreement of Purchase and Sale does not sit in a document repository and stop. In Winnerr it:
  1. Marks the document FULLY_SIGNED.
  2. Emits a DOCUMENT_SIGNED event on the internal event bus.
  3. Re-syncs the document’s obligations (DocumentObligation rows) so the closing date, financing-condition waiver deadline, and deposit due date appear in the command center.
  4. Surfaces those obligations in the Locker feed, sorted by urgency.
The platform is document-type-agnostic—the same flow works for any PDF you upload—but the OREA/TRREB packs are the premium path: fields are mapped to real legal vocabularies, closing dates are validated as business days, and obligations are derived exactly from the canonical data rather than extracted by AI.

​
Document states

A document moves through a clear, human-gated lifecycle:
StateMeaning
DRAFTCreated and open for editing in the wizard. AI may populate fields (marked with a provenance badge), but the human reviews before generation.
GENERATEDRendered to PDF. This step is explicit and human-initiated—AI does not auto-generate.
SENT_FOR_SIGNATUREAn active signature envelope exists.
FULLY_SIGNEDAll signers have signed; the completion certificate is attached.

​
Usage metering

Winnerr meters completed documents (rendered via the wizard or the API) against your plan’s monthly allotment. The meter is visible in the hub header and never blocks generation—going over the allotment triggers overage billing and a nudge to upgrade, not a paywall. API-generated and UI-generated documents are counted equally. See Billing for plan limits.
  • Generate — form packs, template upload, the wizard.
  • Sign — sending for signature, the signer experience, audit trail.
  • Locker — obligations feed and semantic search.
  • Click — clickwrap consent and acceptance log.
  • Documents API — REST endpoints for all four modules.