Expansion as a pipeline of source-labeled, re-checkable facts

The discipline

What business expansion analysis actually involves

A single site decision ends when the lease is signed. An expansion program doesn't end; it accumulates. Candidate sites waiting on negotiations. Opened stores whose neighborhoods shifted after opening. Competitors who arrived — or closed. Population grids that moved between one planning cycle and the next. Managing that inventory of places means keeping three things under control at once: comparability (every site measured the same way), currency (knowing when each measurement was true), and drift (what has changed since).

Spreadsheets and screenshots handle the first two badly and the third not at all — a pasted map image has no capture date anyone trusts and no definition of what changed. LocateRight's expansion workflow is built for exactly those three properties: dated evidence, identical terms per site, and factual diffs instead of memory.

Step one

Campaigns: give the portfolio a shape

A campaign is a named container for the locations a program is actually tracking — the three Riyadh districts under negotiation, the two coastal markets being watched, the eleven opened stores whose trade areas need a quarterly check. The site list belongs to the campaign from creation; adding structure to an expansion means deciding, deliberately, which places are in scope.

Each site inside is analyzed under the same terms you would use at a single location — the same categories, radius conventions and evidence blocks — which is what makes later comparisons fair: the pipeline's evidence is generated by one method, not by five analysts with five browser windows.

Step two

Snapshots: evidence with a date on it

When a site's analysis is worth keeping, it is saved to the campaign as a snapshot. The storage rule is strict by design: the analysis is kept verbatim — no reshaping, no scoring, no edits after the fact — and stamped with its capture time. Snapshots are append-only; a saved capture can never be overwritten, so the trail is a trail. A site with one snapshot is documented; a site with two is measurable, because the platform's comparison needs exactly that pair.

The discipline this imposes is the useful part: snapshotting forces a decision to name what was known when it was made. Twelve months later, when a new district's competitor count surprises you, the earlier capture answers whether the neighborhood changed or the first read was wrong.

Feeding the pipeline

Bulk screening, where many locations start as a spreadsheet

Expansion queues rarely begin as campaigns; they begin as lists. Bulk analysis takes a CSV of labeled sites — coordinates, per-site radius, optional category — and returns one table of per-location raw observations, computed sequentially with no column ranking the rows and no winner declared. Completed rows can be matched by name into a campaign's existing sites, so the screening evidence lands in the pipeline it was meant for; rows with no matching site are honestly reported as unsaved.

Bulk is one mechanism inside this workflow, not the whole of it: the table screens, the campaign carries forward. The full bulk analysis tool covers formats and limits.

Leaving the tool

Reports and exports for the people who weren't in the meeting

Expansion decisions travel as documents. A campaign's current report can be exported as JSON; an individual snapshot downloads as its full analysis (JSON) or a flat CSV; a change comparison exports the same movement lists as CSV. Because every block carries its source, dataset version and retrieval date inside the payload, the exported file remains the traceable artifact it was built from — evidence a partner or lender can check, not a slide they have to trust.

The boundary of this workflow

What expansion analysis here does not do

• No forecasts. A snapshot diff is a comparison of two dated observations. It does not project the next quarter, model demand, or estimate what a new store earns — no part of the platform predicts revenue, market share or growth, and the shipped analysis note says so in the results themselves: raw observations only — no ratings, no predictions, no advice.
• No recommendations. Nothing in a campaign says “expand here.” The five change labels describe movements; choosing among markets remains a decision made from evidence, not a tool output.
• No invented economics. Rent, income and employment are not in the data catalog, so no screen in the workflow displays them — a gap stated as a gap.
• No quiet edits. Append-only snapshots with capture timestamps mean the past of a pipeline cannot be rewritten by its present.

How the pieces connect

One architecture, six questions

LocateRight's pages each own one question about locations. Expansion analysis owns the portfolio over time: it consumes single-location evidence, reads movement inside defined catchments and competitive sets, is fed by bulk screening, and hands its documented sites to the shortlist decision. The practice underneath all of it is location intelligence done honestly — what the sources hold and when they were fetched, inventoried on the data-sources page, with plan allowances on pricing.