Count people by intended use, not by spreadsheet availability.

We create a traceable forecast from roles, active use, deployment waves, contractors, hiring, reassignment, and current vendor rules.

Define the licensed population.

Start with the people who will use the relevant team capabilities, then distinguish pilot users, production users, temporary workers, administrators, future hires, and contingency assumptions.

Baseline

Named current users with role, manager, team, and planned go-live wave.

Change

Known hiring, departures, role movement, acquisitions, and project staffing.

Rules

Current vendor definitions for user assignment, transfer, device use, and any relevant minimums.

Forecast fields

Field	Purpose
Person or approved role pool	Trace demand to accountable business need
Use case	Explain why team capability is required
Wave and date	Align purchase with deployment readiness
Confidence	Separate committed demand from planning assumptions
Owner	Assign review, reassignment, and departure actions

Avoid artificial precision.

Use scenarios: committed baseline, expected growth, and bounded contingency. Record the event that would move demand from one scenario to another.

Do not count dormant directory accounts as demand
Do not assume concurrent licensing without confirmation
Do not hide contractor or seasonal patterns
Do not buy ahead of an unowned deployment plan
Do not treat forecast as vendor entitlement record

Seat planning FAQ

How many devices can one user use?

Confirm the current official license terms and applicable agreement. Greybridge does not provide authoritative vendor interpretation.

Can licenses be reassigned?

Ask Devolutions for current reassignment rules and document the answer in your entitlement procedure.

Build a forecast procurement can trace.

Start with the role and rollout roster.

Plan the seat model