Why programme status must not transfer across a group

Corporate groups are often presented as a single market identity. Customers may recognise the brand rather than the legal entity, and group websites may describe capabilities collectively. Programme evidence cannot follow that shorthand. A conclusion reached for one entity, service and jurisdiction must remain attached to that scope unless the evidence and decision explicitly cover another.

Ownership alone does not make entities interchangeable. Subsidiaries can have different permissions, contracts, governance, customer types, operational controls and insolvency positions. Even wholly owned entities remain legally distinct. A parent’s resources or policies may be relevant evidence, but they do not automatically establish how a subsidiary performs a regulated or contractual obligation.

Shared branding creates a similar risk. Two entities may use the same name and visual identity while serving different territories or products. A website may route visitors after detecting location, and terms may change according to customer classification. The public record must identify the route actually reviewed and avoid presenting a brand-level conclusion where only one legal entity was assessed.

A shared address or director can help connect records, but neither proves common controls or outcomes. Registered offices can serve many unrelated entities. Directors may hold multiple appointments. Common service providers may administer payments, compliance functions or technology without assuming the regulated obligations of their clients. These relationships should be described precisely rather than used as proxies for status.

The non-transfer principle also applies between RMCA programmes. FDRC addresses trading-market protection, complaints and redress evidence. PSCR addresses payments, safeguarding and institutional evidence. A group entity examined in one programme does not acquire status in the other, and evidence suitable for one module may not answer the questions required by the other.

Material changes reinforce the need for separation. A restructuring, licence variation, new contracting entity or migration of customers can alter the scope while branding remains constant. A group-level label would hide that transition. Entity-level records can instead preserve the historic state and show when responsibility moved, which source evidenced the move and what remained unresolved.

This does not prevent connected evidence from being displayed. A governed architecture can link a parent, subsidiary, trading name, payment provider and programme record while keeping each relationship typed and dated. The links aid navigation; they do not merge legal identity or carry conclusions across the graph. Readers can see context without being invited to infer equivalence.

Status therefore follows the evidence scope, not the logo. Any future programme decision requires its own defined entity, service, jurisdiction, evidence period and independent governance. Observatory records and fictional demonstrations illustrate this architecture only. They do not establish, preview or imply a live decision for any real firm or group.