Cross-Training and Skill-Mix Review (generic process)

Cross-Training and Skill-Mix Review (generic process) is the generic process card, GP-505, for the periodic review by which a workforce function checks that its skill mix can survive the events its continuity partner plans for. The method (the designed skill graph, the pooling-benefit arithmetic, the investment decision, the currency policy) is on Cross-Training and Skill Mix Strategy and is not restated here. What this card adds is the review that keeps the strategy honest between annual decisions: the refresh of the skill-coverage matrix from the capability record, the resilience test that asks which event classes the current mix survives and names the binding skill where it does not, the hand-off of the resulting gaps to the training plan, and the cadence. Business continuity is a partner function; the review is the workforce function's standing contribution to preparedness, and its output feeds the configuration archive of Placement Under Duress (generic process), since a configuration that assumes a skill at a node is only as good as the matrix behind it. The card is part of Process Standardization and sits under the continuity-interface section of the function catalog in Anatomy of a ROC Standard.

The resilience test rests on a result established for manufacturing flexibility and confirmed for service pools: a modest, deliberately connected cross-training pattern captures most of the benefit of full flexibility, and its value lies in which links exist, not how many. The review's job is to check that the links the strategy designed still exist on the floor.

Process profile

The profile extends the L0 identity fields of Process Decomposition (L0–L3). Local values are held by the deploying function and marked SET LOCALLY.

Field	Generic value
Card	GP-505 · local card id assigned by the standards committee at deployment
Class	strategic
Trigger	the review calendar; a post-event review (GP-501 step 14) that finds a coverage gap; an archive refresh (GP-502 step 14) that retires a configuration for want of a skill
Cadence	the matrix refresh and resilience test quarterly (SET LOCALLY; quarterly is typical [A], and matches the quarterly graph audit the method page calls minimum hygiene); the full review annually, feeding Annual Strategic Workforce Planning Cycle (generic process)
Scope in	the capability-record refresh and reconciliation; the matrix roll-forward; the resilience test per event class; the gap ranking; currency enforcement; the training hand-off; the archive request; the sign-off
Scope out	the investment decision and its valuation (the method page); training delivery (the training function); multi-skill scheduling; the placement decision a gap may call for
Inputs	the capability record (skills, languages, proficiency, currency dates); the roster and the attrition forecast of Supply and Attrition Forecasting (generic process); demand by skill; the scenario catalog's event classes; the configuration archive; post-event findings
Outputs	the refreshed skill-coverage matrix (skill by node by proficiency by currency); the resilience report (pass, fail with the binding skill named, or cannot-run per event class); the ranked gap list; the training hand-off; the archive change request; the stale-edge list, an edge being a link in the skill graph between an agent and a skill
Upstream	the capability record's steward; GP-105; the scenario catalog; GP-501 and GP-502
Downstream	the training lead; GP-502 (the archive); GP-101 (the annual strategy); scheduling (Multi-Skill Scheduling)
Resources	the capability record as a queryable object; the roster; a coverage model that can remove a node or a share of supply and re-route; the training calendar. Platforms are named at L3, never here
Decision points	is the record current enough to run; does any critical skill or language fall below floor under any event class; training, or placement and archive change; sign
Authority tier	the refresh and the test at tier 1, the analyst seat inside guardrails; the training-or-placement routing at tier 3, the operations manager or ROC duty lead (the placement lead sits at that tier); the hand-off and the archive request at tier 4, the function head; a hand-off that changes a partner's scope to the executive sponsor by exception
Risk and compliance flags	training obligations in collective agreements; works-council consultation on training measures; client-dedicated agents who may not be cross-trained onto other books; a matrix that reports skills nobody has used in months
Variant-prone steps	the hand-off where a works council is consulted on training; the reconciliation where a partner holds its own skill records; the matrix where dedication forbids a link
Automation candidates	five L1 steps (listed below)

L1 and L2

The method at L1 and L2 is on Cross-Training and Skill Mix Strategy: inventory the graph, cost it, quantify the pooling benefit, rank the investment, sequence the pipeline against speed to proficiency, enforce currency, compensate, review annually. A deploying function copies it through Wiki:Packs/Process Decomposition. What follows is the review flow that wraps the method; its sub-steps are the method's, so no separate L2 table is carried. The resilience test in step 5 is the card's own instrument and reuses the outcome vocabulary of The Placement Gate, so that a cannot-run is recorded rather than skipped.

