1. Skill Development Platform
  2. Features
  3. Cohort scheduling
Feature · Cohort scheduling

Cohort scheduling

Move accepted cohort work into its planned delivery period while keeping attendance and achievement distinct.

OverviewAssessment Evidence Review
Skill Development Platform · Cohort scheduling

Assessment Evidence Review

Learning evidence

New
ParentLine numberLearner referenceScoreOccurred atRevision
LR-91709820LR-7059014 Oct250
LR-60325740LR-6847012 Oct70
LR-77196730LR-4307510 Oct400
LR-96415890LR-3124526 Oct760
LR-2486430LR-2567508 Oct460
6 of 6 records
LR-705Learning evidence · LE-81250
Pending
ParentLR-91709
Line number820
Score90
Occurred at14 Oct
Revision250
Example screen with sample data

What you can do

Put the accepted request on the delivery calendar

Learning Coordinator uses the request’s start and end dates to organize the delivery period. Once the program request is Accepted, the guarded scheduling action moves it to Scheduled and records attendance activity. The operation receipt lets the team inspect the saved scheduling outcome and identify the request revision used for the action.

Scheduling establishes the cohort’s operating plan. Assessment evidence and credential decisions follow their own checks. Keep that distinction clear when discussing progress with the delivery team: a scheduled cohort can be ready for instruction while the assessor still needs to record and verify the evidence required for learning completion.

How the work is organized

  • Planned dates. Start and end dates sit on the request beside its program, learner count and owner. The coordinator can compare accepted and scheduled work before confirming the next delivery action.
  • Guarded scheduling. The action checks organization, current revision and Accepted state. Its recorded result moves the request to Scheduled and creates an attendance evidence line for that request.
  • Delivery follow-up. The coordinator follows the scheduled work with the assessor and keeps supporting files available. Assessment scores and verification states are examined separately before the completion command is requested.

What to agree during setup

Decide what the planned start and end dates represent for the cohort. Use the provider’s time zone consistently and agree who maintains the dates if delivery changes. Name the person who checks that the accepted scope is still correct before requesting scheduling.

Agree the operating meaning of the attendance line created by the scheduling action. Staff should know what additional attendance or assessment evidence the delivery procedure requires, and who records it. Establish the handoff to the Assessor so a scheduled request does not sit without an owner for the next evidence task. Keep any classroom, content or conferencing connection aligned with the planned dates.

Check the handoff on an actual case

Use an accepted rehearsal request with a start date and an end date the team recognizes. Have Learning Coordinator request scheduling against its current revision. Inspect the Scheduled state, the attendance evidence line and the completed operation receipt. Ask the Assessor to identify what evidence still needs to be recorded for the learning outcome.

Repeat the scheduling request with the same operation identity and inspect how the saved outcome is reused. Check that another attendance line is not created for the same scheduling effect. Then attempt scheduling from an ineligible request state or an old revision and confirm rejection. Verify that scheduling has created no score, verified assessment or credential before the team proceeds to assessment work.

What your team sees

  • Cohort Schedule — Accepted and scheduled requests with their start and end dates, program and owner.
  • My Learning Requests — Assigned delivery work needing the coordinator’s next action.
  • Assessment Evidence Review — Assessment entries awaiting the verification procedure after delivery activity.

Follow the work through

Follow schedule and assessment, then use verify learning completion when the evidence is ready.

What it keeps track of

Data model
Learning requests
Enrollment and delivery requests for a program cohort, tracked from request through completion.
Learning evidence
Individual pieces of attendance, assessment, credential or payment evidence recorded against a learning request.
Operation receipts
Durable receipts for every guarded operation executed against a learning request.
Programs
Skill programs offered by an organization, with eligibility and delivery contact details.

Who uses it

Permissions
Learning Coordinator
Requests scheduling and follows delivery activity.
Assessor
Records the outcome evidence.
Program Administrator
Checks exceptions affecting accepted scope.
Auditor
Examines the scheduling receipt alongside later evidence.

Set up Skill Development Platform your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started