Classify the source
Label each item as a provider claim, supplied document, buyer reference, or observed test result. Note its date and scope. A network-wide statement may not answer a question about one facility.
Track closure
Assign an owner and next action to every unresolved requirement. Where evidence conflicts, preserve both versions and request a reconciliation. Directory inclusion should never be treated as proof that this work has already been completed.
Keep an evidence trail
For each assessment, record the requirement, the supporting example or document, the date, and the unresolved questions. Distinguish a published capability from an account-specific demonstration. Mark missing information as unknown. Where you use a numerical score, explain the meaning of the scale and the reason for the weight. Your notes should make it possible to revisit a conclusion when the proposal or operating conditions change.
Record what is established
Keep the date and scope of the evidence beside the conclusion. Identify whether an answer applies to your products, the proposed facility, and the activities you intend to buy. List exclusions and unresolved points with the same care as confirmed capabilities. The record should show the limits of the research rather than imply an audit that has not taken place.
Use this question in your next meeting:
What would someone need to see to reach the same conclusion?
Go deeper: The documents to request before choosing a 3PL. The companion article includes an editable worksheet and links to provider profiles.
Further reading
Shopify: fulfilling orders. Background on fulfillment workflows and working with fulfillment services.