Procurement Lessons from the Bristol Heritage Trust

The recent agency transition at the Bristol Heritage Trust has highlighted severe gaps in our vendor management protocols. When the outgoing agency concluded their contract last month, our internal team expected a seamless knowledge transfer. Instead, we found ourselves dealing with missing source files, undocumented decisions, and a chaotic repository that lacked any single source of truth. It quickly became clear that nobody had enforced the transition clause included in the master services agreement.

We must admit that our procurement team should have known better than to release the final milestone payment before verifying the contents of the handover pack. We trusted the vendor's word blindly, taking it for granted that professional standards alone would guarantee a clean handover. This oversight led directly to weeks of unnecessary file archaeology and frantic damage limitation by the incoming team.

Looking back at the vendor exit, several structural flaws became painfully obvious. The outgoing agency argued that their scope of work ended the moment their retainer expired, while our team assumed that ongoing support was implicit. Such ambiguity always gives rise to friction, especially when complex dual design systems and harmonising brands are involved. We failed to establish a rigid handover checklist at the project's inception.

Furthermore, the reliance on tacit knowledge rather than documented specifications created massive vulnerabilities. When key designers left the outgoing studio, critical rationale vanished with them. The incoming team was left to inherit chaos, forcing them to reconstruct work from scratch rather than building upon existing foundations. Frankly, it was a textbook example of how not to manage a digital asset transfer.

We also neglected our own design ethics board oversight during the final weeks of the contract. By failing to conduct a proper ethical review of the incoming deliverables, we exposed the foundation to potential intellectual property risks. The fact that we have run similar digital transformations in the past makes this oversight all the more embarrassing for our senior leadership.

Our procurement framework must evolve to prevent such fiascos from recurring. In view of recent events, we are introducing mandatory transition clauses that penalise incomplete documentation. Furthermore, we will require joint workshops during the final fortnight of any vendor relationship, ensuring that knowledge transfer happens collaboratively rather than asynchronously.

It is worth noting that the outgoing agency acted within the strict letter of their contract, even if their actions strained professional courtesy. They were under no legal obligation to clean up legacy folders once the final invoice cleared. Therefore, pointing fingers at the vendor is counterproductive; the root cause stems from our own ambiguous contracting practices.

We owe it to our stakeholders to maintain rigorous operational standards across all digital initiatives. Supposing we had implemented strict file-naming conventions on day one, the incoming team would have saved countless hours of forensic reconstruction. Instead, we treated documentation as an afterthought rather than a core deliverable.

Moving forward, all future agency transitions will be managed through a centralised portal where every asset must pass automated validation checks before sign-off. We are slated to pilot this new system in Bristol next quarter, with rollout planned across all regional offices by winter. No matter how urgent a project feels, shortcuts in documentation will no longer be tolerated.

Ultimately, this painful experience serves as a timely reminder that robust procurement is every bit as important as creative excellence. We might have avoided this entire ordeal had we consulted our legal advisors before finalising the vendor exit. We have learned our lesson, and our next procurement cycle will reflect these hard-earned insights.

Read again and choose the right answer

What primary issue did the Bristol Heritage Trust encounter during the agency transition?

• A complete lack of funding for the new design system
• Missing source files, undocumented decisions, and an empty handover pack
• A legal dispute over brand ownership in London

What does the procurement note admit about the charity's own actions?

• They should have known better than to release the final payment prematurely
• They deliberately withheld documentation from the incoming agency
• They refused to sign the original vendor contract

How does the charity plan to prevent similar issues in future agency transitions?

• By banning all external agencies and hiring only freelancers
• By introducing mandatory transition clauses, joint workshops, and centralised validation checks
• By suing the outgoing agency for breach of contract in Manchester

What root cause does the report ultimately identify for the botched handover?

• Malicious intent by the outgoing agency directors
• Software incompatibilities between different design tools
• The charity's own ambiguous contracting practices and lack of documentation oversight

Sources: photo by RDNE Stock project on Pexels