Draft Headcount IDs in Scenarios

Why do draft headcount need IDs?

Without IDs, it becomes difficult to trace headcount from draft state to approved state, once the scenario is merged. Having a unique ID assigned creates an audit trail of the headcount from scenario to hiring plan.

How it Works:

• Every new draft headcount is automatically assigned a unique headcount ID

• The ID is sequentially generated, following the same logic as IDs generated for approved headcount

• There are no duplicates or conflicts across approved and draft headcount

• The same ID persists when the headcount / scenario is approved, ensuring traceability

• Scenario exports will also include the draft IDs

FAQs

What if a scenario with draft IDs never gets merged?

• The IDs stay reserved for the drafts as-is.

What happens when a scenario is cloned?

• Cloned scenarios generate new IDs for all draft headcounts (no reuse).

Does the user need to do anything manually?

• Nope! All IDs are handled automatically for both new and existing un-merged scenarios.