A clear route through vendor diligence.
Start with public records. Request additional evidence for the requirement your organization is actually reviewing.
Review the firm and its proposed work.
Company record
Legal identity, public identifiers, the company status line, and routes to the issuing records.
Open company recordCapabilities and work packages
Advisory scope, four service lanes, procurement context, and the current capability statement.
Review federal capabilitiesWork-product evidence
A clearly labeled fictional example showing source references, a control gap, a decision memo, and assigned actions.
Inspect sample deliverablesExperience and accountability
Separate client work, internal work, prototypes, and methods. Identify the principal responsible for the work and corrections.
Review relevant experienceAsk for the document your review requires.
| Evidence | Review purpose | Request route |
|---|---|---|
| Insurance documentation | Assess relevant coverage, limits, exclusions, and effective dates. | Specify the requirement and proposed scope. |
| Tax and onboarding records | Complete an authorized vendor setup process. | Confirm the recipient and approved transfer channel. |
| Experience support | Evaluate relevance, role, artifact, and limitations. | Identify the capability claim that needs support. |
| Proposed statement of work | Define outputs, dependencies, review responsibilities, and acceptance. | Discuss the decision need and intended users. |
Send the requirement in plain language.
Include your organization, role, business contact, procurement or vendor-review purpose, the specific document needed, and timing. Explain the permitted recipient and handling route if your process already defines them.
No attachments, credentials, full tax identifiers, banking details, or confidential procurement files in the first message. This page does not grant access to a private document room.
alfonso.evans@