The Turnover Math Is Not a Surprise
Every four-year election cycle produces a substantial wave of state CIO changes. NASCIO's median tracking showed state CIO tenure at approximately 19 months in January 2024, after an unusually active 2023 departure period (Greene Barrett), and just over two years in NASCIO's October 2025 survey. NASCIO's executive director, Doug Robinson, has said: "When there is a change in governor, even of the same party, there's usually a change in CIO" (StateScoop, November 2018). A 2019 Government Technology analysis found a sitting CIO survives a change in governor only about one-third of the time (GovTech, June 2019); GovTech's 2024 restatement put new-CIO turnover at 60 percent (GovTech, Aug 2024). Those figures are several cycles old; treat them as directional, not a current measurement. Robinson has also said the rate of new CIOs rises when the governor's party changes (StateScoop, November 2018).
The 2023 departure wave illustrates a related risk: Doug Robinson called that year's 23 CIO-level transitions "double the ordinary" (Greene Barrett). He said most were departing to the private sector, and noted that turnover of that scale is expected after years with many new governors, as in 2019, whereas only nine new governors took office in 2023. The point is not that elections alone cause every departure; it's that high baseline churn combined with a 39-race election creates concentrated risk for 2027 regardless of how any individual transition originates.
A Gartner webinar on October 15, 2026 addressed how government CIOs should plan for disruption from the November elections, including gubernatorial party flips, subtler leadership shifts when a party retains control, and changes to policy priorities and funding models. A Tyler Technologies-sponsored paper states that navigating change is a crucial skill for state CIOs.
None of this is new information. What's new is the timing: November 3 is close enough that documentation started today will be complete in time to matter. Documentation started in January will arrive after the first consequential decisions have already been made wrong.
What Goes Wrong When Documentation Doesn't Exist
The failure modes in state IT transitions are documented across enough cycles to be predictable.
Inherited projects without context. A new CIO receiving a large modernization project—an MMIS replacement, a legacy benefits system migration, an ERP rollout—without a detailed current-state briefing will make changes based on visible signals rather than actual risk. In Spartan X's assessment, vendor substitutions and scope reductions that look decisive at the outset can add a year or more to delivery timelines, because an incoming vendor must rebuild the institutional context the outgoing vendor held. The vendor already knows the project; the new CIO has to catch up while the contract clock runs.
Budget commitments that outlive the leadership who made them. Multi-year technology contracts, Advance Planning Documents with federal cost-sharing conditions, and capital budget requests submitted in one administration obligate the next one. New political leadership that doesn't understand these commitments often resists or seeks to undo them—at cost to schedule, vendor relationships, and federal matching funds.
Security continuity gaps. Open incidents, ongoing remediation commitments tied to federal grant terms such as the State and Local Cybersecurity Grant Program, data-sharing agreements, cyber-insurance carriers or audit findings (and CISA's Known Exploited Vulnerabilities catalog, which CISA says organizations should use as an input to their vulnerability management prioritization), and active vulnerability disclosure timelines don't pause for transitions. If the incoming CIO doesn't know an incident is open, no one is accountable until something surfaces publicly.
The vacancy period. Robinson has said new governors typically fill the CIO position last (StateScoop, November 2018), and GovTech documented that in 2011 incoming Kansas Gov. Sam Brownback took more than 10 months to name a CIO (GovTech, June 2019). A vacancy of several months is common in practice. Budget submissions, vendor escalations, and press inquiries during that window route to whoever is available, not whoever is qualified.
What to Document Before November
A transition brief is not a strategic plan or a catalog of accomplishments. An incoming CIO and their transition team need the current operational picture: what is running, what is broken, what has a clock on it, and who to call. The following structure is a recommended starting point, focused on what an incoming team needs to act on rather than what gets prepared and ignored.
Active project register. For each active project above a defined spending threshold: the prime vendor and contract expiration date; the current phase and deliverables in flight; the next milestone with its dependency; the open risks and unresolved issues; the name of the state employee who holds the primary vendor relationship; and the first decision the incoming CIO will face within 90 days. Keep this document live, not static—projects move faster than briefing cycles.
Budget commitments with a clock. FY2027 budget requests in process with the legislature or the governor's budget office. Multi-year obligations and encumbrances. Remaining ARPA/SLFRF spending against the December 31, 2026 expenditure deadline: Treasury's SLFRF final rule overview states funds must be obligated by December 31, 2024 and expended by December 31, 2026 (see also Treasury's SLFRF program page; a UNC School of Government piece covers the local-government side). Federal matching conditions—CMS enhanced FFP on Medicaid IT modules, Unemployment Insurance grants, SLCGP cybersecurity grants—that require compliance with specific program requirements to keep the match rate. Cloud contracts and SaaS subscriptions by renewal date.
Security and incident status. Current posture against the security requirements the state is actually bound by (federal data-sharing agreements such as IRS Publication 1075, which applies to state and local agencies receiving federal tax information; SLCGP grant conditions; and the state's own security policy); open incidents with their remediation commitments; third-party risk assessments in progress; the contracts and in-house teams responsible for ongoing monitoring. A one-page summary suitable for a morning briefing, not a full audit report.
Organizational knowledge map. For each major system: which career employees hold the institutional knowledge, how long they've been in the role, and whether their departure would leave a gap. Open recruitments with hiring authority status. The distinction between state employees and contractors on active programs. Where documented runbooks exist and where they don't.
The Career Executive's Position
Political CIOs change. Deputy CIOs, enterprise architects, and program managers often don't. In the weeks between an election and an inauguration, career IT staff carry more authority than their titles suggest. That creates both opportunity and risk.
What career staff should do proactively. Governor's transition teams increasingly include technology advisors—sometimes from the private sector, sometimes from previous administrations. Getting access to those advisors before inauguration is feasible and valuable. A career deputy who briefs the transition team on commitments and constraints shapes what the incoming CIO inherits. The alternative is watching a new CIO discover constraints through vendor escalations and legislative questions.
What to flag and what to hold. Identify the decisions that have a hard deadline in the first 30 to 60 days: contract renewals, federal reporting deadlines, budget submission windows, open incident remediation dates. Flag those explicitly. Do not overwhelm the incoming CIO with every problem simultaneously. The goal is ensuring the time-sensitive decisions are made with enough information, not comprehensive orientation in week one.
Resist first-90-day change pressure. New administrations frequently feel pressure to demonstrate visible change. A CIO who replaces a vendor or restructures a program in the first quarter may be responding to political signaling rather than operational evidence. Career staff who can articulate the cost of a change—time, money, federal funding implications, incumbent institutional knowledge—provide a check on decisions that look decisive but create problems in year two.
What an Incoming CIO Actually Needs in Week One
The incoming CIO's first obligation is to the new governor, who has a mandate and a timeline. The career IT organization's job is to make that mandate achievable within the constraints of what's already running.
Week one should answer three questions for the incoming CIO:
What can't wait? Two to five items with hard deadlines in the next 30 to 45 days. These are not the most important issues; they're the ones where inaction has a specific cost.
What looks like it can change but actually can't? The projects where the switching cost—financial, federal compliance, vendor knowledge—is prohibitive. A candid briefing on these prevents the incoming CIO from promising constituents something that would cost years to deliver.
Who are the five career employees whose departure would stop critical programs? Retention risk in state IT is real, and key departures often cluster around transitions. The incoming CIO needs to know who those people are and what it would take to keep them.
The Structural Fix: Designate Acting Authority Now
The vacancy problem has a straightforward mitigation: formal acting designations before November 3. A deputy CIO with explicit authority to make operational decisions—defined scope, defined dollar threshold, defined escalation path—can hold programs together through a transition without waiting for a new political appointment.
States that have managed transitions well have typically done two things: documented the operating model before the transition started, and designated the career leader who would carry it. Neither requires a change in law; both require deliberate administrative action while the outgoing administration still has authority to take it.
Sources and further reading
- CIO retentions under new governors 'surprising,' says NASCIO director — StateScoop (January 2019), covering NASCIO executive director Doug Robinson on transition patterns
- 20 states are probably getting new CIOs — StateScoop (November 2018), prior election cycle analysis
- The Club of 50: Data on State Chief Information Officers — Government Technology (June 2019), CIO survival and vacancy data
- Will the 2024 elections lead to a massive CIO changeup? — Government Technology (August 2024)
- State CIOs Navigate Through Uncertainty — NASCIO (October 2025), median tenure
- NASCIO 2026 State CIO Survey coverage — Government Technology (September 2026)
- Where Did All the CIOs Go? — Greene Barrett (January 2024), 2023 CIO transitions
- Navigating Political Change Without Slowing Innovation — Tyler Technologies-sponsored paper (GovTech Papers, 2026)
- US Fall Elections: Risks, Scenarios and Implications for Government CIOs — Gartner webinar, October 15, 2026
- State and Local Fiscal Recovery Funds: Final Rule Overview — U.S. Department of the Treasury (expenditure deadline)
- State and Local Fiscal Recovery Funds — U.S. Department of the Treasury
- Safeguards Program (Publication 1075) — IRS
- State and Local Cybersecurity Grant Program — CISA
- Known Exploited Vulnerabilities Catalog — CISA
- 2026: The Final Countdown Has Begun for ARP SLFRF — UNC School of Government (January 2026)
Spartan X's state government work spans AI strategy, cybersecurity and enterprise architecture advisory for state leadership in Colorado and Florida. That is the system-level context a career team needs when it documents which commitments are structural, which are fungible, and what a new principal must decide in the first weeks of a term.
