12
Work items in the active scoring model
Current Ranked Work
The ranking model is intentionally visible so people can understand why one item belongs above another.
| Rank | Work Item | Priority Score | Why It Is Here |
|---|---|---|---|
| 1 | INC-2041 Remote Access Latency Infrastructure / active disruption |
96 points 97% urgency confidence |
Active business disruption, high service visibility, vendor dependency, and leadership update requirement. |
| 2 | SEC-2274 MFA Exception Review Governance / security risk |
88 points 91% risk confidence |
Not outage-driven, but carries audit and control exposure with a hard review expectation. |
| 3 | REQ-2188 Temporary Staff Access Setup Approval-bound access request |
84 points 89% delivery confidence |
User onboarding blocked, technically ready, and primarily waiting on named approval. |
| 4 | REP-2335 Public Data Refresh Validation Repeat-issue candidate |
79 points 86% pattern confidence |
Moderate user impact today, but elevated because repeat-failure risk could become externally visible. |
| 5 | ENH-2219 Leadership Dashboard Automation Data / reporting improvement |
72 points 82% value confidence |
High recurring value, but depends on sponsor tradeoff rather than immediate incident pressure. |
| 6 | COL-2303 Teams Ownership Cleanup Collaboration improvement |
54 points 77% value confidence |
Useful operational hygiene work, but lower immediate business risk than the items above. |
Priority scores combine urgency, business impact, service dependency, aging, approval delay, repeat-issue potential, and leadership visibility. The point is not to let AI decide alone. The point is to make the reasoning explicit enough for humans to trust or challenge it.
AI Reordering Recommendations
Suggestions should be framed as explainable decision support, not as blind automatic reprioritization.
Raise+11 points
REP-2335 Public Data Refresh Validation
Recommendation: move from rank 4 to rank 3
Reason
Repeat-failure risk and public visibility are now higher than the current placement suggests.
Evidence
Recent anomaly pattern plus past delay history increase exposure before the next refresh window.
Assign To AI Operation: Eligible to assemble repeat-issue evidence, compare historical failures, and draft a validation work package.
Raise+9 points
REQ-2188 Temporary Staff Access Setup
Recommendation: keep technically ready items above lower-urgency enhancements
Reason
End-user onboarding delay is business-visible and immediately unblockable once approval arrives.
Evidence
Approval dependency is named, technical readiness is complete, and user wait time is increasing.
Assign To AI Operation: Eligible to prepare approval reminders, least-privilege checklist, and summary note for service desk review.
Lower-8 points
COL-2303 Teams Ownership Cleanup
Recommendation: keep visible, but below higher-risk dependency work
Reason
Operationally useful, but lower business impact and lower near-term risk than current queue neighbors.
Evidence
No current outage, no hard compliance date, and stakeholder review is already scheduled.
Assign To AI Operation: Eligible to prepare ownership-review checklist and archive-planning draft; not eligible for workspace changes.
Hold0 point change
SEC-2274 MFA Exception Review
Recommendation: keep in the top tier of manager-visible work
Reason
This remains high because security exposure and audit consequences outweigh its lack of outage impact.
Evidence
Time-bound exception plus control-review requirement create enterprise risk if deferred.
Assign To AI Operation: Eligible to compile exception history and draft a review packet under security-owner approval.
How The Score Is Built
The ranking model should be transparent enough that a manager can defend it or override it.
Business disruption
How much the issue affects staff, services, leadership visibility, or public-facing work.
Time pressure
Deadlines, aging, service windows, and whether delay meaningfully worsens the outcome.
Governance and control
Security, compliance, audit, and policy exposure that may not appear in standard incident severity.
Hidden blockers
Vendor reliance, approval chains, or upstream dependencies that increase operational fragility.
Pattern pressure
Whether the work represents a recurring issue that should be elevated before it becomes a bigger problem.