New York City Registration Renewal and Record Keeping

OSE registration renewal should be a calendar routine, started before expiry, with documents gathered early and the renewal confirmation filed on receipt. Hosts who treat renewal as an emergency on the expiry date risk a lapse, during which platforms may block listings and bookings may need cancelling. A lapse in peak season costs more than the time saved by delaying renewal, and it creates a gap in the registration history that later queries may notice.

Set the renewal reminder at least a season before expiry, or at the interval OSE guidance suggests, whichever is earlier. Note the reminder in the unit file alongside the original registration date and any update history. When renewal is complete, update every listing's registration details if they changed, and check platform verification again. A renewed registration that listings do not reflect is only half updated.

Between renewals, hosts must update registration where occupancy, ownership, tenancy or building situation changes materially. A host who moves, a tenant host whose lease changes, or an owner who changes the occupying household should check the update rule before operating under the new situation. Operating under an outdated registration that describes a previous occupant or situation risks revocation and enforcement, even if the original registration was valid.

Updates should be documented like renewals: the change, the date, the OSE update submitted, and the confirmation received. Keep that update history with the original registration, so the unit's registration story reads as a continuous, dated record rather than a single old confirmation plus unexplained changes. A continuous record answers queries; a fragmented record invites them.

Stay logs for hosted stays should record, per stay, the dates, guest count and names as permitted, channel, booking reference, payout reference, and a note confirming host presence. That presence note, kept contemporaneously, is the record that distinguishes a hosted stay from an unhosted pattern if occupancy is ever queried. A log that records only dates and income cannot prove presence, while a log with a presence note per stay can.

Guest privacy matters in logs. Record only what is needed for compliance and operations, store logs securely, and do not share guest details beyond what a booking, safety or legal duty requires. A tidy, minimal log, kept securely, serves both compliance and privacy better than an expansive guest dossier.

Monthly, reconcile the stay log with platform statements and payout records, noting cancellations, alterations and refunds in the month they occur. That monthly habit catches guest-count errors, duplicate listings and platform reporting gaps while messages are fresh. Annually, review total hosted nights, guest patterns, registration validity and building permission together, before the next season, and note the review date.

Annual review should also check whether the hosting pattern has drifted. A hosted operation that gradually adds extra guests, extends stays informally, or lets while the host is away has drifted from its registered pattern, even if each drift seemed small at the time. An annual pattern check, comparing actual stays with the registered hosted model, catches drift before it becomes enforcement.

Registration records should sit alongside building and lease permission records in the unit file. A registered hosted stay in a building that bans short lets, or under a lease that forbids hosting, still faces private enforcement. Hosts should recheck building and lease permission at renewal time, not only at first registration, since building rules and leases change. A renewal that updates OSE registration but ignores a new building ban leaves a gap.

Safety records belong in the same file: alarm checks, exit information and emergency contacts for the unit. Safety checks dated and filed show responsible hosting, and they help answer any safety query that accompanies a registration or building enquiry. A host file that covers registration, building, lease and safety together is a complete compliance picture.

Recheck OSE guidance on nyc.gov before each season and at renewal, and update the unit file with check dates. Archive old listings, old registration versions and superseded guest information, rather than leaving them live or mixed with current records. A clean file, with current documents prominent and old documents archived but retrievable, is easier to use in a query than a large undifferentiated folder.

This guide is general information only, last verified on 26 October 2026.