7.2 Managing Filled, Unfilled, Close & Freeze

7.2 Managing Filled, Unfilled, Close & Freeze

Quick Summary: After Create Position, seats live as unfilled or filled objects you must manage. Freeze temporarily blocks hiring into a position; Close retires the seat. Availability date supports planning when a seat may be filled. None of these actions replace Terminate Worker—and termination alone does not remove the seat.

Blueprint tasks T30 Manage filled and unfilled positions and T31 Close and freeze positions test whether you can operate the position lifecycle after creation. Many exam stems mix worker events with seat events; your job is to keep them separate.

Filled vs Unfilled (Vacant) Positions

Under Position Management:

Persistence is the point

When a worker terminates, transfers out, or otherwise leaves the seat:

• The Worker employment ends or moves.
• The Position typically becomes unfilled again.
• History of who occupied the seat can still matter for workforce planning narratives.

That is why Position Management supports vacancy reporting and backfill against the same position ID. Job Management does not leave a durable empty seat object in the same way (Chapter 4 contrast).

Configuration scenario: Position P-1200 “Store Manager – Downtown” is filled by Alex. Alex resigns (Terminate). P-1200 remains in the Downtown Sup Org as an unfilled seat with the same Job Profile and cost center. Recruiting backfills P-1200 rather than inventing a new headcount story—unless finance decides to close the store manager seat because the location is consolidating.

Managing Unfilled Positions

Unfilled seats are active inventory. Good administration includes:

1. Confirm restrictions still match the plan (Edit Position Restrictions if the open role was re-leveled).
2. Confirm availability (availability date in the past or present if you intend to hire now).
3. Confirm not frozen or closed before blaming security for a failed Hire.
4. Report and clean orphans — open positions that no longer have budget pollute vacancy dashboards.

Common unfilled-position work

Exam trap: An unfilled position is not automatically a Worker, a Job Profile, or a security group. Searching for “open jobs” in a business sense still maps to Position objects in Position Management.

Managing Filled Positions

A filled position is still a first-class object:

• Seat attributes (restrictions) remain the design of the role.
• The worker’s job is the occupancy instance.
• Changing who sits there uses staffing movements (Change Job, Hire into vacant after exit, etc.).
• Changing what the seat is may use Edit Position Restrictions plus worker-aligned events when the incumbent must match new rules.

Filled-position decision table

Freeze Position

Freeze Position temporarily prevents staffing events from filling (or further staffing) the seat while keeping the position record.

When freeze is the right tool

• Enterprise hiring freeze on selected seats
• Reorganization in progress—do not backfill until the new structure lands
• Budget hold for one quarter with intent to reopen
• Seasonal pause without eliminating the role permanently

Freeze vs other actions

Exam trap: Freeze is not delete, not Terminate Worker, and not automatic conversion to Job Management. Unfreeze (or the tenant’s equivalent end-freeze action) restores the ability to staff when policy allows.

Configuration scenario: Finance freezes all open director-level positions in Corporate HQ for 90 days. HR Partners still see the position IDs in reports, but Hire into those seats is blocked until the freeze lifts. After Q2, they unfreeze critical seats and leave non-critical ones frozen or closed based on the revised plan.

Close Position

Close Position retires the seat as available capacity. Use close when the role is eliminated—not when you only need a pause.

Close characteristics

• Seat is no longer available to fill through normal Hire into that position.
• Historical data and audit trail are preserved (Workday prefers inactivate/close patterns over hard delete).
• Closing is the Position Management parallel to “this budgeted FTE no longer exists.”
• Closing does not by itself run payroll reverse journals for all past incumbents or wipe the Job Profile catalog entry.

Close vs freeze decision cues

Availability Date Concepts

Availability date on a position supports when the seat may be treated as available to fill. Exam-relevant ideas:

1. Future-dated capacity — Create Position effective and/or available in the future so headcount appears when the budget period starts.
2. Planning alignment — Workforce plans and recruiting timing key off availability, not only create-submit timestamps.
3. Distinct from freeze — A seat can be unfrozen but still not “available yet” if availability is future-dated; conversely, a past availability date does not help if the seat is frozen or closed.

Configuration scenario: Create Position for a new lab tech seat effective 1 June with availability date 1 September (lab build-out completes in August). Recruiting can plan against the known position ID, but operational Hire is aligned to September availability—not to the June create moment alone.

Lifecycle Diagram (Memorize for T30–T31)

Create Position
      │
      ▼
 Unfilled ──Hire──► Filled
      ▲               │
      │               │ worker leaves (Terminate, transfer out, etc.)
      └───────────────┘
      │
      ├── Freeze ──► (blocked) ──Unfreeze──► Unfilled/Fillable again
      └── Close  ──► retired (not available to fill)

Diagnostic Pattern: “Why can’t we hire into this position?”

Work this list in order on scenario questions:

1. Is the org Position Management and is the Position ID correct?
2. Is the position closed?
3. Is the position frozen?
4. Is availability date still in the future?
5. Do position restrictions conflict with the proposed hire (profile, location, worker type)?
6. Is the initiator missing security / is the Hire BP awaiting approval?

Mixing these causes is how wrong answers get written. Close and freeze are seat controls; security is access; restrictions are attribute validation; Terminate is a worker event.

What This Section Deliberately Leaves to Chapter 8

• Full Terminate employees process design (T34)
• Contingent contract and end-contract flows (T35–T36)

Here, only remember: worker exit vacates a Position Management seat; it does not auto-close or auto-delete the position unless your process includes an explicit close/freeze step.

Master filled/unfilled management plus freeze vs close and availability, and T30–T31 become pattern recognition instead of vocabulary guesswork.