Compare identity vendors across evidence-backed evaluation dimensions without treating unknown values as zero.
The scorecard is a decision aid for structured vendor evaluation. Unknown dimensions are excluded from the composite denominator, and every saved comparison should be checked against current vendor evidence before procurement.
Define the decision, workflow, regions, risk tolerance, implementation constraints, and mandatory requirements before scoring vendors. Use the same dimensions and evidence dates for every candidate. The scorecard intentionally excludes unknown values from the composite denominator so missing information cannot silently become a failing score or an assumed capability.
For each scored dimension, retain the product and edition reviewed, source URL or document, retrieval date, evidence owner, and any jurisdiction or deployment boundary. Separate provider assertions from contractual commitments, independent testing, customer references, certifications, and buyer-run results. Record exceptions, fallback paths, manual-review requirements, accessibility needs, data retention, residency, subprocessors, and incident-response obligations.
A score organizes evidence; it does not certify a vendor or predict production performance. Weighting should reflect the buyer's actual workflow and risk, and a close result should trigger deeper validation rather than false precision. Recheck material claims before procurement because product scope, ownership, integrations, certifications, pricing, and regulatory obligations change.
Use the scorecard to identify the claims that need a demonstration, security review, contractual commitment, reference call, or controlled pilot. Test representative documents, devices, user populations, accessibility needs, attack conditions, and exception paths rather than relying on a best-case demonstration. Record the acceptance threshold and who can approve an exception before testing begins.
Revisit the comparison when evidence expires or a finalist changes its product, hosting model, subprocessors, ownership, commercial terms, or supported geography. Preserve the earlier score and its date instead of silently overwriting it; a time-stamped trail makes later procurement and risk decisions easier to audit.
Use the Identity Stack Builder for market orientation, the comparison methodology for evidence rules, and the gap assessment to identify controls that the shortlist must address. Legal, privacy, security, procurement, finance, accessibility, and operational owners remain responsible for their specialist review.