Case File No. 001 · From the field
UCPath
An ordinary payroll modernization that became a near-billion-dollar case study in governance that could deliver but could not see itself.
Overview
UCPath was the University of California's attempt to replace eleven aging campus payroll and human-resources systems with a single systemwide platform for roughly 190,000 employees. Scoped in 2011 at $306 million all-in, to be live by 2014, with $753 million in promised savings, the project instead climbed toward a true cost near $942 million, ran nearly five years late, and delivered none of the projected savings [CSA 2016-125.2, p. 1, 16, 18]. The governance finding is sharper than the cost overrun: UC's governance was strong at deciding and building, and structurally unable to see itself — the board with the authority to intervene was, for years, not told what mattered.
Timeline
The UCPath Governance
Organizations
Owner and manager of the UCPath project; subject of the audit.
Original implementation lead; released in 2013 for failure to perform. [p. 7]
The governing/oversight body; the party kept inadequately informed. Its Finance and Capital Strategies Committee charter was amended in 2016 to cover UCPath as a large-scale enterprise system. [p. 23]
The UC chief financial officer and chief operating officer, holding overall accountability. [p. 9]
Managed standard transactions for payroll and benefits for all 200,000+ UC employees.
Tasked with "readiness activities" in anticipation of moving their HR and payroll data to the new system.
Deployment sites; absorbed ~$193M in their own implementation costs (net ~$140M after reimbursements). [p. 17]
Shared-services center created to run centralized payroll/HR.
Independent oversight body that produced the reports.
Directed the audit.
Independent expert engaged by the auditor; identified five project-management weaknesses. [p. 24]
Governance Outcomes
Every coded segment is put to the same five questions and tallied by governance domain. 21 narrative findings are counted here; 9 further segments — recommendations, entity responses, auditor comments and follow-ups — are recorded but not tallied. Each finding counts once, under its primary domain.
Q1 Was it set up?
Whether the mechanism was defined in the first place · §8 Design state · 21 coded findings
View as table
| Domain | D1 Set up — clearly | D2 Set up — partially | D3 Never set up | D4 Conflicting evidence | D9 Unclear | Total |
|---|---|---|---|---|---|---|
| G5 Information & Transparency | 0 | 3 | 1 | 0 | 0 | 4 |
| G6 Vendor & Third-Party | 0 | 2 | 0 | 0 | 0 | 2 |
| G7 Change & Lifecycle | 0 | 2 | 0 | 0 | 0 | 2 |
| G10 Adaptation & Learning | 0 | 2 | 0 | 0 | 0 | 2 |
| G4 Risk & Control | 0 | 1 | 0 | 0 | 0 | 1 |
| G3 Oversight & Assurance | 1 | 1 | 1 | 0 | 0 | 3 |
| G1 Structure & Authority | 3 | 0 | 1 | 0 | 0 | 4 |
| G2 Decision Rights | 2 | 0 | 0 | 0 | 0 | 2 |
| G9 Stakeholder & External | 1 | 0 | 0 | 0 | 0 | 1 |
Q2 Did it work in practice?
Whether the mechanism actually operated as designed · §8 Operational state · 21 coded findings
View as table
| Domain | O1 Worked as intended | O2 Worked, with exceptions | O3 Bypassed / overridden | O4 Didn’t operate | O5 Not yet applicable | O9 Unclear | Total |
|---|---|---|---|---|---|---|---|
| G5 Information & Transparency | 0 | 0 | 2 | 2 | 0 | 0 | 4 |
| G7 Change & Lifecycle | 0 | 0 | 2 | 0 | 0 | 0 | 2 |
| G4 Risk & Control | 0 | 0 | 1 | 0 | 0 | 0 | 1 |
| G3 Oversight & Assurance | 1 | 1 | 0 | 1 | 0 | 0 | 3 |
| G1 Structure & Authority | 2 | 1 | 0 | 1 | 0 | 0 | 4 |
| G6 Vendor & Third-Party | 0 | 2 | 0 | 0 | 0 | 0 | 2 |
| G10 Adaptation & Learning | 0 | 2 | 0 | 0 | 0 | 0 | 2 |
| G2 Decision Rights | 2 | 0 | 0 | 0 | 0 | 0 | 2 |
| G9 Stakeholder & External | 1 | 0 | 0 | 0 | 0 | 0 | 1 |
Q3 How solid is the proof?
How well evidenced the finding is · §8 Evidence state · 21 coded findings
View as table
| Domain | E1 Direct evidence | E2 Corroborated | E3 Single source | E4 Conflicting evidence | E5 Absence evidenced | E9 Not evidenced | Total |
|---|---|---|---|---|---|---|---|
| G2 Decision Rights | 2 | 0 | 0 | 0 | 0 | 0 | 2 |
| G10 Adaptation & Learning | 2 | 0 | 0 | 0 | 0 | 0 | 2 |
| G4 Risk & Control | 1 | 0 | 0 | 0 | 0 | 0 | 1 |
| G9 Stakeholder & External | 1 | 0 | 0 | 0 | 0 | 0 | 1 |
| G5 Information & Transparency | 3 | 1 | 0 | 0 | 0 | 0 | 4 |
| G3 Oversight & Assurance | 2 | 1 | 0 | 0 | 0 | 0 | 3 |
| G1 Structure & Authority | 2 | 2 | 0 | 0 | 0 | 0 | 4 |
| G6 Vendor & Third-Party | 1 | 1 | 0 | 0 | 0 | 0 | 2 |
| G7 Change & Lifecycle | 1 | 1 | 0 | 0 | 0 | 0 | 2 |
Q4 Did it matter?
How strongly the finding is linked to the outcome · §11 Governance–consequence relationship · 21 coded findings
View as table
| Domain | R0 No link to outcome | R1 Possible link | R2 Contributed | R3 Major contributor | R4 Primary cause | R9 Unclear | Total |
|---|---|---|---|---|---|---|---|
| G5 Information & Transparency | 0 | 0 | 0 | 4 | 0 | 0 | 4 |
| G7 Change & Lifecycle | 0 | 0 | 0 | 2 | 0 | 0 | 2 |
| G1 Structure & Authority | 0 | 1 | 0 | 1 | 0 | 2 | 4 |
| G2 Decision Rights | 0 | 0 | 1 | 0 | 0 | 1 | 2 |
| G6 Vendor & Third-Party | 0 | 0 | 2 | 0 | 0 | 0 | 2 |
| G4 Risk & Control | 0 | 0 | 1 | 0 | 0 | 0 | 1 |
| G3 Oversight & Assurance | 1 | 0 | 2 | 0 | 0 | 0 | 3 |
| G10 Adaptation & Learning | 0 | 2 | 0 | 0 | 0 | 0 | 2 |
| G9 Stakeholder & External | 0 | 1 | 0 | 0 | 0 | 0 | 1 |
Overall Did it work?
The effectiveness assessment the other four questions support · §9 Governance effectiveness · 21 coded findings
View as table
| Domain | A1 Worked | A2 Worked, with limits | A3 Materially limited | A4 Fell short | A9 Not enough evidence | Total |
|---|---|---|---|---|---|---|
| G5 Information & Transparency | 0 | 0 | 0 | 4 | 0 | 4 |
| G7 Change & Lifecycle | 0 | 0 | 0 | 2 | 0 | 2 |
| G4 Risk & Control | 0 | 0 | 0 | 1 | 0 | 1 |
| G1 Structure & Authority | 0 | 1 | 1 | 1 | 1 | 4 |
| G3 Oversight & Assurance | 0 | 1 | 1 | 1 | 0 | 3 |
| G10 Adaptation & Learning | 0 | 0 | 2 | 0 | 0 | 2 |
| G6 Vendor & Third-Party | 0 | 1 | 1 | 0 | 0 | 2 |
| G2 Decision Rights | 0 | 2 | 0 | 0 | 0 | 2 |
| G9 Stakeholder & External | 0 | 1 | 0 | 0 | 0 | 1 |
Documents
Replace with a real URL (program charter, board/regents materials, status reports).
Audit Reports
Replace with the audit and a one-line summary of its findings.
News Coverage
Replace with a real article and a short excerpt.
Research Notes
Governance Mechanisms
AI Summary
Placeholder for an AI-generated summary of the UCPath case. Replace, or generate from the case content once the sections are filled in.
Lessons Learned
- Consolidation is a governance decision before it is a technology one.
The hardest questions were about oversight and accountability, not software.
- Phased rollouts buy time but widen the risk window.
Add the specifics from the case record.
Stay informed
Get a daily email when new information is added to this case.
Contribute to this case
Have a document or a correction? Send it to our research team for review.
