Where should the tool not be used?
Ask for roles, regions, job families, candidate groups, or workflow stages the vendor excludes from intended use.
Vendor limitations
A vendor limitation statement turns broad product claims into a usable operating record. It helps buyers know where the tool should not be used, which workflows need human review, and what evidence is still missing.
Questions
Ask for roles, regions, job families, candidate groups, or workflow stages the vendor excludes from intended use.
Request notes on excluded workflows, sample limits, stale tests, unsupported data, and settings that change the evidence quality.
Record the document date, product version, model update timing, and whether the vendor will notify buyers about material changes.
Ask for reviewer instructions, override paths, escalation triggers, and examples of outputs that should not be relied on without more review.
Next step
After limitations are documented
Use the Evidence Hub to decide whether limitations affect vendor scoring, renewal evidence, pre-audit prep, or the monthly operating file.
Open evidence hubKnown exclusions, supported roles, model versions, and reviewer instructions can change. Compare monthly updates with a one-time checklist.
Compare monthly workflowCheck the Pro contents, checkout access, and sample update before moving limitation tracking into the paid operating file.
Review checkout accessFAQ
No. Treat it as one buyer record alongside audit summaries, human review instructions, change notices, and internal workflow notes.
Record the gap, ask for a narrower summary or support article, and route the issue into renewal, procurement, or legal review before relying on the feature.