Self-Scheduling and Flexible Workforce Administration (generic process)

From WFM Labs

Self-Scheduling and Flexible Workforce Administration (generic process) is the generic process card, GP-204, for the process by which a workforce function administers the parts of its schedule that people choose rather than receive: who is eligible to self-schedule, claim open shifts, swap or join a flex pool; the rule set those choices are validated against; the catalogue of claimable shifts and the tiered windows in which it is claimed; the open-shift pool between windows; the gap-fill ladder when choice leaves coverage short; and the periodic fairness review that decides whether the model is working. The card owns the process at L1 and L2. It does not own the mechanisms or the evidence: the self-service mechanisms, the guardrails and the research on autonomy and well-being are on Autonomy and Schedule Self-Service, and the spectrum of flexible workforce models, the matching-market framing and the activation logic are on Self-Scheduling and Flexible Workforce Models. It is part of Process Standardization and sits under the scheduling section of the function catalog in Anatomy of a ROC Standard.

The process matters because the method pages are explicit that the value of self-scheduling comes from the rule set and the gap-fill logic, not from the portal, and that a self-scheduling model with no fairness design reproduces the seniority sort it was meant to replace. A rule set is a process artifact: it has an owner, a change control and a review, and this card is where those are held. One documented hospital attempt at self-scheduling failed on exactly this point, through unclear rules and an unadministered fairness question rather than through the idea itself.[1] The market the process administers is a two-sided matching market, and the literature on such markets is clear that the rule design determines the outcome.[2]

Process profile

The profile extends the L0 identity fields of Process Decomposition (L0–L3) with the facts a standards committee needs before any step is drawn. Local values are held by the deploying function and marked SET LOCALLY.

Field Generic value
Card GP-204 · local card id assigned by the standards committee at deployment
Class both, in the catalog's four-class vocabulary (strategic · real-time · both · supporting): the eligibility and rule-set work is planned; the open-shift pool and flex activation run close to the day
Trigger the period's requirement and the fixed-roster build from GP-201, which leave the claimable residual; a rule-set change request; the fairness-review calendar
Cadence windows per scheduling period (weekly is typical at Level 3 [A]); the pool continuous; the eligibility register on each roster change; the fairness review quarterly (SET LOCALLY)
Scope in the eligibility register; the rule set; the claimable catalogue; the tiered windows; validation of picks, swaps and releases; the open-shift pool; the gap-fill ladder up to flex-pool activation; the fairness review; revealed-preference capture
Scope out the fixed-roster build (GP-201); the maintenance of claimed shifts once committed (GP-202); same-day levers (GP-302); the contract forms themselves (the HR partner); the evidence on well-being (Autonomy and Schedule Self-Service)
Inputs the requirement less the fixed roster; the roster with contract type and standing; the rule set; the premium structure; the flex-pool register and its triggers; last review's fairness metrics
Outputs the eligibility register; the published rule set with its version; the claimable catalogue; validated commitments written to the schedule of record; the pool state and ageing; the gap-fill record; the fairness report; the revealed-preference file
Upstream GP-201; GP-103 for the variance signal that triggers activation; the HR partner for contract terms; Shift Design for the catalogue
Downstream GP-202 and GP-303, which read commitments as schedule of record; GP-302 at the ladder's last rung; GP-601 for rule-set changes; GP-602 for the preference file
Resources a self-service portal with rule validation; the rule register; the catalogue; the flex-pool register; the fairness metrics. Platforms are named at L3, never here
Decision points is a person eligible; does a rule change touch a statutory or contractual term; does a pick pass the rule set; does coverage meet the floor after the windows; which rung of the ladder; does the review show a structural hole or an equity breach
Authority tier pick validation and the pool at tier 1 (the scheduler seat inside guardrails); an eligibility change on an individual and the assignment rung of the ladder at tier 2; flex-pool activation and a premium above the cap at tier 3; the rule set and the fairness design at tier 4
Risk and compliance flags a claimed shift is a published schedule where notice-period statutes apply; access-to-hours rules that put existing part-time staff ahead of new hires or external pools; guaranteed-hours obligations that accrue from flexible contracts over a reference period; co-determination over the distribution of working time; swap restrictions in collective agreements; premium races the method page warns of
Variant-prone steps the eligibility criteria; the ladder's rung order; the premium cap; the pick-window tiers; a consultation step before a rule-set change; the reference-period review for flexible contracts
Automation candidates thirteen L2 sub-steps in seven groups (listed below)

L1 flow

