Before You Accept a Month Long Stay: Run the Legal Gate

A guest asks for a month. The revenue looks steady, the turnover disappears and the booking is sitting there waiting for an answer. Before you give one, note that stay length can change which body of law applies to the arrangement, and that is not something you can settle from a booking screen.

This page does not tell you whether to accept. It sets out the gate you run first, the thresholds that exist in different systems, and why the number everybody quotes is not one number at all.

TL;DR

• There is no single thirty day line. Different systems use different thresholds.
• The IRS treats a residence rented fewer than 15 days differently from other cases.
• Salt Lake City requires a minimum of two consecutive nights and caps a licence at 200 nights.
• Longer stays can engage tenancy law, which is local and is not decided by a platform.
• Pause the acceptance, document the local position, then accept or decline.

Key facts this decision rests on

The Thirty Day Rule does not Exist

Ask five hosts where short term becomes long term and you will hear thirty days from at least four of them. The number is real in some places and meaningless in others, and it comes from different systems that do not agree with each other.

One number. Several unrelated systems.

Three systems, three sets of thresholds

Federal tax rules use their own day counts. Local licensing rules use theirs. Tenancy law uses another set again, and it is the one that decides whether your guest becomes a tenant.

What the Federal Tax Rules Actually Say

The federal thresholds are worth knowing because they are the ones most often mistaken for tenancy rules. They are not tenancy rules and they decide nothing about your guest's status.

The short rental exception

The IRS states a rule for a dwelling unit used as a residence and rented for fewer than 15 days. In that case the guidance is to not report any of the rental income and to not deduct any expenses as rental expenses.

The personal use test

The IRS also describes a personal use test using 10% of the total days you rent the unit to others at a fair rental price, and separately describes a vacation home rented at fair rental value for more than 300 days during the year.

Three federal numbers. None of them is thirty.

The IRS further states that residential rental property includes any real property where 80% or more of the gross rental income for the tax year is from dwelling units. That is a classification rule, and again it is not about your guest.

Licensing Rules Use Their Own Numbers Too

Local licensing adds a third set of thresholds, and they can run in the opposite direction from what you expect.

Salt Lake City states that short term rental stays must be for a minimum of two consecutive nights, and that each licensed short term rental is limited to 200 rental nights per calendar year.

A floor and a ceiling, in the same rule set.

Read those two together against a month long booking. A single long stay consumes a substantial share of an annual night cap, which is a licensing consequence rather than a tenancy one.

Three systems, three thresholds, and only one of them is about your guest.

The Question that Actually Matters

Strip away the tax and licensing detail and one question remains. At what point, under the law that governs your address, does an occupant stop being a guest?

That is a local legal question. Only.

Why it cannot be answered generally

Tenancy protections are set by state, province, city or some combination. The trigger may be a number of nights, the presence of an agreement, the establishment of residence, or something else entirely.

A platform setting does not decide it. A booking length does not decide it by itself. What decides it is local law applied to your specific arrangement, which is why the gate exists.

Run the Gate before you Answer the Guest

The gate is five questions. None of them requires you to be a lawyer, and all of them require you to stop before answering.

Five questions. One pause. Then decide.

Question two is the one that needs a professional if the answer is not clearly documented by your local authority. That is not a counsel of perfection, it is the point where a wrong guess is expensive and slow to reverse.

Document the Controls before you Accept

If the legal position is clear and permits the stay, there is still a documentation step. Accepting a long stay on the same terms as a weekend booking leaves gaps you will notice later.

• The agreement or terms local law requires for a stay of that length.
• How and when payment is collected across the period.
• What your insurance covers for an occupancy of that duration.
• The condition record at the start of the stay, dated.
• The process if the occupant does not leave at the end.

The last one is the one nobody writes down.

It is also the one that matters most if things go wrong. Knowing in advance what the process is, and whether it is a landlord process or a guest process, changes what you agree to today.

Accept or Decline, and Record Which

The gate produces a decision and the decision deserves a record. Both outcomes are legitimate, and a declined booking with a reason is a better outcome than an accepted one with a shrug.

Accept

You accept when local law is documented, the licence permits it, the controls are in place and the night allowance still works for your year.

Decline

You decline when any of those is unresolved and cannot be resolved before the guest needs an answer. Speed is the guest's constraint, not a reason to skip the gate.

An unresolved question is a decline, not a maybe.

The licensing side of this sits on the rules by city hub, which routes you to the authority for your address. If you are in Austin specifically, the Austin licence guide covers the process there. If a long stay is under consideration because bookings are weak, run the booking layer audit first, because a month long stay is a large commitment to make for an undiagnosed reason.

Pause. Document. Then decide.

Four Reasons Hosts Skip This Gate

The gate is short. It still gets skipped, and the reasons are predictable enough to name.

The booking looks like easy money

A month of continuous occupancy with no turnover is genuinely attractive. That is exactly why it deserves a pause. Attractive offers are the ones people accept without checking.

Easy revenue. Slow to reverse.

Somebody said thirty days is fine

The number circulates because it is true somewhere. It is not true everywhere, and the person who told you is unlikely to be operating under your local law.

Their jurisdiction is not your jurisdiction.

The guest is applying time pressure

A deadline set by somebody else is not new information about your legal position. If the gate is incomplete when the deadline arrives, the deadline decides for you, and it decides badly.

Their urgency. Your property.

It has worked before

A previous long stay that ended cleanly tells you about one occupant, not about the law. The risk here is not frequent. It is severe, which is a different thing and needs a different response.

Rare and severe still needs a gate.

What a Completed Gate Buys you

Running the gate once is not wasted effort even when you decline. You now hold a documented local position that the next request can reuse.

Do it once. Reuse it many times.

That position ages, so give it a review date like any other source card. Tenancy law changes and licensing rules change, and a position from two years ago is a starting point rather than an answer.

Documented, dated, and due for review.

The second benefit is faster decisions. With the local position already documented, the next month long request is a two minute check against controls rather than a research project.

The first gate is slow. The rest are quick.

The third is that you can say no cleanly. A host who knows why they decline gives a clear answer quickly, which is better for the guest than a slow maybe that ends in a decline anyway.

A fast no beats a slow maybe.

Write the rule while nothing is pending.

Check the law once. Date the answer.

Reuse it. Review it.

Decline anything the gate cannot clear.

That is the whole gate.

It costs one booking at most.

It protects the property itself.

Those are not the same size.

A last word on proportion. Most long stays end exactly as expected, with a guest who leaves on the agreed day. The gate is not a prediction that yours will not. It is a response to how much is at stake in the case where something does go wrong, and how little it costs to check first.

Most stays end fine.

The gate is for the ones that do not.

Cheap to run. Hard to undo.

That is the whole case for it.

Run it once. Date it. Move on.

Then answer the guest.

Ask the length.

Check the law.

Check the licence.

Check the night cap.

Check the agreement.

Five checks. One pause.

Say yes or say no.

Write down which.

Add the date.

Close the file.

Reuse it next time.

Review it next year.

Questions Hosts Ask About This Decision

Operator Notes

Three notes below are reserved for Sean and are deliberately unfilled. Nothing has been written into them on his behalf, and no view below is attributed to him.

• The local checks Sean completes before accepting a month long stay: ______________________________.
• What Sean documents at the start of a longer occupancy: ______________________________.
• When Sean declines rather than waiting for a legal answer: ______________________________.