Multi-Branch Readiness Programme

This is an illustrative engagement written to show how Noriva works. It is not client work, and it contains no client name, figure or verified result.

A single site was performing well and a second lease was under discussion. The readiness question was never asked, and the honest answer to it was no: recipes were partial, purchasing lived in one person's relationships, training was delivered by demonstration, and the judgement calls that hold a service together existed only in the founder's head.

Work was ordered by value per page written. The top twenty items by volume were documented with full recipes, yields, portions, plating and the common failure to avoid. Opening and closing routines became checklists rather than prose. Purchasing specifications were written for the items that matter, with a reference price so drift becomes visible.

Test readiness before location. If someone who did not build the first site could not run the second one from the documents that exist today, then documentation is the real first project — not the lease.

The judgement rules — when to comp, when to remake, when to stop taking orders, how much to prep on a quiet day — were written as if-then statements. They were the most awkward part to write and the most valuable part of the result.

The documents were then tested rather than filed: handed to someone who had not been there, with every question they asked recorded as a gap. A fixed-versus-flexible register was agreed so that menu length, hours and local additions can adapt by site while core recipes, brand expression, service standards and reporting stay identical.

The expansion question changed from "where" to "when the documents pass the test", which is a considerably cheaper question to answer.

Qualitative outcomes only: a documented core the founder does not have to be present to enforce; training that transfers rather than degrades with each copy; a purchasing specification and reference price that make drift visible; and an explicit register of what is fixed and what may vary, which removes most of the arguments multi-site management otherwise consumes.