RA-LR1 Lease Rider: What NYC Owners Must Attach

What RA-LR1 Is

RA-LR1 is HCR's New York City lease rider for rent-stabilized tenants. On HCR's leases page, Form RA-LR1 is listed as the New York City lease rider for rent-stabilized tenants, and HCR states that owners must attach and serve it to rent-stabilized tenants signing a vacancy or renewal lease in New York City.

The rider is not just a courtesy document. HCR's Fact Sheet #2 explains that the New York City lease rider and ETPA lease addenda describe rights and obligations under rent laws and regulations. It also says the rider or addenda should accompany a vacancy lease and renewal leases.

For owners, the practical point is simple: the rider belongs inside a controlled lease package workflow. If the team treats it as a static attachment, it becomes easier to miss the current form, attach it to the wrong lease package, or send it before the rent and lease records underneath it have been reviewed.

When Owners Attach It

The most important timing question is not "Where is the form?" It is "When does the workflow require it?" HCR's lease guidance says owners must attach and serve RA-LR1 to rent-stabilized tenants signing a vacancy or renewal lease in New York City. Owners should verify the current HCR form and instructions before finalizing any lease package.

The current RA-LR1 form is marked with an October 2024 revision date. That date is a reminder to verify the current HCR form before using a saved PDF, email attachment, desktop copy, or old lease template. The operating process should include version control so the leasing team knows which rider belongs in the package.

For a Yardi team, this is where workflow ownership matters. The leasing team may generate the lease package, property management may own tenant and apartment status, accounting may own rent fields, compliance may review rider-sensitive questions, and the system administrator may control templates and document routing. If no one owns the handoff, the rider can become a downstream symptom of upstream data drift.

Owner questions to answer before attaching RA-LR1

• Is this a rent-stabilized apartment in New York City?
• Is the tenant signing a vacancy lease or renewal lease?
• Is the current HCR rider being used?
• Do the lease dates, rent fields, and tenant records match the lease package?
• Has the team reviewed preferential rent or higher actual rent fields where applicable?
• Is the executed rider retained with the lease record?

RA-LR1 vs. RTP-8 vs. Annual Registration

RA-LR1, RTP-8, and annual rent registration are connected, but they should be managed as separate operating workflows. Each controls a different owner task, and each needs its own review path before records are sent, signed, or filed.

Keeping the workflows separate helps teams avoid using the right information in the wrong place. RA-LR1 belongs with the lease package, RTP-8 belongs with the renewal offer workflow, and annual registration belongs with the filing process. They should cross-check each other, but one should not replace the controls required for another. For the filing side, use the ORRA / ARRO annual registration guide as the companion workflow.

Records to Review Before the Lease Package

A clean RA-LR1 workflow starts before the rider is attached. The lease package should be built from records the team trusts: apartment status, tenant status, lease dates, rent fields, renewal status, rider version, and document retention rules.

HCR's Fact Sheet #2 says the rider includes elements such as the subject address and apartment, signatures, information about the prior tenant's rent, information that helps explain how the current rent was calculated, and owner and tenant rights and duties. Owners should verify the current rider and HCR instructions before relying on any internal summary of required rider details.

Operationally, the best question is not "Can we attach the PDF?" It is "Can we explain the data behind the lease package?" If the answer depends on one person's spreadsheet, memory, or local folder, the process is fragile.

Vacancy Lease Workflow

Vacancy lease packages create the greatest risk of stale assumptions because a new tenancy often brings together apartment history, prior legal regulated rent, rider language, bedbug disclosure, lease generation, rent setup, and document execution at the same time.

HCR's leases page explains that individuals renting a rent-stabilized apartment for the first time sign a vacancy lease, and that a completed lease rider or addenda must be attached to the vacancy lease and future renewal leases. It also identifies the bedbug disclosure form for New York City vacancy lease tenants.

For owners, the practical workflow is to review the apartment record before the lease package is produced. Confirm whether the unit is rent stabilized, whether the prior rent and current rent fields are clean, whether the current rider is being used, and whether the supporting records can be retrieved later if a reviewer asks how the lease package was built.

