Leases
Vacancies and renewals
The best leasing systems keep inventory movement visible. Abode supports renewal workflows, vacancy recovery, and a simple e-signature contract that can activate the lease once the signature event lands.
Renewal risk
Expiring leases can be separated from the new-lease pipeline
Vacancy visibility
Vacant units and listings stay tied to property structure
Signature flow
Status updates can activate a lease automatically
Keep renewals out of the net-new pipeline
A renewal is an operational retention workflow, not the same object as a fresh application.
- Track lease expirations separately so the team can work retention before a unit becomes vacant.
- Use vacancy views to coordinate listings, applicants, and projected move-in timing.
- Keep leasing communication attached to the lease or applicant record so underwriting and negotiation history remain visible.
E-signature handoff
The current e-signature route is a provider-shaped stub that already matches a production-style contract.
/api/dashboard/leasing/e-signatureSends a lease document for signature and accepts status updates that can activate the lease.
- Authentication
- Management dashboard session with leasing write access
- Constraint 1
- The route currently stores signature requests as transactions with type E_SIGNATURE.
- Constraint 2
- When status becomes SIGNED, the lease can move to ACTIVE.
- Constraint 3
- The API shape is ready for a provider such as DocuSign or Dropbox Sign.
Request examples
{
"leaseId": "lease_01J8V0C3NQVE6NR2A6A0R3JH4G",
"signerName": "Maya Chen",
"signerEmail": "maya@example.com",
"documentUrl": "https://cdn.theabode.ai/drafts/lease-1258-2b.pdf"
}Response examples
{
"id": "txn_01J8V0F7J4CJ89A7H8FMD4S3WD",
"status": "SENT",
"message": "Signature request sent to maya@example.com"
}Implementation detail
This is a front-end wiring contract today, not a fully externalized provider integration. The important part is that the platform already treats signature state as a real workflow boundary.