Choosing the model

Third and last of the three irreversible decisions. Changing the employment model after work relationships exist is not a configuration change. It is a data migration, and it has statutory consequences for service dates — which is where legal entitlements attach. Treat it as irreversible. Not "difficult". Irreversible. The default recommendation is single assignment, unless you have a concrete case that needs more. And the reason is not technical: simplicity has real operational value. Every additional layer is one more thing every HR user navigates, every day, forever — and one more thing for them to get wrong. That cost is invisible on a design document and extremely visible in a support queue. The questions that force multiple assignments: does anyone do two different jobs for the same employer, concurrently, with separate pay or reporting? Are there bank, casual or relief workers who work across departments? Does the client operate…

In this module: Module 10 · The Employment Model and Assignments

1. 1Work relationships and assignments
2. 2The employment model options
3. 3Choosing the modelFree preview
4. 4Setting the model
5. 5Creating work relationships
6. 6Assignment attributes
7. 7Multiple assignments in practice
8. 8Assignment statuses
9. 9People groups and default expense account
10. 10Areas of responsibility revisited
11. 11What breaks
12. 12Lab briefing: relationships, concurrency and long-term leave