Backfilled By
Description
The person who filled the backfill for this person's departure or move from the job.
- Code name: backfilledBy
- Sensitivity: Highly sensitive
- Data type: Person
- Data category: Recruiting
- Entity type: Job
- Read only: Yes
- Properties: This field inherits the properties of the Person data type.
ChartHop has three related backfill fields. They serve different purposes:
Field | Lives on | Shows | Use it for |
|---|---|---|---|
Backfill For | The new or open job | Who this job is replacing (cleared once filled) | Managing the hiring workflow |
Historic Backfill | The current job | Who held this job before | Pay comparison on the current role |
Backfilled By | The leaving person's row | Who replaced them | Turnover and backfill reporting |
How it works
Backfilled By reads the leaving person's row and returns the first person who filled their seat after they left or moved.
- Separate backfill job: When a backfill job was created using the Backfill action, someone hired into that backfill job counts as the replacement from the moment the backfill was created. This means a hire can count even before the original person's last day.
- Same job reused: When no separate backfill job exists and the same job was rehired into after the departure, only hires after the original person's last day count.
- First fill only: The field always shows the first replacement. If that person later leaves, the field still shows them. To follow the chain of replacements, use backfilledBy.backfilledBy.
- Empty when: No backfill exists, the backfill is still open, or a departure has been announced but no one has been hired yet. The field never returns the leaving person themselves.
- Internal moves count: On a person who moved to a new job internally, the field shows who filled their old seat. This makes it useful for internal-mobility reporting as well as turnover reporting.
- Works in scenarios: The field reads scenario changes, so in a planning scenario it shows who is planned to fill the seat.
Access
Backfilled By is highly sensitive. Viewers without sensitive access see no value, including the existence of the field. A hidden (highly sensitive) backfill job or an unannounced hire also stays hidden.
See Report on who backfilled departed employees for CQL examples and Data Sheet usage.