The platform is not the operating system
Artlogic provides galleries with a valuable relationship between inventory data and the public website. But the presence of a specialist platform does not, by itself, create a coherent digital operation. Decisions still need to be made about titles, images, availability, canonical pages, artist context, internal links, event archives and responsibility for review.
When those decisions are made inconsistently, the cost is rarely visible as a single failure. It appears as duplicated pages, incomplete records, outdated claims, missed links and staff time spent rediscovering how something was handled before.
Small inconsistencies compound
A missing description on one work may be immaterial. The same gap across a catalogue weakens discoverability and collector understanding. One uncompressed image may pass unnoticed; a library of them changes mobile performance. An old event page may seem irrelevant, yet a well-maintained archive can preserve authority, context and routes into an artist’s work.
These are governance problems expressed through a website. They persist because they fall between curatorial, sales, administrative and technical responsibilities.
Control begins with a register
The most effective improvement is often not a redesign. It is a shared record of what exists, what standard applies, what has been checked and who owns the next action. A practical register can connect page purpose, canonical status, metadata, imagery, internal links and review dates without requiring the whole team to become technically specialised.
Templates and checklists then make quality repeatable. New exhibition pages launch with the right elements. Artist records are reviewed against the same standard. Changes can be prioritised by commercial importance rather than tackled in whichever order they are noticed.
Optimise before replacing
Platform constraints are real, and there are circumstances in which migration is justified. But replacing a website before understanding the operating weaknesses can reproduce the same problems in a more flexible system. An independent audit should separate what the platform prevents from what process, content or configuration can resolve.
The goal is not technical perfection. It is a controlled digital asset whose quality does not depend on one person remembering every past decision.