Chicago IT Provider Score Ranges: Reading the Spread

What do the Chicago IT provider score ranges actually show?

They show distance. Across the 93 Chicago firms IT Support Chicago tracks, the average published score is 20.9% against a range of 0.8%-77.8%. A shortlist assembled from the top of that range therefore sits a long way from the typical tracked firm, and the size of that gap is itself the information a buyer should read before comparing any two names.

The published score combines 4 criteria scored from public evidence. A further 6 criteria apply only inside a signed-in custom evaluation and carry no weight in the published number: 2 are scored from third-party data against the buyer's own location and size, and 4 are scored only from a firm's own answers to our inquiry questions. So the public total is a partial picture by construction, not a verdict on total capability.

The practical consequence is that a total is a summary of four unevenly distributed measurements, and summaries hide their inputs. Two firms landing near the same published total can be built from entirely different component mixes. Our methodology write-up in the Chicago IT provider rankings and reviews sets out how each component is built and where public evidence runs out.

How the four scored criteria sit across the tracked firms

The weights are close together; the distributions are not. IT Support Chicago weights Client Reputation 29 of 100 and Proactive Issue Reduction 27 of 100 in its published score. Security Certification carries weight 24 of 100 and Employee Reputation weight 20 of 100. Read the medians and middle halves below alongside those weights and it becomes clear why identical totals can come from opposite component mixes.

Two things in the table are worth reading together. The criterion carrying the heaviest weight also shows the widest middle half. And the number of firms we scored differs by criterion, from 93 of 93 down to 50 of 93 — a firm outside one of those counts is a firm we hold no record for on that criterion, never one we assessed and found lacking.

When you compare a shortlist, ask which components produced each firm's total rather than reading the total as a single quality signal. A firm strong on the widest-spread criterion and quiet on another can publish a number close to a firm with the reverse profile.

How wide is the Client Reputation band, and what should you read into it?

It is the widest band of the four. On Client Reputation IT Support Chicago records a median of 34.4, a mean of 44.6 and a middle half of 18.9 to 73.7, scored for 93 of 93 firms. That band is much wider than the other components, and the gap between the median and the mean is itself a detail worth noting before treating the component as a simple pass or fail.

The component aggregates client ratings from Clutch, Google, and other public review platforms through a Bayesian model, adjusted for volume, recency, and platform credibility. Those adjustments matter for how you read a raw review count. One weakness we record on tracked firms is client reviews on a single platform only — Google — and a high review count concentrated in one place is a different signal to our model than the same count spread across several platforms.

For a buyer, that means the reputation figure is not a substitute for looking at where the reviews live. Check how many platforms a provider appears on, how recent the newest reviews are, and whether the review population resembles your size and industry. Our guide to Chicago IT provider review profiles covers what to look for before you treat a rating as evidence about your own likely experience.

What does an unscored Proactive Issue Reduction criterion mean?

It means silence in our records, not evidence that a firm is reactive. Proactive Issue Reduction is scored for 50 of 93 firms in IT Support Chicago's records, with a median of 8.0 and a mean of 14.3. The middle half runs from 0.0 to 24.3, so both the low cluster and the missing scores need careful reading.

The criterion is built by classifying employee job titles as proactive — architects, security engineers, consultants — against reactive titles such as help desk, network operations centre (NOC), and support techs, using Apollo.io workforce data. Attainment is calculated as one minus the reactive share, multiplied by 100, where the reactive share is reactive titles divided by reactive plus proactive titles. A firm outside the scored count is one we hold no workforce record for; it has not been assessed and found lacking.

If preventive work is central to what you are buying, the score is a prompt rather than a conclusion. Ask the provider directly how its staff is split between preventive and reactive roles, how that split has changed over the past year, and which named people would hold the preventive work on your account. Our proactive IT staffing ratio guide sets out the questions and the documentation worth requesting.

How should you turn the spread into a shortlist?

Start from the criterion mix your organization actually needs, then look at totals. Our position at IT Support Chicago is that bigger is not inherently better and right-sizing matters more than headcount. A larger provider is not a safer default, and neither is the highest published total — both are proxies standing in for a fit question you can answer more directly.

In practice that means deciding, before you open the rankings, which of the four components maps to your risk. A firm with a heavy compliance obligation should weight the certification component and then verify each entry itself; a firm whose last provider drowned in tickets should weight the preventive-staffing component; a firm replacing a provider after a service collapse may care most about reputation and employee stability, since turnover is a risk even when clients are happy today.

Then treat the published score as a starting filter rather than an answer. Ask each shortlisted provider to explain the parts of its profile our public data cannot reach — scope, coverage hours, escalation paths, and who actually staffs your account. We cover how to hold a total and a fit assessment side by side in our guide to IT provider score versus buyer fit.

The limitation to keep in view: every figure above describes the firms we track and the evidence we could collect, at the point we collected it. Public evidence moves, workforce records are incomplete, and four public criteria cannot capture how a provider behaves during a bad week. The spread tells you where to look harder, not who to sign.