Learning requests

Learning Coordinator prepares a request with a recognizable number and subject, the selected program and learner count. A start date and optional end date describe the planned delivery period. The owner identifies the staff member responsible for answering questions and coordinating the next action as the request moves through its lifecycle.

The request links attendance and assessment evidence, credential cases and supporting files. That shared context lets the team follow a cohort without treating each document or review as unrelated work. Program Administrator examines the current request and program before acceptance, using the expected revision to ensure the decision applies to the scope being discussed.

• Cohort scope. The subject and learner count explain what the team is preparing. The selected program and organization establish which offering and provider own the work.
• Assigned coordination. The owner follows the request through Requested, Review, Accepted, Scheduled, Completed or Withdrawn states. Planned dates help the coordinator identify work that needs attention.
• Supporting context. Attachments retain relevant files with their uploader and visibility. A guardian-consent note can capture context that the team must review under its agreed eligibility procedure.

Choose a request numbering convention and decide how the subject identifies the cohort. Agree who maintains the learner count when scope changes and how the team recognizes a newer revision. Use a consistent convention for learner references in later evidence so the assessor can relate a result to the intended person within the request.

Define the acceptance checks for the pilot program. If consent information is relevant, agree who examines the supporting evidence and what the note should explain. Set the request owner deliberately and identify who handles a correction or withdrawal. Keep internal working material separate from files intentionally shared with other authorized users.

Prepare a rehearsal request for a digital-skills cohort with a known program and planned dates. Assign the Learning Coordinator, enter the intended learner count and attach the delivery instruction. Ask Program Administrator to explain the scope from the saved request and program before accepting it.

Then change the rehearsal scope and attempt an earlier acceptance request with an old revision. It should be refused, prompting the team to inspect the current record before trying again. Repeat a successful operation with the same identity and examine its saved receipt. Finally, ask another coordinator to locate the request and explain who owns the next action without relying on the preparer’s memory.

• Open Learning Requests — Requests in preparation, review, acceptance or scheduling with their program and planned dates.
• My Learning Requests — Assigned cohort work for the person responsible for coordinating it.
• Learning Request Board — The current lifecycle state of each request without mixing it with individual evidence outcomes.

Use program request acceptance, then move into schedule and assessment.