PBSA and student HMOs house the same people, often on the same streets, but they are different businesses. A purpose-built student accommodation scheme is a single large asset run like a hospitality operation. A student HMO portfolio is a set of shared houses run like lettings. The demand overlaps; almost nothing else does, including the software that runs them well.
This is a straight comparison of PBSA vs HMO student housing across the dimensions that actually shape operations, followed by an honest read on software fit. If you run both, the goal is not to pick a winner, it is to understand where the models diverge so your tooling and processes match each one.
Two models, one demand
Both models let to students, but the unit and the relationship differ. PBSA lets beds and studios inside one managed building, usually with amenities, a front desk and on-site staff, on licence agreements tied to the academic year. A student HMO is a shared house, typically let room by room or as a joint tenancy to a group, dispersed across a portfolio of separate properties. For the legal definition that sits under the HMO side, see what is an HMO.
That difference in physical form drives everything downstream: how you bill, how you comply, how you staff, and what a unit of inventory even means. Take them in turn.
It is worth being clear that neither model is inherently the better business. They occupy different points on the same trade-off curve between scale and flexibility. PBSA concentrates a lot of beds behind one front door, which buys operational efficiency and a premium product but demands capital and a service operation. HMOs spread fewer beds across many doors, which lowers the entry cost and diversifies risk but multiplies the number of things you have to keep track of. Choosing between them, or running both, is really a choice about where on that curve you want to sit.
The comparison
| Dimension | PBSA | Student HMO |
|---|---|---|
| Asset shape | One large building, purpose-built, often with amenity space and on-site team | Multiple converted or adapted houses across a geographic portfolio |
| Contract | Individual licence agreements, mostly academic-year term | Room-by-room lets or a joint tenancy for a whole group |
| Billing | All-inclusive, one rate covering rent, bills and amenities, billed per bed | Rent plus bills, sometimes split, sometimes inclusive; deposits and joint liability common |
| Compliance focus | Building-scale fire safety, planning use class, licensing where applicable, on-site safeguarding | HMO licensing, room and amenity standards, per-property certificates, distributed inspections |
| Staffing | Centralised on-site team, hospitality-style, front desk and maintenance | Lean, mobile or outsourced, travelling between properties |
| Inventory unit | Bed or studio inside one building, high density | Room within a house, low density, scattered |
| Turnover pattern | Synchronised academic cycle, mass intake and mass departure | Academic cycle but staggered across houses and tenancy start dates |
Contract and billing: the operational fault line
The clearest split is how money is structured. PBSA typically sells one all-inclusive price per bed, which makes billing uniform and forecasting clean but concentrates collection risk into a single synchronised cycle. Student HMOs more often carry a mix: rent plus a bills arrangement, deposits under protection rules, and joint-and-several liability across a group where one missed payment becomes everyone's problem to resolve.
This matters for software because the two demand different things. PBSA billing rewards bulk operations: mass invoicing, cohort-level payment tracking, and the ability to see at a glance which beds in a 600-bed building have not paid. HMO billing rewards flexibility: per-room rent, split bills, deposit protection tracking, and the ability to model joint liability so a shared debt is chased correctly.
Compliance: scale versus dispersion
Both models are heavily regulated, but the shape of the compliance load differs. PBSA concentrates risk in one building, so the burden is depth: building-scale fire strategy, planning conditions, and licensing where it applies, all in one place with one set of certificates to keep current.
HMO compliance is about dispersion. Each property may need its own HMO licence, its own gas and electrical certificates, its own room-size and amenity checks, and its own inspection history. The individual requirements are not always more complex, but tracking them across dozens of scattered addresses, each on its own renewal clock, is where portfolios lose control. Right to Rent checks apply on the residential-tenancy side too, and the student position has nuances worth confirming; see the Right to Rent for international students checklist.
Staffing and resident experience
PBSA runs closer to hospitality. An on-site team handles front desk, maintenance, community events and incidents, and residents expect amenity and service in exchange for a premium all-inclusive price. Student HMOs run closer to traditional lettings: a leaner, often mobile team manages a spread of houses, with less amenity and, usually, a lower price point. Neither is better; they are different products for different budgets and preferences.
The staffing shape also changes how work is dispatched. In PBSA a maintenance issue is a ticket to a team already in the building, so response is fast and the coordination problem is small. In an HMO portfolio the same issue means routing a contractor or a travelling handyperson to one of many addresses, sequencing visits efficiently, and making sure a job at one house does not leave another waiting. The operational skill in HMOs is logistics across a map; in PBSA it is throughput inside a single site during peak periods.
Cost and margin profile
The two models also carry cost differently, and it shows up in the margin. PBSA has high fixed operating costs: the on-site team, the amenity space, the plant and the front desk are there whether the building is at 90% or 99% occupancy. That fixed base makes occupancy and rate the dominant levers, because a small change in either drops almost straight to the bottom line. It also makes the synchronised void, the point at which academic-year contracts all end together, a concentrated risk that a good summer let strategy exists to soften.
Student HMOs carry lower fixed cost per property but a heavier per-unit administrative and compliance overhead, spread across many small assets. The margin pressure is less about one big void and more about the cumulative drag of managing many separate properties, each with its own certificates, its own tenancy dates and its own maintenance history. Where PBSA rewards operational scale, HMOs reward tight process discipline across a portfolio that never quite stands still.
What a unit of inventory means
This sounds abstract but it decides whether your reporting is honest. In PBSA the meaningful unit is the bed or studio, and occupancy, void and revenue only make sense at bed-night level inside one high-density building. In HMOs the meaningful unit is the room within a house, and a per-property view can hide a half-empty house behind a portfolio average. Both models need per-bed or per-room reporting rather than per-property, but for different reasons: density in PBSA, dispersion in HMO. Get this wrong and every downstream number, void rate, yield, arrears exposure, is measured against the wrong denominator, and the operator ends up managing to a figure that does not reflect what the building or the portfolio is actually earning.
Software fit
The question is not which product is better, it is which capabilities each model leans on hardest.
What PBSA leans on
- Bulk intake and mass onboarding for a synchronised September cycle.
- Bed and studio level inventory, occupancy and void inside a single building.
- All-inclusive billing at scale, with cohort-level payment tracking.
- Amenity, front-desk and incident workflows for an on-site team.
- University nomination and block-booking handling.
What student HMOs lean on
- Per-room letting across a dispersed portfolio of separate addresses.
- Distributed compliance tracking: per-property licences, certificates and inspections on independent renewal clocks.
- Flexible billing: split bills, deposits under protection rules, joint-and-several liability.
- Maintenance coordination for a mobile team travelling between houses.
- A portfolio view that surfaces the weak property rather than hiding it in an average.
A system that only models one property as one big building will misrepresent an HMO portfolio, and a system built for scattered houses will struggle with the density and synchronised operations of a large scheme. Some operators run both models and need tooling that handles each without forcing one into the other's shape.
Which should you choose?
If you are deciding where to invest rather than which software to buy, the trade is roughly: PBSA offers scale, uniformity and a premium all-inclusive product, at the cost of higher capital intensity, concentrated risk and a hospitality-grade operation. HMOs offer lower entry cost, geographic diversification and flexibility, at the cost of dispersed compliance and thinner margins per unit. Many portfolios end up with both, which is precisely why the reporting model has to be consistent underneath.
Where this fits
For a fuller evaluation of tooling by model, see our PBSA software and broader student housing software overviews, the best student housing software comparison, and, once you have chosen a model, the student room allocation and PBSA summer lets posts for the operational detail underneath.
