All tools
DELIVERABILITY OPERATIONS / DATED RUNBOOK / LOCAL MODEL

Ramp with feedback,
not a magic curve.

Build a receiver-aware sending schedule, document readiness, and turn live complaints, bounces, and deferrals into an explicit proceed, hold, or pause decision.

Dated schedule Receiver mix Health gates
WARMUP RUNBOOK BUILDER
NEW DEDICATED IP / MEASURED MODEL

57 send days to reach 25,000/day

Target first appears Fri, December 18, 2026; the runbook ends after 7 send days at target.

Calendar span63 days

63 active send days

Target dateDec 18, 2026

57 send days

Warmup sends236,204

Through first target day

Full runbook386,204

Includes 7 target days

VOLUME CURVE

Bars represent planned volume, not a mailbox-provider capacity promise.

Oct 23, 2026First target: Dec 18, 2026Dec 24, 2026
LIVE HEALTH GATE
Eligible for operator review

The entered metrics remain below this planner’s conservative guardrails. Confirm per-provider reputation and SMTP evidence before approving the next volume step.

Gmail’s published target is below 0.1% user-reported spam and never 0.3% or higher. Bounce and deferral thresholds here are conservative planning guardrails, not universal provider standards.
PRE-SEND READINESS
0 / 6 confirmed

A schedule does not compensate for missing authentication, consent, unsubscribe, or monitoring controls.

DATED SENDING MANIFEST
DayDateStatusTotalGmailMicrosoftYahoo/AOLOtherCumulative
1Oct 23, 2026Ramp5025137550
2Oct 24, 2026Ramp50251375100
3Oct 25, 2026Ramp63321696163
4Oct 26, 2026Ramp63321696226
5Oct 27, 2026Ramp793920128305
6Oct 28, 2026Ramp793920128384
7Oct 29, 2026Ramp9949251510483
8Oct 30, 2026Ramp9949251510582
9Oct 31, 2026Ramp12462311912706
10Nov 1, 2026Ramp12462311912830
11Nov 2, 2026Ramp15578392315985
12Nov 3, 2026Ramp155783923151,140
13Nov 4, 2026Ramp194974929191,334
14Nov 5, 2026Ramp194974929191,528
15Nov 6, 2026Ramp2431226136241,771
16Nov 7, 2026Ramp2431226136242,014
17Nov 8, 2026Ramp3041527646302,318
18Nov 9, 2026Ramp3041527646302,622
19Nov 10, 2026Ramp3801909557383,002
20Nov 11, 2026Ramp3801909557383,382
21Nov 12, 2026Ramp47523811971473,857
22Nov 13, 2026Ramp47523811971474,332
23Nov 14, 2026Ramp59429714989594,926
24Nov 15, 2026Ramp59429714989595,520
25Nov 16, 2026Ramp743372186111746,263
26Nov 17, 2026Ramp743372186111747,006
27Nov 18, 2026Ramp929465232139937,935
28Nov 19, 2026Ramp929465232139938,864
29Nov 20, 2026Ramp1,16258129117411610,026
30Nov 21, 2026Ramp1,16258129117411611,188
31Nov 22, 2026Ramp1,45372736321814512,641
32Nov 23, 2026Ramp1,45372736321814514,094
33Nov 24, 2026Ramp1,81790845427318215,911
34Nov 25, 2026Ramp1,81790845427318217,728
35Nov 26, 2026Ramp2,2721,13656834122720,000
36Nov 27, 2026Ramp2,2721,13656834122722,272
37Nov 28, 2026Ramp2,8401,42071042628425,112
38Nov 29, 2026Ramp2,8401,42071042628427,952
39Nov 30, 2026Ramp3,5501,77588853235531,502
40Dec 1, 2026Ramp3,5501,77588853235535,052
41Dec 2, 2026Ramp4,4382,2191,10966644439,490
42Dec 3, 2026Ramp4,4382,2191,10966644443,928
43Dec 4, 2026Ramp5,5482,7741,38783255549,476
44Dec 5, 2026Ramp5,5482,7741,38783255555,024
45Dec 6, 2026Ramp6,9353,4681,7341,04069361,959
46Dec 7, 2026Ramp6,9353,4681,7341,04069368,894
47Dec 8, 2026Ramp8,6694,3352,1671,30086777,563
48Dec 9, 2026Ramp8,6694,3352,1671,30086786,232
49Dec 10, 2026Ramp10,8375,4182,7091,6261,08497,069
50Dec 11, 2026Ramp10,8375,4182,7091,6261,084107,906
51Dec 12, 2026Ramp13,5476,7733,3872,0321,355121,453
52Dec 13, 2026Ramp13,5476,7733,3872,0321,355135,000
53Dec 14, 2026Ramp16,9348,4674,2342,5401,693151,934
54Dec 15, 2026Ramp16,9348,4674,2342,5401,693168,868
55Dec 16, 2026Ramp21,16810,5845,2923,1752,117190,036
56Dec 17, 2026Ramp21,16810,5845,2923,1752,117211,204
57Dec 18, 2026Target25,00012,5006,2503,7502,500236,204
58Dec 19, 2026Stabilize25,00012,5006,2503,7502,500261,204
59Dec 20, 2026Stabilize25,00012,5006,2503,7502,500286,204
60Dec 21, 2026Stabilize25,00012,5006,2503,7502,500311,204
61Dec 22, 2026Stabilize25,00012,5006,2503,7502,500336,204
62Dec 23, 2026Stabilize25,00012,5006,2503,7502,500361,204
63Dec 24, 2026Stabilize25,00012,5006,2503,7502,500386,204

