Real Estate and Property Management Case Studies
Professional5 Case StudiesUpdated Sep 2026
Property management looks simple from the outside. A building needs rent collected, repairs completed, and owners kept informed, so the work appears to be a set of routine tasks. In practice the difficulty lies in who owns each task, how quickly it must move, and what the people paying for it expect to see. The five cases that follow come from fictional firms of different sizes and portfolio types. Each starts with a visible problem and works back to the roles, service levels, and workflow data that produced it.
Case Study 1
Unclear ownership behind missed routine repair targets
Fallowmere Property Group, a regional residential manager with 2,300 units across four communities.
The situation
Fallowmere Property Group manages 2,300 residential units across four communities, and its coordination team of nine people sits between residents, vendors, and the owners who pay for it all. Over two quarters the team missed its routine work order target, closing 61 percent of requests within three business days against a goal of 90 percent. Emergency calls met the four hour window, but routine requests drifted. Leasing agents at each site had been absorbing maintenance coordination during busy turns, and the operations director and the leasing manager both assigned priorities to the same people without agreeing which list came first. Nobody could say who owned a stalled request without opening the tracker.
The challenge
Mariana, the operations director, wanted the team to simply work the queue harder. Tomas, the leasing manager, argued that turns were the real emergency and routine repairs could wait. Both had a point, and both were measured on different numbers. The owners, meanwhile, expected a monthly report that showed routine closures recovering within one quarter. Nobody had agreed on who decided when a turn outranked a repair.
Analysis
The first pass at a case like this is usually a role audit, and Fallowmere's audit found three overlaps. The leasing agents, coordinators, and site supervisors each touched the same work order, but none of them owned the close. The tracker showed that 38 percent of stalled requests had changed hands at least twice before anyone assigned a vendor. Service levels existed on paper, a four hour emergency window and a three day routine window, but no one was named against them. Routine requests sat longest in the status labeled waiting on approval, which turned out to mean waiting on whichever manager had last commented.
Teams grounded in Real Estate and Property Management usually start accountability work with a single decision rule rather than a new meeting. Fallowmere wrote a priority order, emergencies first, then turns with a lease date inside ten days, then routine repairs, and the operations director alone could reorder it. Each open request received one named owner, and that owner's name appeared in the status field, not in a comment. The 90 percent target stayed, with an interim goal of 80 percent by the end of the first quarter. Leasing got a weekly view of its own stalled turns, and owners got the same figures monthly.
Actions taken
- Write one priority rule for the coordination desk and name the operations director as the only person who can change its order.
- Assign every open request a single owner in the status field, and retire the waiting on approval label after two weeks of cleanup.
- Hold a fifteen minute stand up each morning at every site where leasing and maintenance share a queue, reviewing only requests older than the window.
- Publish a weekly scorecard to owners showing closures against the 90 percent target, the 80 percent interim goal, and the named owner for each late item.
Results
Within two quarters the routine closure rate rose from 61 percent to 84 percent. That was still short of the 90 percent target, but the owners accepted the trend. Requests that changed hands twice before assignment dropped sharply once the priority rule went live, and nearly every open item carried a named owner. Tomas stopped pulling coordinators into busy turns, because leasing could now see its own stalled work each week. Emergency response stayed inside the four hour window throughout. The next budget review focused on desk staffing, not on individual performance.
Questions for discussion
- Which of the five causes would you measure first, and what data would confirm it?
- How would you set the rule for when a turn outranks a routine repair during peak leasing months?
- What evidence would convince owners that the 90 percent goal is still realistic after two quarters of misses?
Case Study 2
Rebuilding trust with an owner after missed deliveries
Cobble Harbor Property Services, a third party manager for 14 office and retail assets, eight of them owned by one regional investment fund.
The situation
Cobble Harbor Property Services manages 14 office and retail assets, and eight of them belong to a single regional investment fund. Its asset manager, Denise, had been asking for clearer reporting for two quarters before she escalated in writing. Her complaints were specific: the monthly performance package arrived an average of nine days after month end, a lobby renovation at the Lantern Street building ran eleven weeks past its schedule, and owner inquiries were taking days to answer against a one business day standard. The fund's investment committee was scheduled to review the portfolio at the end of the quarter, and Denise had been asked to explain the variance.
The challenge
The account team wanted to send a reassuring letter and move on. Ruben, the regional director, thought that would confirm everything Denise already suspected. The fund needed a clear answer on what was late, who owned the fix, and what would be different by the next report. Cobble Harbor had no single document that stated the agreed service levels, and the team kept two versions of the reporting calendar.
Analysis
Promises and delivery had drifted apart, and no one had measured the gap. The agreement in the management contract called for owner inquiries acknowledged within one business day and resolved within five, but the inquiry log showed acknowledgment inside that window only about a third of the time. The reporting package depended on three systems, a work order platform, a general ledger export, and a leasing database, and each was owned by a different person. Roles were clear on paper but blurred in practice, since each side assumed the other would catch variances.
The immediate response separated three concerns and gave each one a named owner. Cobble Harbor sent Denise a written account of each within two business days, with an owner and a date attached to every open item. The renovation could not be recovered in full, so the team offered a revised schedule built on the contractor's milestones, plus a fee credit for the part of the overrun caused by its own late approvals. Commitments were made measurable: the package by the fourth business day, inquiries acknowledged within one business day in at least 95 percent of cases, and a weekly call until the quarter closed.
- 1Written account issuedEach concern listed with an owner and a date.
- 2Revised renovation scheduleBuilt on contractor milestones, with fee credit applied.
- 3Reporting calendar resetPackage locked to the fourth business day, with backup data.
- 4Inquiry standard trackedAcknowledgment rate reported weekly against the 95 percent target.
- 5Weekly status callOwner and manager review open items until the quarter closes.
Actions taken
- Send Denise a written account of each concern within two business days, with an owner and date for every open item, and copy the fund's board liaison.
- Offer the revised renovation schedule with contractor milestones attached, and apply the fee credit before the next invoice rather than after a dispute.
- Assign the property manager for each building to own its fixes, while the account lead owns the explanation to the fund and holds the calendar.
- Publish the monthly package on the fourth business day from a single data pull, and report inquiry acknowledgment rates to Denise every Monday until the quarter closes.
Results
By the end of the quarter the monthly package had arrived on the fourth business day for three months running. Inquiry acknowledgment inside one business day rose from about a third to 96 percent. The renovation finished four weeks behind its revised schedule, which the fund accepted because each milestone had been visible. Denise presented one page of commitments and results to the investment committee, and the management agreement was not reopened. Cobble Harbor absorbed the fee credit, but it kept all eight fund buildings under contract.
Questions for discussion
- Which commitments in this case were specific enough to hold the team to, and which were too loose?
- How should responsibility for an escalation be divided when the account lead and property managers each own part of the problem?
- When does a fee credit repair trust, and when does it signal that the real problem has not been named?
Case Study 3
Untangling the make-ready handoffs in a residential portfolio
Tamarack Hill Residential, an owner-operator managing 1,850 apartments across six buildings.
The situation
Tamarack Hill Residential manages 1,850 apartments across six buildings, and every move-out starts the same recurring workflow, called make-ready internally. Units were supposed to be listed within ten days of the move-out walkthrough. Over the last two quarters the median was closer to seventeen days, and about a fifth of the turns required a second scope of work after a vendor had already priced the first one. The regional operations lead, Kwame, had pulled the job logs for the six buildings and found the same pattern in each: the inspection notes lived in a photo app, the scope was written from memory, and approvals sat in an inbox for days.
The challenge
Kwame wanted to redesign the whole make-ready flow at once, with a new software module and a revised role for each site. Ines, the portfolio finance lead, was wary of spending before the team could show which handoff caused the most damage. The site managers had heard redesigns before and mostly wanted fewer surprises on their calendars. Any change had to protect the service level on turns already in progress, and it had to be explainable to owners who saw only the final invoice.
Analysis
The team mapped the workflow as a chain of eight handoffs, from notice to listing, and timed each one from the job logs. The longest delays did not sit in the vendor work, which averaged under three days once started. They sat between the walkthrough and the scope, where notes were retyped, and between the scope and approval, which waited on one person's login. Rework followed the same gap. When the scope was written from memory, roughly one in five turns needed a second version, and each revision restarted the approval clock. Roles were implied, so the inspector, coordinator, and site manager each assumed someone else checked the photos.
Three options were on the table. A software module could attach inspection photos to the scope, but it cost more than the site budgets could carry in one year. A single scope writer for all six buildings would stop the rewrites, yet it would take work away from site managers who had resisted that before. A standard scope template for the twelve most common turn types, plus an approval rule for small scopes, was the cheapest and fastest. The team chose the template and approval rule first, set a median target of 12 days to listing within two quarters, and kept the module under review.
- In the first weekSite managers review the draft template and approval threshold.
- By week threeTemplate live at two pilot buildings with photo checks.
- End of first quarterApproval rule applied across all six buildings and tracked weekly.
- Mid second quarterMedian days to listing reviewed against the 12 day target.
- End of second quarterModule decision made using two quarters of turn data.
Actions taken
- Replace the memory based scope with a standard template for the twelve most common turn types, populated from the inspector's photo notes before the walkthrough closes.
- Set an approval rule that clears any scope under the site threshold within one business day, with the coordinator not the manager holding the clock.
- Give each building a named coordinator who reviews every open turn weekly against its service window, and escalates any turn that has passed nine days.
- Track the median days to listing and the rewrite rate each month, and hold the module decision until two quarters of data show whether the template held.
Results
The rewrite rate fell from roughly one in five turns to about one in twenty by the end of two quarters. Median days to listing dropped from seventeen to thirteen, still above the twelve day target but enough that owners stopped raising individual units at monthly meetings. Small scopes cleared inside a day for most of the portfolio, and coordinators took the approval clock without much resistance once they could see their own stalled list. The software module stayed under review, and no new purchase was made. Site managers kept writing walkthrough notes, which the template now read directly.
Questions for discussion
- Which handoff would you redesign first if only one change were possible, and what evidence supports that choice?
- What signs would show that the approval rule is creating its own delays?
- How would you keep site managers involved in template design without reopening who writes the scope?
Case Study 4
Rolling out a vendor invoice portal against resistance
Lindenfield Commercial Properties, a manager of nine office buildings and about 60 recurring vendor contracts.
The situation
Lindenfield Commercial Properties manages nine office buildings and about 60 recurring vendor contracts. In the first week of the rollout the company required that every vendor invoice enter through a new portal, retiring email submission and paper approval. The policy was meant to shorten approval times, which had averaged 14 business days, and to give owners a single audit trail. Within two weeks, building engineers were emailing invoices directly to accounts payable, and three of the largest vendors had stopped submitting through the portal at all. Accounts payable reported a backlog of 212 invoices that had been entered twice or not at all.
The challenge
Sanjay, the director of property accounting, supported the portal but warned that the policy had been written without the people who would absorb its failures. Hana, a building engineer at the largest site, said she could not afford to wait on a vendor that refused the portal before paying for an emergency repair. The company had committed to a go live date with the lender's reporting team, and the owners wanted proof of uptake before the next quarter's review. Leadership had to decide whether to enforce the policy as written, pause it, or change it.
Analysis
The concerns were not one objection but four, and each came from a different role. Building engineers feared that a portal would slow emergency payments, which was a legitimate concern given that the old process allowed a verbal approval for urgent work. Accounts payable worried about duplicate entries and unclear ownership of rejected invoices. Vendors resisted new log in steps for contracts that paid quarterly. Owners wanted the audit trail without approving invoices already received. Mapping the four concerns against the service levels showed that the policy had promised a five business day approval window without naming who held the clock at each stage.
The sequence mattered more than the message. Lindenfield kept the policy but paused enforcement for emergency repairs, which removed the engineers' most immediate objection, and each site ran two weeks of training with a named power user. Vendors with fewer than five invoices a month received a phone enrollment rather than a login email. The measures were specific: the share of invoices entered through the portal, the number of emailed invoices received by accounts payable, and the approval time against the five day window. The target was 90 percent portal entry by the end of the first quarter, reviewed every week until it held for a month.
Actions taken
- Exempt emergency repairs from enforcement for two months, and let engineers send a same day photo that the portal entry must follow.
- Run enrollment calls for every vendor with fewer than five invoices a month, and confirm each login with the vendor's own accounts contact before the first payment.
- Assign each building a named power user who answers portal questions within one business day and reports any vendor still submitting by email.
- Report portal entry share, emailed invoices received, and approval time against the five day window every week, and publish the figures to building engineers.
Results
Portal entry reached 88 percent of invoices by the end of the first quarter, just short of the 90 percent goal. Emailed invoices reaching accounts payable fell to a small fraction of their earlier volume. Approval time on portal invoices dropped from 14 business days to 6, though the overall average stayed higher because two vendors still sent email. The enforcement pause ended on schedule, and the three largest vendors were enrolled before it did. Sanjay kept the backlog report on his weekly list until it had stayed clear for a month.
Questions for discussion
- Which concern from accounts payable or building engineers deserves the most weight, and why?
- How would you separate reluctant compliance from real adoption when measuring uptake?
- What should trigger a return to full enforcement once the pause ends?
Case Study 5
Staging three competing capital projects on thin evidence
Brandt Ridge Property Company, an owner and manager of 16 mixed use and light industrial buildings.
The situation
Brandt Ridge Property Company owns and manages 16 buildings, mostly older mixed use and light industrial space. Its executive group had three initiatives competing for the same capital reserve in the next budget cycle: a building automation retrofit across eight sites, a conversion of a vacant warehouse into flex units, and the purchase of a neighboring parking structure that would secure access for two tenants. Each had a sponsor, and each sponsor had a credible case. The data behind them was thin. The automation estimate rested on one pilot building, the warehouse conversion relied on a market survey of 37 prospective tenants, and the parking figures came from a seller's own traffic counts.
The challenge
Sofia, the chief financial officer, wanted a ranking by the end of the month so the board could approve one project. Gareth, who ran asset management, argued that the automation retrofit was the only option with a measurable operating payoff, and that the others were bets. Priya, the operations director, pointed out that the automation project would consume the same maintenance staff needed for any warehouse conversion. The board expected a recommendation with a clear downside number, and no one yet had one for any of the three.
Analysis
Agreeing on criteria came before any scoring, because the three sponsors had been arguing from different standards. Brandt Ridge settled on four criteria: expected return within the reserve period, downside exposure if the assumption failed, effect on service levels for existing tenants, and whether the project could be stopped early. Each score carried a data quality rating. The automation case scored well on return but poorly on evidence, since its one pilot building sat in a different climate than most sites. The warehouse depended on tenant intent, and the parking purchase on a seller's traffic counts.
The recommendation was a staged commitment rather than a single approval. Stage one spent a small share of the reserve on better evidence: sensors at three automation sites, a pre-commitment survey for the warehouse, and a traffic study run by the company itself. Each stage had a go or stop test tied to a delivery target, such as an 8 percent verified drop in energy spend at the pilot sites. Service levels for existing tenants stayed protected, because no stage could pull a maintenance crew off its response windows. The board saw the downside for each stage in advance, so a stop would be a planned outcome.
- Gather evidence Sensors, tenant surveys, and traffic studies fund the next test.
- Test against targets Compare results with energy, leasing, and service level thresholds.
- Decide next step Board reviews the downside figure before releasing the next stage.
- Reallocate or release Unspent reserve returns to the pool for the next budget cycle.
Actions taken
- Fund stage one at a capped share of the reserve, and write the stop test for each initiative into the board paper before any spending begins.
- Score each initiative on the four criteria with a data quality rating beside every number, and show the board the weakest rating first.
- Protect existing tenant service levels by ring fencing maintenance crews, so no stage can pull staff off response windows without operations approval.
- Assign the asset manager to own the go or stop recommendation at each gate, and have finance release the next tranche only on a signed note.
Results
The board funded stage one for the automation retrofit and the warehouse survey, and held the parking purchase for a neutral traffic study. The sensor results came back below the 8 percent threshold, so the retrofit moved to a narrower second gate covering two sites. The warehouse survey produced letters for about 40 percent of the flex units, enough to keep the project alive but not to start construction. Most of the reserve stayed uncommitted and returned to the pool for the next cycle. Each stop was written down in advance, so no sponsor was surprised by one.
Questions for discussion
- What return would you accept in exchange for better evidence, and how would you justify that trade to the board?
- If the board cared only about downside exposure, which initiative would move to the front of the queue?
- How should the reserve be handled if the first stage shows that none of the three initiatives meets its test?
Learning Resources
Professional CASE STUDIES
China, India, United States, Indonesia, Pakistan, Nigeria, Brazil, Bangladesh, Russia, Japan, Mexico, Philippines, Vietnam, Egypt, Turkey, Germany, United Kingdom, France, Italy, Canada, South Korea, Australia, Spain.