Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Campus Operations edition of September 7, 2026

Public-sector association guidanceMixedNewly relevant · Jan 2026

Workforce survey exposes gaps between AI use, policy awareness and ROI measurement

EDUCAUSE with AIR, NACUBO and CUPA-HR · Higher education workforce · Predominantly United States; includes international respondents

Publisher
EDUCAUSE: The Impact of AI on Work in Higher Education
Original publication
January 12, 2026
Source retrieved
2026-09-08
Read original source

What happened

Respondents report widespread work-related AI use alongside limited awareness of guidance and limited institutional ROI measurement.

Why it matters

Use as a diagnostic starting point for campus administrative and IT work; validate conditions locally before extrapolation.

Evidence and measured results

Email survey, September 29–October 13, 2025: 1,960 qualifying responses. Reported recent AI use was 94%; policy awareness 54%; institutional ROI measurement 13%. These are respondent reports, not an institutional census or causal productivity estimates. Methods and demographic tables were inspected.

Limitations and uncertainty

Constrained sampling and response bias; question denominators vary. No experimental baseline, verified financial return or campus-specific diagnosis. Sponsorship is disclosed. The survey covers AI beyond generative AI.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-08; this does not change the original publication date. Labels below come from the analysis itself.

Sales

Role takeaway

For CIO, HR and finance discussions, use the survey's measurement gap to ask how the campus currently knows whether administrative AI is useful. Which tasks have reliable baselines, who reviews errors, and can staff explain permitted data use? A bounded engagement could establish a workflow inventory and an evaluation plan for one service. The value hypothesis is better investment decisions and fewer unexamined exposures, subject to local evidence. Do not turn respondent percentages into campus penetration estimates, a sales opportunity list, guaranteed savings or evidence that any particular product is required.

Pre-sales engineering

Role takeaway

Begin with a low-risk document or service-desk workflow and representative sanitized inputs. Map source permissions, retrieval boundaries and output destinations before selecting an architecture. Prerequisites include an accountable data owner and an approved test set. Run equivalent tasks with the current process and the proposed assistance, including review time and intentionally misleading inputs. Measure factual errors and unauthorized disclosure attempts as well as elapsed time. The proposed proof should reveal whether quality survives acceleration; survey enthusiasm cannot substitute for this test. Keep integrations read-only until the owner accepts evidence for expanded permissions.

Delivery

Role takeaway

Assign an administrative service owner, an IT implementation lead and a finance reviewer. Establish the baseline, deliver accessible task training, and record support and correction work during the trial. Dependencies include staff availability and agreement on what successful service means. Hold checkpoints before data access and before renewal. Proposed acceptance requires a complete cost ledger, documented quality assessment and staff demonstrations of correct escalation on sensitive cases. These are proposed measures, not reported results. Risks include self-selection of enthusiasts, hidden review work and pressure to convert perceived time savings into premature staffing reductions.

Implementation considerations

Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.

Architecture and integration

What must connect, and where does the AI sit in the workflow?

Pair approved-tool access with a workflow inventory and data-flow map. Survey responses do not select cloud, on-premises or hybrid hosting.

Governance

Who approves, reviews and stays accountable for outcomes?

Test whether employees can apply guidance to actual tasks, separately from whether a policy document exists.

Security and privacy

What data, permissions and controls need testing?

Examine unapproved channels through a confidential staff inventory, then review sensitive-data handling and retention. Avoid treating aggregate survey responses as evidence of a local breach.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Budget accessible training and review effort as paid work; involve staff representatives before changing job expectations.

Procurement

What should contracts, pricing and exit terms secure?

Require a measured renewal decision incorporating license, support, integration and review costs.

Operating model

Which teams own the service once it runs?

Give service owners responsibility for quality and finance responsibility for benefit validation; shared governance should resolve conflicts.

What changed

New to the full archive. Older context is newly relevant to the September campus access initiatives assessed in this edition and fills the previous edition's workforce-measurement gap; not a claim of publication since the last run.

Publication history

  1. 2026-09-07Campus Operations · Issue 024 resources
Read preserved resource versions (JSON)

Stable resource ID: educause-ai-work-survey-2026