Supplier resources · Evidence request
Ask for evidence behind the answers.
Follow up an initial supplier response with a request for product-specific documentation, migration plans and customer implications.
How to use this template
Replace the fields in square brackets and adapt the questions to the supplier’s initial response. Remove questions already answered adequately.
You can edit the email below before copying it. Edits are not saved by PQCPrep and may be lost on refresh. Send the email through your usual application and use approved channels for confidential documents.
What to check in the evidence
- Match your deployment. Check that documents apply to your product, version and configuration.
- Check dates. Record when evidence was issued and whether it has been superseded.
- Separate delivery from plans. Release notes and available features answer a different question from roadmap commitments.
- Read the scope. Testing or certification may cover only particular components or configurations.
- Record customer work. Identify actions, costs, owners and dependencies that your business must manage.
- Track unanswered questions. Missing evidence is an information gap; it does not by itself establish that a supplier is unprepared.
Supplier documentation is one input to due diligence. Specialist review may be needed to evaluate technical claims and their relevance to your systems.
Related template
Starting the conversation with a supplier?
Use the initial supplier enquiry →
This is an original PQCPrep resource.
Template version 1.0 · 7 October 2026