An infrastructure audit should not begin with a catalogue of hardware. It should begin with the learning, teaching and administrative experiences the institution must support.

Map critical journeys

Observe how users enrol, access content, submit work, collaborate and obtain support. These journeys identify which systems and connections are genuinely critical.

Test resilience in context

Capacity, backup and security decisions should reflect peak academic periods, distributed users and recovery priorities. A technically available system can still fail if it is too slow or difficult to use.

Infrastructure creates value when it quietly enables the institution’s academic purpose.

Prioritise a practical roadmap

Separate urgent risk, operational improvement and strategic investment. Assign ownership, budget and measurable outcomes so the audit becomes an improvement programme rather than a report.