A schedule is a hypothesis with stop conditions.

Warmup is a controlled increase in wanted, authenticated email while receivers learn the behavior of a changed IP or domain. The curve is only an initial operating plan. SMTP responses, complaints, bounces, authentication, and provider reputation data decide whether the next increase is justified.

SEND

Use the most relevant, permissioned audience available.

OBSERVE

Separate results by receiving provider and traffic stream.

ADAPT

Proceed, hold, reduce, or pause before the next step.

New IP, new domain, and migration are different changes.

A dedicated IP needs its own sending history. A new domain can be unfamiliar even on provider-managed shared infrastructure. A migration can preserve domain reputation while changing IPs, DKIM keys, return paths, headers, and cadence. Record exactly what changed and segment that traffic instead of treating every scenario as “brand new.”

New dedicated IP

No established IP history; provider-specific capacity matters.

New sending domain

Domain identity is new; shared-IP capacity may already be managed.

ESP migration

Preserve cadence and segment the infrastructure change.

Restart after inactivity

Treat prior history as stale and rebuild predictable traffic.

Ten thousand messages is not one reputation event.

Capacity and feedback emerge independently at Gmail, Microsoft, Yahoo, corporate gateways, and other destinations. A list that is 70% Gmail warms very differently from one that is 10% Gmail. The manifest makes the assumed split explicit so operators can compare planned and actual volumes per receiver.

Hold before a weak signal becomes a pattern.

Google tells senders to increase slowly, send at a consistent rate, begin with engaged recipients, monitor SMTP responses and Postmaster Tools, and reduce volume when bounces or deferrals rise. Its current guidance says to keep user-reported spam below 0.1% and avoid ever reaching 0.3%. Open rate is not a receiver-side control signal: Google says it does not track opens and cannot verify third-party open-rate accuracy.

PROCEED

All readiness controls pass and provider-level signals remain stable.

HOLD

Keep or reduce current volume while investigating a deteriorating signal.

PAUSE

Stop the affected stream when complaints or delivery failures cross a serious guardrail.

Move the audience in observable cohorts.

Preserve the old path long enough to shift traffic deliberately. Start with recent, consented recipients, compare receiver-level outcomes, and avoid changing provider, From identity, content architecture, cadence, and audience policy all at once. If the new path is deferred, route only according to a documented rollback plan; uncontrolled retries can turn throttling into a volume spike.

Email warmup FAQ.

Is this an automatic warmup service?+

No. It creates a planning runbook and exports. It does not send mail, manufacture engagement, open messages, or interact with recipient accounts.

How long should warmup take?+

There is no universal duration. AWS says dedicated-IP reputation can take roughly two to six weeks depending on provider, while its standard automatic warmup increases over 45 days. Actual receiver feedback should control your pace.

Should I warm a shared IP?+

Your email service provider generally manages shared-IP capacity. You may still need to ramp a new domain, new traffic stream, migration, or major volume change. Confirm the provider’s responsibilities.

Should warmup mail go to seed accounts?+

Seed testing can reveal rendering or directional placement, but it does not substitute for wanted production mail and real recipient behavior. Never use coordinated opens or replies to manufacture reputation.

Can I warm with cold outreach?+

That creates an avoidable consent and complaint risk. Warmup should begin with the most clearly permissioned and currently relevant recipients available.

RUN THE PLAN WITH REAL SIGNALS

Keep audience, sending, and deliverability evidence together.

Build consent-aware segments, send campaigns and transactional mail, and inspect results from one operational workspace.

Start for free