Every brokerage in the country has vendor SLAs written into contracts. Very few brokerages have vendor SLAs that actually hold across markets. The gap between the two is the difference between a media program that scales and one that runs on heroics.
The reason contract SLAs do not hold is not that the contracts are weak. It is that contracts are reviewed once a year and SLAs need to be enforced once a shoot. The fix is to move SLAs out of the contract footer and into the workflow itself, where the system can flag a violation before the listing agent even knows the shoot ran long.
The four workflow SLAs that cover ninety percent of services
Most enterprise programs we have audited carry eight to fifteen SLAs in their vendor contracts. The dashboard nobody looks at then carries the same fifteen. By the time the operations team has read through them, the next shoot has already started. Four SLAs is the right number. Each one is unambiguous, machine-checkable, and tied to a specific operational outcome.
SLA 1: on-time arrival
Operator is on site within fifteen minutes of the scheduled start. The platform stamps the arrival from the operator app or the GPS-verified check-in. A late arrival is logged the same business day. Repeated late arrivals trigger the coaching cycle, not a year-end review.
SLA 2: complete shot list capture
Every shot the spec requires is captured. Verified at delivery against the spec for that service. A missing shot is flagged before the asset reaches marketing. The vendor either supplies the missing capture inside a defined window or the delivery is rejected.
SLA 3: post-processing within window
Edited deliverables land within the spec window from shoot completion. Photography typically 24 to 48 hours, video 48 to 96, 3D 48 to 72, floor plans within 72. The window is on the vendor; rush options compress it on a per-order basis with the rush surcharge applied automatically.
SLA 4: asset upload to library
Within sixty minutes of post-processing completion, every deliverable is in the asset library with full metadata. Listing address, property type, shoot date, vendor, spec version, status. Without this SLA, the library is a place assets eventually land instead of where they live.
Why the workflow, not the contract
Contract SLAs live in the legal annex. Nobody reads the legal annex during a Friday afternoon rush to get a luxury residential listing live for the weekend. By the time the SLA miss is caught, the listing is already late, the agent has already escalated, and the vendor relationship is already bruised. The contract’s answer is a credit clause that nobody invokes because invoking it requires a longer email than the lost weekend was worth.
Contract SLAs are reviewed after a failure. Workflow SLAs are enforced before one. The difference is whether the platform catches the miss in time to prevent the listing from going live late.
Workflow SLAs run on telemetry. The operator’s arrival is a timestamp. The shot list is a checklist verified at upload. The post-processing window is a clock. The library upload is an event the system can detect. None of these require a human to notice the SLA was missed; they all surface the violation automatically while there is still time to resolve it.
Scoring without micromanagement
SLA enforcement is not surveillance. It is a closed-loop system that rewards the operators who perform and rotates out the ones who do not, without the procurement team having to manage the relationship by hand. The score has three pieces.
Rolling thirty and ninety
Every SLA produces a binary pass-fail per shoot. The roll-up is on two windows: a thirty-day score that catches recent slippage and a ninety-day score that smooths out a single bad week. A vendor whose ninety-day score is strong but thirty-day is degrading enters early coaching. A vendor whose ninety-day score is consistently weak rotates out.
Threshold one: coaching
Below the first threshold (we set it at 88 percent SLA compliance for most services), the vendor enters an automated coaching cycle. The platform attaches the specific spec violations from the recent failed shoots, schedules a coaching call with the regional operations lead, and resumes routing only after the cycle clears. No one has to chase the vendor; the system does.
Threshold two: rotation
Below the second threshold (typically 75 percent), the vendor is rotated out of the local routing pool for sixty days. The rotation is not punitive; it is operational. The vendor still gets the failed deliverables to address. The pool fills with higher performers in the meantime. The platform watches for a return to threshold before re-engaging.
What fails when SLAs do not hold
The visible failure is the late listing. The deeper failures are the ones the brokerage almost never connects back to the SLA program directly.
- Mandate loss. Sellers shopping three brokerages notice the one whose listings consistently go live first. SLA compliance is the input variable.
- Vendor concentration. When SLAs do not hold, offices revert to a handful of trusted operators. Concentration risk grows quietly and surfaces during a spike week or a vendor exit.
- Brand drift. Without workflow SLAs, spec compliance follows the SLA into the abyss. Photography quality across markets drifts and the CMO loses the brand consistency case at the next board review.
- Finance unpredictability. Rush surcharges and SLA credits move from automated rules to ad-hoc adjustments, which is the failure mode finance never forgives.
Implementation sequence
A workflow-SLA program ships in three phases. The whole program should land inside one calendar quarter on a typical enterprise rollout.
- Phase one (weeks 1 to 3). Define the four SLAs per service against the existing spec. Set the coaching and rotation thresholds. Wire the telemetry into the platform.
- Phase two (weeks 4 to 8). Pilot in one region. Surface and tune the SLA dashboards with the regional operations lead. Resolve the false positives that always show up in the first thirty days.
- Phase three (weeks 9 to 12). Roll out across the remaining regions. Vendor communications go out with the published thresholds and the coaching path. The program is fully live by the end of the quarter.
AssetOSX runs this SLA framework as part of every enterprise rollout. The implementation phases are summarized on the enterprise FAQ.
