Where state IT money and staff go next: outlook to 2027

Budgets, audits, statutes and governors' orders from six states show smaller flexible modernization funds, more project oversight, IT staff moving in-house and agency AI rules shifting from executive orders into law.

Six states, four questions

State technology budgets are set one legislature at a time, so a national picture built from official records has to start from a sample. This outlook reads the enacted statutes, budget analyses, auditor reports and governors' orders of six states whose official documents we could open and check on November 16, 2026: California, Maryland, Pennsylvania, Texas, Virginia and Washington. Three of them (California, Maryland and Texas) publish recurring statutory reports on a modernization fund or a legacy-system list, which is why they carry most of the figures; the other three add the executive orders that govern how agencies use AI. The sample is not representative of all states, and nothing here is drawn from trade association surveys. It asks four questions: where dedicated modernization money stands, what is known about legacy systems, what the records show about IT staff, and how AI use by agencies is being governed.

The sample: documents opened for each state
StateMoney and legacy systemsStaff and auditsAI use by agencies
CaliforniaDepartment of Technology reports on its modernization and stabilization funds, January and June 2026 [9] [18]State Auditor report 2022-114 [10]Not reviewed for this piece
MarylandLegislative analysis of the fiscal 2027 budget [1]; project portfolio report [2]Legislative audit follow-up [3]; vacancy data [1]Chapter 496 of 2024, as summarized by the legislature's analysts [1]
PennsylvaniaNot reviewed for this pieceNot reviewed for this pieceExecutive Order 2023-19 and the 2025 pilot results [11]
TexasLegacy and cybersecurity project report [4]; modernization fund [5]State Auditor turnover report [8]S.B. 1964 [6] and 1 TAC chapter 219 [7]
VirginiaNot reviewed for this pieceNot reviewed for this pieceExecutive Order 22 [12] and Executive Directive 6 [13]
WashingtonNot reviewed for this pieceNot reviewed for this pieceExecutive Order 24-01 [14] [15]

Cybersecurity grants, Medicaid and benefits systems, web accessibility and state AI laws aimed at private companies each have their own Moraph outlook; this piece links to them rather than repeating them.

Modernization money: smaller pools, more oversight

California's dedicated funds are running out. The Legislature gave the Department of Technology $25,000,000 in the 2021 Budget Act for a Technology Modernization Fund for projects of $5,000,000 or less, then $25,711,000 more for that fund and $30,000,000 for a Technology Stabilization Fund in 2022 [9]. Both were cut in January 2023: the modernization fund from $50 million to $29.7 million and the stabilization fund from $30 million to $12.5 million [18]. In its January 2026 report the department said the money would be fully spent when the last project ended and that, with $100,000 in remaining statewide funding, future modernization would rely mainly on talent and technical guidance rather than funding [9]. Its June 2026 report says the modernization fund paid for 21 systems across 16 state agencies, that the last project was completed in February 2026 and that the $121,755 left in the fund will cover expected contracting fees; it expected the stabilization money, an appropriation that expired on June 30, 2026, to be fully committed by that date [18].

Maryland is moving the other way in size but tightening control. Its Information Technology Investment Fund, a nonlapsing fund for major projects, carries $124.7 million in the Governor's fiscal 2027 allowance (the proposed budget the legislature's analysts reviewed in early 2026), and ten projects receive at least $5 million each in general funds, for a total of $87.7 million, led by the Comptroller's financial system replacement at $15.7 million [1]. Chapter 497 of 2024 raised the cost threshold for a major project from $1 million to $5 million and created a category of "expedited projects" for IT projects that are not major projects but receive money from the fund [1]. The legislature's analysts recommended deleting the $3 million set aside for expedited projects to give the department time to finish its eligibility criteria and its list of proposed eligible projects [1]; we did not confirm the enacted fiscal 2027 figures, which may differ from the allowance. The portfolio is large: the department's January 2026 report counts 60 active projects across 19 agencies, $315,431,787 appropriated in fiscal 2026 and an estimate at completion of $1.835 billion to $2.495 billion [2].

