ResidentAxis
Sign in Request a pilot

Feature

Lease generation, amendments and e-signatures

Build the lease from the lease — templates and merge fields fill from the terms you already entered — review it against configured rules, sign it natively, and never edit an active lease without an amendment.

Request a pilotProduct overview

The problem

Leases are generated from a Word file and edited by whoever is on shift.

Rent changes get typed over, deposit caps are exceeded by accident, and the signed PDF does not match the terms in the system. When a dispute arrives, there is no version history and no reason recorded for the change.

  • The document and the lease record disagree.
  • State-specific limits (deposit caps, late-fee ceilings, notice periods) are remembered, not checked.
  • Changes to active leases have no reason, effective date or diff.
  • E-signature is a separate subscription with its own audit trail nobody exports.

The workflow

Terms → document → review → sign → amend

  1. Enter the terms once

    Core terms, charges and deposits, rules and clauses, utilities and parties on the lease record.

  2. Generate from a template

    Start from a state / property-kind template (Virginia and Pennsylvania samples plus a generic set ship; add your own), edit sections, add custom language. Merge fields like monthly rent fill from the record.

  3. Review against configured rules

    Deterministic checks — deposit caps, late-fee limits, notice rules, disclosures, risky-language patterns — with statute citations from a versioned rules table. Errors block finalisation; overrides require a reason and are audited.

  4. Send for signature

    Native envelopes with multiple signers, magic-link signing, decline, void and re-route, and an audit certificate PDF.

  5. Lock and amend

    Once active, money, dates and status change only through a formal amendment with a reason and effective date. The database enforces it; the resident is notified; the diff is kept.

The lease terms panel. Every tab is part of one lease record; the document is generated from it.

Capabilities

What is built, what needs configuration, what is planned

Each row is a real capability in the current build. Labels are derived from the codebase and its test suites, not from a roadmap deck.

How to read the labels

Built
Implemented in the current build and covered by its test suite.
With configured integration
Implemented; a live outcome requires a provider you configure (keys, contract, or credentials).
Pilot
Implemented in part and enabled per pilot customer with tuning.
Planned
On the roadmap. Not sold or promised today.

  • Full lease terms model

    Built

    Core terms, charges and deposits, rules and clauses, utilities, parties, payment schedule and move-in/out — one record per lease.

  • Template-driven lease builder with merge fields

    Built

    Start from a state / property-kind template (Virginia and Pennsylvania samples and a generic set ship; add your own), edit sections, fill merge fields from the lease.

  • Rules-based compliance review

    Built

    Deterministic checks (deposit caps, late-fee limits, notice rules, disclosures, risky language) with citations from a versioned rules table. Rules are configured per jurisdiction; they are not legal advice.

  • Locked active leases with formal amendments

    Built

    Money, date and status changes on an active lease require an amendment with reason and effective date; the database enforces it.

  • Native e-signature envelopes

    Built

    Envelopes with multiple signers, magic-link signing, decline, void, re-route and an audit certificate PDF.

  • Signer identity verification

    With configured integration

    A knowledge-based verification step exists as a stub; production IDV needs a provider.

By role

What each party gets

Property managers

A document that always matches the record, with a review step before anything is signed.

Residents

Sign from a link, keep the certificate, and see any amendment with its reason.

Owners and counsel

Templates and rules they approved are the ones in use; overrides are visible in the audit log.

Configuration and pilot notes

Before you rely on it

Things that are set up per operator during a pilot, or that depend on a provider you contract.

  • Compliance rules are configured per jurisdiction and versioned; they are not legal advice and should be reviewed by counsel before use.
  • Templates beyond the shipped samples are added per operator during a pilot.
  • Signer identity verification exists as a stub; production knowledge-based or document IDV needs a provider.
  • Generated legal documents carry a disclaimer footer by design.

Questions about this area

Is the e-signature legally binding?

ResidentAxis captures intent to sign, signer identity as presented, timestamps and an audit certificate, consistent with common e-signature practices. Whether a given signature is enforceable depends on your jurisdiction and document; consult counsel.

Can we keep using DocuSign?

You can upload a signed PDF to the lease record instead of using the native flow. A DocuSign integration is not built.

Does the compliance review use AI?

The shipped review is deterministic rules with citations. An AI-assisted review behind the same endpoint is available with a configured provider and always requires a person to approve the result.

Related

Connected areas

Leasing & applicants

Applications, households, offers, approval to lease, renewals.

Learn more

Resident portal & payments

Balances, receipts, card/ACH via Stripe, Zelle queue, messaging.

Learn more

Move-in, inspections & deposits

Guided inspections, key-release gate, disposition from the diff.

Learn more

See leases & e-signatures on your portfolio.

A pilot starts with a discovery call and your CSV exports. We reply within two business days.

Request a pilot Talk to us