From the Campus Operations edition of September 8, 2026
Campus procurement interviews highlight hidden AI features, opaque terms and support capacity
EDUCAUSE and American Council on Education · Higher education procurement and IT governance · Primarily United States; includes varied institution types
- Publisher
- EDUCAUSE Review
- Original publication
- March 11, 2025
- Source retrieved
- 2026-09-09
What happened
The interview synthesis treats AI procurement as an ongoing review of products, embedded features and third-party use, with cost and transparency constraints.
Why it matters
Directly relevant to campus purchasing and small-team implementation capacity; specific state purchasing rules need local review.
Evidence and measured results
ACE and EDUCAUSE interviewed 12 CIOs, IT leaders and procurement professionals in October–November 2024. Their qualitative findings identify disclosure, pricing and capacity problems. The article also cites a separate survey; its percentages are not reused here. The opening Middlevale vignette is illustrative, not a real deployment.
Limitations and uncertainty
Small qualitative interview sample; no causal estimate of procurement benefits, representative prevalence or current vendor pricing. Guidance is older than this edition and is not a statement of current legal requirements.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-09; this does not change the original publication date. Labels below come from the analysis itself.
Sales
Role takeaway
Ask procurement, counsel, the CISO and the business sponsor where approval stalls and what evidence they need to proceed. Inventory an existing product's newly added AI feature as a bounded engagement before considering an enterprise rollout. The value hypothesis is clearer decisions and fewer surprise obligations, not guaranteed savings. Ask whether staff capacity, recurring inference charges and exit effort are funded. The interview findings justify questions about disclosure and smaller-campus constraints; they do not establish that any particular vendor is unsuitable or that a sale is available.
Pre-sales engineering
Role takeaway
Turn the vendor questionnaire into an evidence map linking each claim to a configuration, contract term or reproducible test. Require a sandbox and representative non-sensitive inputs. Trace prompts, retrieved data, logs and outputs across service boundaries, including embedded assistants and agents. Test role separation and feature-disable behavior rather than accepting an architecture diagram as assurance. Proposed validation should produce an explicit list of verified, unverified and inapplicable controls plus an estimate of integration effort. Deployment choice should follow data and service requirements, not an assumption that cloud or local hosting is inherently adequate.
Delivery
Role takeaway
Make the purchasing lead accountable for contract checkpoints and name an IT service owner for ongoing operation. Coordinate security, privacy, accessibility and business-user reviews before onboarding. Create a release-change register, renewal calendar and tested exit procedure; train staff to route unreviewed features to the owner. Proposed acceptance requires documented owners for material obligations, an approved support budget and successful export or deletion testing within the agreed scope. Track review cycle time and exceptions to improve the process. Risks include review overload, hidden feature activation and unfunded support after initial purchase.
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?
Inventory AI data paths across purchased and embedded services before approving integrations.
Governance
Who approves, reviews and stays accountable for outcomes?
Trigger reassessment when a vendor adds material capabilities, not only at contract signature.
Security and privacy
What data, permissions and controls need testing?
Obtain explicit answers about training reuse, retention, subprocessors and institutional data separation.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Include accessible task testing and funded support time in product evaluation.
Procurement
What should contracts, pricing and exit terms secure?
Negotiate testable obligations, change notification and feasible exit provisions using local counsel.
Operating model
Which teams own the service once it runs?
Align purchasing, IT security and business ownership in one lifecycle review.
What changed
New URL across all archive pages. Included as foundational scrutiny of procurement implementation, which previous editions did not examine at this contract-detail level; not daily news.
Publication history
- 2026-09-08Campus Operations · Issue 033 resources
Stable resource ID: educause-ace-ai-procurement-interviews-2025