Human Capital Managementlifecycle
Employment & Contracts
How do I track who holds which position, on what contract, since when — including acting cover?
An employment assignment binds a person to a seat, a unit, and a manager for a period of time, carrying the contract number, contract expiration, and wage rate. Assignments are historized: the current one is flagged, and past ones stay on record.
What the record holds at once
Held constantEmployment & Contracts 5 states, at the same time
Temporal, not overwritten
Each assignment is a dated record with a current flag; position history survives every change.
Contract fields on the assignment
Contract number, expiration date, and wage per rate live on the assignment, with duplicate-number checks at save.
Acting positions and supervision
Time-boxed acting-position and supervisor records cover seats and add oversight without editing the substantive assignment.
Rules at save
Age, one-manager, and duplicate-contract checks run before an assignment is accepted.
Access follows the assignment
Because permissions attach to seats, closing one assignment and opening another moves access with the person.
How it works
The assignment is the temporal join the rest of the platform trusts: person → employee → position-in-unit → manager, with contract number, contract expiration date, wage per rate, and a current flag. Changing jobs means closing one assignment and opening the next — the history is the audit trail, and seat-based access follows the new assignment automatically.
Business rules run at save: an age check on the employee, a one-manager check so reporting lines stay unambiguous, and a duplicate-contract-number check so two assignments cannot share a contract reference. Acting-position records cover a seat for a bounded period without disturbing the substantive assignment, and supervisor records add time-boxed supervision alongside the manager line.
Ending employment works the same way it is recorded: the current assignment is closed and the full chain — contracts, dates, positions held — remains queryable. continON does not ship a separate resignation or dismissal workflow today; organizations that want a formal exit approval sequence can build one on the process engine.
What this touches
- Organization & positions
Assignments always point at a defined seat in the unit hierarchy. - Payroll
Payroll calculation reads the assignment’s wage rate and position pay data. - Personnel records
Assignments are the employment layer over the employee file. - Process Builder
Formal exit or change-approval sequences can be modeled as workflows.
See employment & contracts running in continON.
A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.