# New-Hire Ramp Quota Schedule Template

> A month-by-month 0/50/75/100% ramp schedule with milestone checkpoints for a new rep's first two quarters, so ramp expectations are explicit instead of improvised.

Free template for sales managers. Topic: [Comp, Quota, Territory & Capacity Planning](https://www.peerlab.ai/library/topic/comp-quota-territory-capacity-planning/). Published by PeerLab in the [Sales Enablement Resource Library](https://www.peerlab.ai/library/). Source: https://www.peerlab.ai/library/new-hire-ramp-quota-schedule-template/

## How to use it

Fill in the new hire's full quota to generate month-by-month dollar targets, then run the checkpoint meeting agenda at the end of every month against the milestone checklist.

## What's inside

- Month-by-month 0/50/75/100% ramp table across 6 months with quota-target formula per month
- Primary focus for each ramp month (certification, outbound motion, pipeline building, first close, exit review)
- Milestone checklist per month (certification complete, pipeline coverage ratio, first closed-won, ramp exit review)
- 4-step checkpoint meeting agenda run at the end of every month
- Exception/extension protocol with a 30-day cap and structural-vs-execution distinction
- Manager notes flagging where ramps typically stall (Month 3→4)

**Ramp curve:** 0% → 50% → 75% → 100% across the new hire's first two quarters (6 months), with a milestone checkpoint at the end of every month.

## The Schedule

| Month | Ramp % of Full Quota | Quota Target | Primary Focus | Milestone Checkpoint |
|---|---|---|---|---|
| **1** | 0% | $0 | Onboarding, product/methodology certification, CRM setup, shadowing | ☐ Certification complete ☐ 1:1 territory review done ☐ First 10 target accounts identified |
| **2** | 50% | $[Full Qtly Quota × 0.5 ÷ 3] | Outbound motion live, first meetings booked | ☐ 15+ discovery calls logged ☐ First opportunity created ☐ Manager pipeline review |
| **3** | 50% | $[Full Qtly Quota × 0.5 ÷ 3] | Building qualified pipeline | ☐ 3x pipeline coverage against Month 3–4 target ☐ First proposal/demo delivered ☐ Q1 close-out review |
| **4** | 75% | $[Full Qtly Quota × 0.75 ÷ 3] | Convert pipeline, first closed-won | ☐ First deal closed-won ☐ Win/loss debrief completed ☐ Coverage ratio ≥ 3x for Month 5–6 |
| **5** | 100% | $[Full Qtly Quota ÷ 3] | Full quota, consistent pipeline generation | ☐ Self-sourced pipeline motion running weekly ☐ On pace to full-quota attainment |
| **6** | 100% | $[Full Qtly Quota ÷ 3] | Full quota, ramp exit review | ☐ Ramp Exit Review completed with manager ☐ Full-quota attainment assessed ☐ Transition to standard territory/comp cadence |

## Fill-In Fields
- New hire name: ______________________
- Start date: ______________________
- Manager: ______________________
- Full annual quota: $______________________
- Full quarterly quota (annual ÷ 4): $______________________

## Checkpoint Meeting Structure (end of each month, 30 min)
1. Review the ramp % milestone checklist above: completed / not completed, with reasons.
2. Review actual pipeline generated vs. the coverage ratio needed for the *next* month's ramp target.
3. Flag any structural blocker (territory, tooling, training gap) separately from effort/execution gaps.
4. Document agreed actions for the coming month.

## Exception / Extension Protocol
- A ramp extension of **up to 30 days** may be granted by the hiring manager where a **structural** blocker is documented (e.g., territory handoff was late, certification program was delayed, product launch pushed the pitch).
- Extensions are **not** available to cover pure execution gaps: those are coached, not extended.
- Any extension must be recorded in writing with a new end date and re-circulated to Compensation/RevOps so commission and quota systems reflect the change.

## Notes for Managers
- Do not let "Month 1 = 0%" become a soft landing with no output: the checklist items above (certification, territory review, target-account list) are the deliverables for that month.
- The jump from 50% to 75% (Month 3→4) is where most new hires stall, this is the point to proactively run a capacity-math quota conversation if pipeline coverage looks thin.