Oversight is where the new money goes. Chapters 845 and 846 of 2025 led Maryland to create a project oversight division with discovery and intervention teams, and the fiscal 2027 allowance holds $3.5 million for 10 discovery sprints, $5 million for 16 intervention teams and $4.3 million for oversight operations [1]. The reason is visible in the results: the share of major projects on schedule fell from 59% in fiscal 2024 to 55% in fiscal 2025, and the share spending within 10% of plan fell from 62% to 23% [1]. The state's auditors had rated the department's accountability and compliance unsatisfactory in March 2024, and a March 2025 follow-up found it had not fully resolved any of the 10 non-cybersecurity findings it reviewed, including findings on project monitoring [3].

The 87th Texas Legislature created a Technology Improvement and Modernization Fund that may be used for state agency legacy system and cybersecurity projects [5]. The Comptroller's fund page shows its purpose and statutory basis but no balance [5], and we could not confirm from an official document what the current biennium appropriates to it.

Moraph's view

Moraph's view: in the three states with recurring reports, the pool of flexible modernization money is not growing. California's is all but spent, Maryland's large fund is spent on a handful of very large replacements and an increasing amount of oversight, and Texas's fund exists in statute without a figure we could confirm. We expect state modernization in 2027 to be paid for through ordinary agency budget requests and federal program money, with central IT offices spending more on review and intervention than on funding projects directly.

Legacy systems: the lists exist, the names stay private

Texas law requires the Department of Information Resources and the Texas Cyber Command to give the Legislative Budget Board, by October 1 of each even-numbered year, a ranked list of agency cybersecurity and legacy modernization projects for funding [4]. The 2026 report covers 81 projects from 26 agencies requesting about $840,565,533, with the group the report labels Quadrant I holding 21 projects and $394,862,854 [4]. The department and the Cyber Command treat the report's contents as confidential under state law, and the version posted publicly gives only aggregate totals [4].

California has caught up on an inventory its auditor said was missing. In April 2023 the State Auditor reported that the Department of Technology had not yet identified the statewide systems that are outdated and need modernization [10]. By January 2026 the department had cataloged 90 critical IT systems named by departments as essential, said it does not publish their names because some have significant stability or security risks, and had completed no new stabilization assessments in its latest reporting period while it reset that program [9]. By June 30, 2026 the inventory had grown to 144 systems, five had been placed in the assessment pipeline with one assessment complete and another under way, and the department counted 20 stabilization assessments and 472 recommendations to date [18]. Maryland's portfolio report gives a concrete example of the age involved: the State Board of Elections' voter registration system, which a new project will replace, is twenty years old [2].

Moraph's view

Moraph's view: the next two years of legacy work will be driven by ranked lists that legislators see and the public does not. Vendors and agencies should expect funding decisions in the 2027 Texas session to follow the published quadrant totals, not individual system names, and should not expect states to publish full lists of the systems at risk.

Staff: steadier IT turnover, a shift from contractors, and old gaps

Turnover among Texas's classified state IT staff is well below the state average. The State Auditor reports statewide turnover of classified employees at 15.4 percent in fiscal 2025, down from 16.5 percent, while the Information Technology occupational category, with an average headcount of 4,978.75, had 442 separations and a turnover rate of 8.9 percent [8]. Within it, systems analysts turned over at 8.7 percent and cybersecurity analysts at 9.1 percent [8].

Maryland is converting contract work into state positions. The fiscal 2027 allowance adds 11 regular positions and 91 contractual full-time equivalents to the Department of Information Technology; 86 of the contractual positions were previously paid through vendor contracts and would move in-house to generate savings and reduce dependence on vendors [1]. The department had 34 regular positions vacant on December 31, 2025, a vacancy rate of 12.98% [1].

California's auditor recorded the older problem. Agencies it surveyed named hiring and keeping qualified IT staff as their greatest challenge; as of August 1, 2022 the Department of Technology had a 14 percent vacancy rate, with 153 vacancies among roughly 1,000 positions, and it had estimated in 2018 that 45 percent of its workforce was at retirement age or within five years of the average retirement age [10]. Those figures are now more than three years old, and we found no newer official count for this piece.

