# Portfolio wide deployment of training, one company at a time

A portfolio wide deployment of training goes company by company: a first company proves the shared standard, and a readiness gate decides when the next company starts. This page is for operating partners and group leaders who plan how Elvina would reach each company they own. It covers the order, the gates and who approves in each company.

## Who this is for

Teams that run several companies with frontline staff and have already decided to put them on a shared training standard. Think of private equity firms, holding groups, family offices and owners who keep buying. The question here is the order of work, not whether a shared standard is worth having.

## What changes after an acquisition

Each new acquisition changes the rollout plan. A company bought mid-rollout arrives with its own habits, its own key people and no history with the shared standard. It should not cut in line. It starts with its own routines captured, and it joins the shared standard only after its own approver signs off.

- The rollout order is revisited each time a company joins
- The new company's routines are recorded before anything is replaced
- Its approver, not the operating team, decides what reaches its staff

## How Elvina works across companies

In a pilot, each company gets its own space in Company Knowledge with its own approvers, and that split is confirmed before work starts. Creation Studio drafts the shared standard once, then adapts it where a company has an approved difference. Managers assign lessons by company, role and group on the Learning Platform, so progress is read company by company. How the operating team sees all companies at once is agreed for the pilot, not offered as a finished feature. Today our team does most of the build on the platform, and Elvina picks up each step as it is confirmed.

Rollout gates

| Stage | Who decides | Gate before moving on |
|---|---|---|
| First company | Operating partner and the company's approver | New hires pass the first-week readiness check, which is available now |
| Next company in the order | That company's approver | Its own material approved and its managers trained on the review step |
| Change to the shared standard | Operating team proposes, each company approves | Every company approves the changed lesson before staff see it |
| New acquisition | Operating team sets its place in the order | Founder and key people recorded first |

## A worked example

A fictional holding group owns three garage door repair firms in nearby states and is about to buy a fourth. The operating partner wants one standard for how technicians handle customers on service calls, without stopping work anywhere.

- The firm that hires the most technicians goes first, because its service manager agrees to own the result
- Her team approves a shared standard for taking the request, explaining approved repair options, getting the customer's go-ahead and closing the visit, plus two local differences
- New technicians there take the lessons and a readiness check on the customer-facing steps of a real service call, available now, before the second firm starts
- The fourth firm, bought mid-rollout, first records its founder's way of quoting jobs, then waits its turn

## What we need from you

We need an operating partner who owns the rollout order and a first company with a manager who will own the result. Every company also needs a named approver. We agree in writing what the operating team may see of each company's training data, before the first lesson goes out.

## What we do not promise yet

We do not publish portfolio terms, rollout timelines or a set pace per company. Separate company spaces, shared standards and a portfolio view of progress are tested in the pilot, not offered as finished features. Portfolio terms are discussed separately with each partner. Elvina does not judge a company's managers or make staffing decisions.

## Questions people ask

**Q:** What does a portfolio wide deployment look like?

It runs company by company. A first company proves the shared standard, a readiness gate decides when the next company starts, and every company keeps its own approver. A company bought during the rollout starts at the beginning rather than skipping ahead.

**Q:** Which portfolio company should go first?

One that hires often, has a manager willing to own the result and has routines that are written down or easy to record. Avoid starting with the company in the most trouble, because it tests too many things at once.

**Q:** Can the operating team see progress in every company?

That view is agreed and set up for the pilot. The Learning Platform tracks progress by company, role and group, and what the operating team sees beyond that is written into the pilot scope first.

**Q:** How do we keep a shared standard current across companies?

Change the source once and let Creation Studio redraft the affected lessons for each company's approver. Nothing reaches staff until that approver signs off, so a company with an approved local difference keeps it.