systeme.io Course Modules on Fixed Dates: Drip vs Workflow

A mindset coach who moved onto systeme.io in 2025, Adela D., rated it five stars on Capterra and listed one gap: "I would like my course modules to drip on specific dates and that feature is not available." The review says the feature had been requested.

That's a cohort. Everyone starts together, module 2 opens for the whole group on a Monday, and the live call that week assumes everyone can see it. systeme.io's drip setting doesn't work in dates. It counts days, and one line of its help center says it counts them per student.

There's still a way to pin modules to dates, and it isn't in the course settings. A workflow can wait until an exact date and tag the student, and an automation rule can then widen that student's access to the next module. Every piece of that is in systeme.io's help center, and it costs one rule per release date. That cost, more than the course itself, decides the plan.

Three ways to put dates on a course

If the cohort only needs a shared start, the order form does it on any plan. If each module needs its own date, the drip is the wrong tool and the dated workflow is the right one.

Why a dripped course drifts

The help article on dated course access sets the start: "Your students will gain access to the course on the selected day at 12:00 AM (midnight) in your time zone." Buyers get the access email when they pay, and the course stays locked until the date. The access types article adds that with a start date set, "the drip schedule will begin from that date."

So far that sounds like a cohort calendar. The trouble is how the same article describes the delay on each lecture: "The delay is in days and begins after viewing the previous lecture (1)." On that reading, a student who opens lecture 1 on Thursday instead of Monday gets lecture 2 three days late, and every lecture after it. A worked example further down the same article counts days from enrolment instead, so the article doesn't settle it.

For a self-paced course, that doesn't matter. For a cohort with a weekly live call, it can mean some students arrive at the call without the module. systeme.io's access-dates article lets you check what actually happens: under Assets, Courses, Students, the student's menu has Show lectures access dates, which lists the unlock dates for one student. It only works for Drip content access. Run a test student through a week before you rely on the drip for dates.

Building the dated release

Each release in its own module

Partial access, the setting this build uses, works by module: on the order form you choose which modules a buyer gets. So week 1 is module 1, week 2 is module 2, and so on. Lectures inside a module open together.

An order form with module 1 and a start date

On the cohort's order form, add the course as a resource with Partial access to module 1, and switch on Grant access on specific date with the cohort's first day. Buyers get their login straight away and the course opens at midnight on day one.

Use one order form for each cohort. The dated-access article doesn't say what happens to students who've already bought if you change the date later, so I wouldn't reuse a form for the next group. My course, coaching and VIP guide explains why each order form gets its own funnel.

The release workflow, built before the first sale

Create a workflow under Automations, Workflows, and set the trigger to New sale on the cohort's offer, which the help describes as "When a customer purchases an offer." For each release, add a Delay set to Exact date, the morning that module should open (the workflows article says a timezone selector appears next to the date, preset to your account's timezone), followed by an Add a tag action named for the week, such as "week-2". An optional Send an email step after it can tell the group the module is open.

The access itself comes from automation rules. For each week's tag, create a rule with the trigger Tag added and the action Enroll in course, with Partial access to the modules released so far. The free-access article shows Partial access on that rule action, and the automation rules article notes that a rule only reacts to tags added once it's in place, so every rule has to exist before the workflow tags anyone. A six-week cohort needs five rules, for weeks 2 to 6.

Activate the workflow before the order form takes a sale. The workflows article says they don't act retroactively: a sale made before activation never starts the workflow, so a buyer from the day before won't be picked up.

One thing the help center doesn't settle is progress. The access types article says progress is kept, as far as possible, when a student moves between partial-based access types, so widening Partial access from module 1 to modules 1 and 2 should keep module 1's progress. Check it with a test student.

Late joiners

If someone buys after the week-2 date, the workflow's first delay is already in the past. The help center doesn't say whether that step fires at once or waits. Either close the cart before the first release date, or put a test address through after a date has passed and watch what it gets.

A test cohort on a second address

Buy with an email address of your own on a test cohort whose dates are a few minutes apart, then log in as that student. The course should open at the start, show module 1 only, and add module 2 at the second date.

A shorter build, if your account offers it

The workflows article lists Enroll in a course among workflow actions without showing its options. If the action in your account offers Partial access, the workflow can widen access itself after each dated delay, with no tags or rules, and its last step can switch the student to Full access. That would fit a whole cohort into one workflow. The help center doesn't document it, so open the action and look before you plan around it.

Which plan a dated cohort needs

Limits as systeme.io's pricing page listed them on October 9, 2026 (yearly prices checked October 8):

On Free, the documented build holds one dated release. The order form opens module 1 on the start date, the single workflow tags the student on the second date, and Free's one rule opens module 2. That's enough for a cohort course in two parts, with nothing to pay. A weekly course needs more: each module after the second needs another rule, and Free has one.

The lines that move a cohort course to Startup:

• Two cohorts overlap. The release dates live inside the workflow, so cohort 2 needs a second workflow while cohort 1 is still running. Startup has five.
• More than one dated release. Each release after module 1 needs a rule. Free has one rule; Startup has 10.
• Your one workflow is already in use, for example a lead magnet sequence.
• The cohort passes 500 students, Free's cap on students.
• Sales approach $10,000. That's Free's lifetime sales cap (what happens at the line). One cohort of 50 at $200 is the whole allowance.

The cohort seller in r/elearning who wanted "a low cost, ideally just a monthly fee and not fees per student" is the buyer Startup suits. It's $17 a month, $170 if paid yearly, and nothing is charged per student. For a weekly cohort the trigger arrives before the first sale: a third module means a second rule. Later, the overlap adds another: the day you open sales for cohort 2 while cohort 1 still has releases to come, you need a second workflow. Upgrade to Startup before the first cart opens, not after a release fails to fire. Startup's contact limit is 5,000, and my guide to sizing a plan by students shows how to count cohorts and leads against it.

FAQ

Can students start the course before the start date? No. systeme.io says they get an access email when they pay, "but the course will only be unlocked on the specified date."

Can a cohort's access expire? With Full or Partial access, yes: the dated-access and course-selling articles offer an expiration delay in days. The access types article limits expiry to Full access, so the two articles disagree; test a Partial-access expiry before you promise one.

Can I give a free preview before the cohort starts? Yes, by giving Partial access to an opening module from an opt-in page, as in this walkthrough of a free preview. Keep the preview module outside the dated releases.

Does systeme.io drip content by calendar date? No. The drip counts days, and the access types article says per student. The documented way to open modules on set dates is a workflow with Exact date delays that tags each student, paired with a Tag added rule per release that widens their Partial access. That needs one rule per release date, which is why a weekly cohort outgrows Free's single rule. Test the first release with a second email address before the cohort starts.

Can I check when a student's lectures will unlock? For Drip content access, yes. Under Assets, Courses, Students, the student's menu has Show lectures access dates.

What time does a dated course open? At midnight in your account's time zone on the date you pick, per systeme.io's dated-access article.