Decision steps are questions. Owners are seats.

  1. Confirm the model scope for the period: which units run self-scheduling, which hold a flex pool, which stay on a fixed roster — scheduling lead.
  2. Maintain the eligibility register on each roster change, by the criteria in force — team lead maintains, scheduling lead owns.
  3. Maintain the rule set: minimum picks, weekend minimum, rest and hours, change buffer, commitment rule, skill floors, premium structure — scheduling lead, with the compliance lead.
  4. Does a proposed rule change touch a statutory or collective-agreement term? If so, route it through GP-603 before GP-601 — compliance lead.
  5. Build the claimable catalogue from the requirement less the fixed roster — scheduler.
  6. Open the pick windows in tiers and close each on the calendar — scheduler.
  7. Validate every pick, swap and release against the rule set and accept or reject with reason — scheduler, inside guardrails.
  8. After the windows close, does coverage by interval and skill meet the floor? If not, run the ladder: pool, capped premium, flex activation, assignment by fairness rule, overtime through GP-202 — scheduling lead.
  9. Administer the open-shift pool between windows: post, claim, release, and age the unclaimed — scheduler.
  10. Activate the flex pool on its triggers and notify in the register's order — real-time lead, approved at tier 3.
  11. Write every commitment to the schedule of record as a version — scheduler.
  12. Run the fairness review on the calendar: distribution of desirable and undesirable shifts by cohort, window outcomes, premium concentration, swap access, activation equity — scheduling lead.
  13. Does the review show a structural hole or an equity breach? If so, raise a catalogue or rule-set change — scheduling lead.
  14. Capture the revealed-preference file for the next catalogue and the reforecast — scheduler.

L2 step table

Thresholds, calendars and system names are L3 values marked SET LOCALLY. Durations are typical [A] unless marked.

Step Sub-step Owner (seat) Inputs Outputs Duration Automation candidate Documentation join key
1 Confirm the model per unit from the plan of record scheduling lead plan of record; model register period scope half a business day N 204-01a
2 Apply the criteria to each roster change team lead roster change; criteria register update minutes per change Y (the test; not the criteria) 204-02a
2 Decide a contested eligibility case team lead case decision with reason SET LOCALLY N 204-02b
3 Hold the rule set as a versioned register scheduling lead rule register current version continuous N 204-03a
4 Screen a rule change for statutory or contractual touch compliance lead change request routing decision one business day N 204-04a
5 Subtract the fixed roster from the requirement by interval and skill scheduler requirement; fixed roster residual minutes Y 204-05a
5 Cut the residual into claimable shifts from the catalogue scheduler residual; catalogue claimable catalogue half a business day Y 204-05b
6 Open each tier, notify, close scheduler catalogue; eligibility register picks SET LOCALLY Y 204-06a
7 Validate a pick, swap or release against the rule set scheduler request; rule set accept or reject with reason seconds Y 204-07a
7 Review rejections for rule errors scheduler rejection log corrections; rule defects daily N 204-07b
8 Compute coverage against the floor after close scheduling lead commitments; requirement gap by interval and skill minutes Y 204-08a
8 Issue the capped premium offer as a rung of the ladder scheduling lead gap; premium structure offer record SET LOCALLY Y 204-08b
8 Decide the move to the next rung and record it scheduling lead gap after the offer; ladder order gap-fill record SET LOCALLY N 204-08c
9 Post, claim and release in the pool scheduler pool; eligibility register pool state continuous Y 204-09a
9 Age the unclaimed and alert at the band scheduler pool state ageing alert continuous Y 204-09b
10 Test the activation triggers real-time lead reforecast; variance band activation proposal minutes Y (the proposal) 204-10a
10 Approve activation and notify in order operations manager; real-time lead proposal; flex register activation record SET LOCALLY N 204-10b
11 Write commitments as a version scheduler accepted commitments schedule of record minutes Y 204-11a
12 Assemble the fairness report by cohort scheduling lead commitments; history; cohorts report one business day Y 204-12a
13 Decide hole or breach; raise the change scheduling lead report change request SET LOCALLY N 204-13a
14 Capture picks, order, unclaimed and clearing premium scheduler window and pool logs preference file minutes Y 204-14a

Variants

The known variant classes for this process, recorded per Standard and Variant in Process Documentation:

  • Statutory. Where a predictive-scheduling statute applies, a claimed shift is a published schedule and the notice period and change premium are parameters of step 11, SET LOCALLY.[3] An access-to-hours rule that offers additional hours to existing part-time staff before new hires or an external pool fixes the ladder's rung order; a parameter of step 8. A jurisdiction that obliges an employer to offer guaranteed hours when a flexible contract's worked hours exceed its contracted hours over a reference period adds a reference-period review step after step 14; the HR partner owns it, the function head approves the variant, and it takes a row.[4] Co-determination over the distribution of working time inserts a consultation step before any rule-set change in step 3; a row, as on GP-201.
  • Contractual. Collective-agreement swap restrictions parameterize step 7. An agreement that prohibits an open-shift marketplace outright sets the automation effect of the unit's row to blocks against candidates 3 and 5 below, and against candidate 4 where the windows are marketplace windows. A client contract that requires named dedicated staff makes them ineligible; a parameter of step 2.
  • Structural. A unit without a portal runs windows by hand; steps 6, 7 and 9 are varied with a review date. A partner node that runs its own flex pool supplies capacity under a contractual floor and does not enter the ladder; a row, reviewed at renewal.
  • Transitional. A unit from a predecessor organization on legacy flexible-contract terms keeps its premium structure under a row with an expiry at renegotiation.

