Refer to the following scenario to answer the question below.

The leave must maintain a distinct 180-day entitlement for each birth event. Selecting Entitlement per Event directs Workday to grant and track an entitlement for each separate qualifying event rather than treating all requests within the balance calendar as one shared entitlement. However, Workday also needs an event-specific value that distinguishes one child’s birth from another.

Configuring Child’s Birth Date as an additional field provides that event identifier. When a worker has more than one birth within the same rolling-forward 12-month window, the different birth dates allow Workday to associate each request with the appropriate event-specific entitlement. The combination prevents requests related to separate births from consuming a single undifferentiated balance.

A validation rule can restrict request behavior but does not establish multiple event balances. Child’s Birth Date by itself captures supporting information but does not instruct Workday to create an entitlement for every event. Conversely, Entitlement per Event without the identifying additional field does not provide the required data for distinguishing the births in this scenario. Both configurations are necessary: the additional field identifies the event, and Entitlement per Event establishes separate entitlement tracking for it.