Feature
One score per vendor, built from what they've actually done
A vendor's reputation inside a PM company usually lives in one coordinator's memory. Meridian rolls job history, SLA adherence and licence/insurance status into a single vendor performance score, visible across every building that vendor works in.
The problem
Vendor performance tracked informally, per building or per coordinator, means a vendor who's slipping in one area of the portfolio can keep getting dispatched elsewhere without anyone connecting the pattern.
Why it matters
Repeat SLA misses or licence lapses are much easier to act on when they're visible as a trend across the whole portfolio, not scattered across individual job records.
How Meridian helps
- A performance score per vendor built from completed job history, not gut feel
- SLA adherence feeds directly into the score, tying response time to future vendor recommendations
- Licence and insurance status factored in alongside performance history
- Score and history visible across every building the vendor is assigned to, not siloed per property
FAQ
What feeds into the vendor score?
Job history, SLA adherence and licence/insurance compliance status combine into a single per-vendor score.
Does the score affect future dispatch?
Vendor recommendation during maintenance triage draws on the performance score, alongside licence status and building approval.