How to check a company's credentials without relying on badges

A company badge can be a useful clue, but it does not prove that a supplier can deliver your particular project. Check the claim behind it: who issued it, whether it is current and what it actually covers. Then compare it with examples of relevant work, the people involved and the commitments in the proposal.

Verify the identity and the claim

Confirm the company's legal name, contact details and the name on the contract. If it claims a registration, accreditation or certification, find the issuing body's record and check the scope and expiry date. A logo displayed on a website may refer to an individual, a past membership or a narrower service than the one you intend to buy.

Do not confuse a routine registration with a quality assessment. Likewise, an award may recognise a specific project rather than every service the company now offers. Record what each check supports and what it leaves unanswered.

Ask for relevant evidence of delivery

Request examples similar to your project in size, audience or complexity. Ask who performed the work, when it was completed, what changed and how results were measured. A project page with attractive images is less helpful than a clear account of the problem and the supplier's role. If a claim is central to your decision, ask for a reference or another way to verify it.

For a team-based service, clarify who will work on your account. Credentials held by a founder do not automatically describe the experience of the delivery team. Ask how work is reviewed and how specialist tasks are covered.

Match checks to the risk

A low-cost, short task may need a concise check. A project involving sensitive data, critical systems or a large commitment warrants more detailed questions about process, insurance, continuity and handover. Use the same proportionate checks for every company on your shortlist. If you are using reviews as evidence, compare the review context rather than accepting a star average as a credential.

Put verified facts, supplier statements and unanswered questions in separate columns. This prevents a persuasive badge from filling an evidence gap it cannot actually close.

Keep a claim-to-evidence record

For each claim, write down its source and the decision it affects. “Certified in a platform” might support technical familiarity, while a recent project example may better support your need for accessible content. Add the issuing organisation, date checked and scope. If the supplier cannot show a record, ask whether the claim refers to a person, the whole company or a former partner. This prevents a broad badge from quietly becoming proof of a narrower skill that nobody has demonstrated.

Frequently asked questions

Does a professional accreditation guarantee good work?

No. It may show that particular criteria were met at a point in time. You still need evidence relevant to your work and current team.

Should I ask every supplier for the same documents?

Use the same core checks for fairness, then request extra evidence where the project creates a specific risk. Explain the extra request so a supplier can provide equivalent evidence in a suitable form.

What if I cannot verify a claim?

Ask the supplier for the issuer, reference number and scope. If it remains material but unverified, record it as uncertainty in your decision.