Building Co. approvals: who actually clears your Tokyo booking

Two days after you book a 28-night stay at a Tokyo furnished studio, the operator emails back. "Apologies, the building doesn't allow stays under 30 nights. Could you adjust to 30?" You ask why. The operator writes a polite paragraph that does not actually name a rule. You read it twice and notice nobody has cited a person, a clause, or a document. The vagueness is the signal. Almost nobody at the operator's company has spoken to the landlord about your specific booking, ever. The decision came from somewhere else.

Most refusals on a Tokyo monthly mansion (manshon — mid-rise concrete apartment; never translate as "mansion") come from a single layer in the chain. Knowing which layer it is changes whether you keep pushing, escalate, or accept and move on. Four companies sit between you and the unit, and your booking request has to clear most of them. But the layer that does the actual deciding is rarely the one the operator names.

The four-layer stack you are sitting at the bottom of

Four parties sit in line between you and the unit you want to book. The order matters.

The landlord. Owns the building, holds title, collects monthly rent under a long-term master lease (the long-term lease the operator signs with the building owner, separate from your short-term lease). Barely thinks about who occupies the unit on any given night.
The Building Co. Holds that master lease. Took on the vacancy risk in exchange for a discount off the landlord's "asking" rent. Wrote the sublease handbook every operator inside the building has to follow. This is the layer that most often says no.
The operator. Signs a sublease with the Building Co. for individual units. Runs the booking calendar, fields your email, and handles check-in. Can sometimes flex on rate and dates, but not on building rules.
You. The midterm guest with a booking request that has to clear all three layers above before it lands.

The parent piece on master-lease economics walks the cash flow up that chain. This piece walks the approval flow down it. The two are not the same path. Cash moves up the stack one transaction at a time. Approvals get delegated downward and then escalated upward only when a request falls outside what the lower layer is authorized to handle.

What the Building Co. is actually doing

A Building Co. is not a property manager. It is not a hotel chain. It is the master-lease holder, the company carrying the building's main financial risk. The Building Co. pays the landlord the same amount whether the units fill or sit empty. Their entire business model is making more money on the sublease side than they pay on the master-lease side.

Two consequences fall out of that arrangement and explain almost everything the Building Co. does.

The first is that they are extraordinarily sensitive to regulatory risk on the building. A 27-night stay on a building licensed as residential creates a hotel-act problem (see licensing tiers). A pet on a no-pet building creates a damage risk the master lease likely does not cover. A four-person stay in a studio creates a fire-code problem the ward office could flag on inspection. Any of these costs the Building Co. orders of magnitude more than the lost revenue from refusing the booking. The math is one-sided in favor of "no."

The second is that they delegate the operator-level decisions through a written handbook. That handbook is the document the operator reads when your email lands. It is rarely public. It is typically 20 to 60 pages. It governs minimum stay length, allowable guest categories, smoking, pets, mid-stay extensions, key handover, damage definitions, and overnight visitors. The customer-facing terms on the booking page are a short translation of the handbook. Anything the operator can do without asking the Building Co. is in there. Anything not in there has to go up the stack.

So when the operator types "the building won't allow it," they almost always mean a clause in the handbook. The Building Co. wrote the rule. The landlord delegated authority to the Building Co. five or seven years ago when the master lease was signed. The operator agreed to follow the rules as a condition of getting the sublease in the first place.

Why each layer has the rules it has

The rules each layer holds are not arbitrary. They reflect what each party is being paid to manage.

The landlord is paid to take a passive cash stream and not have to think about the unit. They wrote no rules about your stay. That level of detail is exactly what they offloaded to the Building Co. when they signed the master lease. Anything the operator frames as "the landlord said" is the operator translating Building Co. policy into a name the customer is more likely to accept.

The Building Co. is paid to absorb vacancy risk and make sure the building's residential character stays intact for the master-lease term. So they wrote a conservative handbook. They cannot afford a regulatory blowback. They cannot afford a damage event their insurance does not cover. They cannot afford the building's residential classification getting downgraded by the ward office. The handbook protects against all three.

The operator is paid to fill the calendar with the highest-quality customers the handbook allows. The handbook sets what they can say yes to. Within the bounds, they can negotiate rates, waive specific fees when the math works, and route exception requests upward. Outside the bounds, they cannot say yes, even when they want to. So they say "the building" because saying "the handbook" exposes the layer above. "The building" reads to a customer as "the wall, the staircase, the literal physical thing." It is the operator borrowing legitimacy from something tangible.

