Drop policies

A drop policy defines how long someone has to leave a program on their own, how long a refund stays available, and whether they may come back afterwards. Without a policy there are no restrictions at all.

Availability

Plan: Drop policies are not plan-gated and are not a module your organization turns on.

Permission: editing a policy needs the manage-drop-policies permission — the standalone editor under Scheduling simply sends you back to the Scheduling home page without it. Reading the Drop requests list needs the see-drop-requests permission, and the per-row Cancel button appears only with the cancel-drop-requests permission.

Don’t see this in your account? See Plans, permissions & modules.

What this does

A drop policy attaches to one enrollable thing — a program or one of its offerings. It does not apply to individual modules; someone drops a program, not a lesson.

The policy has two jobs. It sets the deadlines after which a person can no longer take themselves out (only an admin can), and it sets the refund and re-enrollment rules that apply when they do leave.

Turning the policy off deletes it. With no policy, a drop is unrestricted and there is no refund window.

A “program” may be renamed in your organization; see Terminology.

Before you start

• You can manage drop policies in your organization.
• Decide two numbers up front: how many days someone has to leave on their own, and how many days a refund stays available. Setting the refund window longer than the drop deadline produces a warning, because people would still be refund-eligible after they can no longer drop themselves.

Set a drop policy

1. Open Programs, open the program, and choose Drop policy under Scheduling in the left rail. This is the path to use — it loads the policy already saved on the program.
2. Turn the Drop policy switch on. The rest of the form appears.
3. Under Deadlines, set the Self-drop deadline — choose None (always allowed), Day-offset (a number of days after enrollment), or Specific date.
4. Optionally set Admin-only after (optional) — a date past which only an admin can process a drop.
5. Under Refund & re-enrollment, set the Refund window in days after enrollment, and switch Allow re-enrollment and Preserve progress on re-enrollment on or off.
6. Check the Drop timeline preview above the two cards. It draws Day 0, the end of the refund window, the end of self-drop, and the admin-only tail, so you can read the policy the way a learner experiences it.
7. Choose Save policy.

Amber warnings appear inline when the numbers contradict each other: one when the refund window outlasts a day-offset self-drop deadline, and one when an Admin-only after date falls before a specific-date deadline.

Caution

There is a second route — Scheduling → Edit drop policy, then pick a program. That editor opens on Lurno’s defaults rather than on the policy you already saved, and saving overwrites the existing policy with whatever is on screen. Use the program’s own Scheduling → Drop policy to change a policy you have already set up.

Watch drop requests

Scheduling → Drop requests lists every withdrawal in the organization, newest first. Filter by All, pending, processing, executed, cancelled or rejected; each filter carries a count.

• View history opens a drawer with the request’s full status timeline.
• Cancel appears on pending rows and stops the request before its effective date.

Rows currently identify the learner and the item by a shortened identifier rather than by name, so use View history to confirm you have the right request before cancelling.

What the policy actually enforces

The deadlines apply to a person dropping themselves. Once the self-drop deadline or the admin-only date has passed, their own request is refused; an admin acting on their behalf is not blocked.

Whether a learner sees a “leave” control on a program at all is decided by a flag on their individual enrollment, set when the enrollment is created — not by the drop policy. The drop policy only shapes what happens when a drop is allowed. See Transfers & removals.

Reference

Option	What it controls
Drop policy (on/off)	Off means no restrictions and no refund window; turning it off removes the policy
Self-drop deadline	None, a day-offset from enrollment, or a specific date
Admin-only after	Date past which only an admin can process a drop
Refund window	Days after enrollment that a refund remains available
Allow re-enrollment	Whether someone may enroll again after dropping
Preserve progress on re-enrollment	Whether previously-completed items are restored if they return

Troubleshooting

A learner couldn’t drop themselves. The self-drop deadline or the admin-only date had passed. Check both on the Deadlines card, or process the drop as an admin.

A learner has no way to leave at all. That’s the per-enrollment self-withdrawal flag, not the drop policy. Turning a policy on doesn’t give anyone a leave button.

The refund warning won’t go away. The refund window is longer than the self-drop deadline. Either shorten the refund window or lengthen the deadline — the warning is telling you people will be refund-eligible at a point when they can no longer act for themselves.

Turning the policy off lost my settings. The switch deletes the policy rather than parking it. Turn it back on and re-enter the values.

My policy reverted to 14 days and 7 days. Someone opened it from Scheduling → Edit drop policy and saved. That editor starts from the defaults. Re-enter the values from the program’s own Drop policy view.

There’s no Drop policy option on a module. Correct — drop policies attach to programs and offerings only.

A dropped person still occupies a place. The drop policy has no seat-handling setting. Capacity is managed in Enrollment; see Enrollment overview.

Save fails with a permission error. Editing the policy needs the manage-drop-policies permission. See Roles & permissions.

Related

• Schedules & release windows
• Drip content
• Prerequisites
• Transfers & removals
• Enrollment overview