Implementing a franchise tool: pilot a whole trading cycle before go-live

Tool implementation succeeds when the network proves a complete workflow and knows who owns every control. Installing accounts and importing data are only parts of the change. Use a pilot with explicit acceptance, rollback and reconciliation criteria before extending the system across English locations.

What to take away

Name the outcome and owners

Write one measurable outcome, such as reducing duplicate entry between sales and royalty reporting while preserving an auditable correction trail. Assign a business owner, technical lead, data owner, supplier contact and representative local user. The franchisor and franchisee should settle who approves configuration changes and who supports frontline staff.

Create a decision log for scope, exceptions and accepted risks. This stops a temporary workaround from silently becoming the standard process.

Configure access before adding data

Build roles for real jobs rather than copying one administrator profile. Test a joiner, a manager moving sites and a leaver. Require strong authentication and remove shared credentials. The NCSC's small organisations guide covers account protection, devices, backups and recognising attacks.

Cloud use does not transfer every obligation to the vendor. The NCSC's shared-responsibility guidance explains that the split depends on the service, while customers still need to select an appropriate service, configure it securely and decide which data to place there. Put the agreed split in the operating runbook.

Prepare and rehearse migration

Profile the source data before copying it. Identify duplicates, missing identifiers, obsolete users and records that should not move. Set a cut-off time, field map, reconciliation totals and rejected-record process. Use a protected trial extract and remove it when the rehearsal ends.

The ICO's accountability guidance covers processor contracts, processing records and evidence such as consent and breach records. Update the data map, retention rules and supplier record before production use, not after the database has moved.

Pilot an entire trading cycle

Choose a site that reflects common complexity without carrying the network's highest initial risk. Run opening, sale, correction, refund, supplier invoice, management report and period close. Include an outage or failed integration. Record elapsed time, errors, support contacts and manual work.

Finance implementation needs a separate statutory check. HMRC's software readiness guidance explains authorising compatible software and checking the accounting period before creating digital records for Making Tax Digital for Income Tax. Apply the current guidance only where the operator is in scope, and involve the accountant in authorisation and opening balances.

Train for exceptions

Short role-based sessions are more useful than one tour of every menu. Give staff a normal task, a correction and an escalation. Keep a searchable local guide showing the approved process, evidence to retain and help route. Do not let supplier training overwrite franchise responsibilities or England-specific procedures.

Decide whether to go live

Require signed acceptance for access, data totals, integrations, reports, backups, support and exit export. State who can delay launch. Keep the former system readable until agreed reconciliations and retention decisions are complete.

After release, review issues daily for the first trading cycle, then at scheduled intervals. Remove pilot accounts, close temporary permissions and compare promised benefits with measured results. A controlled implementation ends with a stable operating record and known limitations, not merely a completed supplier project plan.

Keep an enhanced support rota through the first reporting deadline, not just opening day. The first royalty reconciliation, VAT period or month-end may expose mapping errors that ordinary trading does not. Record the fix, the affected records and whether earlier outputs need correction.

Before you act

Common questions

What should a pilot trading cycle cover?

Run opening, sale, correction, refund, supplier invoice, management report and period close. Include an outage or failed integration. Record elapsed time, errors, support contacts and manual work. Choose a site that reflects common complexity without carrying the network's highest initial risk.

How should access be configured before data is added?

Build roles for real jobs rather than copying one administrator profile. Test a joiner, a manager moving sites and a leaver. Require strong authentication and remove shared credentials. Put the agreed cloud responsibility split in the operating runbook.

What must be signed off before going live?

Require signed acceptance for access, data totals, integrations, reports, backups, support and exit export. State who can delay launch. Keep the former system readable until agreed reconciliations and retention decisions are complete. Review issues daily for the first trading cycle after release.