You sign the lease, you get a login, and you open the portal expecting to find out how the building works. There is a button to pay rent and a button to submit a maintenance request. There is a documents tab, and the documents tab is empty.
So you learn the building the way people have always learned buildings. You watch what your neighbours put out on which day. You guess at the bins. You discover on the third Tuesday that the elevator needed to be booked. You find out what the intercom does by having a delivery driver give up on you. Somewhere around week six you have assembled, through trial and minor humiliation, roughly the information the building could have handed you on day one.
The obvious reading of this is that you got a bad landlord. The more useful reading is that you got a normal one.
The gap has been measured
AppFolio's 2026 research found that 78% of renters say convenient services matter when they choose a home, and only 33% believe their property manager will actually deliver them. That 45-point gap is not a customer service problem. It is the difference between what an industry sells and what it operates, and it is remarkably stable across operators of very different quality.
The consequence shows up on a predictable schedule. Resident sentiment does not decline gradually through a tenancy — it drops sharply and bottoms out around the thirty-day mark, which is precisely when the accumulated small confusions of the first month have resolved into a general impression that nobody here is paying attention. A non-renewal costs an operator somewhere between four and seven thousand dollars per unit once make-ready, vacancy and re-leasing are counted. Roughly half of all units in a market-rate portfolio turn every year.
The industry has built the shelf. It has not stocked it, and it does not think stocking it is anyone's job.
Four complaints, one cause
Grace Hill's research into move-in experience identifies five recurring complaints: the unit was not clean, repairs were slow, communication was poor, common areas were dirty, and parking was a mess. Read them as operational failures and you get an expensive, slow improvement programme. Read them again more carefully and four of the five are something else.
Slow repairs is very often not a maintenance capacity problem. It is the absence of published emergency-versus-routine definitions, stated response bands, and any visibility into whether a ticket was received. Residents do not experience an eight-day repair as slow if they were told it would take eight days. They experience an unexplained silence as slow, and they experience it as evidence about the operator's character rather than about the work order.
Poor communication is pure information architecture — there is no published table of who to contact for what, with hours and expected response windows. Dirty common areas are frequently caused by residents themselves, moving in with cardboard nobody told them where to put. Parking conflict is nearly always the enforcement of a rule that was never stated, which is experienced not as fairness but as a trap.
That reframe is the arbitrage. Fixing operations is slow and expensive. Fixing the information layer is fast and cheap, and it removes a meaningful share of the same complaints.
Why the content never gets written
Not because operators are lazy. Five structural reasons, each of which has to be designed against separately.
Nobody owns it. Leasing is measured on signed leases and its attention ends at signature. Operations inherits a resident it never met, carrying expectations it cannot see. The property management software vendor's scope ends at "we gave you a documents area." The seam between leasing and operations is an org-chart boundary, and the information falls straight through it.
It is genuinely hard to assemble. A complete building guide requires knowledge held across the superintendent, the property manager, the leasing agent, the waste contractor, the fire safety plan, the municipality, three utilities and the lease. No single party holds all of it, and there is no natural moment at which they are all in the same room.
It decays. This is the one that surprises people. On 1 January 2026 the City of Ottawa stopped collecting residential recycling; the provincial producer-run programme took over, administered by Circular Materials, and the accepted materials list changed with it. Buildings of six or more units first occupied from 2026 onward were made ineligible for that programme until 2031, and now need a private contract to receive City garbage collection at all. In a single Ottawa portfolio, two buildings three blocks apart can have different streams, different contractors and different rules — and every handbook written before December 2025 is wrong about the most common question a new resident asks.
The benefit is diffuse. The cost of not doing this shows up as scattered staff minutes and a slightly lower renewal rate. It never appears as a line item anyone is accountable for.
And no KPI improves. There is no onboarding completeness measure in any standard multifamily reporting pack. The gap is not tolerated so much as invisible.
What the vendors actually sell
There is no shortage of software. Property management platforms provide the transaction rails. Resident experience apps add events, amenity booking and package alerts. Move concierge platforms — several of them free to the operator, monetised through referral marketplaces for internet, insurance and movers — provide genuinely good task checklists, automated reminders and two-way sync.
Every one of them ships an empty vessel. They provide the container and the workflow. The operator is still expected to author, structure, translate, localise and keep current twenty distinct domains of building-specific and municipality-specific information — and to notice, unaided, when a municipality changes something underneath them.
Onboarding software is a solved problem. Onboarding content is not.
What a standard would have to do
THRESHOLD is an attempt at the missing half. Three claims sit underneath it, and each is a departure from how handbooks are normally written.
First, timing is part of the requirement. A forty-page PDF issued at lease signing satisfies nothing; it arrives when the resident cannot act on it and is unfindable when they can. Every obligation carries a stage.
Second, mode is part of the requirement. The waste rules exist in most buildings — in a document, attached to an email, read once while packing. At the moment of decision, standing in front of three identical bins, the resident has nothing. An item delivered in the wrong mode is scored as not delivered, which is the clause most likely to be argued with and the one that makes the score describe outcomes rather than compliance.
Third, currency is part of the requirement. Wrong information creates reliance, and reliance creates liability. Every item carries a source and a review date, and an item past its review date scores zero.
Twenty-five stages, twelve information types, four delivery modes, seventy-one scored requirements across three conformance levels. It is free to read and free to score yourself against, and both will stay that way.
The number that starts the conversation
Most operators who complete the assessment score somewhere in the thirties. Their first reaction is that the number must be wrong, because they know how much material they have produced. Usually they are right about the material and wrong about the conclusion: most of what they have exists, and fails only because it is out of date or because it never reaches the resident at the moment the decision is made.
That is a much smaller problem than the score suggests, and a much more specific one. It is also, for what it is worth, the reason the resident in the first paragraph learned the building from their neighbours.