Ask IT leaders across Scotland’s councils, health boards, universities and national bodies about their last IT service management (ITSM) procurement and one confession keeps coming up: after the third vendor demo, it was all a bit much of a muchness.

The same portals, the same forms, the same dashboards. They are not wrong. Modern ITSM tools have converged, and on a big screen in a meeting room they are genuinely hard to tell apart. 

That matters more in Scotland right now than it has for years. Budgets are under the hardest pressure in a decade, public service reform is asking every organisation to do more with less, and the national Digital Strategy is pushing for shared platforms, reusable components and a “Once for Scotland” mindset.

The ITSM platform you choose today will shape how your service desk, your asset estate and your data behave for the next five years. Picking wrong has never cost more. The differences that matter are visible, if you know where to look. 

Watch the change, not the finished form 

Every demo shows a polished request form. Very few show what it takes to build one. Ask the vendor to add a field, change a workflow and publish a form live, in front of you. If that needs a developer or a change request to the supplier, your team’s ideas will always sit in someone else’s backlog. 

This is the frustration we hear most often from public sector IT leaders, and it is rarely about licence cost. It is about capable, experienced teams who cannot realise their own ideas without paying consultants.

A council launching a new starter process for seasonal staff, or a health board rolling out a new device workflow, should be able to do it themselves in days, not wait months for a statement of work. Configuration by your own people is what turns “design once, reuse many times” from a slogan into reality. 

Look past pretty dashboards 

Reporting is the next place demos mislead. A dashboard that looks good on launch day tells you nothing about the question your chief executive or board will ask next quarter. Twenty monitor failures in a week across a school estate should be a signal your team sees coming, not a surprise buried in an Excel pivot table. 

Ask to see ready-made operational reports, then ask to see the underlying data model. Can every ticket, asset, user and cost flow into Power BI without an export and a spreadsheet in between? Scotland’s public bodies are being asked to evidence value for money and outcomes more rigorously than ever. Your service management data should make that easy, including for questions nobody has thought to ask yet. 

Insist on service desk and assets as one 

Many organisations still run their service desk in one tool and track hardware and software in another, with a spreadsheet stitching them together. The cost of that gap is hidden but real. When every ticket already knows the device, its owner, its warranty and its history, users stop repeating themselves, leavers stop walking out with laptops, and finance trusts the numbers at renewal time. 

For organisations with dispersed estates, from island schools to rural health centres and regional police and fire stations, this is not a nice to have. Knowing exactly what is deployed where, who has it and when it is due for refresh underpins sustainable budgeting, cyber resilience and licence compliance. Ask every vendor to show a single record joining a ticket to an asset to a person, without switching systems. 

Fit beats features in a Microsoft estate 

Most of Scotland’s public sector runs on Microsoft 365. Staff already live in Teams and Outlook, devices are managed through Intune, while national programmes are investing in Microsoft 365 skills across local government. An ITSM platform that meets users where they already work simply does not have an adoption problem. 

This is the thinking behind ALVAO: ITSM and IT asset management in one platform, designed for Microsoft 365, so Entra ID, Intune, Teams and Power BI do the heavy lifting using skills your team already has. There is no parallel identity model to maintain and no separate portal to train people on. 

The same logic applies to AI. Every public body in Scotland is being asked what it is doing with Copilot and automation, and the honest answer is that AI is only as good as the data underneath it. Connected tickets, assets and owners give AI solid, governed foundations. Another disconnected silo does the opposite, and makes responsible AI adoption harder to evidence. 

Will they be a partner, or just a vendor? 

No demo shows what happens after go-live, yet that is where most of the value is won or lost. Ask who will run your onboarding: a named consultant who knows your environment, or a link to the documentation? Ask a genuinely hard question about your own setup and watch for honesty rather than enthusiasm. Ask for a reference from an organisation your size, and call them. 

Scottish public bodies also have their own realities: information governance, data residency, procurement routes and accessibility obligations. A good partner engages with those from the first conversation rather than treating them as paperwork after contract signature. When every tool looks similar on screen, the supplier who treats you like you matter is what separates a purchase from a decision you will still be proud of in year three. 

Put us to the test at DigitalScotland 

ALVAO has spent 27 years building service and asset management for Microsoft-first organisations and is available on G-Cloud. We are happy to be measured against every question above. 

Come and find us at DigitalScotland 2026 at the EICC on 24 November. Get a true partnership to elevate your ITSM to the level your users deserve.