You are paid nothing. You hold the booking request. The operator's reply is the operator's compressed answer to three questions. Does the handbook permit this outright? Is the handbook flexible on this? Does the handbook prohibit this outright? Each of those three answers leads to a different response shape from the operator.

A taxonomy of the no, sorted by whether it moves

Refusals fall into three buckets, and the bucket determines whether escalation is worth your time.

Hard handbook prohibitions. Stay-length minimums tied to the building's residential license never move. The Building Co. cannot wave 25 nights through without putting the master lease at risk on the next ward audit. Pet bans usually do not move. Smoking bans never move. Headcount limits above the unit's stated capacity never move. If the operator's answer references one of these categories, escalation is not a path. The Building Co. wrote the rule for a reason that has nothing to do with you. Everything to do with their next master-lease renewal.
Handbook-discretionary items. Mid-stay extensions, late check-out, early check-in, and back-to-back-booking fee waivers are things the operator can decide on their own. The handbook sets the bounds. Same with holding luggage between bookings. These items move with the right framing. Ask for the specific outcome and the reason. A seven-night extension at standard rate is a different request from a seven-night extension at 10% off. The operator may say yes to one and no to the other.
Items that look hard but are sometimes soft. Overnight visitors are the main one. Most handbooks ban un-registered overnight guests, but most operators will register a named visitor on a 48-hour written request. A flight itinerary or hotel transfer attached to the request helps. The Building Co. cares about un-registered guests because they are an unknown risk. A registered guest is a known one.

A short hidden category is worth naming separately: items that look soft but are hard. The departure cleaning fee waiver is the textbook example (see cleaning fee mechanics). The operator's margin lives in that line. A single waiver does not endanger the building. It endangers the operator's spreadsheet. The spreadsheet decides whether the operator gets to keep the master lease next year. So a fee waiver looks like something the operator should be able to do. But it is one of the rarest yeses you will get.

How to phrase an escalation that actually moves

When you push back, frame the question to the decision-maker who can actually say yes.

A push that names the Building Co. directly works. Something like "Can you ask the master-lease desk whether a one-time exception applies for a 28-night academic conference stay?" gets escalated. The operator will sometimes route it up. Master-lease desks have written-procedure exceptions for specific guest categories: conferences, corporate relocations, medical stays. Maybe 5 to 10 percent of one-time exception requests clear this way. Naming the Building Co. makes the request readable to the people who can actually answer it.

A push that names "the landlord" never works. The landlord has no role in this decision and never will. The operator will not pretend to route the message because the landlord cannot say yes if the message arrives. The request sits.

A push that runs the math works when the calendar is empty. Something like "I see the unit is open through November 14. If I extend by 9 nights at standard rate, your sublease cost is covered for the month; otherwise the unit sits empty." The operator may run the numbers. Then they route an extension request upstream with the specific dates and rate. That request clears faster than a generic "can I extend?" Being specific makes it easier for the upstream desk to approve. It gives them something concrete to say yes to.

A push that cites a regulator never works. Saying "the 30-night rule is just a 旅館業法 (ryokan-gyō-hō — Ryokan Business Act, the public-health statute that licenses lodging buildings) thing" reveals that you have read the statute. It also reveals that you have missed the actual cost. The Building Co. cannot afford a single 28-night stay even if they wanted to. The ward office samples occupancy data on residential buildings annually. An irregularity in that data costs the building's residential classification, which costs the Building Co. several hundred million yen of master-lease value. Your two-night reduction would not pay for it.

Timing matters as much as phrasing

When you ask matters almost as much as how you ask. The upstream desks at the Building Co. work on different time scales than the operator does.

The operator answers within 1 to 2 business days on routine requests. An extension that fits the handbook clearly gets a same-day or next-day yes-or-no. A rate negotiation within the operator's discretion gets the same. The operator's email queue is not the bottleneck.

The Building Co.'s master-lease desk works on a 3-to-10-business-day cycle for exception requests. They batch decisions. They route through a compliance review when the request touches anything regulatory. A booking that needs Building Co. approval should land at the operator's inbox 10 business days before the check-in date, not 3. If you send the request late, the operator may have to refuse it even if it would have cleared on the merits. They simply cannot route it up and back in time.

The landlord, when they do enter the picture (which is rare), works on a 30-day cycle if they work on any cycle at all. The landlord side does not get involved in booking-level decisions. They get involved when the Building Co. wants to renegotiate the master lease, change the building's classification, or escalate a recurring policy issue. None of those happen on a guest's booking timeline.

