Branding agencies tool implementation: a pilot checklist

Branding agencies tool implementation should begin only when the chosen edition, contract, data flow and acceptance tests describe the same service. Configure a small, reversible workflow first and keep production material outside it until every mandatory gate has a recorded owner and a result.

This sequence was developed from desk research checked on 5 September 2026. No account, integration, asset migration or recovery route was tested.

The checklist is written for branding agencies of every size — the large international studios such as Pentagram, Landor, Wolff Olins, Interbrand and Design Bridge and Partners, and independent UK studios such as Johnson Banks, SomeOne and The Clearing — whether the platform serves one studio team or a network of offices, and whether the licence sits with the agency, a parent group or the client.

What to take away

Freeze the approved design

Record the business owner, service owner, security lead, privacy reviewer, accessibility lead, rights owner and supplier contact. Save the signed order, product edition, data terms, subprocessor list, architecture, approved integrations, change controls and exit commitments.

Create a migration manifest before moving anything. It should name the source, owner, file count as a local observation, permitted use, target location, transformation, validation method and deletion decision. Quarantine duplicate, corrupt, unsupported or rights-unknown files for human review.

For each asset, record the rights fields the IPO intellectual property overview treats as separate: the copyright owner, the licence type, the territory, the term or expiry and the permitted media. Where a UK trade mark applies, add the register number and the class it covers.

The ICO's data protection by design guidance says privacy measures should be considered from the start and through the processing lifecycle. Translate that principle into the real configuration. Document purposes, roles, access, retention, rights handling, transfers and deletion before importing personal information.

Retention has a clause-level test. UK GDPR Article 5(1)(e) requires that personal data be kept no longer than necessary, so the manifest should name a retention period for each category and the deletion method. ICO retention schedules guidance gives example periods for common records.

Editions, contract terms and exit commitments

Brand teams use asset management products such as Adobe Experience Manager Assets, Bynder, Frontify or Brandfolder, and general platforms such as Dropbox, Box or Microsoft SharePoint. Cost depends on the edition, not the headline seat price alone.

Editions differ by seat count, storage, permissions, audit logs, API access and single sign-on. Check the vendor's public price page or a written quote.

Confirm in writing: named users against concurrent access, annual against monthly terms, whether a test environment is charged, storage or API overage charges, and the notice period.

Prices quoted to UK buyers often exclude VAT, charged at the standard rate of 20 per cent. Exit fees come from the signed order. Ask what the contract charges for exporting data in a standard format, how long access continues after notice, and whether early termination attracts a fee.

Build with harmless fixtures

Use synthetic files that contain no client secrets, personal information, licensed fonts or restricted stock. Create roles for administrator, designer, approver, external collaborator and viewer only where the contract supports them. Start with least access and record who can change it.

The NCSC guidance on using SaaS securely separates provider controls from customer configuration. Check authentication, recovery, sharing defaults, integrations, logs and administrator actions. Do not infer safety from the provider's general security page.

Run task-based acceptance tests

Give each test an input, expected output, evidence location, owner and pass or fail result. Include these tasks:

WCAG 2.2 provides technical criteria for relevant web content. It does not show that the selected product, agency configuration or exported client material is accessible. Log barriers and keep the affected task on hold.

Name the criteria in the test script. Keyboard: 2.1.1 (Level A), 2.4.7 Focus Visible (Level AA) and 2.4.11 Focus Not Obscured (Level AA). Target size: 2.5.8 (Level AA). Entry and login: 3.3.7 Redundant Entry (Level A) and 3.3.8 Accessible Authentication (Minimum) (Level AA).

Pilot one genuine workflow

After fixture tests pass, choose a low-risk, authorised project. Define the eligible users and files, pilot period, help route, success measures, incident threshold and rollback trigger. Do not copy live archives into the system merely to make the pilot realistic.

Illustrative figures for the pilot: 30 calendar days, a review on day 15 and at least 90 per cent of acceptance tasks passed on first attempt. Treat a severity-one incident as one that stops a critical task or exposes client material. Set the threshold at one severity-one incident, or three severity-two incidents in any seven days.

Keep asset rights visible. The IPO's intellectual-property overview separates the main forms of protection and explains general ownership routes. Link each imported asset to its owner, permitted use, territory, expiry and source. Tool access does not grant reuse rights.

Run a short support rehearsal during the pilot. Submit a synthetic access problem through the contracted route, record the acknowledgement and test escalation without inventing a universal response target. Confirm who can pause migration while the issue remains open.

Move, hold or roll back

The decision owner may extend the pilot, approve a bounded production use, return a failed test for repair or roll back. Stop after unexplained access, missing logs, broken rights metadata, inaccessible critical work, an unresolved transfer or an export failure.

Worked example: on day 18 of a 30-day pilot, an export test returns three files without rights metadata. The rights owner and the access owner log a severity-one incident. The decision owner named in the signed order, the operations director, stops migration the same day and returns the export test for repair.

Before wider use, remove fixtures and verify deletion. Re-run access, recovery, export and accessibility tests after material configuration or supplier changes. Preserve an offline inventory and exit instructions so the agency can continue essential work if the service is suspended or the contract ends.

Close the pilot with a signed record of passed, failed and untested requirements. A production approval must name its permitted scope; it should not silently authorise different clients, information or integrations.

Reviewing a branding agency's tool stack

Directory listings and reviews tend to cover the work rather than the tool stack, so put the same questions to every agency you compare. Shortlist on the portfolio first, then check:

An agency that answers from a signed order is describing a service. One that answers from memory is describing an intention.

Before you act

Common questions

Who owns the rollback decision?

The decision owner named in the signed order, usually the operations or service owner. That role records the trigger, the evidence and the decision in the pilot log.

How long does the rollout take after the pilot?

Illustrative planning: 4 to 8 weeks to a bounded production use, with about two days a week of internal effort across design operations, IT and legal review. Asset volume, integration count and the security review length change that.