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
Ask vendors what the AI tool is not designed to do.
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
Turn limitations into a buyer checklist.
Which validation does not apply?
Request notes on excluded workflows, sample limits, stale tests, unsupported data, and settings that change the evidence quality.
When was the documentation updated?
Record the document date, product version, model update timing, and whether the vendor will notify buyers about material changes.
What should reviewers check?
Ask for reviewer instructions, override paths, escalation triggers, and examples of outputs that should not be relied on without more review.
Next step
Fold limitations into renewal and rollout records.
FAQ
Common buyer questions.
Is a vendor limitation statement enough by itself?
No. Treat it as one buyer record alongside audit summaries, human review instructions, change notices, and internal workflow notes.
What if a vendor will not share limitations?
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.