Property Manager Work Order Triage

Purpose

Turn a batch of work orders from a property manager into a schedule that puts the dangerous ones first and does not burn a truck on doors nobody can open. A manager's list arrives in the order the tenants complained, and that order carries no information about harm. Somewhere in a list of fourteen flickering lights and dead outlets there is usually one ticket describing a burning smell, and it is not at the top.

The second thing this SOP fixes is the quiet killer of multifamily and small-portfolio work, which is access. The electrical work on these tickets is rarely difficult. The visit fails because nobody knew the tenant works nights, the manager's master key does not open that unit, or the dog is in the kitchen. An access field filled in before scheduling is worth more to the shop than any dispatch software.

Scope

Covers intake, hazard screening, sequencing and scheduling of batched electrical work orders received from a property manager, landlord or facilities coordinator for multifamily buildings, small office parks and strip retail.

Does not cover the repairs themselves, which are the individual service SOPs; does not cover pricing or contract negotiation with the property manager; and does not cover fire alarm, sprinkler or elevator systems beyond flagging a loss and routing it to the provider who holds that contract.

Roles and handoffs

Procedure

1. Screen every ticket for the four conditions that jump the queue, at intake, before anything is sorted. Those are a burning smell, smoke or visible arcing; anyone reporting a shock from a device, appliance or fixture; water entering a panel, fixture or device; and a loss of power to a life-safety system such as egress lighting, a fire alarm panel or an elevator. Acceptance: every ticket carries one of those four flags or an explicit "none," with the intake time recorded. Wrong looks like a flag assigned from the manager's summary line rather than from the tenant's own words, since a manager writes "light not working" over a call that mentioned a smell. Stop rule: any of the four flags means the ticket leaves the batch and is dispatched on its own schedule that day. Hazard: on a burning-smell or arcing report, the caller is told before anything else that everyone leaves that area now, that no switch or breaker is to be operated, and to call 911 from outside; on a shock report, that the equipment is not touched again and stays unplugged; on water in a panel, that nobody opens or operates it and the room is kept clear.

2. Name who owns the equipment on every ticket. Common area and building systems, tenant demised premises, or tenant-owned equipment. Acceptance: an owner field filled per ticket, plus written authorization where the work sits in the other party's domain. Wrong looks like a tech entering a tenant's suite on a landlord's work order with no tenant notice. Stop rule: a ticket for tenant-owned equipment, meaning their own appliance, machine or fixture, goes back to the manager as out of scope rather than being absorbed. Hazard: none at this step, it is a classification made at a desk.

3. Get the authorization limit in writing, per property, before the batch is scheduled. Acceptance: a not-to-exceed stated in technician hours per ticket, signed or emailed by the manager, and refreshed at least annually. Wrong looks like a limit somebody remembers from last year, which is how a tech ends up two hours into unpaid work. Stop rule: no written limit means each ticket is treated as a diagnose-and-call, with the tech instructed to stop at the diagnosis and phone before repairing. Hazard: none at this step, it is a document check.

4. Fill the access field before a ticket may be scheduled. Acceptance: entry method, whose key or code, the tenant's contact and preferred hours, notice period required, and any pet or restriction, all present on the ticket. Wrong looks like "manager will meet you," which is not a time and not a phone number. Stop rule: a ticket with no access method comes out of the batch and goes back to the manager; it is never scheduled hopefully. Hazard: sending a lone tech into an occupied residential unit is a personal-safety exposure as well as a scheduling one, so the tenant is called ahead, the tech confirms an adult is present where the property requires it, and no tech enters a unit where the occupant refuses entry.

5. Sequence the batch by what a delay costs, harm first. The measure is the consequence of waiting a week, and it sorts into five bands in this order: the four hazard flags, which are dispatched same day and are not in the batch at all; a life-safety system out of service; a whole unit or area without power or light; a single device dead; and appearance-only items. Acceptance: every remaining ticket assigned to one band, with the batch listed in band order and no ticket sitting above a ticket in a higher band. Wrong looks like a manager's "urgent" label overriding the bands, since urgency in that field usually means the tenant called twice. Stop rule: any ticket that cannot be placed in a band is called back for detail rather than assigned to the middle. Hazard: none at this step, it is a sort made at a desk.

6. Batch by trip, then hold the batch to the sequence. Group by building and by access window, and within a group keep the band order from step 5. Acceptance: each trip sheet showing tickets in band order with an estimated duration per ticket against the property's authorization limit. Wrong looks like batching by proximity alone, which puts two cosmetic tickets ahead of a stairwell with no egress lighting because they share a floor. Stop rule: a trip whose estimated total exceeds the window drops tickets from the bottom band up, never from the top. Hazard: none at this step, it is planning done at a desk.

