Two students and an admin are discussing upgrading campus computer labs. Ethan (Student) Honestly, the current machines are just too slow. It's frustrating when you're trying to run basic applications and they lag or crash. We really need faster equipment, especially with how dependent we are on the labs during peak project weeks. Chloe (Student) I get that, Ethan, but it's not just about speed. The software is out of date, too. Some programs we need for coursework haven't been updated in years. I think it's just as important to look at licensing costs and make sure we're running the latest versions. Mr. Brooks (Admin) I completely understand both your concerns. The student usage reports do show increased demand, particularly around assessment periods. But with the current funding limitations, we can't afford a full overhaul right away. We'll need to be strategic about which upgrades come first. Ethan (Student) That's fair, but maybe we can start by identifying the labs with the worst performing machines. An equipment evaluation across all the labs could help us target the most urgent hardware needs. That way, we’re not just guessing where to invest. Chloe (Student) Exactly. And we can pair that with a review of the software licenses. Some tools are barely used and still cost a lot. If we cut back on unused programs, maybe we could free up part of the budget for updates that students actually need. Mr. Brooks (Admin) Good points. If we combine a phased implementation strategy with careful budgeting, we might be able to get the essentials sorted this term. I'll work with IT to assess both equipment and licensing. Then we can draft a realistic upgrade roadmap. Ethan (Student) Would it help if we collected direct feedback from students about what tools and machines they rely on the most? That kind of input could justify which items are truly critical, especially when pitching the case for more funding next term. Chloe (Student) I agree. Maybe we could circulate a short survey. We'd get better insight into usage patterns and which software features are lagging. That data would make our case stronger when requesting approvals for larger updates. Mr. Brooks (Admin) Then here's what we'll do. We’ll start with critical updates prioritise failing hardware and essential software licenses while gathering student feedback and completing the evaluation. I'll submit the budget request for the full upgrade next term and base it on real data from this process.