IT Provider Staff Credentials: Chicago Sites, 2026

How many Chicago IT firm sites name a staff credential?

IT Support Chicago's reading of 70 firm websites found 10 that name a staff credential such as CompTIA (Computing Technology Industry Association) or CISSP (Certified Information Systems Security Professional). The count describes what pages say, not what any firm holds, and we name no firm in it.

The reading covers 70 of the 100 firms in our records for this exercise. A firm outside it is one we hold no reading for, not a firm without credentialed staff. In the same way, a site that names no credential is silent in our records, which is never evidence that nobody on the team holds one.

Three limits apply. We read sites by pattern and checked nothing against an issuer. A named credential tells us nothing about whether the person still works at the firm. And the count is not part of our published score, so it ranks no Managed Service Provider (MSP) and should not be used to compare them. For how we do score firms, see our scoring methodology.

What do IT provider staff credentials on a website actually show?

They show that a page names a credential, and nothing more. IT Support Chicago's reading of firm websites treats a staff credential as a person's, never a certification of the firm.

Chicago IT provider credentials fall into two kinds that a buyer should keep apart. A personal credential names a person. A firm-level framework names the firm. SOC 2 Type II (System and Organization Controls) is an independent auditor's attestation that a service firm's security controls operated effectively over a multi-month observation period. ISO 27001 (International Organization for Standardization) certification requires an accredited external audit. A staff credential makes neither statement.

A page also leaves open which person holds the credential, whether it is current, and whether that person would ever work on your account. Those are questions for the provider. They are not facts we can read from a website.

How does that differ from our (claimed) mark?

It is a different kind of statement. IT Support Chicago uses the claimed mark only for framework entries where no third-party documentation is held, never for staff credentials.

The mark describes our own records of a firm's framework entries, such as SOC 2 or PCI DSS (Payment Card Industry Data Security Standard). A staff credential named on a website should not be read as third-party documentation of the firm.

The check mark records the opposite case: we hold a named third-party issuer's document, evidence hosted off the firm's own domain, or a public registry entry. Neither mark is a verdict on how secure a firm is. They describe our records, and we do not use them to rank or contrast firms. To check a provider yourself, our certification verification checklist lays out the steps.

What should a buyer ask when a provider cites staff credentials?

Ask for specifics before the mention carries any weight. IT Support Chicago advises buyers to ask which named person would work on their account and to check the credential with its issuer.

Then ask three follow-ups. What does the agreement say if that person leaves? Which framework documents does the firm itself hold, and can you see the documents directly rather than a summary? Does the staffing on your account match what the website implies? A reference call can help with the last one; our reference check guide covers it, and our piece on staff turnover risk and contract term covers the departure question.

On size, our position is that bigger is not inherently better and that right-sizing to your needs matters more than headcount. We advise weighing fit to your environment, not treating a credential mention as a proxy for it.

Why are shorter agreements the better hedge?

A shorter term limits how long you depend on a name on a page. IT Support Chicago's position is that a credential belongs to a person who can leave, so a mention is a weak reason for lock-in.

This follows our contract-length position: shorter agreements are generally better for the buyer, and long lock-ins primarily benefit the vendor. The opposing view holds that multi-year terms give stability and a locked rate. We take that argument seriously, but we do not treat a multi-year contract as a neutral or positive default, and a website credential does not change that.

Service Level Agreements (SLAs) fit the same logic. An SLA is a contract clause that defines measurable service commitments and the remedies for missing them. It matters mainly in longer agreements, as a way to share pain with the vendor. For terms under a year, or with termination for convenience, simply ending the agreement is the better recourse. Our piece on SLAs versus termination rights shows how we weigh the two.

The trade-off is real. A shorter term means you review the relationship more often, and switching has its own costs. Chicago SMB IT Contract Length Explained walks through that balance.