What to Look for in Collection Management Software

Most collection management software is genuinely bad. Not just old. Bad. The interfaces look like they were designed in 2003 because many of them were, and the vendors have spent the intervening years bolting new features onto old architecture without ever reconsidering whether the thing actually works. If you've spent time in Axiell, KE EMu, or Calm, you already know this. You've probably developed your own workarounds.

So if you're evaluating alternatives, what should you actually be looking at?

Spectrum 5.1 compliance has to be real, not claimed

Spectrum 5.1, published by Collections Trust, is the UK standard for collections management procedures. If your institution holds Arts Council England accreditation or is working toward it, Spectrum compliance isn't a nice-to-have. It's expected.

The problem is that "Spectrum-compliant" means different things to different vendors. Some support all 21 procedures properly. Others support a handful and call the rest configurable. Others wave vaguely at a help article.

Ask specifically which Spectrum 5.1 procedures are native to the system and which require workarounds. Ask how they handle object entry and exit, location and movement control, and condition checking. If the salesperson can't answer without checking, that tells you something.

VitrineCMS is a modern collection management platform built with Spectrum 5.1 support as a core requirement rather than a retrofit. We built it that way partly because registrars told us, repeatedly, that they'd spent years working around systems that weren't designed for UK museum practice.

Provenance documentation is a real test of any system

Ask any vendor how their system handles provenance. The specifics of the answer will tell you more than an hour of demo.

Good provenance tracking means you can attach source documentation to an object record, log ownership history with named parties and date ranges, flag records where provenance is incomplete or under review, and pull a report on that status when you need it. It should also be possible to link provenance information to acquisition records and track any research undertaken.

A free-text notes field is not good provenance tracking.

This isn't pedantic. Under Museums Association guidance on ethical collecting, institutions are expected to research and document provenance thoroughly and to have policies for how they respond when provenance is uncertain. If your CMS can't support that workflow, the work ends up in email threads and shared spreadsheets, and then someone leaves and takes the context with them.

The specific questions worth asking: Can you attach PDFs and scanned documents directly to a provenance record? Can you log multiple previous owners with individual date ranges and sources? Can you set a provenance status field and filter on it?

Loan management needs to be a proper module, not a workaround

Temporary loans are among the most process-heavy tasks in collections work. Object entry and exit procedures, condition reporting at both ends, facility reports, indemnity documentation, courier arrangements, due date tracking. If your CMS treats loans as an afterthought or a bolted-on extra, you'll end up managing half the process somewhere else anyway.

The minimum a loan management module needs to do: create incoming and outgoing loan records linked to specific object records, generate loan agreements from templates, attach condition reports at both loan dispatch and return, track loan end dates with reminders, and produce a movement log for any object on loan. Some systems also support UKGOV indemnity fields, which matters if you're handling government-indemnified loans.

When you're in a demo, don't let the vendor drive. Ask to see how they'd record an incoming loan from initial enquiry through to return of the object. If the workflow requires jumping between modules in a way that doesn't reflect how the work actually happens, that friction compounds over time.

Usability matters more than feature count

This point gets underweighted in almost every CMS evaluation.

A lot of collection management systems were built by people who think primarily in database terms rather than workflow terms. The result is software that is technically capable of doing most things but requires significant configuration and training to do any of them. In a large institution with dedicated IT support and a separate training budget, that might be manageable. In a museum where the collections manager is also handling acquisition paperwork, loans administration, and ACE reporting, software that requires deep expertise to use correctly is software that doesn't get used correctly.

Usability is also not just about a clean interface. It's about whether someone can create a new object entry record without consulting the manual. Whether the field order reflects how you'd actually think about the information. Whether search returns sensible results fast, because sometimes there's a lorry at the loading bay and you need to find a record in thirty seconds.

If a vendor won't let you run a proper pilot with real data before you commit, that's a flag. Confident software gets piloted.

Pricing and what it actually includes

Legacy CMS vendors are often opaque about cost. You'll request a demo, work through a sales process, and eventually receive a quote that depends on user count, selected modules, and contract length. That's not always bad faith, but it makes budget planning difficult and puts smaller institutions at a disadvantage in any negotiation.

Before going deep into any evaluation, check two things. First, is the pricing publicly available? Second, what does that price actually include?

Per-user licensing can become expensive quickly when multiple staff members need access. Module pricing can make a base cost look reasonable while hiding that anything useful costs extra. Ask vendors for a total cost of ownership figure that includes implementation, data migration, and ongoing support.

VitrineCMS pricing is published. The Professional tier is £79 per month and the Institution tier is £349 per month. Both include Spectrum 5.1 support, loan management, provenance tracking, and condition reporting. Those aren't optional extras.

On data migration

Switching systems is painful. Anyone who tells you otherwise is either selling something or has never done it.

Your current records are probably inconsistent. Field use will have drifted. Location hierarchies won't map cleanly to a new system. Terminology may have diverged from authority files. All of this is normal, and none of it is insurmountable, but you need to know about it before you migrate rather than after.

A reasonable implementation process involves a data audit before migration begins, a documented mapping of fields from your current system to the new one, and a QA phase where you verify records after migration. Build time for cleanup into your project plan. It will be needed.

When evaluating vendors, ask specifically how they've handled migration from your current system. If they've done it before, they should be able to describe the common sticking points. Collections Trust has documentation standards guidance worth reading before any migration project, partly because it helps you make decisions about what data to prioritise and what to let go.

There's no perfect system. Every platform involves tradeoffs between features and cost, or between configurability and usability. The institutions that tend to be most satisfied are the ones that piloted the software with real data, involved the people who would actually use it in the decision, and resisted choosing based on feature lists alone.

If you want to see how VitrineCMS approaches collection management for UK museums and galleries, you can start a free trial without going through a sales process first.