A resident moves in on a Saturday. By Tuesday they have asked where the bins go, how to report a broken cupboard door, whether the parking space is assigned, and what day rent comes out.

None of those questions is difficult. All of them are avoidable. The welcome packet is the document that answers them once, in writing, before they are asked.

It is not the lease. It is not a compliance document. It is the practical guide to living in the property, and it is one of the simplest pieces of resident communication a manager can produce.

For the internal side of getting a new tenancy set up, meaning records, system configuration and the first billing cycle, see the guide to tenant onboarding. This page is about what the resident receives.

Contract vs Practical Guide

Worth stating first, because most weak welcome packets fail by trying to be something else.

• Not a substitute for the lease. The lease and any documents incorporated into it govern. The packet explains practicalities and points back to the lease for anything that creates an obligation. Say in the packet that the lease controls, and avoid restating lease terms in a way that could read differently from the document itself.

• Not a place for required disclosures. Disclosures that must be delivered in a particular form, at a particular time, or with acknowledgement, should be handled through the leasing documentation in line with applicable requirements, with a record of delivery. Requirements vary by jurisdiction, so confirm what applies rather than assuming a welcome packet satisfies them.

• Not a rules enforcement document. Community rules that carry consequences need to be enforceable under the lease or a document incorporated into it. The packet can summarise them and point to the binding version.

• Not a marketing brochure. A resident who has already signed does not need to be sold to. They need to know how the boiler works.

The useful test: if a sentence creates or changes an obligation, it belongs in a lease document rather than in the packet.

What to Include

Six sections cover most of what a new resident actually needs.

1. Contacts and hours. Who to call, for what, and when. Office hours, the maintenance line, the emergency number and what qualifies as an emergency. Make the emergency definition explicit, because otherwise you will receive emergency calls about a dripping tap and no call at all about a smell of gas.

2. Rent and payments. When rent is due, the accepted payment methods, how to set up the portal or automatic payment, and what reference to use. Point to the lease for late fee terms rather than restating them, since those are contractual. Where the packet explains the payment options available, it should match what the resident will actually see when they go to pay rent.

3. Maintenance. How to submit a request, what information helps, what response to expect, and what the resident is responsible for. Include the small things that generate the most calls: resetting a tripped breaker, finding the stopcock, replacing filters, what to do if they lock themselves out.

4. The building and the unit. Bin days and location, recycling, parking arrangements, mail and parcel handling, laundry, storage, communal areas, guest access, quiet hours, and anything specific to the building.

5. Utilities and services. Which accounts are the resident's, which are included, who the providers are, and where the meters are.

6. What happens next. The condition report and how to return it, the inspection schedule, when renewal will be discussed, and how notice works if they decide to leave. Setting the renewal expectation at move-in makes the conversation twelve months later routine rather than a surprise, because the renewal offer then arrives as something the resident was told to expect.

The Condition Report Is the Most Important Thing in the Packet

Everything else in the packet saves time. This one saves money.

The move-in condition report can provide an important baseline when the property's condition is assessed at move-out and any permitted deposit deductions are considered. A resident who completes it carefully, notes existing marks and damage, and returns it promptly creates a clear record of the unit's condition at the start of the tenancy. If the manager never receives it back, the file may lack the resident's documented confirmation of the starting condition.

So the packet should:

• Explain what the report is for, in one sentence

• Say when it must be returned

• Encourage photographs

• Say that the resident should record anything at all, however minor

• Confirm what happens after it is returned

Make it easy to complete and easy to return. A form that has to be printed, filled in by hand, scanned and emailed will come back late or not at all.

This connects directly to the other end of the tenancy, where the move-out instructions letter refers back to this same report.

Getting It Read

A twenty-page PDF sent as an email attachment on move-in day is not a welcome packet. It is a file nobody opens.

• Keep it short. Include the information residents are most likely to use, with the most important items first. A document long enough to feel like a manual tends to be filed rather than read.

• Front-load the useful part. Contacts, rent, maintenance and bins in the first two pages. Everything else after.

• Use headings a person can scan. A resident looking for the bin day should find it in ten seconds.

• Send it before move-in day, not on it. Someone unpacking boxes will not read a document. Someone deciding whether to book a removal van will.

