An owner-side guide to the New York City rent-stabilized renewal lease form, the timing windows owners need to manage, and the Yardi data that should be clean before renewal packages go out.
RTP-8 is the renewal lease form owners use for New York City rent-stabilized apartments. It is not just a PDF to send near the end of a lease. It is a timed workflow that touches tenant records, apartment status, rent fields, lease expiration dates, renewal term selection, required riders, and document retention.
This guide is written for owners, managing agents, property managers, leasing teams, compliance teams, and Yardi administrators who need rent-stabilized renewal packages to be accurate before they go out. It is operational guidance, not legal advice, and it does not replace HCR Fact Sheet #4, current HCR instructions, Rent Guidelines Board orders, or counsel.
HCR Fact Sheet #4 says owners should send the renewal lease offer no more than 150 days and no less than 90 days before the current lease expires.
The tenant response window, owner return window, renewal term selection, and lease expiration date should be tracked as one controlled workflow.
RTP-8 is separate from the RA-LR1 lease rider and separate from annual rent registration, but all three depend on clean apartment, tenant, lease, and rent records.
The applicable Rent Guidelines Board order supplies the renewal guideline context; teams should verify the current order before finalizing renewal packages.
The safest process is to clean Yardi records before RTP-8 packages are generated, not after a tenant, reviewer, or attorney identifies a mismatch.
Chapter 1
What RTP-8 Is
RTP-8 is HCR's renewal lease form for New York City rent-stabilized apartments. HCR's leases page identifies RTP-8 as the New York City renewal lease form, and owners use it to offer a one-year or two-year renewal term to a rent-stabilized tenant.
The form sits inside a broader renewal package. It should be coordinated with lease dates, rent fields, tenant information, the applicable Rent Guidelines Board order, and the RA-LR1 lease rider when the rider is required. Treating RTP-8 as a standalone attachment is where preventable mistakes begin.
For owner-side teams, the practical question is not simply whether the form exists. It is whether the renewal offer is being produced from records the team trusts, sent within the required timing window, returned by the tenant, countersigned by the owner, and retained with the lease record.
Plain-English distinction: RTP-8 is the renewal lease form. RA-LR1 is the New York City lease rider. Annual registration is a separate filing workflow. They are connected, but they are not interchangeable.
Chapter 2
Timing Windows Owners Need to Manage
HCR Fact Sheet #4 explains the timing rhythm owners need to manage. It says the renewal lease offer should be sent not more than 150 days and not less than 90 days before the current lease expires. It also describes the tenant's 60-day response period and the owner's 30-day period to return a fully signed copy after receiving the signed renewal from the tenant.
Those windows create an operating calendar, not just a compliance note. If the lease expiration date, renewal offer date, tenant response date, owner return date, and document storage step are not tracked together, the renewal workflow becomes hard to defend later.
For a team on Yardi, this is where reporting and workflow ownership matter. A renewal pipeline report should show which rent-stabilized units are approaching the offer window, which packages have been sent, which tenant responses are outstanding, and which fully executed renewals still need to be stored.
Timing questions to answer before packages go out
Which rent-stabilized leases expire in the next 150 days?
Which renewal offers are inside the 90- to 150-day window?
Which tenant responses are due or overdue?
Who is responsible for returning the fully signed renewal copy?
Where will the executed renewal package be retained?
Chapter 3
Records to Review Before Preparing RTP-8
A clean RTP-8 workflow starts before the form is prepared. The renewal package should be built from records the team trusts: apartment status, tenant names, lease dates, expiration date, legal regulated rent, preferential rent where applicable, renewal term options, applicable guideline year, and document-routing status.
HCR's Fact Sheet #4 says rent-stabilized tenants have the right to select a one-year or two-year renewal lease term. That means the form cannot be treated as a generic renewal notice. It has to reflect the correct tenant, correct unit, correct current lease, and correct term choices before it is sent.
Operationally, the best question is not "Can we generate the form?" It is "Can we explain the records behind the renewal offer?" If the answer depends on a spreadsheet, local folder, or one person's memory, the workflow is exposed.
Confirm rent-stabilized apartment status.
Confirm tenant names, occupancy, and lease expiration date.
Review legal regulated rent and preferential rent fields.
Verify the applicable guideline period before finalizing amounts.
Confirm RA-LR1 rider handoff where required.
Define where the fully executed renewal will be retained.
Chapter 4
RTP-8 vs. RA-LR1 vs. Annual Registration
RTP-8, RA-LR1, 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.
Workflow
What It Answers
Why Owners Should Keep It Separate
RTP-8 renewal lease form
What renewal offer is being made to the rent-stabilized tenant?
The form controls renewal timing, term selection, tenant response tracking, and owner return workflow.
RA-LR1 lease rider
What rider must be attached and served with NYC rent-stabilized leases?
The rider is part of the lease package and needs its own version control and document retention process.
Annual rent registration
What annual building and apartment information must be filed through HCR's registration workflow?
Annual registration is a recurring filing process, not a renewal offer or lease-package attachment.
Keeping the workflows separate helps teams avoid using the right information in the wrong place. RTP-8 belongs with the renewal offer workflow, RA-LR1 belongs with the lease package, and annual registration belongs with the filing process. For the filing side, use the ORRA / ARRO annual registration guide as the companion workflow.
Chapter 5
Renewal Increase Context
RTP-8 depends on the applicable Rent Guidelines Board order, but renewal math should not live only in a form-preparation note, spreadsheet, or one person's local checklist. The Rent Guidelines Board apartment orders are the public source owners should verify before finalizing renewal amounts.
For leases beginning between October 1, 2025 and September 30, 2026, Order #57 is the current order at the time this guide was prepared. Owners should verify the applicable order for the lease term they are preparing because guideline periods change annually.
From an operating standpoint, the renewal amount should not be calculated in isolation. The team should be able to trace the current lease, term selection, guideline period, legal regulated rent, preferential rent where applicable, and final renewal package back to the same source records.
Keep the math controlled: Use RTP-8 for the renewal offer workflow, but keep annual increase guidance tied to the current Rent Guidelines Board order and your internal review controls.
Chapter 6
Tenant Response and Owner Return Workflow
The RTP-8 process does not end when the renewal offer is sent. HCR Fact Sheet #4 describes a tenant response period and an owner return step after the tenant signs the renewal. That means the workflow should track sent, pending, returned, countersigned, and stored status.
This is where renewal work often drifts into email threads and spreadsheets. A leasing team may know the package went out, but accounting may not know which term was selected. A property manager may know a tenant responded, but the executed document may not be stored where future reviewers can find it. A Yardi administrator may see the lease date update, but not the paper trail that supports it.
The cleaner process is to assign ownership before volume builds up. Decide who sends renewal offers, who monitors response deadlines, who reviews exceptions, who updates lease and rent fields, who returns the owner-signed copy, and who confirms document retention.
Status points to track
Renewal offer prepared.
RTP-8 package sent to tenant.
Tenant response pending.
Tenant-selected renewal term received.
Owner-signed copy returned.
Executed renewal package retained with the lease record.
Chapter 7
Common RTP-8 Breakdowns Owners Run Into
RTP-8 issues usually look like form problems, but the root cause is often data ownership. Late offers, stale templates, incorrect lease dates, unclear term selection, mismatched rent fields, missing rider handoffs, and weak document retention usually point back to process drift before the package went out.
Owners should verify current HCR instructions and seek legal guidance for case-specific questions. From an operating perspective, repeated failure points should be corrected upstream in the source system, report logic, workflow checklist, or approval process.
Breakdown
Likely Root Cause
Operational Response
Renewal offer goes out late
Lease expiration dates are not being monitored far enough ahead
Use a renewal pipeline report that flags upcoming expirations before the 150-day mark.
Wrong form version is used
Old PDF, saved desktop copy, or stale template
Centralize form version control and verify HCR sources before sending packages.
Rent fields do not match the renewal package
Source-system drift, spreadsheet edits, or unclear accounting review ownership
Clean Yardi rent fields and document the review path before renewal packages are generated.
Tenant response is not tracked
Email-based process without a clear status owner
Define sent, pending, returned, countersigned, and stored statuses before renewal volume builds.
Executed renewal is hard to find later
Weak document retention or inconsistent naming
Store the executed package with the lease record and define retrieval ownership.
Chapter 8
Where Yardi Data Needs to Be Clean
Yardi can support RTP-8 readiness when the operating records are clean before renewal packages are generated. The important work is making sure the renewal offer, lease dates, apartment status, tenant record, rent fields, term selection, rider handoff, 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 tenant communication and package timing. Property managers understand occupancy and unit status. Accounting teams understand rent fields. Compliance teams understand escalation questions. A strong renewal process gives each group a clear handoff.
If recurring renewal issues keep showing up, bring the workflow back upstream. Review how renewal packages are generated, how rent-stabilized status is maintained, how reports are validated, how tenant responses are tracked, and how final documents are stored. Then decide which issues belong in configuration, process, training, reporting, or legal review.
Lease datesConfirm current lease start and expiration dates before renewal windows are calculated.
Tenant and unit dataReview tenant names, apartment status, rent-stabilized status, and occupancy records before sending packages.
Rent fieldsValidate legal regulated rent, preferential rent where applicable, and related renewal reporting fields.
Document workflowConfirm the current form is used, the RA-LR1 handoff is handled, and the executed package is retained.
Review ownershipDefine who reviews exceptions, who escalates questions, and who approves package release.
Chapter 9
RTP-8 Readiness Checklist
Use this checklist before rent-stabilized renewal 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 the current lease expiration date and renewal window.
Download or verify the current RTP-8 form 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.
Verify the applicable Rent Guidelines Board order before finalizing renewal amounts.
Confirm whether the RA-LR1 lease rider belongs in the renewal package.
Track sent, pending, returned, countersigned, and stored statuses.
Retain the executed renewal package with the lease record.
Move repeat corrections back into Yardi so the next renewal cycle starts cleaner.
FAQ
RTP-8 Renewal Lease Form FAQ
What is RTP-8?
RTP-8 is HCR's renewal lease form for New York City rent-stabilized apartments. Owners use it to offer a one-year or two-year renewal term to a rent-stabilized tenant.
When must owners send RTP-8?
HCR Fact Sheet #4 says owners should send the renewal lease offer not more than 150 days and not less than 90 days before the current lease expires. Owners should verify current HCR instructions and counsel before sending renewal packages.
How long does the tenant have to respond?
HCR Fact Sheet #4 describes a 60-day tenant response period after the renewal offer is served. Teams should verify the current instructions and track the response status as part of the renewal workflow.
Is RTP-8 the same as RA-LR1?
No. RTP-8 is the renewal lease form. RA-LR1 is the New York City lease rider for rent-stabilized tenants. They can be part of the same renewal package, but they serve different purposes.
Does RTP-8 replace annual rent registration?
No. RTP-8 is a renewal lease form. Annual rent registration is a separate recurring filing workflow. They are different tasks, but both depend on clean apartment, tenant, lease, and rent records.
How does RTP-8 connect to Yardi?
RTP-8 preparation depends on clean tenant records, lease dates, apartment status, legal regulated rent, preferential rent where applicable, renewal term tracking, rider handoffs, and document retention. Yardi can support the workflow when those records and reports are maintained before renewal packages are prepared.
Sources
Sources to Verify Before Sending Renewal Packages
This guide is operational guidance, not legal advice. Owners should verify current renewal lease requirements, forms, guideline orders, and lease-package instructions with HCR, the Rent Guidelines Board, and counsel before sending renewal lease materials.