Lease agreements

Digital lease viewing and in-app e-signing — from a typed template or a brought-in file, signed by every tenant and the landlord, with an inventory and condition record.

Lease agreements — a lease belongs to a tenancy as a versioned document (tenancyLeaseVersions). It comes from one of two sources: a template (a leaseTemplates definition with a typed field schema — the Taza “Residential Lease (AB / Tsuut’ina reserve)” is the first), auto-filled from the home, tenancy, and listing and completed by the owner; or a brought-in file the owner uploads to execute as-is. Both render a readable body in the tenant portal.

Template fields — each open blank in a template declares a kind: auto (bound from app data — premises, rent, parties, deposit, dates), choice (checkboxes that switch whole sections, e.g. fixed-term vs month-to-month, pets on/off), manual (owner free-text), constant (an editable default fee or notice period), derived (computed, e.g. Due on Signing), and repeatable (the tenant list). A lease can only be issued once every required blank is filled.

Execution — every tenant (joint and several) plus the landlord signs in-app: read the rendered lease, then type or draw a signature. Each signature is recorded with the signer’s email-verified session, a server timestamp, IP, and the content hash of the exact version signed. The lease reaches executed only when the full required set has signed (landlord counter-signs last by convention). Editing anything after a lease is issued voids the collected signatures and creates a new version — a signature is only valid against the bytes that were signed.

The executed copy — on the final signature the system generates a tamper-evident signed PDF: the lease plus an audit certificate listing every signer, method, time, IP, and the document hash. It is stored in the document vault and downloadable by the landlord and every tenant from their portals, permanently.

Inventory & condition (Schedule 1) — the lease’s inventory and condition record is the tenancy’s condition report (tenancyConditionReports / tenancyConditionItems): room-by-room and furnished-contents lines (seeded from the home’s furnishing inventory) with a condition code, notes, meter readings, and photo evidence per item. Both parties review and sign it at move-in; move-out re-runs it against the move-in baseline to support deposit deductions.

See ADR 0027 (lease document model) and ADR 0028 (e-signature + multi-party execution).