ODOE Approval Workflow

Approval Workflow

Shows how requests move through review, approval, escalation, and final authorization.

Why It Matters

Approvals should be visible, time-bound, and easy to escalate.

Government IT often waits on review, authorization, or leadership tradeoffs as much as on technology. This page makes that visible by showing where an approval sits and who needs to act next.

Access approvals Security exceptions Prioritization tradeoffs Change authorizations
current queue
6

Items in approval state

needs follow-up
2

Aging approvals

automated
3

Reminder / routing actions

clear
1

Executive decision currently pending

Core Approval Flow

The goal is to make authorization simple enough to follow and strong enough to govern risk.

1

Request Submitted

The request enters through the shared intake path with the business need, desired timing, and affected users or systems.

2

IT Review

IT validates that the request is understandable, classifies the work, and determines whether approval is required.

3

Business / Risk Approval

The right approver confirms access, ownership, risk acceptance, or tradeoff decision depending on the request type.

4

Implement And Notify

Once approved, IT proceeds with the work, records the decision, and updates the requester and stakeholders.

Who Approves What

Different requests should not all route to the same person. This keeps governance simple and credible.

Request Type Primary Approver Secondary Review Example
Access / identity Business owner or supervisor IT validates least privilege Temporary staff onboarding
Security exception Risk owner / manager Security governance review MFA exception review
Priority tradeoff Leadership sponsor IT manager outlines queue impact Leadership dashboard automation vs other enhancement
Planned change Service owner / change authority IT readiness confirmation Energy Strategy site update