---
doc_id: playbooks/landlord/time-to-deposit-compression
url: /docs/playbooks/landlord/time-to-deposit-compression
title: Time-to-Deposit Compression
description: unknown
jurisdiction: unknown
audience: unknown
topic_cluster: unknown
last_updated: unknown
---

# Time-to-Deposit Compression (/docs/playbooks/landlord/time-to-deposit-compression)



Article 33: Time-to-Deposit Compression [#article-33-time-to-deposit-compression]

SECTION: Landlord Performance Playbook
JURISDICTION: New York State / New York City
AUDIENCE: Landlord, Property Manager, Leasing Operator

***

Executive Thesis [#executive-thesis]

The deposit is the commitment. Until the security deposit and first month's rent are collected, the approved applicant is a verbal commitment — not a contractual one. Every hour between lease signing and deposit collection is an hour the tenant can change their mind, discover a competing option, or reconsider the financial commitment. Time-to-deposit compression means structuring the payment process so that the deposit is collected simultaneously with — or within hours of — lease execution.

Operational Framework [#operational-framework]

**Concurrent collection (best practice):** Structure the lease signing workflow so that the deposit and first month's rent are collected as part of the signing event — not as a separate follow-up step. E-signature platforms can include payment processing (ACH authorization, wire instructions) in the signing workflow. The tenant signs the lease and initiates payment in a single session.

**Accepted payment methods:** ACH transfer (most common — typically clears in 1–2 business days), wire transfer (same-day for time-critical situations), certified bank check (for in-person signings), cashier's check. Do not accept personal checks for security deposits — the check can bounce after the tenant moves in, and the landlord has no recourse other than a separate collection action.

**Payment confirmation before key handoff:** Do not provide keys, access codes, or move-in clearance until the deposit has cleared. For ACH, this means waiting 1–2 business days after initiation. For wire transfer, confirmation is same-day. Communicate this to the tenant upfront: "We release keys upon confirmed receipt of the security deposit and first month's rent."

Decision Framework [#decision-framework]

If the tenant requests a delay in deposit payment ("Can I pay next week?"), evaluate the request against fall-through risk. A 48-hour delay for a bank transfer is reasonable. A week-long delay signals wavering commitment or financial strain — both of which increase the probability that the tenant will never pay.

Risk Factors [#risk-factors]

Accepting a signed lease without a deposit creates an unenforceable commitment. If the tenant backs out before paying, the landlord has a signed lease but no money and no recourse — and has held the unit off-market for the signing period.

Key Takeaway [#key-takeaway]

The lease without a deposit is a letter of intent, not a commitment. Collect the deposit concurrent with the signature — never after. The tenant who signs today and pays next week is not a tenant. They are a prospect with a document.

***

Intelligence Layer [#intelligence-layer]

1. KPI Mapping [#1-kpi-mapping]

* Primary KPI: Deposit collection timing (hours from lease signing to cleared payment)
* Secondary KPI: Application → Occupied unit (end-to-end conversion)

2. Targets [#2-targets]

* Deposit collected within 24 hours of lease signing in 100% of transactions
* Zero leases signed without concurrent deposit initiation
* No keys released before deposit confirmation

3. Failure Signals [#3-failure-signals]

* Signed lease without deposit collected (maximum exposure)
* Average deposit collection lagging 3+ days after signing
* Key handoff before payment confirmation

4. Diagnostic Logic [#4-diagnostic-logic]

* Pricing: Not the primary diagnostic at the deposit collection stage
* Marketing: Not applicable
* Friction: Payment process friction (limited payment methods, unclear instructions) delays deposit collection
* Product Mismatch: Not applicable
* Lead Quality: Tenants who delay deposits may be financially strained — this is a screening quality signal

5. Operator Actions [#5-operator-actions]

* Integrate payment collection into the e-signature workflow
* Accept ACH, wire, and certified check — do not accept personal checks
* Communicate payment-before-keys policy upfront
* Follow up within 2 hours if deposit initiation is not confirmed after signing
* Hold the unit as available until deposit is confirmed — do not reject other applicants prematurely

6. System Connection [#6-system-connection]

* Leasing Stage: Lease execution → Move-in
* Dashboard Metrics: Time-to-deposit (hours), deposit collection rate, payment method distribution

7. Key Insight [#7-key-insight]

* A signed lease without a deposit is not a commitment. It is a risk. Collect payment concurrent with signature — every time.

<!-- BOTWAY_AI_METADATA
ARTICLE_ID: landlords-33
TITLE: Time-to-Deposit Compression
CLIENT_TYPE: landlord
JURISDICTION: Both

ASSET_TYPES: apartment, multifamily

PRIMARY_DECISION_TYPE: leasing
SECONDARY_DECISION_TYPES: leasing, operations

LIFECYCLE_STAGE: lease

KPI_PRIMARY: Deposit collection timing (hours from lease signing to cleared payment)
KPI_SECONDARY: Application → Occupied unit (end-to-end conversion)

TRIGGERS:
- Approved tenant delaying payment
- Signed lease without deposit
- Key handoff process

FAILURE_PATTERNS:
- Deposit > 72 hours after signing
- Personal check accepted for deposit
- Keys released before payment confirmed

RECOMMENDED_ACTIONS:
- Integrate payment into signing workflow
- No personal checks
- Hold unit until deposit confirmed

UPSTREAM_ARTICLES:
- landlords-32

DOWNSTREAM_ARTICLES:
- landlords-34

RELATED_PLAYBOOKS:
- glossary

SEARCH_INTENTS:
- When should I collect the security deposit?
- What payment should I accept for a deposit?
- Should I give keys before the deposit clears?

DATA_FIELDS:
- Deposit collection timing (hours from lease signing to cleared payment) data
- Application → Occupied unit (end-to-end conversion) data

REASONING_TASKS:
- diagnose
- optimize
- calculate

CONFIDENCE_MODE:
- high
-->

***