1. Open the review on the calendar or on a trigger, naming the event classes in scope. Owner: the capacity planner.
2. Refresh the capability record: skills, languages, proficiency and currency per agent and per node, reconciled to the roster. Owner: the workforce analyst.
3. Is the record current enough to run? If the share of stale edges exceeds the limit (SET LOCALLY), the review returns cannot-run and the data fix comes first. Owner: the capacity planner.
4. Roll the matrix forward to the horizon: apply the attrition forecast and the training pipeline's scheduled output. Owner: the workforce analyst.
5. Run the resilience test per event class: remove the supply the class removes (a node, a platform, a share of headcount), re-route per the configuration archive, and test whether every critical skill and language keeps its coverage floor at the crisis service target. Owner: the workforce analyst.
6. Does any critical skill or language fall below floor under any class? Name the binding skill per failing class. Owner: the capacity planner.
7. Rank the gaps by exposure (the class's likelihood and impact from the scenario catalog) and by lead time (the skill's time to proficiency). Owner: the capacity planner.
8. List stale edges for refresher or removal under the currency policy. Owner: the team leads.
9. Is each gap a training gap, or a placement gap? A gap no training can close in the lead time goes to the archive as a configuration change. Owner: the placement lead.
10. Hand off the training plan: skill, count, node, proficiency target and need-by date back-computed from the ramp. Owner: the capacity planner, to the training lead.
11. Sign the review: the hand-off, the archive request and the stale-edge list. Owner: the function head.
12. Publish the matrix and the resilience report; log the review; feed the annual strategy. Owner: the capacity planner.

Variants

Recorded per Standard and Variant in Process Documentation:

• Statutory. Where a works council holds consultation or co-determination rights over vocational training measures, the hand-off at step 10 inserts a consultation step owned by the works-council liaison and approved by the function head.
• Contractual. A client contract that dedicates agents forbids certain links in the matrix; the exclusion is a constraint-register entry read at step 5, SET LOCALLY, no row. A partner that cross-trains at its own discretion varies step 10 to a request through the partner's oversight owner, under a variant row reviewed at renewal.
• Structural. A node whose routing cannot distinguish skills at the matrix's grain varies step 5 to test at the coarser grain, with a review date.
• Transitional. A unit from a predecessor organization whose skill records live in another system carries a reconciliation step at step 2 under a variant row with an expiry at the record cut-over.

L3 register

Job aid	Anchored to	Form
The capability-record extract and its reconciliation to the roster	step 2	work instruction
The currency limit and the cannot-run rule	step 3	work instruction
The matrix layout and the roll-forward procedure	step 4	work instruction
The resilience test procedure, with the event classes and the removal each implies	steps 5 to 6	playbook
The gap ranking sheet	step 7	work instruction
The currency rule and the stale-edge list	step 8	work instruction
The training hand-off form	step 10	work instruction
The review calendar and the sign-off record	steps 1 and 11	work instruction

Automation candidates

Released per class of action on a published catch rate per Human Gates and Number Grades. The card carries no L2, so candidates are named at L1; the five are ranked by how easy a catch rate is to publish for each.

1. The record extract and reconciliation (step 2): a query against the system of record, and skill-record drift is the review's commonest finding [A].
2. The stale-edge list (step 8): a date comparison against the currency rule; after #1 because it reads the currency dates the extract supplies.
3. The matrix roll-forward (step 4): arithmetic on the attrition forecast and the pipeline; after #2 because the attrition forecast is [E].
4. The resilience test computation (step 5): deterministic given the archive and the floor; after #3 because it depends on the archive being current, which GP-502 refreshes on its own cadence.
5. The hand-off form draft (step 10): assembled from the ranked gaps; last because its output is a document whose errors the signer finds, not a rule.

The sign-off (step 11) is never a candidate; it commits training budget and may change where work sits. The training-or-placement decision (step 9) also stays human, because routing a gap to the archive changes the function's placement rather than its training, and the workforce-flexibility literature treats the cross-training pattern and the coordination policy that deploys it as separate design choices to be evaluated together, not settled by the pattern alone. The gap ranking is computed, but its exposure weights come from the scenario catalog, which a person maintains.

Maturity Model Position

Four scales on this wiki use the word level; the launch page states which is which. Cross-Training and Skill Mix Strategy places the documented graph at Level 2 and the annual, valued strategy at Level 3; this card is the review between those decisions. On the WFM Labs Maturity Model™ a function that refreshes its matrix on a calendar and hands off gaps is at Level 2; one that runs the resilience test against the scenario catalog, records cannot-run and feeds the archive is at Level 3; one whose matrix is read by the placement engine as a constraint class and whose test is released on a published catch rate is at Level 4.

See Also

• Process Standardization — the hub and the inventory this card belongs to
• Cross-Training and Skill Mix Strategy — the method: the designed graph and the investment decision
• Placement Under Duress (generic process) — the archive the resilience report feeds
• Crisis Trigger and Re-Plan (generic process) — the post-event review that can trigger this card
• Scenario Planning and Contingency Staffing — the event classes the test runs against
• Multi-Skill Pooling and the Double-Counting Trap — why the test counts pooled, not summed, requirements
• Chaining and Flexibility Design — the link topology the test checks for
• Standard and Variant in Process Documentation — how the variants above are recorded