Moraph's view

Moraph's view: the Texas figures do not support a picture of IT staff churning out of state service; IT turns over at a little over half the state rate. The pressure is elsewhere: replacing the experience that retires, and finding staff to run oversight and AI governance work that new statutes now assign. Maryland's move from vendor contracts to state contractual positions is the pattern we expect other states to test where budgets are tight, because it trades contract cost for headcount that legislatures can see.

AI use by agencies: from executive orders to statute and rule

Texas has put agency AI governance into law. S.B. 1964, effective September 1, 2025, requires the Department of Information Resources to set by rule an AI code of ethics for state agencies and local governments and minimum risk standards for "heightened scrutiny" AI systems, both in line with the NIST AI Risk Management Framework; it also requires agencies to disclose when the public interacts with a public-facing AI system, and agencies or their vendors to assess heightened scrutiny systems [6]. The department adopted 1 TAC chapter 219, effective March 18, 2026; agencies and local governments must adopt the code and designate an employee as AI Risk Officer, and must inventory the heightened scrutiny AI systems they use [7] [16]. The department noted that the local governments covered may include about 1,100 rural communities [7].

Maryland did the same by statute in 2024. Chapter 496 of 2024 requires units of state government to inventory their data and their AI systems and to assess the impact of AI systems, creates a proof-of-concept procurement path, and puts the AI Subcabinet into law; the fiscal 2027 allowance holds $2.1 million in general funds for AI innovation [1].

Executive orders remain the main tool elsewhere in the sample, and they change with governors. Virginia's Executive Order 22 of September 18, 2026 rescinded Executive Order 30 of January 18, 2024, while keeping the policies, standards and guidelines published under it in effect until replaced through a future executive or agency action, and created an AI Task Force and an AI Policy Planning Unit [12]. The Virginia Information Technologies Agency now lists Executive Order 30 as rescinded but still lists its standard EA-225 on acceptable and ethical AI use by agencies and suppliers, and posted a job aid for a new AI registry dated October 2026 [17]. On October 23, 2026, Executive Directive 6 told the Secretary of Public Safety and Homeland Security to set up a Cyber Consortium to plan for AI-related cyber attacks, engaging with the Chief Information Officer of the Virginia Information Technologies Agency [13]. Washington's Executive Order 24-01, signed January 30, 2024, set deadlines in 2024 and January 2025 for procurement guidelines, high-risk use criteria and a training plan for state workers [14], and the governor's office still lists it as active [15]. Pennsylvania's Executive Order 2023-19 created a Generative AI Governing Board; the Governor's office reported that employees in a pilot with 175 staff from 14 agencies reported saving an average of 95 minutes per day, a self-reported figure the state published for its own pilot rather than an independent measure [11].

Moraph's view

Moraph's view: AI use rules written into statute, as in Texas and Maryland, give agencies fixed duties (an officer, an inventory, an assessment) that survive a change of governor, and they create staff work that budgets must fund. Rules set by executive order are faster to issue and faster to replace, as Virginia shows. Federal moves against state AI laws, covered in our state AI laws outlook, are aimed at private-sector rules and so far leave states' rules for their own agencies alone.

What to watch in 2027 and 2028

  • Texas's 2027 regular session, which receives the ranked legacy and cybersecurity list [4].
  • Maryland's fiscal 2028 budget analysis for the Department of Information Technology, which will report whether project schedule and cost measures recovered [1].
  • California's next Department of Technology reports, and how many of the 144 inventoried systems receive stabilization assessments now that the stabilization appropriation has expired [18].
  • Virginia's replacement for the AI policies and standards kept in effect from Executive Order 30 [12].

