Using Microsoft Copilot for Resource List Processing

I used Microsoft Copilot to convert a list of requested resources, provided by a faculty member as a Word document, into a spreadsheet ready to share with our acquisitions specialist. What would have taken me at least 20 to 30 minutes took the system only a few seconds. Because I believe in keeping humans in the loop, I reviewed the results and found them to be wholly accurate.

Before using the tool, I considered the potential impacts of using AI for such a task and made an intentional decision to explore its possibilities despite reservations regarding the Copilot model. I also considered whether the task was appropriate for AI assistance and whether the tool was a good fit for the work. Too often, in our rush to embrace new technology, I think we overlook these important steps of critical discernment.

In this case, I already knew that I do not prefer the Copilot/Microsoft user experience and had been paying attention to some of the data privacy and transparency questions that have arisen regarding Copilot. Because this product is already available and provided by the institution, I recognized that it is likely to be a first choice for many internal users. I wanted to gain firsthand experience using it. The cross-platform integration also made Copilot a natural choice because I needed the final product to be an Excel spreadsheet ready for internal use.

Using a tool like this for basic data processing, a task that requires speed and efficiency rather than creativity or relational awareness, proved to be a natural fit. I can easily see using tools like this with larger datasets in the future.

Overall, it was a positive experience, and I will likely replicate the workflow on other platforms to compare the results.