Build an orientation roster and issue a traceable revision Skill Workbench · 2026-10-23 · Original fictional teaching material Classify administrative records, fill sessions under a fixed capacity rule and revise invitations when a missing date is confirmed. For an administrative or training coordinator. All staff IDs are anonymous fiction; this course does not make employment eligibility decisions. - Keep incomplete records separate from future starts and completed actions. - Fill sessions using an explicit cutoff, sorting rule and capacity. - Identify moved and waitlisted records after a correction and communicate the revision. CASE CONTRACT 1. Schedule active staff who have not completed orientation and whose recorded start date is on or before 2026-10-23. 2. A missing start date requires clarification. Do not treat it as an old date, a future date or an invitation. 3. Sort the staff to schedule by start date, earliest first, then staff ID. Fill the morning session first, then the afternoon session, respecting the stated capacities. 4. Active staff starting later go on the future-start list. Staff already complete or marked inactive are not scheduled in this run. Dates are ISO calendar dates in the same local calendar. 5. The administrative cutoff and session rules are fixed fictional policy. No employment selection, legal requirement or private staff data is evaluated. 6. Unit 3 is a new planning version: H6’s date is confirmed as 2026-10-20; all other records and two session capacities remain unchanged. Review and notify affected invitations rather than silently replacing a sent list. 1. Separate ready records from administrative follow-ups Give every source record a visible disposition. A scheduling list begins with a defined run date and an administrative rule. For this course the cutoff includes 23 October 2026. Active staff who have not completed orientation and have started by that date can be scheduled. A future start is a different state from a missing date, even though neither goes straight into this run. Evaluate status and completion before treating a date as a scheduling signal. An inactive record is not invited in this run, and an already-complete record needs no new session. Keep those dispositions visible so a reviewer can reconcile why some input records do not appear on the invitation list. A blank date does not mean an old date or a future date. It is a clarification item with an owner and next step. Guessing can displace another person from a limited session. The course’s list is administrative planning, not a decision about someone’s employment or right to training. Count all dispositions once. Ready, future, clarification, complete and inactive should cover the source records without overlap. This gives the handoff a simple integrity check before capacities and invitation times are introduced. Worked example: distinguish blank from future An active incomplete record dated 26 October belongs on the future-start list for a 23 October run. An otherwise identical record with no date belongs on clarification. They need different next actions, so one generic excluded list loses useful information. Use cutoff 2026-10-23 and the supplied administrative rule. No session allocation is required yet. Small administrative roster staff_id | status | start_date | orientation_complete W1 | active | 2026-10-20 | no W2 | active | 2026-10-26 | no W3 | active | | no W4 | inactive | 2026-10-19 | no W5 | active | 2026-10-21 | yes YOUR EXERCISE Staff IDs ready to schedule: __________________ Staff IDs needing date clarification: __________________ Future-start staff IDs: __________________ Records outside the ready-to-schedule list: __________________ Your explanation: Write a reconciliation and a concrete follow-up for W3 without treating the missing date as a completed action. FEEDBACK AND WORKED SOLUTION Ready W1; future W2; clarify W3; inactive W4; complete W5. One ready plus four other dispositions covers all five records. Staff IDs ready to schedule → W1. W1 is active, incomplete and started before the cutoff. Staff IDs needing date clarification → W3. No start date is recorded for W3. Future-start staff IDs → W2. W2 starts after the cutoff. Records outside the ready-to-schedule list → 4. W2 future, W3 clarification, W4 inactive and W5 complete are four different records. TRANSFER QUESTION Which disposition would change if the missing date were verified as 2026-10-22? 2. Fill sessions and reconcile the full roster Apply date order and capacity without dropping unresolved records. The next roster is separate from the warm-up. First classify it using the same cutoff rule, then sort only the ready records by start date and staff ID. Filling the morning session first is an explicit policy here; it is not a universal training practice. Keep the full sorted queue so the assignments can be reproduced. Capacity is counted in people, and a staff member appears in only one session. Fill the morning places, then afternoon places. If ready records exceed capacity, keep the remainder on a visible waitlist rather than silently omitting them. This baseline happens to fit four ready records into four places. Clarification and future-start lists remain outside the allocated sessions. They still need a disposition in the roster review. A count of invitations alone cannot show that all source records were checked, so reconcile scheduled plus the other administrative states back to the input count. The workbook produces a planning roster, not proof that invitations were sent or that orientation was completed. Those are subsequent actions with their own evidence. Your note should identify who resolves the missing date and keep that request open until confirmation arrives. Worked example: preserve a capacity boundary Five ready people and two sessions of two seats yield four assignments and one waitlist entry. Do not count the fifth person as trained or remove the record. The session capacity constrains assignment, not whether the source row exists. You are arranging two orientation sessions for a fictional internal team on 23 October 2026. The anonymous roster includes completed orientations, a future start and one missing date. Produce the two session lists and a separate follow-up list. This is an administrative scheduling exercise using the stated rules, not an employment or eligibility decision. Anonymous orientation records staff_id | status | start_date | orientation_complete H1 | active | 2026-10-19 | no H2 | active | 2026-10-20 | yes H3 | active | 2026-10-23 | no H4 | active | 2026-10-26 | no H5 | inactive | 2026-10-20 | no H6 | active | | no H7 | active | 2026-10-22 | no H8 | active | 2026-10-21 | no Sessions on 2026-10-23 session | capacity morning | 2 afternoon | 2 YOUR EXERCISE Morning session staff IDs: __________________ Afternoon session staff IDs: __________________ Staff IDs requiring date clarification: __________________ Future-start staff IDs: __________________ Total scheduled staff: __________________ Your explanation: Write the scheduling handoff, including who must clarify H6’s date and how you will avoid treating the unresolved record as a completed action. Your note is not automatically graded. FEEDBACK AND WORKED SOLUTION Morning: H1 and H8. Afternoon: H7 and H3. Clarification: H6. Future start: H4. H2 is already complete; H5 is inactive. The roster reconciliation is 4 scheduled + 1 clarification + 1 future + 1 complete + 1 inactive = 8 records, so every source record has a disposition. Morning session staff IDs → H1, H8. Eligible staff in start-date order are H1, H8, H7, H3. The first two fill the morning session. Afternoon session staff IDs → H7, H3. H7 and H3 fill the two afternoon places. The cutoff includes 23 October itself. Staff IDs requiring date clarification → H6. H6 has no recorded start date. Keep a separate follow-up item instead of silently dropping or scheduling this record. Future-start staff IDs → H4. H4 starts on 26 October, after this run’s cutoff. H2 is already complete and H5 inactive; neither belongs on the future-start list. Total scheduled staff → 4. Four eligible incomplete records fill the four available places; H2, H4, H5 and H6 are not scheduled in this run. TRANSFER QUESTION Which list would show a fifth ready record when both two-seat sessions were already full? 3. Revise the invitation plan when a date is confirmed Identify who moves and preserve a clear replacement notice. The missing H6 date is now verified as 20 October 2026. Treat this as a new planning version and rerun the ready queue. Inserting the confirmed record into its correct date position can move existing assignments; simply appending it to the afternoon ignores the stated ordering rule. Compare the revised morning, afternoon and waitlist against the baseline. A person can remain scheduled while changing session, and another can move from scheduled to waitlisted. These are separate effects that a revision notice should name explicitly so recipients do not act on inconsistent lists. Do not silently overwrite invitations that might already have been sent. Identify the superseded version, obtain the coordinator’s approval of the revised plan and notify affected recipients. This course records the planned changes only; it provides no evidence that notifications or attendance occurred. Reconcile the new ready count against capacity: five ready records, four seats and one waitlist entry. H6 leaves the clarification list because the source date is now known. The future, complete and inactive dispositions otherwise stay the same. Worked example: a correction can move existing assignments A two-seat session holds people starting on the 19th and 21st. A newly confirmed person started on the 20th. Date ordering moves the 21st-start person to the next available session; keeping the old list and adding a third seat would violate the capacity. H6’s verified start date is now 2026-10-20. Use all other baseline records unchanged. Morning capacity=2 and afternoon capacity=2; put remaining ready staff on a waitlist. Verified change for the revised roster staff_id | old_start_date | verified_start_date | source_reference H6 | | 2026-10-20 | CONF-H6 YOUR EXERCISE Revised morning staff IDs: __________________ Revised afternoon staff IDs: __________________ Revised waitlist staff IDs: __________________ Revised number assigned to sessions: __________________ How should this change be issued?: __________________ silent: Replace the old file without identifying moved or waitlisted staff. version-notify: Issue a revised plan identifying H6, H8 and H3 changes, and confirm affected notifications. complete: Mark the newly scheduled people as orientation complete. Your explanation: Write the revision note with H6’s source, H8’s session move, H3’s waitlist change and notification confirmation needed. FEEDBACK AND WORKED SOLUTION Ready order H1,H6,H8,H7,H3. Morning H1/H6; afternoon H8/H7; waitlist H3. H6 is no longer a clarification. Identify the superseded roster and confirm notifications to affected people; no attendance is inferred. Revised morning staff IDs → H1, H6. Ready queue H1,H6,H8,H7,H3; the first two fill morning. Revised afternoon staff IDs → H8, H7. The next two fill afternoon. H8 moves from the old morning session. Revised waitlist staff IDs → H3. H3 is fifth in the ready queue and no seat remains. Revised number assigned to sessions → 4. Capacity remains four; the verified date does not create a fifth seat. How should this change be issued? → Issue a revised plan identifying H6, H8 and H3 changes, and confirm affected notifications.. A planning change needs a versioned handoff; scheduling is not attendance or completion. TRANSFER QUESTION If invitations have already been sent, what confirmation would you require before treating the revised list as the one recipients will follow? PORTFOLIO REVIEW Keep all three exercise records and explanations. Fixed checks can be scored; explanations are ungraded. Do not infer occupational certification. SOURCE O*NET 13-1071.00 task 18870 · 08/2019 · Schedule or conduct new employee orientations. O*NET 13-1071.00 task 18866 · 08/2019 · Prepare or maintain employment records related to events, such as hiring, termination, leaves, transfers, or promotions, using human resources management system software. https://www.onetonline.org/link/summary/13-1071.00 O*NET 31.0, USDOL/ETA, CC BY 4.0. Skill Workbench authored the teaching and fictional practice; no endorsement.