Operations CoordinatorOperations CoordinatorPowered by StealthAgents
Research

How requester concentration shapes workload risk

A source-led method for measuring how strongly operational demand depends on a small set of requesters across volume and effort.

OperationsCoordinator Editorial Team · Published · 4 min read
Illustrated research title card showing workload shares distributed across requester groups and time periods

Requester concentration and workload dependence

Requester concentration is high when a small set of stable requester identities accounts for a large share of operational demand. Measure both request counts and defensible effort exposure, test the result under alternate identity groupings, and avoid treating concentrated demand as unnecessary demand.

This is a dependency and planning study. It does not rank requester value, assign blame, or show what workload could be removed.

The 2023 US merger guidelines describe markets with a Herfindahl-Hirschman Index above 1,800 as highly concentrated and flag a merger that raises the index by more than 100 points in such a market. The DOJ merger guidelines provide transparent arithmetic, but those legal market thresholds must not be imported as workload-risk cutoffs.

Define requester identity

Choose whether the unit is a person, account, department, customer, location, or channel before aggregating. Preserve the raw identity and maintain a versioned crosswalk so renamed or merged entities do not appear as new demand sources.

Keep unknown and shared identities visible. Assigning a shared inbox to the most common user can manufacture concentration.

Freeze the eligible request population and observation window. Exclude records only under declared rules and report excluded counts by reason.

Measure more than volume

Calculate each requester share of entries, handling touches, elapsed exposure, and completed work where those fields are reliable. A requester with many simple requests can dominate volume but not effort, while a low-volume requester can dominate specialist time.

Report the largest shares, a cumulative concentration curve, and at least one all-requester summary. Show raw counts beside every percentage and avoid a threshold chosen after seeing the result.

Repeat the calculation by week or month. A single annual value can hide seasonal projects, temporary incidents, or a recent structural change.

Test sensitivity and context

Recalculate after grouping known aliases and after separating shared accounts. If conclusions change materially, identity resolution is part of the finding.

Stratify by request type, required skill, and channel. Concentration may reflect a legitimate ownership model, a specialized workflow, or inconsistent intake rather than dependency on one relationship.

Compare arrival concentration with capacity coverage. Demand concentrated in one requester becomes a different operational risk when several people can handle it than when one specialist holds the only access or knowledge.

Use the result carefully

The study can identify where planning depends on a small number of demand sources and where identity data is weak. It cannot determine whether those requests are valuable, avoidable, or appropriately scoped without process-owner review.

An operations coordinator can maintain requester crosswalks, recurring summaries, and exceptions. Service and business owners decide whether the pattern calls for intake changes, cross-training, capacity reserves, or no action.

The demand coverage study addresses capacity alignment, the arrival clustering study examines timing, and the Research index collects related designs.

Sources and limits

The DOJ thresholds govern a specific competition-law analysis, not requester management. An internal study should publish its identity crosswalk, observation window, count and effort measures, and sensitivity results without labeling a requester as risky or dispensable.

Frequently asked questions

Is high requester concentration always risky?

No. It can reflect a deliberate service model. Risk depends on volatility, capacity coverage, access, and the consequence of sudden change.

Should effort be measured with elapsed time?

Not automatically. Elapsed time can include waiting. Use handling time or touches only when their capture is reliable, and show volume as a separate measure.

How should shared inbox requests be counted?

Keep the shared identity unless a documented field supports a more specific owner. Report that grouping choice in the sensitivity analysis.

From clients of our parent company · Stealth Agents reviews

★★★★★
Great communication, efficient and proactive assistant, visible business growth.
Sarah JacobyStealth Agents client
★★★★★
The easiest VA onboarding process. Communicative and helpful throughout.
McKay JaeckelStealth Agents client
★★★★★
Lindsay has been incredible. She handles the tactical work, which has freed me up to focus on bigger-picture initiatives.
Chad SubletStealth Agents client
★★★★★
They have made a real difference in our day-to-day operations and truly feel like part of our internal team.
Alex BehrensStealth Agents client
★★★★★
The team learned my brand and goals and transformed my business. My dream team.
Martine CadetStealth Agents client
★★★★★
We especially appreciate how diligent and pleasant Evy is. True pros.
Rich CochranStealth Agents client
★★★★★
Agents tackled diverse tasks seamlessly and manager Charm consistently provides excellent talent matches.
George AssiStealth Agents client
★★★★★
Stealth Agents provided me with a fantastic virtual assistant who has been an absolute asset.
Lee MaasenStealth Agents client
★★★★★
Paolo is exceptional. Communicative, fast turnaround, quality work every time.
Lynda Sunshine WestStealth Agents client
★★★★★
Continuously impressed by professionalism, punctuality, attention to detail, and the kind family approach.
EvanStealth Agents client