Multi-site tronc management

Two to five sites. Usually still run by the owner and one finance person. The main risk is informality: each site does roughly the same thing, nobody has written down the differences, and the owner is often the one quietly settling the split. The first job is getting one set of written rules and taking the owner out of the allocation.

Six to twenty sites. Area managers appear, and so does drift. Staff work shifts at more than one site, a second brand arrives with different service, and site-level spreadsheets multiply. This is where a single independent troncmaster, a clear cross-site rule and central records make the biggest difference.

Twenty sites and more. The tronc is now a control environment that a board, a lender or a buyer will ask about. What matters is per-brand rule sets that are deliberate, exception reporting, and being able to produce any worker's records quickly. Expect this conversation in any refinancing or sale.

A single group tronc pools everything and shares it under one set of rules. It is administratively tidy and works well where staff move between sites and the brand experience is uniform. Its weakness is fairness: a busy flagship subsidising a quiet site is difficult to explain, and difficult to defend if challenged under the Tips Act.

Per-site troncs keep money where it was earned and are the easier conversation with staff. The overhead is real — more schemes, more reconciliations — and cross-site working needs an explicit rule rather than a case-by-case decision.

Hybrid structures, where each site runs its own pool under group-level rules and a single troncmaster, are common in estates of five sites and above.

• Local improvisation. A site manager adjusts the split for a leaver, a new role or a difficult week, and never records why.
• Inherited sites. An acquired site keeps its old arrangement informally while appearing on paper to be inside the group scheme.
• Cross-site shifts. Hours worked at another site get allocated wherever is convenient.
• Approval creep. Head office starts reviewing allocations before payment, quietly destroying independence across the whole estate at once.
• Records held locally. A worker's request for their tip records turns into a search across site-level spreadsheets.

The consequence of a group-level failure is that the exposure multiplies by the number of sites and the number of years, which is why groups get audited before they get optimised.

1. One appointed independent troncmaster for the estate, with documented terms of reference.
2. Group-level scheme rules, with brand or site variations recorded as deliberate exceptions.
3. A single method for attributing hours, including cross-site working.
4. Central distribution through the tronc PAYE scheme, not site payrolls.
5. A standing rule that operational management does not approve allocations.
6. A periodic review as sites open, close, rebrand or change service model.

Finance directors generally want three things each period: what was collected, what was distributed and to whom, and confirmation that the two reconcile to the till and card data. Beyond that, the useful reporting is exception-based — sites whose distribution profile has moved, roles whose average share has drifted, and any period where the pool and the payout did not agree.

The same pack answers most diligence questions later, which is the cheapest form of transaction preparation available to a hospitality group.

Most groups already have something in place, even if it differs between sites. We don't switch everything off on day one. A typical handover runs over the first one or two pay periods:

1. Collect each site's current rules, recent distributions and how tips reach payroll.
2. List the differences between sites and decide, with you, which are deliberate (and become a written brand rule set) and which are drift (and stop).
3. Agree a single cross-site rule: hours follow the site where they were worked.
4. Separate any mandatory service charge from voluntary tips. It attracts NIC however it is shared, so it should not be presented as a tronc saving.
5. Run the first period alongside the old method so the numbers can be compared before staff are paid on the new basis.
6. Issue the written policy to staff, then distribute centrally from that point on.

We work from the exports your tills, rota and payroll already produce. You don't need new software to move over, and we won't promise integrations we haven't built for your systems.

A new or acquired site should not be absorbed silently. The sequence that keeps the estate clean is: review what the site does today, close out the old arrangement with a final documented distribution, appoint the group troncmaster for that site, issue the rules that will apply, and tell the staff before the first distribution under the new basis rather than after.

Where the site arrives through a transfer or acquisition, the historic position matters as much as the future one — see tronc in TUPE transfers and acquisitions.

Should a multi-site group run one tronc or one per site?

Both models work. A single group tronc gives consistency and simpler reporting but has to justify sharing across sites that generate very different tip levels. Per-site troncs keep the money where it was earned and are easier to explain to staff, at the cost of more schemes to operate. The deciding factor is usually whether staff move between sites.

Can different brands in the same group have different tronc rules?

Yes. Rules should reflect how each brand actually operates — a fine-dining site and a high-volume bar rarely justify the same weightings. What must be consistent is the governance: the same independent decision-maker, the same standard of records, and a documented reason for each difference.

How do you handle staff who work across several sites?

Their hours are attributed to the site where they were worked, and the allocation follows those hours. Problems arise where a group has per-site troncs but no rule for cross-site shifts, which is one of the most common gaps we find in group schemes.

What does a board or lender usually want to see?

That the National Insurance treatment is defensible, that there is no unquantified historic exposure, and that the group can produce tip records on request. That is a documentation question as much as a compliance one.