Calendar & Scheduling

Plan your testing roadmap with the CADENCE Calendar. Schedule tests, avoid conflicts, and maintain a consistent testing velocity.

Calendar view

Navigate to Dashboard > Calendar to see a monthly view of your testing schedule.

  • Navigate between months using the arrow buttons
  • Test slots appear on the calendar with experiment names and status
  • Color coding indicates slot status (scheduled, in progress, completed)

Scheduling tests

Create test slots to reserve time for experiments:

  1. Navigate to Dashboard > Calendar
  2. Create a new slot by selecting a date range
  3. Assign an experiment to the slot (or leave it as a placeholder)

One experiment per slot

Each time slot can only have one experiment assigned to it. This is enforced at the database level to prevent double-booking. If you need to run multiple tests simultaneously, create separate slots.

Schedule templates

Templates let you set up recurring testing cadences so you don't have to create slots manually each week.

Creating a template

Navigate to Dashboard > Calendar > Configure:

  1. Name your template (e.g., "Weekly test cycle")
  2. Define the pattern (weekly, biweekly, etc.)
  3. Set the slot duration
  4. Save the template

Generating slots

Templates can auto-generate test slots. The system creates future slots based on your template pattern using a database function. This means your calendar stays populated without manual work.

Templates (experiment templates)

Navigate to Dashboard > Templates to browse a library of pre-built test ideas:

  • Search and filter by category (e.g., headlines, CTAs, pricing, layout)
  • Each template includes a hypothesis, suggested variants, recommended metrics, duration, and difficulty level
  • Use templates as inspiration when planning what to test next

This is different from schedule templates. Experiment templates provide test ideas and starting points; schedule templates define when tests run.

Backlog

Navigate to Dashboard > Backlog to manage your test idea pipeline:

  • Add test ideas with a title, description, and hypothesis
  • Score each idea using three sliders: Expected Impact (1–10), Implementation Effort (1–10), and Strategic Value (1–10)
  • Auto-calculated priority score ranks ideas automatically using the formula: (impact × 2) + (11 − effort) + strategic
  • Browse templates for inspiration when the backlog is empty

Higher-scored ideas appear at the top. Use the backlog as your testing pipeline — review it weekly and pick the top ideas to schedule on the calendar.

Putting it all together

A healthy testing workflow looks like this:

  1. Ideas flow into the backlog from the team, analytics, and customer feedback
  2. Weekly review: Open This Week on Monday morning to see what needs decisions and what's coming up
  3. Schedule on the calendar using templates for consistent cadence
  4. Run the test for the full scheduled duration
  5. Make decisions from This Week — Ship Winner, Keep Control, or Extend directly from the action cards
  6. Review cumulative impact in Impact View
  7. Document and iterate — archive the test, update the backlog with new ideas

Best practices

Plan 2–4 weeks ahead. Having a visible testing roadmap builds team confidence and prevents last-minute scrambles.

Don't overlap conflicting tests. Two tests on the same page targeting the same audience can interfere with each other. Use the calendar to spot conflicts.

Stick to the schedule. Don't stop tests early because of impatience. The calendar helps enforce discipline by setting clear start and end dates.

Review the backlog weekly. Priorities change as you learn. Keep the backlog fresh by removing stale ideas and adding new insights from completed tests.

Use templates for recurring patterns. If you run weekly hero tests, create a template so setup takes seconds instead of minutes.

Next steps