5
Contract-backed partners tied to key services
Vendor Accountability
Manage vendors as operational dependencies, not background assumptions.
Vendor management is now route-native in `apps/web`, making contract-critical services, escalation readiness, and evidence-backed accountability visible in the production shell.
1
Vendor case requiring active management
1
Vendor relationship slipping on responsiveness or evidence quality
30 min
Major-incident vendor acknowledgment expectation
Vendor Register
Vendor relationships should be visible in terms of dependency, responsiveness, and current operational posture.
| Vendor | Service Dependency | Current Performance | Owner / Next Action |
|---|---|---|---|
| Remote access provider | High-severity remote access continuity | Active escalation; response engaged but deeper RCA still needed | Nina / maintain evidence pressure and case cadence |
| Identity service partner | MFA and authentication integration support | Healthy response and no current service watch | Service desk lead / quarterly review only |
| Public web hosting partner | Publishing and website edge stability | Healthy, but maintenance communication quality needs improvement | Elena / revise communication expectations |
| Observability platform support | Monitoring and alert pipeline assistance | Performance watch on one support ticket aging path | Carlos / document repeated delay pattern |
| Data integration vendor | Upstream source availability and schema reliability | Stable overall, but pre-check evidence should be tighter | Jamie / improve issue packet template |