So a clean rule of thumb: extension requests 10 business days out, exception requests 14 business days out, anything novel 21 business days out. The upstream desks need time to say yes to a request the lower layer would otherwise have to refuse for lack of process.

A short note on the master-lease renewal cycle

One detail about how the Building Co. thinks helps make the rest of their decisions legible. The master lease with the landlord runs for a fixed term, typically 5 to 10 years. The Building Co. wants the landlord to renew that lease at the end of the term. They want renewal on terms similar to or better than the existing ones. They make every decision in the meantime with that renewal in mind.

That means everything visible to the landlord matters. Building condition matters. Neighborhood reputation matters. Whether any guest under any operator's sublease has ever caused a complaint to the building management company matters. The handbook is the Building Co.'s way of preempting any single guest from being the reason renewal becomes a negotiation. A 27-night stay that the ward office flags is not just a one-time fine. It is a black mark on the master-lease renewal file the landlord will see in three years.

So when you read a handbook prohibition that seems disproportionate to the actual risk of your specific stay, the prohibition is not aimed at you. It is aimed at the file. The Building Co. is protecting an asset whose value depends on the file being clean at renewal time.

How different operators interpret the same handbook

Two operators with subleases inside the same building will sometimes give you different answers to the same question. The handbook does not change between them. What changes is how much discretion each operator has carved out for themselves on the borderline cases.

A few operator behaviors that come up regularly:

Conservative operator. Reads the handbook strictly. Any ambiguity gets pushed up the stack. They will say no to a 28-night booking even if the handbook only requires 30, because they are not willing to interpret. Slow on email. Long lead times for any non-default request.
Bounded-discretion operator. Has worked out, with the Building Co.'s master-lease desk, a few specific exceptions the operator can apply without checking each time. Academic conferences. Corporate relocations from specific employer lists. Medical-treatment stays with documentation. They will reach for the carve-out if your request fits a pattern they have already cleared.
Aggressive operator. Pushes the edges of the handbook on the customer's behalf. Sometimes wins, sometimes the Building Co. pulls the sublease at the next renewal. Less common in the Tokyo midterm furnished segment than in the short-stay hotel-license segment.

You will not know which type your operator is until you ask a question with some ambiguity in it. The shape of their reply tells you. A long, hedged email with "let me check with the building" usually means conservative or bounded-discretion. A short "yes" or "no" with a concrete reason means something else. They have already worked out the answer with the Building Co. and can speak for them.

A short field guide to working the stack

Two practical reads come out of this structure.

The first is to ask which layer said no. The phrasing matters; keep it neutral. "Is this a building-side rule or operator-side discretion?" Most operators will answer plainly. You learn whether to stop pushing or push harder. A "building-side" answer means escalating up. An "operator-side" answer means working the math on this specific stay. Either way, you stop wasting energy on the wrong layer.

The second is that the Building Co.'s name is often discoverable. The company name is sometimes printed on the building's mailbox panel or on the elevator inspection notice. It is also searchable in the Houmukyoku (法務局 — Legal Affairs Bureau, the national land-registry office) property registry for ¥600 per pull. If you are negotiating a long stay or a complex booking, the name is worth knowing. It tells you which handbook your operator works inside. It also tells you whether other operators on the same building have been more flexible. Same handbook, different translator on the customer side, different answer. A 90-night academic researcher booking is a different conversation when you can say something concrete. Like: "I notice unit 305 also lists with a different operator and they confirmed availability."

A practical follow-on. Once you know the Building Co.'s name, ask the operator which other operators list units in the same building. This piece of information sometimes opens a route around a refusal. A second operator with a different read of the handbook on the same borderline item is not the operator violating the handbook. It is the operator using their own exceptions.

A maxim for the next time the no comes back

Here is the short version, the one worth carrying with you the next time an operator emails back with a refusal you do not understand:

The landlord owns the unit. They do not enter the conversation.
The Building Co. owns the rules. They wrote the handbook the operator reads.
The operator owns the calendar. They have a little room to say yes within the handbook.
You own the booking request. The reply you got is the operator's compressed answer.

When the no comes back, the layer that said it is what determines whether you keep asking. A "building-side" no means escalating with the Building Co.'s name and a specific carve-out request. An "operator-side" no means working the math on the specific stay. A "landlord" no, if it ever comes, is the operator hiding the actual decision-maker. The right move is to ask the next question one layer up.

— HalfKey lists furnished Tokyo apartments on residential teiki-shakka leases for stays of 30 days to 12 months. Browse listings for your dates.