Scheduled delivery

What it is#

Scheduled delivery is the practice of having briefs ship on a pre-set cadence rather than being sent manually by an account manager.

Two flavors:

1. Time-based schedule — "1st of every month at 9am client local time," "every Friday at 8am ET," "1st business day after quarter-close." Cron-like; predictable.
2. Event-based trigger — "send when revenue crosses a threshold," "send when a campaign ends," "send when a Linear epic closes." Driven by data, not the calendar.

Most agencies use time-based for monthly + quarterly, event-based for ad-hoc + status.

Why scheduling matters#

Manual sending fails three ways:

• Inconsistency: different clients get briefs on different days of the month depending on AM availability
• Lateness: the "I'll send it tomorrow" promise that becomes the "I'll send it next week" reality
• Capacity: an AM with 8 clients runs out of Mondays before the monthly cadence completes

Scheduled delivery removes these failure modes entirely. The brief ships on the schedule because the schedule, not the AM, is in charge.

What "scheduled" requires#

For scheduling to actually work, three things have to be in place:

• Reliable rendering: the render cycle succeeds even when an upstream data source is intermittent
• Reliable approval routing: approvers get notified in time to sign off before delivery
• Failure handling: if rendering fails, the system surfaces it to a human before the scheduled send rather than silently delivering an incomplete brief

SendBriefs handles all three by default.

Pause + resume#

Sometimes you need to not send. A contract dispute, a client going dark, a re-pitch in progress. Scheduled delivery supports per-client pause without breaking the template or the audit log — you resume, and the next cycle ships.