The repair invoice is only one cost of a maintenance request, and it is often paid by the property owner. Your property management company also spends time receiving the request, finding missing information, arranging access, chasing approval, updating the resident and checking that the work is complete.
That coordination cost becomes difficult to see when it is spread across several roles. A ticket may appear inexpensive while consuming an hour of staff time and repeated interruptions for the company owner.
Measure the management company’s work separately from the property’s repair spending. That distinction helps you decide whether the problem is workload, rework, approval delay, vendor reliability or the way service is priced.
Separate whose cost you are measuring
| Cost | Usually belongs in which analysis? | Treatment to confirm |
|---|---|---|
| Vendor repair invoice | Property-owner operating cost | Allocation under the management agreement and responsibility for the repair |
| Coordinator time | Management-company delivery cost | Loaded labor cost or a consistent internal hourly allocation |
| Manager escalation time | Management-company delivery cost | Time spent making or reconstructing decisions |
| Repeated scheduling or corrected records | Management-company rework cost | Count once and identify why it occurred |
| Maintenance software | Management-company or allocated service cost | Include the relevant share rather than the entire technology budget |
| Vacancy caused by an unresolved issue | Property-owner economic impact | Establish facts; do not automatically attribute all vacancy to maintenance |
| Lost management client | Management-company commercial impact | Analyze separately, with evidence of the departure reason |
Do not add an owner’s repair bill to your company payroll cost and call the total your maintenance margin. Likewise, a coordination fee collected from a client is revenue, not a reduction in the underlying hours required to deliver the service.
Collect a representative sample of work
Choose a period that reflects your portfolio, and note any unusual weather, major repair project or staff absence. Pull work-order counts and statuses, then sample the actual coordination effort. Your software may show when a ticket changed status without showing how long a colleague spent chasing a vendor.
Use a simple activity log: work-order reference, person, minutes, activity, whether it was rework and the reason. Track intake, scheduling, approvals, resident updates, invoice review and closure. Include time spent by managers and owners; their involvement is often the hidden part.
Keep the exercise practical. A short representative sample can expose the dominant cost drivers before you attempt a detailed time study. Explain that the purpose is understanding the process, not rewarding staff for underreporting time.
Separate active work from elapsed delay. A ticket can wait three days for approval while consuming only a few minutes of handling time, yet still create a serious service problem. Conversely, a request closed the same day can consume extensive rework.
Calculate an explicit cost per completed work order
Here is a hypothetical monthly example. All rates are loaded internal planning rates, not wage benchmarks. The time categories are mutually exclusive, so rework is not also included in routine coordination.
| Activity or cost | Calculation | Amount |
|---|---|---|
| Routine coordination | 80 hours × $30 | $2,400 |
| Manager escalation | 6 hours × $50 | $300 |
| Additional rework | 10 hours × $30 | $300 |
| Allocated maintenance software | Monthly allocation | $240 |
| Recorded coordination cost | Total | $3,240 |
If 240 work orders were completed during that month, the period-based coordination cost per completed work order is $3,240 ÷ 240 = $13.50.
This is an allocated period measure. The numerator may include effort on tickets still open at month-end, while some completed tickets began earlier. It is useful for trend monitoring when definitions stay consistent, but it is not the exact lifetime cost of each ticket. For that question, follow a defined group of work orders from opening through closure and collect all related effort.
Also state what the calculation excludes: repair invoices, general office overhead, unrecorded time and other costs not included in the sample. A partial measure is still useful if it is labeled accurately.
Read the backlog alongside the cost
A low cost per completed ticket can conceal premature closure or a neglected difficult backlog. Track open work by age, urgency and blocked reason, and reconcile the count:
Closing backlog = opening backlog + new requests − completed requests, adjusted separately for duplicates, cancellations or other changes in scope.
For example, 100 open requests plus 260 new requests minus 240 completed requests leaves 120 open. Even though the company closed many tickets, the queue grew by 20. Show duplicate removals separately so cleaning records is not represented as completed repair work.
Use age bands appropriate to the type of request and your obligations. Emergency work should not be hidden in a monthly average. For ordinary blocked work, distinguish awaiting owner decision, awaiting vendor, awaiting access and awaiting internal action. The intervention depends on the reason.
Find the failure that creates repeated work
Consider an illustrative sample of 40 rework events. Twenty involve missing access details, 12 involve incomplete vendor evidence and eight involve repeated approval requests. Rather than asking everyone to “work faster,” examine the point where those facts should have been collected.
A revised intake record might require the access arrangement before routine dispatch. A closure checklist might specify the evidence needed from the vendor. An approval request might present the amount, scope and decision required in one message, with a documented escalation route.
If the 20 access-related events each consumed 15 minutes, they account for five hours, or $150 at the example $30 rate. Removing half would release 2.5 hours valued at $75. That is an illustrative capacity value, not necessarily cash saved. It becomes a cash benefit only if an actual expense changes, or a measurable business benefit when the capacity is put to useful work.
Preserve the controls that protect service quality
Triage needs a clear emergency route and staff trained to recognize when remote coordination is insufficient. Dispatch needs current vendor and access information. Approvals need the correct authority for that property. Closure needs evidence that the required work and communication are complete.
A coordinator can compare the invoice with the authorized scope and available photographs, but should escalate discrepancies rather than assume an invoice proves satisfactory completion. Reopened requests and repeat complaints are useful quality signals. Count them alongside speed so the team has no incentive to close unresolved work.
Use the remote-team playbook for handoff and escalation agreements. The tenant management guide connects maintenance to the wider resident experience.
Decide whether to improve the process, add capacity or review scope
If the sample shows substantial duplication, repair the process first. If the process is sound but incoming work consistently exceeds available capacity, consider staffing or coverage changes. If the company is delivering work that the management agreement does not price or define clearly, review service scope with the appropriate commercial and legal advice.
Write one action record: problem, evidence, change, responsible person, implementation date and review measure. Recalculate the same cost measure after enough comparable work has occurred, and review backlog age, reopened cases and resident updates at the same time.
Maintenance coordination is easier to manage when the company can see the work and the decisions behind it. If you need help clarifying those responsibilities and improving the process, BetterTeam Consulting is a relevant next step.
