A weekly planning tax
Every week a team meets to decide who is in nurture and what goes out. The decision is re-made from memory and dashboards instead of read off a plan.
Wave · Send Schedule
Your content calendar was built by a human. Your send calendar should be derived.
Teams have intelligence tools, a content library, and a MAP, and still spend hours each week deciding who to reach. Wave derives a month-view calendar of exactly who to reach each day from each contact's buying-group progress, predicted channels, and cadence timing. Every day has a list. Every contact has a next theme and a channel.
Quick answer
The Send Schedule Calendar is a Wave feature that derives a month-view calendar of who to reach on each day from your own data. It is not a calendar you build. Wave computes each contact's next send date from their buying-group curriculum progress and cadence predictions, places them on that day, and shows their role, next theme, and preferred channel when you click in.
Key capabilities
- Month-view calendar derived from your data
- Daily count of contacts ready for a next send
- Per-day drill-in with role, next theme, and channel
- Computed by the same engine as the next-up card
- Suppression parity with channel writeback
- Zero manual configuration
- Core console route for every tenant
Last updated June 2026
The problem
The who-do-we-reach-this-week meeting should not exist.
The last-mile problem in B2B demand gen is that teams have the tools, the content, and the contacts, and still burn hours every week deciding who to activate. The intelligence exists, but turning it into a day-by-day plan is manual labor.
Build the calendar yourself
Every MAP lets you build a calendar, but you pick the audience, the content, and the timing by hand. The system does not derive it from what your contacts are actually ready for.
Lists by hand from properties
Admins assemble enrollment lists by hand from contact fields each week. It is slow, error-prone, and stale the moment a contact's readiness changes.
How Wave does it
Derive the calendar from progress, channel, and timing.
Wave computes when each contact is ready for their next piece of content and places them on the calendar automatically, so the plan reads itself instead of being assembled.
- 01
Compute each contact's next send
For every contact with an active committee seat and a queued next theme, Wave computes a suggested send date from their curriculum progress and cadence timing, the same engine behind the per-person next-up card.
- 02
Place them on the day
Each contact lands on the calendar on their predicted send day. Every date carries a count of contacts whose next send falls there, so the month reads at a glance.
- 03
Drill into any day
Click a date to open the contact list for that day. Each row shows the contact, their committee role, their next theme, and their preferred engagement and promotional channel, drawn from live predictions.
- 04
Respect suppression
The calendar uses the same suppression filter as channel writeback, so do-not-contact, do-not-predict, and deleted contacts are excluded from both the daily count and the drill-in.
Where it fits
Wave's prediction products fused into one planning surface.
The Send Schedule Calendar is where Wave's buying-group progress, channel predictions, and cadence timing come together into a single daily plan, built on the same person-level data layer as the rest of the platform.
Your data
Wave
Send calendar
The calendar is computed on demand from your own data, with no audience lists to build, no date ranges to set, and no content mapping to maintain. It is a core part of the operator console, available to every tenant with no setup. Wave watches its own query latency and warns its team early if the join slows, so the surface stays fast as your contact base grows.
Works alongside Cadence Affinity, Buying Groups, The full Wave platform.
Why Wave is different
A calendar Wave derives, not one you build.
Every MAP gives you a calendar you fill in by hand. Wave computes the calendar from your CRM data, your content library, and your contacts' behavior, so the plan exists before you touch it.
Most tools
Wave
You choose the audience, the content, and the timing for every send.
Wave derives who is ready, what theme they need, and when, from your own data.
Weekly planning is a recurring meeting from memory and dashboards.
Monday morning the plan is already on the calendar, one list per day.
Admins assemble enrollment lists by hand from contact fields.
Wave renders the list automatically, scoped to contacts with a verified next action.
A static content calendar that ignores each contact's readiness.
A living plan that reflects where each contact actually is in their journey.
FAQ
Questions buyers ask about Send Schedule Calendar.
What is the Send Schedule Calendar in Wave?
It is a Wave feature that derives a month-view calendar of who to reach on each day from your own data. Wave computes each contact's next send date from their buying-group curriculum progress and cadence predictions, places them on that day, and shows their role, next theme, and preferred channel when you click in. It is a calendar you read, not one you build.
Who appears on the calendar?
Contacts with an active committee role and a queued next theme. This is an intentional constraint: the calendar represents contacts Wave has identified as ready for a specific next action, not a generic contact list. If Wave has a verified next step for a contact, they appear on their predicted day.
How is the send date for each contact computed?
Wave uses the same next-up engine that powers the per-person card. It combines how far a contact has moved through their buying-group curriculum with their cadence timing and last touch to produce a suggested send date, then places the contact on the calendar on that day.
What do I see when I click a day?
Clicking a date opens a contact grid for that day. Each row shows the contact name, their buying-group role, their next theme, and their preferred engagement and promotional channel, drawn from live Wave predictions. Large days are capped for display with the full count shown, so the view stays fast.
Does the calendar respect suppression and consent?
Yes. The calendar applies the same suppression filter as Channel Affinity writeback. Contacts marked do-not-contact, do-not-predict, or deleted are excluded from both the daily count and the day drill-in, so the plan never surfaces a contact you should not reach.
Do I need to configure anything to use it?
No. The calendar produces results automatically from existing Wave data. There are no audience lists to build, no date ranges to set, and no content mapping to maintain. It is a core part of the operator console, available to every tenant with no feature gate.
How is this different from a calendar in my MAP?
Every MAP lets you build a calendar by choosing the audience, content, and timing yourself. Wave derives the calendar from your CRM data, content library, and contact behavior. The calendar is not a schedule you create, it is a schedule Wave computes for you from what your contacts are actually ready for.
How do I see the Send Schedule Calendar on my own data?
Book a 20-minute walkthrough. We will configure a tenant against your stack and show you a derived month-view calendar on your real contacts, including the daily counts and the role, theme, and channel for each contact on a given day.
See it on your data
See a daily contact plan derived from your own data.
Book a 20-minute walkthrough. We will run the Send Schedule Calendar against your contacts and show you the derived month view, daily counts, and per-contact theme and channel Wave would produce.
Request a demo Download the one-pager (PDF)