A property-management account is not a collection of cleaning jobs. It is a shared operating system connecting two companies — and it succeeds only when scope, information, authority, execution, economics and governance are deliberately aligned.
What you'll be able to do:
Decide whether a portfolio is worth taking, launch it without destabilizing the operation, and govern it on evidence rather than on goodwill.
Free, and free to stay. No email, no account.
A property manager does not buy cleans. They buy the removal of an operational risk they would otherwise carry themselves. That makes the relationship a shared operating system: two companies whose scope, information, authority, execution, economics and governance have to line up or the account degrades.
It also means the failure modes are different. A portfolio that arrives before the systems do does not produce a bad clean — it produces a bad month, across every property at once.
The chapter puts a deliberate gate in front of the portfolio: qualification and opportunity assessment, a portfolio capacity test, and a concentration-risk check that asks what happens to the company if this one account leaves.
What follows is design rather than negotiation — scope of services and SLA planning, a responsibility and approval-authority matrix, an escalation map with issue classification, and a launch readiness gate with pilot selection. Account profitability is reviewed as an ongoing measure, because a large account that loses money loses it at scale.
Once a portfolio is accepted, the work is design. Scope of services and SLA planning define what is included and what is an exception. A responsibility and approval-authority matrix settles who may decide what — before a guest is standing in a property nobody is authorized to act on. An escalation map with issue classification means a problem travels at a speed matched to its severity.
Information flow is a first-class part of that design. Two companies sharing an operating system need the same picture of what happened at a property: readiness confirmed, exceptions raised, evidence attached. When that flow is missing, both sides fall back on phone calls and memory, and the account degrades into a relationship maintained by whoever is most persistent.
Governance keeps it honest over time — a PM scorecard in both directions, an account profitability review that catches a portfolio quietly losing money at scale, and defined corrective and exit paths so that ending an account is a process rather than an argument.
Editable templates that make this chapter executable. Free, no signup — as are all 109 of them.
A PM account is a shared operating system between two companies rather than a set of individual jobs. Scope, information flow, decision authority, execution standards, economics and governance all have to be aligned deliberately — and when they are not, the whole portfolio degrades at once.
The exposure created when one account represents enough of your revenue that losing it would threaten the company. The chapter tests for it before launch, because the time to discover it is not the month the contract ends.
Where you can. A launch readiness gate with pilot selection lets both companies find the mismatches on a few properties rather than across the whole portfolio in week one.
The full chapter — with the worked examples, tables and action plan — runs to pages 322–347 of The STR Cleaning Blueprint™. All 427 pages are free.