Coverage describes how large an agreement is, not which package was bought.
Why it matters when the plan changes
Software agreements are usually priced on one dimension, which forces every question about scope through it. Separating coverage from the package being bought lets a customer start with one team and extend without renegotiating what they purchased, and lets the supplier price the population honestly rather than hiding it in a tier. Because coverage also defines whose data may be processed, expanding it is not just a commercial change; data protection principles require that processing stay limited to what is necessary for the purpose, so the boundary has to be documented as it grows.
The tension is between coverage and use. A large covered population does not mean a large number of people actually assessed, and an agreement priced on coverage can leave a customer paying for reach they never use. Matching coverage to the decisions in view keeps the two connected, and treating any extension as a documented change, not an assumption, keeps the processing boundary honest as the agreement grows.
In practice
A company starts with one division covered and its leaders licensed. A year later a second division joins, adding the covered population and the implementation work for the new group, while the package and the underlying model stay the same. Nothing was renegotiated; the agreement grew along the dimension designed to grow.
Evidence
Processing of personal data must be limited to what is necessary for the purpose, which is what defining a covered population does contractually.
Article 5, General Data Protection Regulation (2016)A processor acts on the controller's documented instructions, which is what a defined coverage scope establishes.
Article 28, General Data Protection Regulation (2016)
What it cannot tell you
Coverage describes the size of the contracted population, not the number of people actually assessed, how completely the assessment is finished, or the quality of decisions drawn from it. A wide covered population can sit largely unused, and coverage alone says nothing about whether the teams within it are the ones a decision actually depends on.
How Atlas reads it
Coverage, leader licences and organisation capacity describe the size of an agreement rather than being additional packages. Coverage expands as more teams, units, countries or employees are brought in. Population bands and prices live in the approved price list and contracts rather than in the model, and the contract does not turn a planned feature into an available one.
Questions
The defined population that can complete the Atlas assessment and questionnaire and receive the appropriate employee experience. It is a scope definition rather than a usage commitment, and it sets the boundary within which the rest of the agreement operates.
By bringing more teams, units, countries or employees into the defined population, which adds the covered group and the implementation work for it without changing the package underneath. Under Article 28 of the General Data Protection Regulation (2016), such expansion needs the controller's documented authorisation, since the processor acts only on those instructions.
No. Coverage is who may be; the number actually assessed depends on the decisions in view. A customer can hold wide coverage and use it narrowly, which is why matching coverage to the decisions being made keeps an agreement from carrying unused reach.
Closely. The covered population defines whose data may be processed under the agreement, and Article 5 of the General Data Protection Regulation (2016) requires that processing stay limited to what is necessary for the purpose. Extending coverage extends that boundary, and the extension should be documented as such.
In the approved price list and in contracts, not in the commercial model. The model defines how the agreement is structured. The numbers themselves are customer-specific and live where the signed commitments are held, which is the commercial system and the contract.