• Make the digital version the primary one. A printed copy in the unit is a courtesy; the version they can search on a phone at 9pm is the one that gets used.

• Keep one version per property. Bin days, parking and access differ by building. A single portfolio-wide packet may be inaccurate for properties with different arrangements, which teaches residents to check elsewhere.

What to Leave Out

• Anything requiring a signature. If it needs acknowledging, it belongs in the leasing paperwork with a record of delivery.

• Restated lease clauses. A summary that differs from the lease by a word creates ambiguity about which one applies.

• Late fee amounts, deposit deductions and charge schedules. Contractual, and they change. Point to the lease.

• Rules you do not enforce. A packet listing rules nobody applies teaches the resident that none of it is serious.

• Legal notice periods. Notice requirements for ending a tenancy vary by jurisdiction and change. Say that notice requirements are set out in the lease and applicable law, and point there.

• Staff names. Roles and numbers age better than individuals.

• Information you cannot keep current. A packet listing a contractor who no longer works for you is worse than one that says to call the maintenance line.

The Packet Outline

A working structure. Adjust for property type and portfolio.

What This Prevents

The packet earns its place in the first month.

Most first-month contact from a new resident is informational rather than a problem: where something is, how something works, who to call. Each of those is a question the packet can answer once instead of a member of staff answering it repeatedly.

The second-order effect matters more. A resident whose early questions were answered without friction starts the tenancy with the impression that the operation is organised. That impression is doing work at renewal, at the first maintenance delay, and at the first rent increase.

It also supports the record. Where a resident says they were never told about parking, bin days or the maintenance process, the packet and the date it was sent form part of the evidence, alongside the lease and any other documents provided.

Keeping It Current

The packet can go out of date quickly.

Review it when any of these changes: a contractor or service provider, bin or recycling arrangements, the payment method or portal, office hours, parking rules, building access, or the maintenance reporting process.

A yearly review catches the rest. Set a date, check every phone number and link, and reissue to existing residents when something material changes rather than waiting for the next move-in.

Where the packet is issued as part of a tracked onboarding process, the version sent and the date it went out sit against the resident record, which is what makes "we told you at move-in" a fact rather than a recollection.

Frequently Asked Questions

1. What should be included in a tenant welcome packet?
Contacts and hours including what qualifies as an emergency, rent due dates and payment methods, how to report maintenance and what to expect, unit information such as shut-offs and appliances, building arrangements for bins, parking and mail, utility accounts and meter locations, the condition report, a summary of community rules, and what happens next in terms of inspections and renewal.

2. Is a welcome packet the same as the lease?
No. The lease is the binding agreement. The welcome packet is a practical guide that explains how things work day to day and points back to the lease for anything that creates an obligation. The lease and any documents incorporated into it govern.

3. Should required disclosures go in the welcome packet?
Required disclosures should be handled through the leasing documentation in line with applicable requirements, with a record of delivery. Requirements vary by jurisdiction, so confirm what applies rather than assuming a welcome packet satisfies them.

4. When should the welcome packet be sent?
Before move-in day rather than on it. A resident in the middle of moving will not read it, while a resident preparing to move has time to act on what it says.

5. How long should a tenant welcome packet be?
Short enough to be read, with the most-used information first. The right length depends on the property, services and amount of information residents need. 

6. Should every property have the same packet?
Not entirely. Bins, parking, access and building arrangements differ, so a single portfolio-wide packet may be inaccurate for some properties. Keep a common structure and vary the property-specific sections.

The Document That Answers Questions Before They Arrive

A welcome packet is not a courtesy. It is the operational document that decides how much of your first month with a new resident is spent on questions that have a fixed answer.

Written once per property, kept current, and sent before move-in, it gives residents a practical reference from the start of the tenancy.

RIOO handles the move-in side of a tenancy as part of the leasing workflow, with move-ins and move-outs and leasing management connected to the underlying property and accounting records.

Note: Guidance in this article is general and does not constitute legal advice. Disclosure requirements, notice periods, permitted charges and the treatment of community rules vary by state, locality and lease. Confirm what applies to each property, and deliver required disclosures through the leasing documentation rather than a welcome packet.