What this means for you

  • State CIOs and budget offices: Plan 2027 modernization on agency budget requests rather than central funds where those funds are spent or capped, as in California [9], and expect legislators to ask for schedule and cost measures of the kind Maryland's analysts now publish [1].
  • Agency leaders in Texas and Maryland: Budget the staff time for duties already in law: a designated AI Risk Officer, an inventory of heightened scrutiny systems and impact assessments in Texas [6] [7], and AI system inventories and impact assessments in Maryland [1].
  • Vendors selling to state governments: Expect more review before money moves: Maryland's discovery sprints and intervention teams [1], Texas's assessment duty for vendors of heightened scrutiny AI systems [6], and California's shift from funding to advisory support [9].
  • Legislative staff and auditors: Follow up on open findings: Maryland's auditors found none of the 10 reviewed non-cybersecurity findings fully resolved in their March 2025 follow-up [3].

Moraph predictions

Every prediction is Moraph's view, not a fact. Each has a date, a confidence level (70% means we expect to be wrong about three times in ten) and a test anyone can apply. We score them on this page when the date comes and never remove one. How we make and score predictions.

  1. P1 By Confidence 65% Open

    The Department of Legislative Services analysis of the Maryland Department of Information Technology (F50) in the fiscal 2028 budget reports that fewer than 60 percent of major IT development projects were on schedule in fiscal 2026.

    How we will check: Open the DLS analysis of the FY 2028 Maryland Executive Budget for F50 on mgaleg.maryland.gov and read the Managing for Results measure of major projects on schedule for fiscal 2026; right if the figure is below 60 percent, wrong if it is 60 percent or more; unscorable and marked partly if the measure is no longer reported.

    Basis: The share of projects on schedule fell from 59% in fiscal 2024 to 55% in fiscal 2025, and the share within 10% of planned spending fell from 62% to 23% [1]; the new oversight division was only set up under Chapters 845 and 846 of 2025 [1].

  2. P2 By Confidence 85% Open

    The Texas State Auditor's annual classified employee turnover report for fiscal year 2026 shows a turnover rate for the Information Technology occupational category below the statewide turnover rate.

    How we will check: Open the State Auditor's annual report on classified employee turnover for fiscal year 2026 on sao.texas.gov and compare the Information Technology category total turnover rate with the statewide turnover rate.

    Basis: In fiscal 2025 the Information Technology category turned over at 8.9 percent against 15.4 percent statewide [8].

  3. P3 By Confidence 70% Open

    California's Budget Act of 2027 does not appropriate new General Fund money to the California Department of Technology for the Technology Modernization Fund or the Technology Stabilization Fund.

    How we will check: Read item 7502 of the Budget Act of 2027 as enacted, and the Department of Technology's next report on the two funds, if one is issued; right if neither shows a new appropriation for either fund.

    Basis: Both funds were cut in January 2023, and in January 2026 the department said that, with $100,000 in remaining statewide funding, future modernization would rely mainly on talent and technical guidance [9]; by June 2026 every modernization fund project was complete and the stabilization appropriation expired on June 30, 2026 [18].

  4. P4 By Confidence 50% Open

    Virginia's governor issues an executive order or executive directive that sets requirements for executive branch agencies' own use of AI, replacing the policies and standards kept in force from Executive Order 30 (2024).

    How we will check: Review the executive orders and directives on governor.virginia.gov issued through December 31, 2027; right if one sets agency AI use requirements and states that it replaces policies or standards published under Executive Order 30.

    Basis: Executive Order 22 rescinded Executive Order 30 and kept its policies, standards and guidelines in effect until replaced through a future executive or agency action, so the replacement may come from an agency rather than the governor; it also set up an AI Task Force and an AI Policy Planning Unit [12]; Executive Directive 6 followed a month later on AI cyber risk [13].

Facts on this page link to their sources. Text marked "Moraph's view", and every prediction, is our own analysis, not a fact or advice. Methodology.

Spotted an error? Tell us and we will check it and correct the piece where needed.

  • state CIO
  • IT modernization fund
  • legacy systems
  • state IT workforce
  • AI use policy
  • Maryland ITIF
  • Texas PCLS
  • Texas S.B. 1964
  • California Department of Technology