Vacancy lease preparation questions

• Is the apartment status correct before the lease is generated?
• Does the lease package include the current RA-LR1 rider?
• Are prior rent and current rent fields aligned with the records the team will preserve?
• Are any required disclosures, addenda, or internal review notes handled in the lease workflow?
• Will the executed documents be stored in a place the team can retrieve later?

Renewal Lease Workflow

Renewal leases create a different challenge. The apartment and tenant are already in the system, so teams often assume the rider workflow is safe. That assumption can be risky if lease dates, renewal options, rider version, preferential rent, or document routing have drifted since the prior lease cycle.

HCR's lease guidance says tenants in rent-stabilized apartments have the right to select a one-year or two-year renewal term, and it explains timing rules for renewal offers. The renewal lease form is separate from RA-LR1, but the rider still belongs in the renewal lease package where HCR requires it.

For Yardi users, renewal preparation should be tied to a repeatable review: pull upcoming renewals, identify rent-stabilized units, confirm the renewal dates and terms, review applicable rent fields, attach the current rider, and preserve the executed package. If renewal work happens outside the system, internal controls weaken quickly.

Common Rider Breakdowns Owners Run Into

RA-LR1 issues usually look like document problems, but the root cause is often data ownership. The wrong rider version, missing attachment, inconsistent rent field, missing execution record, or unresolved preferential rent question usually points back to unclear handoffs before the lease package went out.

HCR's Fact Sheet #2 explains that a tenant who is not served with a rider or addenda when signing a vacancy or renewal lease may file the lease complaint form, and it notes that failure to properly serve the rider or provide required information may create overcharge exposure. Owners should verify current HCR instructions and seek legal guidance for case-specific questions.

Where Yardi Data Needs to Be Clean

Yardi can support RA-LR1 readiness when the operating records are clean before lease packages are generated. The important work is not simply attaching a document. It is making sure the rider, lease, apartment status, tenant record, rent fields, renewal workflow, and document retention process all point to the same version of reality.

That means Yardi administrators should not be the only people involved. Leasing teams understand timing and execution. Property managers understand occupancy and apartment status. Accounting teams understand rent fields. Compliance teams understand escalation questions. A strong rider process gives each group a clear handoff.

If recurring rider issues keep showing up, bring the workflow back upstream. Review how lease packages are generated, how rent-stabilized status is maintained, how reports are validated, and how final documents are stored. Then decide which issues belong in configuration, process, training, reporting, or legal review.

RA-LR1 Readiness Checklist

Use this checklist before vacancy or renewal lease packages are sent. It is meant to help teams catch operational issues before they become tenant questions, compliance cleanup, or document-retention problems.

• Confirm the apartment is subject to New York City rent stabilization.
• Confirm whether the package is for a vacancy lease or renewal lease.
• Download or verify the current RA-LR1 rider from HCR before relying on a saved template.
• Confirm tenant names, apartment number, building address, and lease dates.
• Review legal regulated rent and preferential rent where applicable.
• Confirm renewal workflows and rider workflows are aligned but not merged.
• Check whether any rider-sensitive issues need compliance or counsel review.
• Confirm the lease package includes required attachments and disclosures for the situation.
• Retain the executed rider with the lease record.
• Move repeat corrections back into Yardi so next year's workflow starts cleaner.

RA-LR1 Lease Rider FAQ

HCR Sources to Verify Before Sending Lease Packages

This guide is operational guidance, not legal advice. Owners should verify current lease-rider requirements, forms, and lease-package instructions with HCR sources and counsel before sending vacancy or renewal lease materials.

• HCR Form RA-LR1: New York City Lease Rider for Rent Stabilized Tenants
• HCR Leases
• HCR Fact Sheet #2: New York City Lease Rider and ETPA Standard Lease Addenda
• HCR Tenant/Owner Forms
• HCR Rent Registration