The board does not need to become the technical design authority
Universities are being asked to invest across campus networks, cybersecurity, cloud services, learning environments, surveillance, access control, data platforms and digital student services. These decisions are often presented as technology upgrades, but their consequences extend far beyond the IT department. They influence teaching continuity, research capability, administrative efficiency, safety, institutional reputation and the experience of students and faculty.
The board's role is not to select access points, switches or software editions. Its role is to test whether the investment is aligned, evidenced, governable and sustainable. The following questions create that leadership lens.
1. What institutional objective is this investment intended to enable?
The case should begin with the university's direction: academic delivery, research collaboration, student experience, operational resilience, expansion, regulatory responsibility or another defined priority. If the proposal begins with a platform and searches for benefits afterwards, the sequence is reversed.
2. What evidence demonstrates the present constraint?
Ask for evidence from users, operations and systems. This may include service interruptions, coverage studies, application performance, support incidents, manual workarounds, capacity trends or risk findings. Anecdote can signal a problem, but it should not be the only basis for a major capital decision.
3. Have academic, administrative and campus-operational requirements been considered together?
A university is a connected environment. Lecture halls, laboratories, libraries, hostels, offices, healthcare facilities, security operations and public spaces behave differently. A design optimised for one group can create friction elsewhere. The requirement should reflect the full campus context and the criticality of each environment.
4. What can be retained, improved or integrated before replacement?
Boards should expect a reasoned current-state assessment. Components with useful life and adequate capability may be retained or repositioned. Others may create unacceptable risk or operating burden. The answer should be based on evidence rather than an assumption that newer automatically means better.
5. What assumptions were used to size the investment?
Student numbers alone are rarely enough. Device density, simultaneous usage, teaching patterns, research workloads, guest access, residential demand, application behaviour, growth and resilience all affect sizing. Ask which assumptions are measured, which are forecast and how design headroom has been determined.
6. What is the lifecycle commitment beyond the initial CapEx?
The board should see subscriptions, renewals, support, specialist skills, energy, monitoring, training, expansion and refresh implications over a common time horizon. An affordable acquisition can become difficult to sustain if recurring obligations or proprietary dependencies are not visible at approval.
7. How will the proposed environment integrate with what the university already operates?
Campus technology should not become a collection of isolated systems. The proposal should address identity, security, applications, data, monitoring, service management and operational workflows. Integration responsibilities should be explicit, particularly where multiple partners are involved.
8. How will adoption and operating readiness be achieved?
Technology creates value only when people and processes can use it. Ask who will own the service, what skills are required, how faculty and staff will be supported, how procedures will change and what documentation and knowledge transfer will be delivered. A technically successful installation can still become an operationally weak investment.
9. What risks remain, and who has accepted them?
No proposal eliminates every risk. The board should understand material dependencies, migration risk, service disruption, cyber exposure, single points of failure, vendor concentration and unresolved assumptions. Each material risk should have an owner, treatment and conscious acceptance where it cannot be removed.
10. How will the university know that the intended outcome has been achieved?
Approval should be linked to measures that leadership can understand: reliable access in defined spaces, reduced disruption, faster completion of critical workflows, improved visibility, safer operations, research enablement or user adoption. Installation completion and invoice approval are milestones, not the final measure of value.
A better approval conversation
These questions are not designed to slow transformation or second-guess the university's technology team. They help the board distinguish between a purchase request and an investment case. They also create clearer conditions for delivery partners: defined outcomes, agreed requirements, visible responsibilities and measurable acceptance.
A digital campus should be shaped around the institution it serves. When the board keeps purpose, lifecycle value, integration and governance in view, technology can remain an enabler of the university's direction rather than an expensive collection of disconnected projects.
ShivPriya perspective Business First. Technology Second. Vendor Neutral.