L3 register

A localizing team writes these job aids against the generic L2; names only, the content is the function's.

Job aid Anchored to Form
The eligibility criteria and the contested-case procedure step 2 work instruction
The rule register layout, its version and its change path steps 3 and 4 work instruction; governance on GP-601
The residual computation and the catalogue cut step 5 work instruction; catalogue on Shift Design
The window calendar and the tier design step 6 playbook; mechanisms on Autonomy and Schedule Self-Service
The validation rules as test cases, with the expected reason per rejection step 7 work instruction
The gap-fill ladder: rung order, premium cap, activation triggers, assignment rule steps 8 and 10 playbook; models on Self-Scheduling and Flexible Workforce Models
The pool procedure and the ageing band step 9 work instruction
The fairness review template, cohorts and bands step 12 playbook
The response when a shift never clears or a breach is found step 13 runbook

Automation candidates

Flagged at L2 per the method on Process Decomposition (L0–L3); released per class of action on a published catch rate per Human Gates and Number Grades, never on a maturity label.

  1. Pick validation (204-07a) and the eligibility test (204-02a): a rule set and a criteria set evaluated per request; the first candidate because each rule is a test case and every rejection overturned on review is a countable error.
  2. The residual, the catalogue cut and the post-close coverage computation (204-05a, 05b, 08a): arithmetic on the requirement, the fixed roster and the commitments. They rank after validation because the requirement carries its own grade, so the catch rate is published net of forecast error rather than against a fixed rule.
  3. The pool (204-09a) and its ageing alert (204-09b): post, claim, release, age. They rank after the arithmetic because a pool error (a shift posted to the wrong eligibility class, an alert at the wrong band) surfaces through claims and complaints rather than through a check, which makes the catch rate slower to establish.
  4. The window procedure (204-06a) and the commitment write (204-11a): mechanical once designed. They rank after the pool because their errors are visible outside the function where a claimed shift is a published schedule, so the catch rate is published from a longer observation window before release.
  5. A premium offer within the cap, as a rung of the ladder (204-08b): the offer is issued; the decision to move to the next rung (204-08c) is not. It ranks after the mechanical steps because an offer in the wrong order or above the cap is a cost and, in a unionized unit, a grievance, both counted outside the function and later.
  6. The activation proposal (204-10a): computed from the reforecast against the variance band; the activation is approved at tier 3. It ranks after the offer because a mistimed proposal is only known to be wrong once the day has run, so each observation costs a day.
  7. The fairness report (204-12a) and the preference file (204-14a): assembled, not decided. They rank last because their errors are errors of cohort definition, caught only when the review reads them, one review per quarter.

The eligibility decision on an individual (204-02b) is never a candidate: it reads a person's standing. The assignment rung of the ladder is never a candidate: it mandates a person to a shift they did not choose and, in a unionized unit, follows a procedure the agreement fixes. The rule set itself (204-03a) is never a candidate, because it is the standard, and a standard that rewrites itself cannot be certified; the literature on hourly-work flexibility makes the same point from the other side, that flexibility without administered rules becomes instability for the person receiving it.[5]

Maturity Model Position

Four scales on this wiki use the word level; the launch page states which is which. On the WFM Labs Maturity Model™ a function whose self-service is limited to time-off requests and a periodic bid has not yet entered this process and is at Level 2; one that runs weekly windows in tiers against a versioned rule set, with a documented flex pool and a published fairness review, is at Level 3; one whose validation, pool, catalogue and activation proposal are released on published catch rates, and whose ladder runs against the reforecast's variance band, is at Level 4, the integrated practice Self-Scheduling and Flexible Workforce Models describes.

See Also

References

  1. ↑ Bailyn, L., Collins, R., & Song, Y. (2007). "Self-scheduling for hospital nurses: an attempt and its difficulties". Journal of Nursing Management 15(1), 72–77.
  2. ↑ Roth, A. E., & Sotomayor, M. A. O. (1990). Two-Sided Matching: A Study in Game-Theoretic Modeling and Analysis. Cambridge University Press.
  3. ↑ Seattle Municipal Code, Chapter 14.22 (Secure Scheduling Ordinance): advance notice, predictability pay and access to hours for existing employees. seattle.gov.
  4. ↑ Directive (EU) 2019/1152 of the European Parliament and of the Council on transparent and predictable working conditions in the European Union, Articles 10 and 11 (minimum predictability of work; complementary measures for on-demand contracts). eur-lex.europa.eu.
  5. ↑ Lambert, S. J., Haley-Lock, A., & Henly, J. R. (2012). "Schedule flexibility in hourly jobs: unanticipated consequences and promising directions". Community, Work & Family 15(3), 293–315.