How a service promise becomes work the business can deliver

A management fee has to support a specific set of obligations. I examine the work behind a proposed contract: central coordination, owner reporting, specialist support and the service capacity that is not separately reimbursed. Site payroll may pass through the reported revenue without providing additional margin for that central work. The distinction becomes particularly important when a large new mandate appears to offer scale. I want finance and operations to build the proposal together, with the promised scope visible before the commercial conversation closes. We may choose to invest in a new relationship, but that should be a conscious decision with a cost and a review point. It should not depend on colleagues absorbing an unfunded service requirement indefinitely. The nine-property proposal taught us to test the economics earlier, before bid effort made withdrawal feel personally difficult.

A work-order system records what the organisation has done; the resident can tell us whether the problem remains. Both accounts matter. I ask our operating reviews to include a proportionate check of routine closures and a clear route for unresolved work, while urgent matters follow their established response procedures. The purpose is not to make a resident responsible for supervising our contractors. It is to avoid using an internal administrative step as the only evidence of completion. A return visit may be necessary for a legitimate reason, but it should remain visible until the next action is understood. I fund the coordination and training required for that discipline and ask managers to explain recurring patterns. I do not personally diagnose repairs or replace qualified maintenance judgement with a dashboard preference.

A business can add an adjacent service that looks commercially sensible while creating a different operating model. Capital-renovation contracting required project commitments, supervision and financial attention that did not fit comfortably within our recurring community-management work. I examined the activity as a business in its own right, including the contribution we would lose and the overhead that would remain if we exited. That prevented us from presenting withdrawal as an immediate cost-saving exercise. The eventual decision reflected the company we wanted to lead, not a claim that the contracting team had failed. We completed existing obligations and handled colleague transitions explicitly. A CEO needs to be able to explain where the enterprise will stop as well as where it will grow, with the consequences for customers, people and earnings stated clearly.

A community manager works between an owner’s expectations, residents’ needs and the practical capacity of a local team. A central procedure can help, but it cannot anticipate every situation. I want managers to explain the facts, identify the decision needed and understand which authority they hold. Earlier in my career I was inclined to become the person who solved the difficult exception. Regional leadership taught me that this could make the next problem more dependent on me. I now spend more time on how managers prepare an owner discussion, follow an unresolved request and recognise when specialist help is needed. Development should make their judgement more useful without asking them to improvise beyond their competence. The central business has to provide support and realistic resources, rather than praise local initiative while quietly relying on unpaid extra effort.