1. Skill Development Platform
  2. Features
  3. Programs and eligibility
Feature · Programs and eligibility

Programs and eligibility

Keep active skill offerings, entry requirements and delivery contacts clear before accepting a cohort request.

OverviewActive Programs
Skill Development Platform · Programs and eligibility

Active Programs

Programs

New
NameCodeContact nameAddressEligibility noteOrganization
Program 590CDE-492Contact 726C-2EN-778ORG-1137
Program 129CDE-718Contact 359M-7EN-431ORG-4678
Program 439CDE-492Contact 911H-1EN-588ORG-2406
Program 513CDE-358Contact 907T-13EN-991ORG-5759
Program 601CDE-367Contact 544P-3EN-211ORG-2577
6 of 6 records
Program 590Programs · PRG-28605
CodeCDE-492
Contact nameContact 726
AddressC-2
Eligibility noteEN-778
OrganizationORG-1137
Example screen with sample data

What you can do

Establish which program the request concerns

Program Administrator maintains the program name and code under the training provider organization. Contact details and an address identify the person and place associated with delivery. The eligibility note explains what the learning team should check when preparing a request for that offering. An active setting distinguishes the programs intended for current use.

Learning Coordinator selects the program when preparing the cohort request. This gives the acceptance decision a definite context: the team can inspect the same offering, eligibility note and delivery contact before agreeing to proceed. A recognizable program code also helps staff distinguish similarly named offerings when an organization runs several skill-development tracks.

How the work is organized

  • Offering identity. The program name and code identify the training being requested. Keep them consistent with the information used by the delivery team so the request does not depend on an informal title.
  • Entry requirements. The eligibility note gives the coordinator a place to start the acceptance discussion. Agree the evidence needed to confirm those requirements and retain relevant supporting files with the request.
  • Provider context. Each program belongs to an organization with its own active setting, time zone and currency. Team membership connects staff to the provider and their platform account for authorized work.

What to agree during setup

Choose the program coding convention and name who maintains the offering details. Decide how the eligibility note distinguishes an entry requirement from general advice. The Program Administrator should know who can answer an unclear requirement before a cohort request is accepted.

Confirm the delivery contact and address before the pilot. Agree how staff handle a program that becomes inactive while requests are still open. Acceptance checks the active program, so the coordinator should resolve the intended offering before requesting a decision. Establish the provider’s time zone and account membership so planned dates and access are interpreted consistently across the team.

Check the handoff on an actual case

For a rehearsal, use a familiar spreadsheet-skills program. Enter the program code, delivery contact and eligibility note, then ask the Learning Coordinator to prepare a cohort request against that offering. The Program Administrator should be able to identify the program and explain the entry checks from the saved record and supporting files.

Next, try an acceptance request with the program inactive and confirm that it is refused. Restore the intended operating state through the program owner and inspect the current request before another attempt. Test an account belonging to a different provider organization as well. Resolve any mistaken program reference or membership before ordinary delivery work begins, while preserving the earlier request and operation evidence.

What your team sees

  • Active Programs — Current offerings with program codes, eligibility notes and delivery contacts.
  • Open Learning Requests — Cohort requests that show which offering the learning team is preparing or delivering.

Follow the work through

Continue with program request acceptance and agree account responsibilities during implementation.

What it keeps track of

Data model
Programs
Skill programs offered by an organization, with eligibility and delivery contact details.
Organizations
Training provider organizations that own programs, learners and credentialing operations.
Team members
Staff members of an organization with their platform identity and operational role.
Users
Users
Learning requests
Enrollment and delivery requests for a program cohort, tracked from request through completion.
Record attachments
Files attached to a learning request as supporting evidence.

Who uses it

Permissions
Program Administrator
Maintains offerings and handles acceptance questions.
Learning Coordinator
Prepares requests against the intended program.
Admin
Maintains organization membership.
Auditor
Reads the provider context behind recorded decisions.

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