Work Relationships and Assignments
Employment, contractor and agency relationships, the employee profile at the employer, assignments and entry/exit events. The onboarding process references process and access as links.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 5 findings · 14 questions
Relationship Each work relationship has its own identity, parties, type and effective period.
Relationship type
Relationship records distinguish employment, contractor engagements and agency work.
Parties
Each relationship records the parties and facts needed for classification and applicable law assessment.
- Which person, employer or contracting entity and work recipient are parties to this relationship?
- Which staffing provider, if any, participates in this relationship and in what role?
- Which approved classification identifies this relationship as employment, a contractor engagement or agency work?
- Which reviewed determination of applicable labour law is linked to this relationship, considering work locations, relevant parties and jurisdictional rules?
Parallel and repeat relationships
Separate relationship identities preserve concurrent engagements and rehires even when employee numbers are reused.
- Which stable relationship identifier and effective period distinguish this engagement from the person's other engagements?
- Which authorized references to concurrent relationships are recorded for this relationship?
- Which previous terminated relationship, if any, does this separately identified rehire relationship reference?
Assignments and lifecycle Assignment and lifecycle records preserve effective history and link to separately governed processes and access records.
Assignments
Each assignment identifies its target and period within a work relationship.
Assignment change
Assignment changes preserve history and distinguish assignment identity from employee number aliases.
- Did this recorded change create a new assignment version or a separately identified relationship?
- Which employee number, if any, applies to this relationship under its employer's documented uniqueness and reuse rules?
- Which position, functional role or other work target and effective period does this assignment specify?
Lifecycle events
Entry and exit events link to onboarding, offboarding and access follow-up without asserting their completion.
Entry and onboarding
Entry events identify the relationship being started and its onboarding references.
- Which relationship, effective entry date, onboarding process record and access request references are recorded for this entry event?
Offboarding completeness
Exit follow-up retains separate evidence for access review, outstanding work and relationship history.
- What completion status and reviewer are recorded for the access review linked to this exit event?
- Which unresolved items and responsible owners are recorded in this offboarding case?
- Which preserved versions and lifecycle events document this terminated relationship's history?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterprisePEO
- Industry
- Cross-industry
- Tags
- EM-PEO-02W1subjectEmploymentEngagementEmployeeProfileWorkAssignmentLifecycleEvent
What it is Filled
Employment, contractor and agency relationships, the employee profile at the employer, assignments and entry/exit events. The onboarding process references process and access as links.
Why it exists Filled
Employment, contractor and agency relationships, the employee profile at the employer, assignments and entry/exit events. The onboarding process references process and access as links.
Distinguishing features Filled
- Employee numbers follow documented local uniqueness and reuse constraints within their employer scope.
- Every employment, contractor or agency relationship has a stable relationship identifier independent of employee numbers.
- Changing employer creates a new relationship for the same person.
- A rehire creates a separately identified relationship even when the employer retains the same employee number.
- An exit event starts an access review and does not prove that rights were revoked.
- The contour is distinct from the person record and from positions, which exist without this relationship.
What robots and AI may and may not do Filled
Must not
- Record a freelancer as a staff employee by default.
- Treat closing the HR record as proof that all access was revoked.
- Reopen a terminated relationship to record a rehire.
- Use an employee number as a global identifier across employers.
- Discard relationship history when a person leaves.
Only with a human decision
- Classifying a relationship as employment or contracting.
- Confirming that offboarding is complete.
May
- Show all current relationships of a person with their parties and types.
- Report offboarding cases whose access review is still open.
- Record assignment changes as new versions with effective dates.
Moral aspects Filled
- Misclassifying workers can deny them labour rights and expose the employer to liability.
- Incomplete offboarding leaves access open for people who have left.
- Relationship records hold personal data that must be retained and disclosed lawfully.
Who is affected
- Employees, contractors and agency workers
- Employers and staffing providers
- Security and IT teams
Owners Filled
Steward
The head of HR or the person accountable for workforce records.
Master systems
- HRIS
- Personnel register
Links to other meta-models Filled
neighbor
- EM-ORG-02
- EM-ORG-04
- EM-ORG-05
- EM-ORG-06
- EM-PEO-01
- EM-PRD-01
- EM-WRK-02
references
- WM-ORG-005 - conceptual-candidate
- WM-PER-001 - conceptual-candidate
- WM-ORG-016 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Every work relationship has a stable identifier that distinguishes concurrent engagements and rehires.
- An employer-scoped employee number is an alias governed by documented local uniqueness and reuse constraints.
- Each assignment has an identifier and effective versions linked to its owning relationship.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Filled
- A relationship record names a person, relevant employing or contracting parties, a type and a period.
- A relationship record must be distinguished from the person record and from a position.
Capabilities and actions required Filled
- The contour holds parallel and repeated relationships of one person without duplicating the person.
- The contour tracks entry, assignment change and exit events through links to follow-up actions.
Hazards and failure modes required Filled
- Default relationship types can misclassify workers.
- An exit marked complete only in a workforce system can leave access unresolved.
- Reusing an employee number as a relationship identity can collapse separate engagements.
- Assuming that only the employer's jurisdiction determines applicable law can overlook worker protections.
Standards and interfaces optional Filled
- The HR Open Standards Consortium publishes standards for exchanging worker and assignment data.
- The World Wide Web Consortium publishes the Organization Ontology for membership and posts.
- The International Labour Organization publishes the ISCO-08 occupation classification.
Context of use required Filled
- The contour is used in payroll, access management, workforce planning and statutory reporting.
- Applicable labour law requires assessment of work locations, relevant parties and jurisdictional rules, including mandatory protections and conflict-of-law rules.
Sources Filled
- HR Open: exchange of HR data
- W3C ORG and ESCO/SFIA: relationships, skills and levels of responsibility
- HRIS/ATS/LMS practice and independent verification of outcome measurement via SPACE
- Employment Relationship Recommendation, 2006 (No. 198) - Carried over from the published world model wm-org-005-employment; checked live (HTTP 200) on 2026-10-09.
- International Classification of Status in Employment (ICSE-18) Manual - Carried over from the published world model wm-org-005-employment; checked live (HTTP 200) on 2026-10-09.
- Resolution concerning statistics on work relationships - Carried over from the published world model wm-org-005-employment; checked live (HTTP 200) on 2026-10-09.
Open questions
- How are the employer, the labor customer and the staffing provider separated?
- How are rehiring and several parallel relationships accounted for?
- Which changes require a new relationship, and which a new version of an assignment?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-peo-02/brief.json, ver-cy/world-models/card-supplements/em-peo-02.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.