The Service Level Language Worth Agreeing in Advance

Why this matters

Almost every fight with a property management company is a fight about something nobody wrote down. Not price - price gets negotiated openly and both sides remember it. The fights are about who could approve the extra two hours, whether a no-access trip is billable, why the invoice sat for six weeks, and whether the tech should have called the tenant back directly. Each of those is a one-sentence decision that costs nothing at signing and costs days of somebody's time once work is underway.

This card is the language itself. It is written as a schedule of terms you can put in front of a manager, because a manager who is handed drafted language reacts to it, and a manager who is asked open questions defers them. Have an attorney review anything you actually sign; what follows is commercial substance, not legal advice, and terms like late fees, lien rights and termination notice interact with state law that varies.

Clause 1: The authorization ladder

What it decides: who can commit spend, up to what size, without going further up.

Language: "The Manager may authorize work on a single work order up to 3.0 labor hours plus associated materials without further approval. Work exceeding that threshold requires written Owner approval, which the Manager will obtain. Contractor will not proceed above the threshold on verbal assurance that approval is forthcoming."

Why the threshold is in hours: a labor-hour ceiling survives price changes, is unambiguous at the moment a tech is standing in the unit, and does not require anyone to compute a total before deciding whether they can say yes. Set the number where roughly three quarters of your single-visit work on that portfolio lands underneath it, so the ladder is exercised on genuinely large items rather than on every second job.

If omitted: you will do the work on a manager's verbal go-ahead, the owner will decline the invoice, and the manager will be genuinely unable to help you, because they never had the authority they appeared to exercise.

Clause 2: After-hours authority

What it decides: who says yes at 2am, and what you are allowed to do when nobody says anything.

Language: "For emergency conditions outside business hours, Contractor is authorized to perform work necessary to eliminate an immediate hazard, stop an active water release, or restore an unfit dwelling unit to habitable condition, up to 4.0 labor hours plus materials, without prior approval. Contractor will notify Manager at the time of dispatch and provide a written report by 10am the following business day. Work beyond stabilization requires approval under Clause 1."

Why it is separate from Clause 1 and larger: the daytime ladder exists to control spend, and at 2am nobody is available to run it. The emergency ceiling should be set at the level that covers stabilization on your most common night call, not at the level that covers a full repair.

If omitted: your tech either performs the repair and eats the argument, or stops at the hazard and gets blamed for leaving a unit without heat overnight. Both outcomes are avoidable with two sentences.

Clause 3: Scope change during a visit

What it decides: what happens when the job on the work order is not the job in the unit.

Language: "Where Contractor's diagnosis identifies work beyond the dispatched scope, Contractor will stop at the scope boundary, document the finding with photographs, and submit a written scope-change request the same business day. Additional work will not commence until authorized under Clause 1. Diagnostic time already expended is billable whether or not the additional work is authorized."

Why that last sentence matters more than the rest of the clause: the most common quiet loss in property work is diagnostic time on jobs that are then declined. If the diagnosis is not billable, you are running free investigations for an owner who only pays when the answer is convenient. Say it once at signing and it is uncontroversial; raise it after the third declined job and it reads as a grievance.

Clause 4: Access failure

What it decides: who carries the cost of a trip where nobody could get in.

Language: "Manager is responsible for tenant notification and for access arrangements. Where Contractor arrives within the agreed window and cannot obtain access, the first occurrence per unit per work order is not billable. A second failed attempt on the same unit and work order, where Manager confirms notice was delivered for that attempt, bills at one half of the standard trip charge. A third failed attempt under the same conditions bills at the full trip charge, and the unit is removed from schedule until Manager arranges escorted access."

Read the Boolean: both conditions have to be true - a failed attempt AND confirmed notice for that specific attempt. A failure with no notice sent is not billable, because the failure was upstream of the tenant. Writing it that way is what makes the billable tiers credible when you invoke them.

If omitted: access failures are absorbed silently forever, and because they are invisible in your reporting nobody upstream ever fixes the notification process that causes them.

Clause 5: The tenant contact rule

What it decides: the boundary of your conversation with the occupant.

