How to Set Approval Limits With a Property Manager

Why this matters

Every managed account already has an approval limit. Most shops never ask what it is, so they discover it the first time an invoice comes back for an owner signature the manager never had the authority to give. In the gap, your tech has already done the work, your part is already installed, and the person who told you to proceed is now explaining themselves to their client instead of defending your bill.

A limit that is written down, sized to the work the account actually sends, and expressed in something a technician can apply while standing in a mechanical room turns most of that friction off. The limit is the manager's to grant. The design of it is yours to bring, because almost no manager has one structured for a trade vendor and almost every one of them will accept a good proposal.

Step 1: Ask for the limit as it exists, in their words

Open with the plain question: what can you approve without asking anyone, and what happens above that? Ask it of the person who dispatches your work, not of the person who signed the vendor agreement, because those are frequently different limits.

You will get one of three answers. A specific number, which is the easy case. A vague answer such as "routine stuff is fine," which means the limit exists in someone's head and will move when the invoice looks large. Or an honest "I would have to check," which is the best answer of the three and tells you the account is worth the setup conversation.

Write down whatever you get, verbatim, with the date and the person. This becomes your baseline for step 5.

Step 2: Get the last 30 work orders and sort them by sold hours

You cannot size a limit from opinion. Ask the manager to export the last 30 completed work orders in your trade across the properties they intend to send you, then convert each to sold hours as your shop would have billed it. If they cannot export it, use your own last 30 orders on comparable buildings.

Sold hours are the right unit here rather than the total invoice, for two reasons. Your technician can estimate hours on site and cannot estimate a running total that includes parts markup and taxes. And an hours-based limit does not need renegotiating every time your rates change.

Step 3: Compute the limit from the distribution, not from a round number

Sort the 30 orders and find the value that would have cleared roughly 8 out of every 10 without escalation. Not all 10. The largest orders in any set of 30 are usually genuine repair-versus-replace decisions, and an owner is entitled to make those.

Here is a real-shaped distribution from a 60-door portfolio:

Set the limit at 4.0 sold hours. That clears 25 of the 30 orders, or 83%, which is the 8-in-10 target. Setting it at 2.0 clears only 18 of 30, so about 2 orders in 5 escalate and your tech is on the phone constantly. Setting it at 8.0 clears 28 of 30, which sounds efficient and is not: you have taken two decisions a year away from the person who owns the asset, and the first time one of them goes badly the account remembers that you decided it.

Step 4: Translate the limit into a two-part field test

A number alone is not usable on site. Give the technician a test with a small number of conditions, all of which must hold. This is an AND, and the AND is the part that gets dropped.

Proceed under the standing limit only when all three are true:

1. The job type is on the named list agreed with the manager (for example: repair, component replacement, and diagnostics, but not modification or system replacement).
2. Total sold hours, diagnostic time included, are at or under the limit value.
3. Every part needed is truck stock or same-day available, so the order completes on this visit.

Condition 3 does the work people expect condition 2 to do. An order that passes on hours but needs a special-order part with a lead time is not a proceed. It becomes a scheduled return trip with a tenant impact and a date, and the manager needs to know about it before it becomes a complaint rather than after.

Escalate regardless of hours when any of these appear, because these are decisions about the asset or about the tenancy rather than about the repair:

• Anything that changes the tenant's use of the space or their utilities beyond the visit itself.
• Anything touching a life-safety system: alarm, detection, suppression, emergency lighting, egress hardware.
• Betterment, meaning an upgrade rather than a return to prior condition, even when the upgrade is cheaper in labor.
• Work outside your licensed trade, no matter how small it looks.
• Any condition that suggests a cause outside the unit, such as a shared riser, a common-area system, or a structural or water-intrusion source, because the responsible party may not be the one who dispatched you.

Print this list on the same card as the limit. A tech who has the number but not the carve-outs will apply the number correctly and still create the incident.

Step 5: Get it in writing with four fields

An approval limit that lives in a phone conversation is not operative. What you need is short, and any manager can send it in an email:

• The value and its unit. "Up to 4.0 sold labor hours plus same-day parts, per work order."
• The named person who granted it, and who else at their office may exercise it. Managers take vacations.
• The after-hours position. Whether the limit is the same at 9pm on a Sunday, and if it is different, what it is and who answers.
• An effective date and a review date. Ninety days is a reasonable first review.

Keep this in the account record, not in an inbox. When a new dispatcher joins their office and tells your tech to hold, you want to send the note the same hour rather than relitigating it.

Step 6: Recalibrate on a schedule, and damp the movement

Review quarterly, recomputing the 8-in-10 value from the actual orders that quarter. Then change the limit by at most 0.5 sold hours per review, moving toward the computed value rather than jumping to it.

That damping matters. A single cold snap or one bad building will push a quarter's distribution up, and a limit that chases every quarter's number oscillates for a year without settling, which trains the manager to treat it as a suggestion.

Run the example forward. The limit was set at 4.0 hours from the first 30 orders. Next quarter's orders compute to 5.0. The limit moves to 4.5, not to 5.0. If the following quarter still computes at or above 5.0, it moves to 5.0 and stays. If that quarter's spike was a one-off, the number falls back on its own and you never chased it.

The initial set is the exception: on a new account you set the limit directly at the computed value, because there is no prior number to damp against.

Step 7: Report against the limit so it keeps its credibility

Once a quarter, send the manager a two-line count: how many orders ran under the standing limit, and how many escalated. Nothing else, no narrative.

This is the single cheapest thing you can do to keep a limit from being quietly withdrawn. A manager who has to defend a vendor's discretion to an owner wants a number to defend it with, and "38 of 45 orders last quarter completed inside the limit on the first visit" is that number. The counts also make the case for a raise, when the case is real, without you having to ask for one.

What changes the answer

An HOA board rather than an owner widens every tier. A board that meets monthly cannot function as your escalation path for a repair, so the useful move is a board resolution granting the community manager a standing limit, and that resolution is a meeting agenda item, not an email. Ask for it early, because the request itself takes a meeting cycle.

A vendor platform can override the limit you negotiated. Institutional owners often run work orders through software that enforces its own not-to-exceed value per order. If the platform's number and the manager's number disagree, the platform wins at invoicing time regardless of what the manager said, so reconcile them before your first order rather than after your first rejection.

A property in the middle of a sale or a management transition suspends the limit entirely. Authority during a transition is genuinely unclear, and a limit granted by the outgoing manager may bind nobody. Treat every order as an escalation until the new authority is confirmed in writing.

How to verify you got this right

Ask a technician who works the account, without warning, what they are allowed to do without calling. If the answer is a hedge rather than a number and a short list of carve-outs, the limit is documented but not deployed.

Then pull the last 20 orders and check two things. Count the escalations: if fewer than 1 in 10 escalated, the limit is set too high and you are absorbing decisions the owner should be making. Then look specifically for orders that passed the hours test but shipped with a special-order part, because that is the condition the field test most often loses, and each one is a return trip that surprised somebody.

References

• See related: The Three-Party Problem in Property Management Work; Who Actually Signs and Who Only Calls
• See related: How to Get Approval Before You Do Extra Work; How to Handle an After-Hours Call With No Approval Authority
• See related: The Change Order Discipline Commercial Work Demands
• Trade-standard practice for not-to-exceed authorization on managed-property work orders