- 01Training delivered
Company session on AI usage.
- 02Policy created
Written guidance for organisational AI use.
- 03Agent in testing
A bounded application using an approved asset list.
These are separate but connected workstreams; the agent remains in development and testing.
The organisational need
Useful AI adoption involves staff understanding, clear expectations and tools that fit a real task. My work connects those elements through company training, policy creation and a practical agent project.
Training and policy
I delivered a company AI usage training session and created an AI usage policy. This work supports colleagues’ understanding of AI and provides an organisational reference for its use.
A practical application
I built an IT Asset Management Agent around an approved SharePoint IT Asset List. It retrieves records, flags missing or inconsistent information and recommends next steps. An authorised person remains responsible for reviewing information and making changes.
Testing and boundaries
My September 2026 evidence record documents ten baseline cases run twice, with all 20 recorded outcomes marked Pass. The cases cover retrieval, missing data, ambiguous records, update requests, misleading instructions in source notes and an unavailable source.
This is a recorded result for that test set, not a claim of general accuracy or a completed organisation-wide rollout.
How I judge the next step
I consider the time spent checking and maintaining a tool as part of its value. My approach is to compare the overall process with the existing method before deciding whether to expand, improve or stop its use.