Language: "Contractor's techs will communicate with occupants regarding access, scheduling of the current visit, findings within the occupied unit, and any safety instruction necessary for the occupant's protection. Pricing, approval status, responsibility for cause, lease interpretation and scheduling beyond the current visit are directed to Manager. Occupant contact will occur through Contractor's office channels; techs will not use personal numbers for occupant communication."

Why it belongs in the agreement rather than your internal training: it protects the manager as much as it protects you, and a manager who has agreed to it in writing will back your tech instead of apologizing for them. See related: When the Tenant Is Not Your Customer but Is Your Problem.

Clause 6: The documentation deliverable

What it decides: what you hand over, in what form, and how fast.

Language: "Each completed work order will be delivered with: date and arrival time, unit identifier, condition found, work performed, parts used, remaining deficiencies, and photographs of the condition before and after. Deliverable within one business day of completion. Deferred findings will be reported as findings, not as quotes, and will not include pricing."

Why the no-pricing-in-findings line is in there: a findings report with prices attached gets read as a sales document and stalls. A findings report without prices gets forwarded to an owner intact, and the owner asks for a quote. That is the sequence you want, and it also keeps you off the hook for a number quoted before anyone scoped the work.

Clause 7: Payment cycle and the invoice packet

What it decides: when the clock starts, which is a completely different question from how long the clock runs.

Language: "Net 30 from receipt of a complete invoice packet. A complete packet comprises the invoice, the work order reference, the completion documentation under Clause 6, and, where applicable, the written approval under Clause 1 or Clause 2. Contractor will submit packets on a weekly cycle. Manager will notify Contractor within 5 business days of any packet deemed incomplete, specifying the missing item."

Why the packet definition is the load-bearing part: shops fixate on negotiating net 30 down from net 45 and lose far more time to packets that sat for three weeks because a photo or an approval reference was missing and nobody said so. The 5-business-day notification requirement is the clause that converts a silent stall into a specific request you can answer.

Payment cycles at management companies often key to an owner's disbursement schedule that the manager does not control, so ask what their cycle actually is before negotiating a number that cannot be met. Interest or late-fee terms are worth discussing but their enforceability varies by state and by contract type, so get those specific words from an attorney rather than from a template.

Clause 8: Term, coverage and exit

What it decides: which properties are covered, whether you are exclusive, and how either side leaves.

Language: "This agreement covers the properties listed in Schedule A, which may be amended by written agreement. Neither exclusivity nor a volume guarantee is granted or implied. Either party may terminate on 30 days written notice. Work orders open at the date of notice will be completed under these terms, and Manager will pay for completed work regardless of termination."

Why to refuse exclusivity even when offered: exclusivity without a volume guarantee is a commitment on your side and nothing on theirs, and it forces you to staff for a portfolio you may not be given. If they want exclusivity, the price is a stated minimum volume or a retainer, and that trade should be explicit.

The filled-in artifact

Here is the whole thing as a one-page schedule, filled in for a mid-size residential portfolio. This is what you actually put in front of a manager.

Two things to notice about the filled version. Every row is a number or a named party, and there is no row that says "as mutually agreed" - that phrase is where disputes go to be born. And the response-time rows carry their surge exception in the same schedule rather than in a paragraph elsewhere, because a manager scanning this table under pressure will read the row and not the prose.

The three clauses shops most often omit

Diagnostic time on declined work. Omitted because it feels petty at signing. It is the largest silent loss in the relationship, and it compounds: a portfolio that declines a meaningful share of recommended work is one where you have been running free investigations at volume.

The incomplete-packet notification window. Omitted because nobody imagines the invoice will simply sit. Without it, a stalled invoice is indistinguishable from a slow one, and you will not find out which it was until you chase it.

The scope boundary. Omitted because techs "use judgment." Judgment is exactly what a written boundary protects, because the tech who stops at the boundary and documents is now following the agreement rather than being unhelpful, and the manager already agreed that is what happens.

References

• See related: How to Set Response Standards a Manager Can Hold You To
• See related: How to Quote Work a Manager Has to Take to an Owner
• See related: The Property Manager as a Repeat Client
• State law governs late-payment terms, lien rights and termination notice; obtain contract-specific review from a licensed attorney in your jurisdiction