Build a cold-email sending schedule that fits

Bring two decisions into this exercise: the volume you want to support and the finite sequence you intend to run. The volume guide teaches how to count messages; the follow-up guide teaches the purpose and stop rules of later steps. Scheduling turns those decisions into dated work with an owner.

Write down the start and end dates, permitted weekdays, sending windows, known exclusions and who will monitor the queue. Include the team's ability to handle replies. A campaign that creates conversations when nobody can respond may need a different operating window even if the infrastructure is available.

Choose an initial window from the actual audience and operating context. Do not call it the universally best time to send. If timing is a meaningful commercial question, define a separate comparison after the basic schedule works. The first goal is a queue that behaves as intended, not a borrowed timetable with unexplained assumptions.

Record which time zone the campaign uses and why that zone fits the audience group. Keep a reliable source for the contact's relevant working location where needed; a company's headquarters or a guessed country code may not describe the person you are contacting. Leave uncertain records for review rather than silently assigning them a convenient time.

Also record the clock used by account-level controls and reports. Smartlead documents that its account time zone affects the mailbox daily-limit reset, while a campaign can use a different zone. It also explains that an account's limit is shared across campaigns. A second campaign does not create a second independent allocation.

Time-zone rules can change. IANA maintains updates for UTC offsets, boundaries and daylight-saving rules. Use an explicit supported location-based zone when local civil time is your intention, then inspect the resulting dates in the tool. A fixed UTC offset describes an offset, not a complete year-round local calendar.

For handovers, record both the intended local window and its corresponding UTC times for the dates being checked. Recheck around clock changes and relevant holidays. The worked examples below deliberately use UTC throughout so their arithmetic does not depend on a daylight-saving conversion.

A delay and a sending window answer different questions. The delay determines when a follow-up becomes due relative to the preceding step. The active calendar determines when sending is allowed. Capacity, recipient state and account availability still affect whether an eligible item can proceed.

Instantly documents per-lead delays measured from the previous actual send, with calendar days counted even when sending is inactive. A due step must also fall inside an active schedule. Check the current behaviour in your chosen tool instead of assuming that “two days” always means two working days.

In this original fictional example, the window is Monday to Friday, 09:00 to 11:00 UTC, with no additional exclusions. The times below show the earliest window allowed by the stated model. They do not reserve a slot or guarantee an exact send.

Check the allocation at the narrowest relevant level: the account, shared pool, campaign and active window. A monthly average cannot tell you whether a particular Tuesday morning fits. Include existing commitments from every campaign using the same accounts, then check how work is assigned between them.

Consider a deliberately small fictional exercise. An operator has confirmed six available message slots on account A and six on account B for the next window, after other commitments. Eight follow-ups are eligible: five belong to A and three to B. The team also wants to start seven new contacts. Demand is 8 + 7 = 15 against 12 available slots, so the requested queue does not fit.

For this exercise, the operator releases three new starts: one on A and two on B. That creates 11 planned attempts and leaves one slot uncommitted. Four new contacts remain outside the released queue. The spare slot is a deliberate planning choice in this scenario, not a universal reserve or prescribed sending rate.

The account split matters. Two new starts on A would overfill its six-slot allocation even though the combined total might look acceptable. Use the tool's actual assignment and queue behaviour. Where you cannot control or confirm a proposed split, revise the plan rather than treating the spreadsheet as an executed schedule.

Map each decision to a real setting and verify the saved state. Instantly separates its campaign-wide daily limit, new-contact limit and message spacing. It documents follow-up priority by default, with an option to prioritise new leads. These controls perform different jobs; one number does not describe the whole queue.

Multiple time windows are not necessarily automatic routing by recipient location. Instantly states that its schedule layers apply together to the campaign and recommends separate groups and campaigns for different lead time zones. Check this distinction before using several schedules to represent several audiences.

In Smartlead, documented conflicts between account-level gaps and campaign timing can reduce sending. Compare all applicable settings, including other campaigns sharing the account. Do not shorten spacing or increase a limit merely to force a forecast to match a target; first establish which constraint is actually active.

Save the configuration reference with the schedule brief. A colleague should be able to find the selected accounts, calendar, queue priority and responsible owner. Recheck the relevant controls after copying a campaign, moving a list or changing an account group.

A pause changes the queue. Before resuming, establish which messages were attempted, which remain pending and which contacts have replied or become ineligible. Preserve the activity record so the team does not accidentally treat already-attempted work as untouched work.

Start with the next permitted window and its current capacity. Existing eligible follow-ups and other campaigns may already occupy it. Decide what can move, what should stay held and whether the remaining sequence is still relevant. Update downstream due dates when an earlier actual send changes.

A missed window is not a debt that must be recovered in one burst. If the remaining calendar cannot accommodate the target under the agreed conditions, reduce new starts, extend the planning period or discuss a revised capacity plan. Keep restrictions and recipient instructions intact while making that decision.

Assign one person to approve the revised queue. Record the reason for the interruption and the evidence that permits resumption. When the cause is unresolved, a documented hold is more useful than repeatedly toggling a campaign and hoping the next window behaves differently.

Compare the released workload with recorded activity at a defined cutoff. Count the same unit on both sides. An attempted message is not proof of successful delivery or placement, and a contact still waiting in the queue is not automatically a failed send.

Continue the fictional 11-attempt plan. At the review cutoff, there are nine recorded attempts, one cancelled follow-up after a recipient reply and one item still pending because its account was paused. The released workload reconciles as 9 + 1 + 1 = 11. Separately, the four new contacts never released remain outside that queue.

Across the original 15 requested messages, the complete position is nine attempted, one cancelled, one pending and four not released. This explains the shortfall without inventing a delivery result. Give the pending item an owner, check its relevance and place it in a later window only when the conditions permit.

Use repeated observations to improve the schedule. Record whether a mismatch came from timing, allocation, a stop, an account problem or an incorrect assumption. Make one accountable change, then inspect the next relevant window. Increasing the target alone does not resolve the reason a previous plan failed to fit.

Combine the calendar, allocation and queue decision in one short record. Link it to the approved sequence and the current capacity plan. That makes changes visible without duplicating the complete campaign in several places.

Update the brief when the audience group, time zone, accounts, follow-up delays or operating cover changes. For commercial tests of different send times, use the A/B testing guide to define a fair comparison. This worksheet establishes operational clarity; it does not predict the best time for every reader.