Ensure timely, accessible learner participation by adding a due date to the first post in a discussion topic. This improves consistency across the learning management system (LMS) and aligns with institutional policies.
What changed in 20.25.12 (December 2025)
- The Discussion due date on first post option is enabled by default. No org-level configuration is required.
- Due dates you previously set on Classic content topics using Edit Properties in Place are now surfaced consistently across Brightspace tools.
- Discussions availability is unchanged. The feature respects existing start and end dates and availability types (for example, Hidden, Visible with access restricted).
Where the due date appears for learners and instructors
The Discussions due date appears in the following:
- Calendar (if enabled)
- Discussions list page
- Manage Dates tool
- New Content Experience (shows Overdue and Late indicators)
- Quick Eval and Consistent Evaluation
- Work To Do widget (for Classic content items with due dates)
|
Tip: Ensure the Calendar tool is enabled in your org to surface due dates broadly. |
Notifications
Learners can receive a default notification: Discussion due date or end date is 2 days away. This is configurable in web and mobile apps.
|
Tip: Encourage learners to enable mobile push notifications to increase on-time participation |
Reporting and data
A new Due Date field appears in the DiscussionTopics Brightspace Data Set (BDS). This supports tracking participation deadlines and reporting on policy compliance.
Admin preparation checklist
To prepare your org and instructors
- To inform instructors, add a note about the new first post due date option in your release communications and training.
- To update training materials, list where the due date appears (Calendar, Manage Dates, Discussions, Quick Eval, Consistent Evaluation, Work To Do).
- To update analytics, modify dashboards and queries to include the Due Date field in the DiscussionTopics BDS.
- To validate notifications, review Notifications settings and advise learners to enable the relevant alerts.
Permissions and availability behavior
- The feature respects existing start and end dates and availability types. No changes are required to your availability model.
- Instructors choose whether to set a due date per discussion topic.
- The feature is not configurable at the org level (cannot be disabled globally).
|
Important: Changing start or end dates can restrict access. Ensure availability windows align with due dates to avoid confusing learners.
|
Classic content due dates: what you need to know
If you previously set due dates on Classic content topics using Edit Properties in Place, those dates now appear in:
- Calendar
- Work To Do widget
- Manage Dates
- Other relevant Brightspace tools that surface activity due dates
|
Tip: You do not need to re-enter these due dates. They are automatically propagated and treated as first-class due dates across Brightspace. |
Frequently asked questions
Who benefits from this feature?
You and your instructors benefit from more predictable participation and improved assessment workflows.
Does this change how discussion availability works?
No. Availability (start/end dates, visibility) continues to function as before.
Can we disable this feature?
No. It is part of the core platform update and cannot be disabled at the org level.
Will learners be notified?
Yes. A default notification exists and can be managed by learners.