Harrow operating lessons: turning a live asset into operator discipline

Treat the building as evidence, not a marketing proof point

DIFF_RENT Harrow is a live scheme. It has a gym, cinema, coworking, lounges, concierge and front-of-house provision, and community programming. That makes it a useful operating environment, but not a licence to infer performance for a different site. An owner selecting an operator should ask which decisions were learned in live delivery, what the underlying records show, and which assumptions remain to be tested for the proposed asset.

The important distinction is between an operating principle and a measured claim. A principle might be that an arrival experience needs named ownership; a measured claim would require a defined period, source system, population and calculation. Board papers should label each accordingly. This prevents an operator pitch from turning a local observation into an unsupported promise about rent, demand, cost, retention or return.

• Request a decision log showing the issue, hypothesis, action, owner, date and review outcome.
• Ask for redacted source extracts and definitions rather than presentation-only dashboards.
• Separate transferable process lessons from site-specific design, location and resident-profile effects.

Start with an operating thesis before agreeing the management agreement

A credible operator mandate begins with a written thesis: the target resident, intended length of stay, service position, amenity promise, risk appetite and owner priorities. Harrow’s combination of studios and shared spaces illustrates why this matters. A studio is a private home, while the shared offer is a managed service environment; both must be reflected in staffing, rules, access, cleaning and budget responsibility.

The thesis should become a decision hierarchy. Safety, legal compliance and resident welfare cannot be traded against a short-term saving. Below those sit asset protection, service consistency, commercial responsiveness and discretionary programming. Without that hierarchy, site staff receive conflicting instructions: minimise cost, increase activity, protect the building and resolve every request immediately. The predictable result is informal prioritisation and uneven service.

Design the first ninety days as mobilisation, not occupancy administration

Whether the building is newly opening or changing operator, the first ninety days should have a controlled mobilisation plan. Inventory the building, licences, warranties, statutory duties, supplier contracts, access credentials, resident records, deposits, communications history and unresolved defects. Each item needs a named accountable person and an acceptance criterion. A handover that merely transfers keys and passwords leaves the owner unable to distinguish inherited risk from new operational failure.

At Harrow, the practical lesson is that front-of-house, concierge and community activity create many daily handoffs. Mobilisation must therefore map who receives parcels, owns out-of-hours escalation, resets access, closes complaints, approves spend and communicates a disruption. A simple responsibility matrix is more valuable than a large launch presentation when a lift fault, leak or resident safeguarding issue occurs on a weekend.

Use reporting to govern decisions rather than decorate meetings

Monthly reporting should answer four questions: what changed, why it changed, what management did, and what approval is now needed. Reporting that lists activity without exceptions makes the asset manager reconstruct the story. Establish definitions for enquiries, applications, cancellations, arrears, maintenance categories, complaints, voids, concessions and supplier commitments before the first report. Changes to definitions should be version controlled and visible.

An owner should require a short operational narrative alongside the numbers. It should explain risks to resident experience, compliance, condition and cash collection, including matters that have not yet created a financial variance. Equally, require a forecast with assumptions, not a single optimistic endpoint. The discipline is especially important in a live scheme, where individual incidents can be operationally material without proving a wider trend.

• Weekly: safety, urgent repairs, major complaints, arrears exceptions and availability changes.
• Monthly: commercial pipeline, service quality, maintenance backlog, supplier performance and forecast variance.
• Quarterly: risk register, lifecycle plan, policy changes, audit findings and owner decisions outstanding.

Make resident experience operationally specific

Resident experience is not a sentiment slogan. It is the accumulated result of response standards, clear information, clean and functioning spaces, respectful interactions and reliable resolution when something goes wrong. At Harrow, the gym, cinema, coworking and lounges each create different expectations of booking, behaviour, supervision, cleanliness and defect reporting. A generic amenity policy will not answer those practical questions.

The operator should publish service standards that are observable: acknowledgement and update timings, escalation paths, handover rules, closing criteria and communication channels. Do not confuse a closed ticket with a resolved concern. Sampling closed cases, reviewing repeat contacts and reading the resident-facing chronology can reveal whether teams are solving causes or simply controlling inbox volume.

Procure for accountability as well as price

A lean site team relies on suppliers, which makes supplier governance part of the operating model rather than a back-office exercise. The owner should understand who appoints each supplier, who can vary scope, what is included, which service levels apply, how attendance is evidenced and how poor performance is remedied. Contracts should not leave site colleagues negotiating technical terms during an incident.

Tender comparisons need a whole-service view. A low apparent cost can omit call-outs, consumables, reporting, training, insurance or management time. Require an assumptions schedule and a change-control route. The operator should also avoid a single point of failure where practical: maintain escalation contacts, confirm emergency arrangements and test whether access and information survive a supplier change.

Govern the operator with tests, not trust alone

A strong governance model is collaborative but testable. Agree delegated authorities, reserved matters, service standards, data access, audit rights, incident thresholds and dispute escalation before operating pressure arrives. The owner needs direct access to the systems or regular exports sufficient to validate the operator’s account. This is not an attempt to run the site remotely; it is the minimum architecture for informed oversight.

Use structured reviews to test capability. Walk a sample of resident journeys, inspect a sample of completed repairs, trace an invoice to approval, and follow an incident from report to closure. Ask what failed and what changed afterwards. An operator that can describe corrective action, document it and revisit it is usually safer than one that claims its processes never need adjustment.

A formal quarterly review can connect this testing to the business plan. Management should bring decisions that have crossed delegated authority, risks that have changed rating, material supplier concerns and actions whose due date has passed. The owner should record a response, funding decision or request for further evidence. This closes the gap between site intelligence and institutional accountability, while leaving the operator responsible for day-to-day execution.

Finally, the governance calendar should distinguish operational reporting from strategic review. Site teams need timely decisions on repairs, resident communication and suppliers; owners need a wider view of mandate fitness, business-plan assumptions and emerging risk. Combining every question into one meeting either delays operational action or crowds out considered oversight. A documented calendar, with a route for urgent exceptions, gives both conversations proper attention.

Key takeaways

• Harrow is a live scheme; its lessons should be evidenced and not converted into unsupported performance claims.
• An operating thesis, responsibility matrix and definition-controlled reporting create a usable owner mandate.
• Resident experience, supplier control and governance are connected operational systems.

Questions owners ask