Multi location expansion review

Work and handover

We compare proposed sites, identify common records and local differences, and build a dependency tracker for leases, tax, establishment and sector permissions. The output separates opening prerequisites from later recurring tasks.

Give each shortlisted site a stable identifier and record its proposed operator, activity, premises status and target opening sequence. Track dependencies such as landlord documents, technical assessments and entity-level records against that site. This makes it possible to distinguish a delay affecting one location from a shared information gap affecting the entire rollout.

Location-specific evidence

• Site shortlist
• activity at each site
• entity map
• staff plan
• lease status
• existing approvals
• launch sequence.

Keep reusable entity documents in a common index while retaining premises-specific evidence for each location. Record the version supplied for an application and any local clarification requested. When a site leaves the shortlist or its operating model changes, update its status explicitly so the team does not continue work against an obsolete opening plan.

A point to resolve early

A standard store format does not make every municipality’s process identical. Keep a local exception column and evidence for each opening decision.

For a standard retail rollout, one location may include a storage area or service counter absent from the others. Record those differences before reusing the first site’s application checklist. The comparison should show the activity and premises facts behind each local question, rather than treating a common brand and floor plan as evidence of identical requirements.

Scope and authority process

The scope fixes the number of sites and jurisdictions. New locations, technical surveys and licence applications are priced explicitly.

The written engagement identifies the location, authority, application stage and fees. Government charges and third-party costs are addressed separately; authority approval is not guaranteed.

The handover gives the rollout team a site-by-site action list, evidence owners and unresolved dependencies. Keep application preparation, submission and issued decisions as separate stages. Record which recurring tasks pass to the local operations team after opening and who maintains changes to the central register, including additional sites outside the original scope.