An owner-side guide to common HCR and DHCR rent-stabilized forms, when each workflow matters, and which Yardi records should be clean before forms are filed, sent, or retained.
Owners and managing agents often need a practical starting point: which HCR source to verify, which form or online application fits the workflow, and whether the records behind that form are clean before anything is filed, sent, billed, or stored.
This guide is written for owner-side teams, managing agents, property managers, compliance teams, leasing teams, accounting teams, and Yardi administrators working with New York rent-stabilized portfolios. It is a navigation and readiness guide, not a substitute for HCR instructions, current forms, or legal counsel.
HCR's official forms and applications should be verified before relying on a saved PDF, prior-year packet, or internal template.
RTP-8, RA-LR1, RA-44, annual registration, ORRA/ARRO, MBR, MCI, and IAI workflows answer different owner questions.
Some owner workflows are online applications, not just static forms, so the team should confirm access before a deadline.
For teams using Yardi, the form is usually the last mile; the source records, reports, approvals, and documents need to be ready first.
The safest process is to keep official HCR sources, internal Yardi records, and retained documents aligned instead of letting one spreadsheet become the working record.
Chapter 1
How to Use This Forms Library
HCR's Tenant/Owner Forms page is the public starting point for many rent stabilization and rent control forms. HCR also maintains a broader Forms and Applications page and separate online service pages for owner workflows. Owners should verify the current HCR source before using any form or saved version.
The purpose of this BC Solutions guide is different. It does not host official forms or replace HCR instructions. It helps owner-side teams understand which workflow a form belongs to, what records should be checked before use, and where the form fits in the operating calendar.
That distinction matters because form mistakes are often not form mistakes alone. They are source-data mistakes, access mistakes, timing mistakes, approval mistakes, or document retention mistakes that appear when a form has to be filed or sent.
For rent-stabilized renewal work, the most common lease-package forms are RTP-8 and RA-LR1. HCR's leases page says owners must use RTP-8 to offer a renewal lease to rent-stabilized tenants living in New York City. The same page says owners must attach and serve RA-LR1 to rent-stabilized tenants signing a vacancy or renewal lease in New York City.
Those two forms are related, but they should not be treated as interchangeable. RTP-8 is the renewal lease offer workflow. RA-LR1 is the lease rider workflow. Both depend on rent, lease, tenant, unit, and document records, but each one answers a different compliance question.
For a team using Yardi, the renewal package should not start with a blank form. It should start with a renewal pipeline review: lease expirations, 90- to 150-day windows, current tenant names, apartment status, legal regulated rent, preferential rent where applicable, renewal term options, rider requirements, and document retention.
Lease package records to check
Current lease expiration date and renewal offer window.
Tenant name, apartment number, building address, and unit status.
Legal regulated rent and preferential rent where applicable.
Required rider, notice, addendum, and document package.
Where the executed renewal package will be retained.
Chapter 3
Annual Registration and ORRA/ARRO
Annual rent registration is not just a form lookup. It is a filing workflow. HCR's Rent Registration materials and Owner Rent Regulation Applications page are the public sources owners should verify for current registration and online access guidance.
The DHCR annual rent registration deadline guide covers the timing question. The ORRA / ARRO guide covers the filing workflow. Use those guides for detailed deadline and filing steps while keeping form selection tied to source-record readiness.
The key owner-side question is whether the April 1 status of buildings and apartments is reflected cleanly in the source records. Before filing, teams should know who owns ORRA/ARRO access, which buildings are in scope, which apartments require review, and which report will be treated as the source of truth.
Practical rule: annual registration work should not wait until the filing screen is open. Clean the building, apartment, tenant, lease, rent, exemption, ownership, and report records before final filing work begins.
Chapter 4
Ownership and Portfolio Change Forms
Ownership and management changes create their own form workflow. HCR's RA-44 form is used to report a change in ownership or address for an owner or managing agent. HCR's rent registration materials also point owners to RA-44 as a related resource for ownership or address changes.
This is why acquisitions, management transitions, and portfolio restructures can create rent-stabilized cleanup work even before the next renewal or annual registration deadline. A building may move into a new operating structure, but HCR records, Yardi property records, tenant records, user access, billing ownership, and reporting responsibility still need to line up.
When this handoff is missed, the problem may not appear until a filing, tenant question, renewal package, or internal report fails to match the current owner or managing agent record. The safest process is to treat RA-44 review as part of portfolio onboarding, not as a side task after the operating records are already live.
Transition records to verify
Owner or managing agent name and address.
Building registration number and portfolio grouping.
ORRA/ARRO account access and internal user ownership.
Yardi property setup, reporting ownership, and document storage.
Any open renewal, registration, surcharge, MCI, IAI, or tenant-response workflow.
Chapter 5
IAI, MCI, and Rent Adjustment Forms
Some owner forms are connected to rent adjustments, improvements, service changes, or regulated rent history. HCR's Tenant/Owner Forms page lists owner-facing items such as MBR applications, RTP-19, RN-19N, RA-79, and other owner rent regulation applications. Owners should verify which forms apply to the property type, rent program, and current HCR process before taking action.
HCR's IAI and MCI improvements page explains that owners can access IAI filing procedures through current operational bulletins and FAQs, and it references the Owner Rent Regulation Applications system for IAI notification workflows. That makes access, support records, and source-data review just as important as the form name.
For teams using Yardi, these workflows should connect to property, unit, lease, charge, improvement, document, and reporting records. A form may capture the official submission or notice, but the operating evidence usually lives across multiple parts of the system and document trail.
Workflow
Common Form or Application Area
Record Readiness Question
Restoring rent after service restoration
RTP-19
Do service, tenant, order, and charge records support the request?
Individual apartment improvements
RN-19N / ORRA
Are improvement records, documents, photos, consent, and approvals retained?
Major capital improvements
RA-79 and related MCI materials
Do building, project expense, tenant, and document records support the workflow?
Maximum base rent workflows
MBR application materials
Are rent control records, building records, and deadlines being tracked separately?
Chapter 6
Yardi Records to Review First
For Yardi users, the form is rarely the beginning of the workflow. The better starting point is the source record: property, building, unit, tenant, lease, rent, charge, registration, document, and reporting data. If those records do not match, the form may be technically completed but operationally weak.
Before using a DHCR form or online application, the team should confirm which Yardi report or export will be treated as the review source. If the team is using a spreadsheet after export, it should also know which corrections will be made back in Yardi and which are only temporary filing notes.
The same principle applies to renewals, riders, annual registration, ownership changes, surcharge review, and improvement workflows. A form can capture the final submission or package, but the system needs to preserve the history that explains why the form was prepared that way.
Source recordsConfirm property, unit, tenant, lease, rent, charge, and ownership data before form prep starts.
Report logicUse reports as review tools, not automatic approval. Test output against known records.
Document trailStore final forms, support, approvals, and correspondence where future reviewers can find them.
Chapter 7
Common Form Workflow Breakdowns
Form workflows break down when teams treat the form as a one-time task instead of the visible output of a recordkeeping process. The most common issues are stale form versions, unclear ownership, missing access, mismatched rent fields, weak document retention, and corrections that never make it back into the source system.
One pattern is version drift. A saved form packet gets reused because it worked last year, but HCR instructions, online applications, forms, or related guidance may have changed. Another pattern is source drift: the PDF, the Yardi report, the retained lease document, and the spreadsheet no longer tell the same story.
The fix is not to make the form process more complicated. It is to make ownership clearer. Each workflow should have a responsible owner, source report, review path, approval step, and document retention rule before the deadline or lease package creates urgency.
Breakdowns to watch for
Saved forms are reused without checking HCR's current source.
ORRA/ARRO access is discovered too late in the filing cycle.
Lease packages are prepared before rent fields and rider requirements are reviewed.
Ownership changes are not reflected across HCR records, Yardi records, and internal reports.
Report exceptions are fixed in spreadsheets but not corrected in the source workflow.
Final forms are stored apart from the records that explain them.
Chapter 8
Owner Forms Readiness Checklist
Use this checklist before relying on a DHCR form, sending a lease package, filing in ORRA/ARRO, reporting an ownership change, or preparing an improvement-related owner workflow. It is designed to keep form work connected to source records and document retention.
Verify the current form or online application from an official HCR source.
Confirm whether the workflow is a lease package, annual registration, ownership change, rent adjustment, or improvement-related filing.
Confirm who owns the workflow internally and who approves the final treatment.
Review property, building, unit, tenant, lease, rent, charge, and ownership records before form prep.
Confirm ORRA/ARRO access where an online application or filing environment is involved.
Test the source report against known records before relying on an export.
Resolve repeat corrections in Yardi where possible instead of only editing a spreadsheet.
Store final forms, source support, approvals, and correspondence together.
Flag legal or compliance interpretation questions for the appropriate reviewer before submission or resident communication.
Document the final workflow so the same question is easier to answer next year.
Which DHCR forms matter most for rent-stabilized renewal work?
RTP-8 and RA-LR1 are the main renewal package forms for this owner workflow. RTP-8 handles the renewal lease offer, while RA-LR1 is the New York City lease rider that must be attached and served with rent-stabilized vacancy or renewal leases.
Is ORRA the same thing as a DHCR form?
No. ORRA is the Owner Rent Regulation Applications environment. Some owner workflows are completed through online applications rather than only through standalone PDF forms, so access and user ownership should be checked early.
What is RA-44 used for?
RA-44 is HCR's report of change in ownership or address. Owners should review it when ownership, managing agent, or owner address information changes and should verify current filing instructions directly with HCR.
How does this forms library connect to Yardi?
For teams using Yardi, forms readiness depends on clean property, unit, tenant, lease, rent, charge, registration, reporting, user access, and document records before forms are filed, sent, or retained.
Sources
Official Sources to Verify Before Using DHCR Forms
This guide is operational guidance, not legal advice. Owners should verify current forms, filing requirements, online application access, and legal obligations with HCR sources and counsel before filing, sending, or relying on any form.
BC Solutions helps Yardi users align property, unit, tenant, lease, rent, registration, reporting, access, and document workflows before forms become filing, renewal, or resident communication issues.