7. Confirm each ticket the day of, before the truck moves. Call the tenant to confirm the symptom is still present and access still holds. Acceptance: a confirmation logged per ticket, or two documented attempts. Wrong looks like arriving to hear the tenant says it fixed itself, which is a real finding on an intermittent fault and a wasted trip if nobody asked. Stop rule: two failed attempts drops the ticket to the next batch rather than burning the visit, and a symptom the tenant now reports as intermittent stays scheduled, because intermittent is a fault state and not a resolution. Hazard: none at this step, it is a phone call made from the office.

8. Close every ticket back to the manager the same day, with dispositions that mean something. Acceptance: per ticket, one of completed, diagnosed and awaiting authorization, no access, out of scope, or escalated as a hazard, plus a one-line finding. Wrong looks like a batch closed as "completed" with three units never entered. Stop rule: any ticket touching one of the step 1 flags goes back in writing the same day regardless of what else in the batch is still open. Hazard: none at this step, it is reporting done at a desk.

The record this produces

Per batch: each ticket's intake time and hazard flag; the equipment owner; the access method with contact and restrictions; the assigned band; the trip it was placed on; the confirmation call result; the disposition; and the finding line.

The manager gets the dispositions, because that is the document they answer their tenants with. The office keeps the flags and the findings, because a unit that generates three tickets in a year is not three faults, it is one circuit nobody has traced, and that pattern is invisible ticket by ticket. The access field is the one the office should audit quarterly: a property whose tickets keep coming in without access data is costing the shop trips, and that conversation goes better with a count than with a complaint.

Worked pass: 14 tickets, 24-unit building, one property manager

Step 1 screen, reading the tenants' own words rather than the summary lines. Two tickets carry flags: unit 9 reports a burning smell from a bedroom outlet, and unit 3 reports a tingle from the range when touching the sink. Both leave the batch and are dispatched that afternoon. The unit 9 tenant is told on the call that everyone leaves that room now, that no switch or breaker is to be operated and to call 911 from outside if there is smoke; the caller mentions the smell stopped yesterday, and the flag stands anyway, because a smell that stopped is not a fault that stopped.

Step 2: 13 of the 14 are building or demised-premises work. Ticket 14 is a tenant's own microwave, which goes back to the manager as out of scope with a line saying so.

Step 3: the manager's emailed limit is 2.0 technician hours per ticket before a call.

Step 4 fails. Of the 5 single-device tickets, 3 carry no access method at all. Step 4's stop rule fires and those 3 come out of the batch and go back to the manager for access data rather than being scheduled hopefully.

Step 5 sorts what remains. One life-safety item, the rear stairwell egress lighting out. Three whole-unit items, units 4, 12 and 18 with a dead circuit each. Two single-device items, the survivors of the five. Two appearance items, both hallway lens covers. That is 1 plus 3 plus 2 plus 2, which is 8 tickets in the batch, and with the 2 hazard tickets dispatched separately and the 3 access-blocked and 1 out-of-scope tickets removed, the 14 are fully accounted for.

Step 6: one trip covers all 8 in band order, with the stairwell first. Estimated durations total 6.5 hours against a 7.0 hour window, so nothing drops.

Step 7: 7 of the 8 confirm. Unit 18 does not answer twice and drops to the next batch, so 7 tickets go out.

On site, unit 12's dead circuit runs past the 2.0 hour limit at the diagnosis, and the tech calls the manager before continuing rather than finishing and invoicing. Authorization is given for another hour on the phone and noted on the ticket.

Step 8: seven dispositions go back the same day. Five completed, one diagnosed and awaiting authorization, one no access. Separately, both hazard tickets are reported in writing: unit 9's outlet is replaced and the circuit is condemned pending further work, and unit 3's tingle traces to a bonding defect, which is reported as a building item rather than a unit item because it is not confined to that apartment.

References

• The property's own written authorization limits and access policy, which govern steps 3 and 4 and are the only documents in this SOP that are not technical
• See related: Burned Receptacle Response and Circuit Condemnation SOP, for any ticket carrying the burning-smell or arcing flag at step 1
• See related: Grounding and Bonding Verification SOP, for a shock-from-equipment report traced beyond a single unit
• See related: Emergency and Egress Lighting Annual Test SOP, for the life-safety band at step 5
• See related: Troubleshooting Call Intake and Scoping SOP, which owns the single-ticket intake this SOP batches