A preferred contractor network is the curated set of trade organisations you trust for each site, trade and sometimes region. Ranking decides who receives the next job when multiple firms cover the same category. Preferred status is not merely a label — it implies you expect them to accept within SLA, attend with induction satisfied, and close with proof.
OpsChase stores preferred assignments per site or group-wide, respects after-hours flags, and falls back to backups when the primary is silent. Performance scores and do-not-use lists inform future ranking. Open marketplace RFQ remains available when the book cannot cover a locality, but day-to-day operations should not feel like a lead directory.
Load your book, invite organisations once, and set ranks per trade. Raise work orders; assignment targets the top eligible preferred vendor. Chase runs on the same record until proof completes. Review stalled jobs at portfolio level instead of per-site email.
See chase-to-proof for closure mechanics and contractor compliance for document gates.
OpsChase turns this into a working flow: chase your preferred contractors to done, require proof before a job closes, and RFQ with compliance onboarding when you need the market. Book a demo to see it on your sites — one location or many.
- Can franchisees keep local contractors?
- Yes. Site-scoped books and ranks coexist with national agreements.
- How are backups chosen?
- You define ordered backups per site or trade; chase escalates when primaries breach SLA.
- Does preferred block new vendors forever?
- No. RFQ plus onboarding adds firms when you expand coverage.