Partners preparing for a tier upgrade often focus heavily on a single metric, usually consumption revenue, and assume the rest of the review is a formality. That assumption causes avoidable delays. A tier review evaluates several categories simultaneously, and a weakness in any one of them can stall a decision even when the headline number looks strong. Here is what actually gets reviewed.
1. Consumption Revenue and Growth Trend
This is the metric partners are most aware of, and for good reason, since it is often the most heavily weighted. But as covered earlier in this series, AWS looks at both the absolute consumption number and the trend over time. A partner with strong absolute consumption but a flat or declining trend does not present as favorably as a partner with a smaller number trending upward consistently.
2. Customer Reference Quality, Not Just Quantity
AWS does not just count how many customer references a partner submits. Reviewers look at whether the references reflect genuine, substantive customer outcomes relevant to the partner’s category, versus references that are technically valid but thin on detail. A handful of strong, detailed references from customers who can speak specifically to outcomes tends to carry more weight than a larger number of references that read as generic.
3. Technical Validation Status
Where technical validation is a requirement for the tier or category in question, AWS reviews whether that validation is current and complete, not just whether it was completed at some point in the past. Partners sometimes assume a validation completed years earlier still counts at full weight, when in practice program requirements and validation criteria evolve, and older validations can be treated as needing a refresh.
4. Program Participation History
AWS also looks at a partner’s overall pattern of engagement with the Partner Network: participation in relevant training, engagement with ACE, responsiveness to AWS-sourced opportunities, and general activity level within the program. A partner who technically qualifies on the hard metrics but has a thin participation history sometimes gets treated with more scrutiny, because participation history is one of the signals AWS uses to gauge whether a partner will actively use the benefits of a higher tier.
5. Deal Structure Quality Across Reviewed Transactions
Reviewers do not just look at whether consumption revenue hit a threshold. They look at how that revenue was generated, and deals that reflect strong structure, correctly documented Private Offers, properly configured CPPO transactions, and clean EDP alignment where relevant, tend to reflect more favorably than a similar dollar amount generated through less structured or less trackable means. This connects directly to the deal structure principles covered throughout this series: how revenue is generated matters, not just how much.
6. Consistency Across the Evaluation Period
AWS generally prefers to see consistent performance across the full evaluation window rather than a late surge concentrated in the final weeks before submission. A partner who shows steady progress across consumption, references, and participation over the full period presents a more credible growth story than one who shows minimal activity for most of the period followed by a rush of activity right before review.
Strategic Takeaway
A tier upgrade review evaluates consumption trend, reference quality, technical validation currency, program participation, and deal structure quality together, not in isolation. Partners who prepare across all five categories, consistently over the full evaluation period, go into a review with far less risk than partners who optimize heavily for one metric and hope the rest holds up.
Preparing for a tier review and want a full picture of where you actually stand across every category AWS evaluates? Marketeering helps AWS partners run a pre-review audit and close gaps before they become blockers.
