How complete is the GTM vendor onboarding packet at first review?
Review vendor onboarding completeness at first submission, identify returned requirements and distinguish intake delay from approval decisions.
Freeze the first submission
Define the vendor population and review window. Save the first submitted packet and the checklist version that applied at that time. Include withdrawn and delayed onboarding requests, and record exclusions with reasons. This protocol proposes an internal review; it does not report a measured vendor performance rate.
Treat one vendor onboarding request as the case. Later document replacements belong to that case rather than creating extra successful submissions. Keep the intended start date separate from the actual submission date so late intake is not mistaken for slow review.
Classify requirements by evidence status
For every applicable checklist item, record present and usable, present but needing correction, missing, or not applicable with a reason. Identify the reviewer and source location. Document presence alone does not mean a contract, security assessment or other substantive approval has been granted.
Group returns by the actual requirement involved, such as unclear service scope, an incomplete billing setup or an unanswered access question. Preserve the original return reason. Do not replace specific defects with a broad label such as incomplete paperwork.
Measure completeness and time separately
Calculate the share of first submissions that meet the applicable intake checklist, with the numerator and denominator shown. Report later corrections separately. For timing, distinguish time before first review, time awaiting a vendor response and time awaiting an internal decision.
Show open requests and withdrawals beside completed cases. If requirements changed during the window, split the comparison or explain the effect. A lower completion rate may reflect a more demanding checklist rather than a less capable vendor group.
Turn recurring returns into a clearer intake
Illustrative finding: access requests repeatedly arrive without the systems or permissions needed. The intake owner adds a field for the named system, requested role and internal approver, plus an example of an acceptable request.
Review the next set of submissions against the revised checklist. Keep commercial, legal and security acceptance with their designated owners. The intake report can reveal missing evidence and waiting time; it does not decide whether a vendor should be approved.