← Back to catalogue
Published

Work Assignment

vr.wm-org-016 · wm-org-016-work-assignment

Model the time-bounded, scoped binding of a person or non-human agent to a role, position or body of work within an organization, together with the authority, place, effort, preconditions, lifecycle and evidence that make the binding operable and auditable.

World Models Society, people and institutions SOC.ORG.ASN

Bundle → Layer → Finding → Questions Filled

6 bundles · 13 layers · 28 findings · 115 questions

Assignment Identity and Definition What an individual work assignment is as a distinct record: how it is identified, which participants it binds, how it is typed, and what kind of agent may hold it.

Core Assignment Relation

The identity, participant structure and typing of the assignment record itself.

Assignment record identity and versioning

How one assignment instance is identified and kept distinct from the position, the role concept and the person, including identifier priority, correction versus real-world change, and supersession chains.

  1. Which system is the authoritative master for this assignment identifier, and what identifier value and scheme does it issue? identity
  2. If no authoritative master identifier exists, which governed IRI or Dimension-assigned UUID/ULID is used instead? identity
  3. How are two assignments of the same agent to the same post in different periods kept distinct without using a date as the identifier? identity
  4. How is a corrected version of the assignment record distinguished from a genuine change to the assignment in the world? provenance

Participant set and relation shape

The n-ary participants that constitute the assignment: assignee agent, assigning organization or unit, role or post, host organization where different, and the engagement context that gives it a basis.

  1. Which agent, which organizational unit and which role or post does this assignment bind together? composition
  2. Which employment relationship, staffing contract or volunteer arrangement gives this assignment its basis, and is the assignee engaged by a different organization from the one where the work is performed? authority
  3. Is the assignment expressed against a defined post, an abstract role concept, or a bespoke scope with no post at all? classification
  4. Which participant changes may be made in place and which force the creation of a new assignment record? constraint

Assignment type and primacy

Typing the assignment by nature (substantive, acting, interim, seconded, agency-supplied, volunteer, shadow), by permanence, by whether it is the agent's primary assignment, and by how much of the post's authority it conveys.

  1. Which controlled vocabulary supplies the assignment type, and how are locally invented types governed and reviewed? classification
  2. Is this the agent's primary assignment for reporting, headcount and directory purposes, and how is exactly one primary guaranteed? constraint
  3. Does the assignment convey the full authority of the post, a reduced subset, or none at all? authority
  4. Where the assignment is acting or interim, what substantive assignment is it standing in for and until when? relationship

Assignee Agent Kind and Reservation

What kind of agent may hold the assignment and which duties are reserved to natural persons.

Agent kind, natural-person reservation and accountability

Whether the assignee is a natural person, an organizational unit or a non-human software or robotic agent, which duties may not lawfully be held by a non-human agent, and who remains accountable when one is used.

  1. Is the assignee a natural person, an organizational unit or team, or a non-human software or robotic agent? classification
  2. Which duties within this assignment are legally reserved to a natural person and therefore may not be discharged by a non-human agent? constraint
  3. Where a non-human agent holds or supports the assignment, which natural person holds oversight, and do they have the competence, training and authority plus the support needed to intervene? authority
  4. How is the assignee referenced across systems without embedding personal data in the identifier itself? privacy

Assigned agent

ORG Membership.member is a foaf:Agent, covering persons and organizations. FHIR PractitionerRole.practitioner is 0..1 and may be empty for an un-named surgeon at a named hospital. PROV-O distinguishes Person, Organization and SoftwareAgent as agents, but HR occupancy of posts by software agents lacks primary HR-standard support and is recorded as a gap when claimed.

  1. Which person or other agent occupies this assignment, and what master identifier is used for that agent? identity
  2. Is the occupancy an unnamed or pre-allocated role with no designated practitioner, and if so what host and role still identify the slot? composition
  3. Is the holder an organization or post treated as an agent, as permitted for some government ex officio constructions? composition
  4. If a software or robotic agent is claimed as occupant, what primary HR or personnel source supports that claim, or is the claim marked as a gap? exception
Assignment Scope and Authority What the assignment covers and what it empowers: the role linkage, the bounded body of work, the place of work, the authority granted, supervision and delegation, and the share of capacity consumed.

Scope of Work and Place

The role linkage, the concrete body of work covered, and where the work is performed.

Role, post and occupation classification linkage

Which post the assignment fills, which role concepts and external occupation or specialty codes describe it, the title used towards the assignee, and what happens when the underlying post is reclassified.

  1. Which post does the assignment fill, and which role concepts describe what the assignee actually does? composition
  2. Which external occupation, specialty or professional classification codes apply, and at what version of the classification? interoperability
  3. What job title is used towards the assignee, and does it differ from the classified title of the post? definition
  4. If the post is reclassified or the classification scheme is reversioned, does the assignment persist unchanged and under what rule? lifecycle

Bounded work scope and portfolio

The concrete body of work the assignment covers - objectives, services, caseload, accounts, assets, population or operational period - together with what is explicitly excluded and how overlapping claims are prevented.

  1. What objectives, services or caseload does this assignment cover, and what is explicitly excluded from it? definition
  2. Which client, cost centre, project, incident or operational period is the work performed under? composition
  3. How is the scope bounded so that two concurrent assignments do not both claim responsibility for the same work? constraint
  4. How large a change of scope can be absorbed as an amendment before a new assignment record is required? lifecycle

Place of work, mobility and jurisdiction

Where the work is performed, whether it is remote, multi-site or cross-border, and which location-derived legal and safety regimes attach to the assignment.

  1. What is the assignee's designated base location and what other locations does the assignment cover? spatial
  2. Is any part of the work performed remotely, at customer sites, or in another country, and for how long in each case? spatial
  3. Which jurisdictional, tax, safety and working-time regimes follow from the work location, and which prevails where they differ from the engaging entity's home regime? constraint
  4. How is a change of work location recorded so that the earlier location and its effective period remain retrievable? temporal

Performance location and services

FHIR PractitionerRole.location, specialty, healthcareService, contact, characteristic, communication, availability and endpoint describe where and how the occupant provides services. Distinct instances are required when availability, telecom or other details are not the same across services or locations. ORG basedAt and Site capture organizational location independently of occupancy.

  1. At which locations or sites is this occupancy authorized to be performed? spatial
  2. Which specialties and services is the occupant authorized to provide under this occupancy? classification
  3. What official contact details, languages and technical endpoints belong to this occupancy rather than to the person master record? relationship
  4. If locations, services or telecom differ, must this occupancy be split into multiple assignment instances? decision

Authority, Supervision and Capacity

What the assignment empowers the assignee to decide, to whom they answer, what may be delegated, and how much capacity the assignment consumes.

Granted authority and decision limits

The decisions, approvals and financial limits the assignment authorizes, distinguishing authority inherent in the post from authority granted to this assignee, and the validity of that authority in its own right.

  1. What decisions, approvals and financial limits does this assignment authorize the assignee to exercise? authority
  2. Which authorities flow from the post itself and which were granted specifically to this assignee? provenance
  3. Does each granted authority have its own validity period, and does it lapse automatically when the assignment ends or is suspended? temporal
  4. Was the granting agent themselves authorized to confer authority at this level and scope? validation

Supervision, reporting lines and delegation

To whom the assignee reports for this assignment, who may change or end it, whether work or authority may be delegated or forwarded, and how acting cover is recorded when the assignee is unavailable.

  1. To whom does the assignee report for this assignment, and is there more than one reporting line? relationship
  2. Who may amend, suspend, transfer or terminate this assignment, and is that the same party as the reporting line? authority
  3. May the assignee delegate or forward the work or the authority, to whom, and does accountability transfer with it? authority
  4. How is temporary acting cover recorded when the assignee is absent, and does the original assignment remain active during it? process

Effort allocation and capacity share

The share of the assignee's capacity the assignment consumes, how total allocation is validated across concurrent assignments, and which measure prevails when contracted, scheduled and allocated effort disagree.

  1. What share of the assignee's capacity does this assignment consume, expressed in which unit and over which reference period? measurement
  2. How is total allocation across all of the assignee's concurrent assignments validated, and what is the permitted ceiling? validation
  3. Which measure is authoritative when contracted hours, scheduled hours and allocated effort disagree? quality
  4. How is allocation restated for a part-period assignment or one whose allocation changes mid-period? temporal
Assignment Time and Schedule When the assignment is valid, how it relates to preceding, succeeding and concurrent assignments, the working pattern and availability it carries, and the duty and rest limits that constrain it.

Effective Period and Succession

Validity boundaries of the assignment and its relation to other assignments in time.

Effective period, concurrency and succession

The assignment's start and end instants and their precision, the separation of real-world effective time from record time, the treatment of backdating and correction, and the relation to concurrent, predecessor and successor assignments.

  1. What are the assignment's effective start and end instants, at what precision, and is an explicit UTC offset or Z recorded on each? temporal
  2. Is the assignment open-ended, fixed-term or terminated by a defined event, and what exactly ends it? lifecycle
  3. How is the real-world effective time kept separate from the time the record was created, observed or ingested? provenance
  4. Which other assignments does this agent hold over an overlapping period, are such overlaps permitted, and which assignment precedes and succeeds this one for the same post? relationship
  5. How is a same-day transfer between posts represented so that headcount and coverage are not double-counted? measurement

Working Pattern and Duty Limits

The pattern, predictability and availability the assignment carries, and the duty and rest constraints that bound it.

Working pattern, predictability and availability

Normal hours and days, whether they are variable or unpredictable, the reference hours and notice that apply where they are, availability and on-call status, and the boundary to the scheduling system that holds concrete instances.

  1. What normal working hours and days does the assignment carry, and may either the hours or the days vary? temporal
  2. Where the working pattern is unpredictable, what reference hours and days apply and what minimum advance notice of a work assignment is guaranteed? constraint
  3. How are availability windows, on-call and reserve status expressed and time-bounded for this assignment? state
  4. Which scheduling or rostering system holds the concrete shift instances, and how does it reference this assignment? interoperability

Duty, rest and time-limit constraints

Maximum duty and minimum rest limits applicable to the assignment, who verifies fitness and limit compliance before duty, how approved extensions and exceedances are recorded, and how long duty records must be kept.

  1. Which duty and rest limit regime applies to this assignment, and from which legal or sectoral instrument does it derive? constraint
  2. Who verifies before a duty period that the assignee is fit for duty and within the applicable limits, and what is recorded? validation
  3. What is recorded when a limit is extended or exceeded, and who must approve or be notified? exception
  4. How long must duty, rest and fitness records for this assignment be retained, and by whom? retention
Assignment Lifecycle and Change How an assignment moves from proposal to end: its states, the events and approvals that move it, how material changes are made and notified, and what must be handed over and revoked when it ends or transfers.

States and Transitions

The permitted state set and the events, actors and preconditions that move an assignment between states.

State model, transitions and triggers

The complete permitted state set including terminal states, whether active status is stored or derived, which events and approvals drive each transition, what happens automatically at the effective end, and how an erroneous transition is reversed.

  1. What is the complete set of permitted assignment states, which are terminal, and which transitions are forbidden? state
  2. Is active status stored explicitly, derived from the effective period, or both, and which prevails when they disagree? quality
  3. Which events trigger each transition, which require explicit human approval, and which actor performs them? event
  4. What transition occurs automatically at the effective end instant, and what happens if the end data is missing or in the past when discovered? exception
  5. How is a transition made in error reversed while preserving the original entry in the audit trail? provenance

Personnel action events

5 CFR 335.102 authorizes agencies to promote, demote or reassign listed employee categories. Section 335.101 states that a position change does not change competitive status or, with listed exceptions, tenure. Section 335.103 requires merit procedures for covered promotions and details over 120 days, permits retroactive temporary promotion when an appropriate authority so determines, and requires a temporary reconstruction record kept for two years or until OPM evaluation. These events create or replace occupancies.

  1. Which personnel action created or replaced this occupancy: appointment, promotion, demotion, reassignment, reinstatement, transfer or another governed action? event
  2. Did this position change alter competitive status or tenure, or do the 5 CFR 335.101 rules that status and tenure are unchanged apply? lifecycle
  3. Was competition required, and if not which noncompetitive or discretionary exception was used? authority
  4. What reconstruction record of ratings, ranking and selection is retained, and until when? evidence

Change, Handover and Exit

Material change to a live assignment and the controlled exit from it.

Amendment and material change

Which changes may be absorbed as amendments, which require a new record, which are material enough to require written notification within a deadline, and what consent or consultation must precede them.

  1. Which changes to this assignment are material enough to require a written statement of change to the assignee, and by what deadline? requirement
  2. Which changes create a new assignment record rather than amend the existing one, and why? constraint
  3. How is the effective date of each amendment recorded relative to the date the assignee was notified? temporal
  4. What consent, consultation or representative involvement is required before the change takes effect, and was it obtained? authority

Handover, coverage and offboarding

What must be transferred before an assignment ends, which access rights, delegations and assets must be revoked or reassigned on end or transfer, who covers the scope in the interval, and how completion is evidenced.

  1. What work, records, custody and relationships must be handed over before the assignment ends, and to whom? process
  2. Which access rights, delegated authorities, credentials and physical assets must be revoked or reassigned on end or transfer, and within what time? access
  3. On a transfer rather than a termination, which existing authorizations are re-confirmed as still needed and which are removed? validation
  4. Who covers the scope between the outgoing and the incoming assignee, and under what temporary assignment? process

Temporary, acting, detail and time-limited forms

5 CFR 335.102(f) authorizes time-limited promotions for not more than five years unless OPM authorizes longer, with advance written notice that the employee may be returned at any time to the former or an equivalent position. Details and time-limited promotions over 120 days to higher grades generally require competition, counting prior noncompetitive service in the preceding 12 months. Temporary promotion may become permanent without further competition if originally competed and that possibility was advertised. Acting or interim coverage is a common operational form but is not named as such in the fetched 5 CFR text and must not be claimed as a 5 CFR term.

  1. What time limit applies to this temporary promotion, detail or acting occupancy, and was advance written notice given? constraint
  2. May the occupant be returned at any time to the former or an equivalent position, and is that return exempt from adverse-action procedures cited in 5 CFR 335.102(f)? lifecycle
  3. How many days of noncompetitive higher-grade detail or time-limited promotion have accrued in the preceding 12 months, and is further competition required? constraint
  4. Was the temporary occupancy originally competed with notice that it might become permanent, allowing conversion without further competition? decision
Assignment Eligibility and Controls What must be true before an assignment may be made or continued: competence, credentials and fitness, screening and right to work, and the separation, conflict, cardinality and coverage constraints that bound valid assignment.

Eligibility Preconditions

Competence, credential, fitness, screening and legal-permission preconditions of the assignment.

Competence, credentials, training and fitness

The competences, qualifications, licences, training and fitness required before this assignment may be held; how each is verified and evidenced; and what happens to the assignment when a prerequisite expires, is suspended or is revoked.

  1. Which competences, qualifications, licences and training are prerequisites for this assignment, and which are merely desirable? requirement
  2. How and when was each prerequisite verified, by whom, and what evidence is held and where? evidence
  3. What happens to the assignment when a required credential expires, is suspended or is revoked, and how far in advance is expiry surfaced? lifecycle
  4. Beyond skill, does the assignee have the authority and the practical support needed to discharge the assignment, and how is that established? authority

Screening, clearance and permission to work

The screening, vetting or security clearance level the assignment requires, the legal right to work or professional registration in the work jurisdiction, re-screening triggers, and how outcomes are surfaced without exposing sensitive underlying results.

  1. What screening, vetting or clearance level does this assignment require, and on what risk designation is that based? security
  2. What legal right to work or professional registration is required in the work jurisdiction, and until when is it valid? constraint
  3. Who is accountable for re-screening, and at what interval or on which triggering events? ownership
  4. How is a failed, lapsed or downgraded check handled without exposing the underlying sensitive result to assignment consumers? privacy

Constraints and Validation

Separation of duty, conflict of interest, cardinality, coverage and the rules that make an assignment valid or blocked.

Separation of duty, conflict, cardinality and validation rules

Which assignments may not be held together, which may be held but not exercised together, which conflicts of interest must be declared, how many holders a post may have, what minimum coverage is required, and how blocking rules, warnings, exceptions and pre-existing violations are handled.

  1. Which other roles or assignments may this assignee not hold at the same time under a static separation rule? constraint
  2. Which role combinations may be held but not activated or exercised together in a single session or transaction? constraint
  3. How many concurrent holders may this post or role have, what minimum coverage must exist, and what happens when either bound is breached? constraint
  4. Which conflicts of interest or related-party relationships must be declared before the assignment is made, and were they? validation
  5. Which validation rules are blocking rather than advisory, who may grant an exception, and how are pre-existing violations of a newly introduced rule treated? exception
Assignment Evidence, Governance and Interoperability How the assignment is proved to have been properly made, what must be told to whom, how the record is protected, retained and deleted, and how it is aligned to external representations and projected to downstream consumers.

Authorization Evidence and Notification

Who authorized the assignment and on what basis, and who had to be told about it.

Authorization, basis and approval evidence

Who authorized the assignment, acting in which role and at what time, on what documented basis, whether that authorizer was competent to authorize an assignment of this type and authority level, and how the approval chain survives the authorizer's own departure.

  1. Which agent authorized this assignment, acting in which role, and at what instant? provenance
  2. On what documented basis was the assignment authorized, such as a requisition, funded establishment, staffing order or operational plan? evidence
  3. Was the authorizer permitted to authorize an assignment of this type, scope and authority level, and how was that checked? validation
  4. How is the approval chain preserved and interpretable after the authorizer's own assignment or employment ends? provenance

Acknowledgement, notification and disclosure duties

Whether the assignee received the required written particulars within the deadline, whether acceptance is a precondition of activation, and which third parties - workers' representatives, host organizations, clients or regulators - must be informed, including prior information where the assignment places the worker under a high-risk automated system.

  1. Was the assignee given the required written particulars of the assignment, in what form, and by which deadline relative to the start? requirement
  2. Did the assignee acknowledge or accept the assignment, and is acceptance a precondition of activation? evidence
  3. Which third parties must be notified that this assignment exists, with what content, and by when? access
  4. Where the assignment places the worker under a high-risk automated system, were the affected workers and their representatives informed before the system was put into use? requirement

Privacy, Retention and Access

Protection, visibility, retention and deletion of the assignment record and its evidence.

Personal data classification and access scoping

Which assignment fields are personal or specially protected, the lawful basis for each, which roles may see the full record versus only the non-personal scope and period, and what is logged when the record is read, exported or changed.

  1. Which fields of this assignment record constitute personal data or specially protected data, and what is the lawful basis for processing each? privacy
  2. Which roles may read the full record, and which may read only the post, scope and period without the assignee's identity or terms? access
  3. How is the assignment published for organizational transparency without disclosing protected attributes or inferring them from adjacent fields? privacy
  4. What is recorded when an assignment record is read, exported or amended, and how long is that log kept? security

Retention, deletion and legal hold

How long the assignment record and its evidence must be kept and on what basis, what may be deleted or anonymized while preserving organizational history, how a legal hold suspends deletion, and what survives erasure of the underlying person record.

  1. How long must the assignment record and each class of associated evidence be retained after the assignment ends, and under which rule or minimum? retention
  2. Which parts of the record may be deleted or anonymized at end of retention while preserving the organizational and succession history? retention
  3. How does a legal hold or investigation suspend deletion, who may impose and lift it, and how is the suspension evidenced? exception
  4. When the underlying person record is erased on request, what remains of the assignment and under what justification? privacy

Interoperability and Projection

Mapping to external representations and delivery to downstream consumers.

Standard alignment, external identifiers and downstream projection

Which external representations the assignment is mapped to and where those mappings lose information, which external identifiers are held and which prevails on conflict, which downstream systems consume the assignment, and how divergence is reconciled rather than silently absorbed.

  1. Which external standard representations is this assignment mapped to, at what version, and which of its fields have no counterpart in each? interoperability
  2. Which external identifiers exist for the same assignment, and which is authoritative when two systems disagree? identity
  3. Which downstream systems consume this assignment - directory, access management, payroll, scheduling, statutory register - and how and how often are they reconciled? interoperability
  4. Where a target standard conflicts with a local requirement or the mapping is lossy, how is the conflict recorded so that it is visible to consumers rather than hidden? quality

Classifiers Filled

Family
World Models
Category
Society, people and institutions
Entry kind
relationship
Navigation path
NAV.SOC.ORG.ASN
Domain
SOC.ORG.ASN
Industry
Cross-industry
Tags
workassignmentsoc.org.asn

What it is Filled

A Work Assignment is a reified n-ary relationship between an assignee agent, an organization or unit, a role or post, a bounded work scope and a validity period. The model covers how such a binding is identified, classified, authorized, constrained, changed, evidenced and ended. It deliberately holds no definition of the position itself, no contract terms, no person master data and no task-instance execution state; those belong to sibling models and are referenced. The model is format-neutral: JSON, YAML, Markdown, Git, MCP and MongoDB are projections of this semantics, never its source.

In scope

  • Identity, classification and versioning of the individual assignment record
  • The n-ary participant set: assignee agent, organization/unit, role or post, engagement context
  • Bounded work scope: objectives, services, caseload, accounts, operational period, exclusions
  • Granted authority, decision limits, reporting lines, delegation and acting cover
  • Place of work, mobility, cross-border work and the jurisdictional consequences that follow
  • Effort allocation and capacity share across concurrent assignments
  • Effective period, working pattern, availability, duty and rest limits
  • Assignment lifecycle states, transitions, amendment, handover and offboarding
  • Eligibility preconditions: competence, credentials, fitness, screening, right to work
  • Constraints: separation of duty, conflict of interest, cardinality and coverage rules
  • Authorization evidence, acknowledgement, statutory notification and disclosure
  • Personal-data classification, access scoping, retention, deletion and legal hold
  • Alignment to external representations and projection to downstream consumers

Out of scope

  • Definition, classification, grading and description of the position or post itself (WM-ORG-004)
  • Employment contract formation and terms, remuneration determination and benefits (WM-ORG-005)
  • Person, party and agent master identity records
  • Organization structure, unit hierarchy and legal-entity data
  • Role, occupation, skill and competence taxonomies as concepts (referenced as classifiers)
  • Per-task work-item claiming, execution and completion state
  • Permission and entitlement catalogues, and the access-decision engine itself
  • Concrete shift instances, time capture, timesheets and attendance actuals
  • Payroll calculation, cost allocation and inter-company recharge
  • Performance objectives, appraisal outcomes and succession candidate pools

Why it exists Filled

Model the time-bounded, scoped binding of a person or non-human agent to a role, position or body of work within an organization, together with the authority, place, effort, preconditions, lifecycle and evidence that make the binding operable and auditable.

Distinguishing features Filled

  • Binds an assignee, an organization, a role or post, a scope and a period into one record.
  • Differs from a position, which defines the post regardless of who fills it.
  • Differs from an employment relationship, which holds contract terms and pay.
  • Differs from a task assignment: it covers a body of work over time, not one work item.

What robots and AI may and may not do Filled

Must not

  • Treat a draft or proposed assignment as effective.
  • Grant access or authority beyond what the active assignment confers.
  • Keep using delegated authority after the assignment ends or is suspended.
  • Override blocking validations without a registered exception.
  • Disclose protected personal fields to unauthorized consumers.

Only with a human decision

  • Authorizing an assignment.
  • Approving exceptions to eligibility rules.
  • Ending an assignment for cause.

May

  • Propose an assignment and check eligibility rules.
  • Resolve who holds which assignment at a given instant.
  • Detect conflicts such as over-allocation or segregation-of-duties clashes.
  • Project assignment data to permitted downstream systems.

Moral aspects Filled

  • Assignment decisions affect workload, pay prospects and wellbeing; allocation should be fair and explained.
  • Working time and rest limits protect health and must not be bypassed.
  • Cross-border assignments carry tax, social security and immigration consequences for the worker.

Who is affected

  • Assigned workers and agents
  • Managers and colleagues
  • People served by the assigned work

Owners Filled

Steward

A Dimension adopting this model must name a single accountable owner for the assignment register and a named deputy, each identified by their own assignment record so that authority is self-describing.

Roles

Assignment register owner
Own the model instance, its vocabularies, rule sets and their versions; Declare the identity priority, period boundary convention and retention schedule in force; Approve model version changes and publish migration notes
Assignment authorizer
Decide and record authorizations within their own conferred limits; Confirm that the assignment's authority level and scope are within their competence to grant; Attach conditions and compensating controls where an exception is relied upon
Assignment administrator
Create, amend, suspend, transfer and end assignment records on instruction; Issue statements of particulars and statements of change within the applicable deadlines; Track handover, revocation and reconciliation tasks to completion
Controls and assurance reviewer
Maintain separation of duty, conflict, cardinality and coverage rules and their severities; Review registered exceptions, compensating controls and their expiry; Run and act on conflict detection scans and record findings against the rule set version
Data protection and records steward
Classify assignment fields, record the lawful basis and set access scope rules per role; Maintain the retention schedule, disposal methods and legal hold procedure; Adjudicate subject access and erasure requests against retained assignment history
Interoperability steward
Maintain versioned crosswalks to external standards and downstream consumers; Record known losses and conflicts and ensure caveats travel with every projection; Own reconciliation schedules and adjudicate identifier precedence disputes

Links to other meta-models Filled

references

  • WM-ORG-004 Position - The assignment cites the post it occupies; the post's definition, grading and description remain owned by WM-ORG-004. Direction: WM-ORG-016 points outward to WM-ORG-004, complementing the registered COMPOSE relation in which a position is occupied through a scoped assignment.
  • WM-ORG-005 Employment Relationship - The assignment cites the engagement that gives it a basis. Marked not required because agency-supplied, contracted and volunteer assignments rest on a commercial or non-employment arrangement instead; what is required is some engagement context, not specifically an employment relationship.
  • Person, party and agent identity model - Supplies the assignee identity, including non-human agents. This model holds only a reference and never duplicates personal master data.
  • Organization and organizational unit model - Supplies the organization or unit in which the assignment is held and, where different, the host organization where the work is performed.
  • Role, occupation and competence classifier model - Supplies role concepts, occupation codes and the competences that become assignment prerequisites; the classifier owns the concepts, the assignment owns the citation.
  • Access entitlement and identity management model - Consumes the assignment as the temporal and organizational basis for user-to-role assignment, activation and de-provisioning; the permission catalogue and decision engine stay outside this model.
  • Place and work location model - Supplies base and additional work locations from which jurisdictional, safety and working-time regimes are derived.

composes

  • Schedule, roster and availability model - Concrete dated duty and shift instances are composed from the assignment's pattern, availability and limits, and reference the assignment identifier.
  • W3C PROV-O qualified association and delegation - Provenance mixin for authorization, acting-on-behalf-of delegation and role-at-time-of-action, applied to approval records and lifecycle events.

aligned

  • W3C Organization Ontology (org:Membership, org:Post, org:Role) - Primary structural alignment for the reified n-ary agent-organization-role relation with a validity interval. Known divergence: org:memberDuring leaves its range unconstrained, so this model imposes RFC 3339 instants.
  • HL7 FHIR PractitionerRole - Domain alignment showing role code, specialty, organization, location, service scope, period and availability carried on the assignment. Known divergence: FHIR conflates post and membership into one resource and has no separation-of-duty or authority constructs.
  • schema.org Role and OrganizationRole - Publication alignment for lightweight external exposure. Known divergence: no lifecycle status, no authority, and date-only validity, so it is an export target only and never a semantic source.
  • HR Open Standards StaffingAssignment (Contingent Staffing 3.3) - Alignment for the tri-party case in which a resource engaged by one organization is placed with a customer. Known divergence: the consortium's newer JSON API set has no Assignment resource, so no stable modern JSON counterpart exists.
  • NIST/INCITS RBAC constraint model - Alignment for static and dynamic separation of duty and cardinality constraints. Known divergence: standard RBAC user assignment carries no temporal bounds, so the temporal semantics are supplied by this model and must not be assumed on the RBAC side.
  • RFC 3339 timestamp profile - Governs every effective, transition, authorization, notification and observation time in the model, including the reserved meaning of an unknown local offset.

neighbor

  • WM-ORG-004 Position - A post exists independently of the person or persons filling it; the assignment is the time-bounded occupancy of that post. Reclassifying a post does not create an assignment, and ending an assignment does not abolish the post.
  • WM-ORG-005 Employment relationship - The employment relationship is the legal engagement; one engagement can carry several concurrent assignments, and an assignment can rest on a commercial staffing contract or a volunteer arrangement instead of employment. Statutory written particulars attach to the engagement, not to each assignment.
  • Role and occupation classifiers (ESCO/ISCO-08, professional specialty codes) - A role is an abstract concept in a controlled vocabulary; the assignment is a concrete dated instance that cites it. Classifier codes are alignments held on the assignment, not definitions owned by it.
  • Human task / work-item model - A task instance has its own short-lived lifecycle with potential owners and an actual owner established by claiming. A work assignment is the standing eligibility and authority from which potential-owner sets are derived; it does not carry task-instance state.
  • Access management and entitlement model - RBAC user-to-role assignment is a downstream projection of this model. The permission catalogue, role hierarchy and session activation are governed elsewhere; this model supplies the authoritative temporal and organizational basis for provisioning and de-provisioning.
  • Schedule, roster and availability model - The assignment states the working pattern, availability windows and applicable duty limits; the concrete dated shift or duty instances live in a scheduling model that references the assignment identifier.
  • Time capture and timecard model - Hours actually worked are observations evidencing performance under an assignment. They are never the assignment itself and must not be used to infer its effective period.
  • Incident and operational tasking records - Operational tasking documents bind resources to a single operational period and a specific incident objective. They are short-horizon instances of assignment semantics and should reference, not replace, the standing assignment where one exists.

parent

  • WM-ORG-005

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identifier issued by the authoritative master system for assignments in the adopting Dimension, recorded with that system's name or URI
  • Governed global identifier or IRI where one exists for the assignment or its instrument, recorded with its issuing authority
  • UUID or ULID minted by the adopting Dimension, used only when neither of the above exists and never derived from personal data
  • Explicitly not an identifier: any date, period, job title, person name, email address or composite of these

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Filled

  • An assignment record names assignee, organization unit, role or post, scope and validity period.
  • Confused with the position, the employment contract, a roster shift and a task.

Capabilities and actions required Filled

  • Propose assignment: Create a candidate assignment binding an agent, an organization, a role or post, a scope and a period, without conferring any authority.
  • Validate assignment eligibility: Evaluate all prerequisite and constraint rules for a candidate or live assignment and classify each outcome as pass, warning or block.
  • Authorize assignment: Record a competent authorization decision for a validated assignment, together with its basis and any conditions.
  • Activate assignment: Bring an authorized assignment into force at its effective start, conferring the recorded authority and triggering downstream provisioning.
  • Amend assignment: Apply an effective-dated change to a live assignment, classify its materiality and trigger any notification duty.
  • Suspend or resume assignment: Temporarily render an assignment non-exercisable, or restore it, without ending it.
  • Delegate assignment authority: Record that another agent acts on behalf of the assignee for named authorities over a bounded period.
  • Transfer or succeed assignment: End one assignment and start another for the same post or scope with an explicit succession link and a coverage decision for any interval.
  • End assignment and offboard: Close an assignment at its effective end and drive handover, revocation and evidence capture.
  • Resolve effective assignments as of an instant: Return the set of assignments in force for an agent, post or unit at a given instant, using stored state and effective periods with a declared precedence rule.
  • Detect assignment conflicts: Scan the assignment population for separation of duty breaches, cardinality and coverage violations, capacity over-allocation, overlaps and expired prerequisites.
  • Project assignment to a downstream consumer: Emit a consumer-specific representation of the assignment under a published crosswalk and reconcile the consumer's state against this model.
  • Establish detail or time-limited promotion: Create a time-bounded higher-grade or other temporary occupancy with notice of return terms and 120-day competition accounting.

Hazards and failure modes required Filled

  • Lingering access after the assignment ends.
  • Conflicting duties breaching segregation rules.
  • Overwork from overlapping assignments.

Standards and interfaces required Filled

  • HR Open Standards.
  • ISCO-08 and ESCO occupation classifications.
  • W3C Organization Ontology posts and memberships.
  • ISO 8601 date and time.

Context of use required Filled

  • Written-particulars duties are evidenced from UK primary legislation as a concrete instance. Equivalent duties exist elsewhere, notably in EU law, but the enumerated particulars, deadlines and definitions differ by jurisdiction; the EUR-Lex text could not be retrieved during this research and is not relied upon.
  • AI Act obligations on assigning human oversight, informing workers and retaining logs apply to deployers of high-risk AI systems within the EU regime only, and do not generalize to all assignments.
  • ESCO and ISCO-08 alignment assumes a European or ILO-aligned classification context; other jurisdictions use national occupational schemes that map imperfectly.
  • Duty and rest limits are strongly sector- and jurisdiction-specific; the model carries the constraint structure but asserts no particular limit values.
  • Incident-management assignment artifacts are drawn from a United States national framework; comparable national frameworks exist elsewhere with different form sets.
  • The distinction between engaging organization and host organization assumes a legal environment that permits agency or contracted supply of labour.
  • Merit promotion, 120-day detail accounting and five-year time-limited promotion limits are United States federal (5 CFR Part 335) and apply only where that law is the appointing regime.
  • GDPR Article 88 and ICO employment-records guidance apply to EU and UK processing; other privacy regimes may impose different retention and erasure outcomes.
  • Unnamed locum occupancy is drawn from FHIR healthcare practice and may be uncommon in general HRIS.
  • Secondment, labour dispatch and posted-worker constructions are jurisdiction-specific and are represented here only as host-versus-home employer.

Sources Filled

  1. The Organization Ontology (org:Membership, org:Post, org:Role, org:memberDuring) - World Wide Web Consortium (W3C)
  2. FHIR Release 5 - PractitionerRole resource - Health Level Seven International (HL7)
  3. Web Services - Human Task (WS-HumanTask) Specification Version 1.1 - OASIS
  4. Role Based Access Control (RBAC) - INCITS 359-2012 - National Institute of Standards and Technology (NIST) / INCITS
  5. schema.org Role (with OrganizationRole, EmployeeRole, roleName, startDate, endDate) - Schema.org Community Group
  6. ESCO classification - Occupations pillar - European Commission (DG Employment, Social Affairs and Inclusion)
  7. PROV-O: The PROV Ontology - World Wide Web Consortium (W3C)
  8. RFC 3339: Date and Time on the Internet - Timestamps - Internet Engineering Task Force (IETF)
  9. Regulation (EU) 2024/1689 (AI Act), Article 26 - Obligations of deployers of high-risk AI systems - European Commission - AI Act Service Desk
  10. Employment Rights Act 1996, section 1 - Statement of initial employment particulars - UK Parliament / The National Archives (legislation.gov.uk)
  11. RFC 9073: Event Publishing Extensions to iCalendar (PARTICIPANT, VLOCATION, VRESOURCE) - Internet Engineering Task Force (IETF)
  12. NIMS ICS Form 204, Assignment List (v3.1) and ICS Form 203, Organization Assignment List (v3) - Federal Emergency Management Agency (FEMA), U.S. Department of Homeland Security
  13. HR Open Standards APISpecifications repository - HR Open Standards Consortium, Inc.
  14. HR Open Standards - Standards (Contingent Staffing HR-XML 3.3: StaffingOrder, StaffingResource, StaffingAssignment, TimeCard, WorkerOnBoarding) - HR Open Standards Consortium, Inc.
  15. HL7 FHIR PractitionerRole Resource - HL7 International
  16. Role Based Access Control FAQs and INCITS 359 reference model - National Institute of Standards and Technology
  17. 5 CFR Part 335 Promotion and Internal Placement - U.S. Office of Personnel Management
  18. ISA-95 Standard: Enterprise-Control System Integration - International Society of Automation
  19. Regulation (EU) 2016/679 Article 88 Processing in the context of employment - European Union
  20. Employment practices and data protection: keeping employment records - UK Information Commissioner's Office
  21. R198 Employment Relationship Recommendation, 2006 - International Labour Organization

Open questions

  • Retrieve primary retention instruments (statutory limitation periods, tax and social-security record-keeping duties, and the regulator guidance in its original published form) to convert the retention dimension from a declared gap into evidence-backed minimum periods; both providers failed to reach primary text on this dimension.
  • Retrieve an open or licensed normative definition of full-time-equivalent, effort fraction, headcount boundary and coverage metrics (ISO 30414 and ISO 30400 were paywalled or returned HTTP 403 for both providers) so that workforce measurement can stop publishing as an undefined declaration.
  • Retrieve the EU transparent and predictable working conditions directive text from EUR-Lex to generalize the written-particulars and unpredictable-pattern duties beyond the single national statute currently relied upon, and to resolve whether particulars attach per engagement or per assignment.
  • Retrieve HR Open Standards position and assignment JSON schemas and the IEC 62264-1 personnel object model text to firm up the interoperability crosswalk and to convert the ISA-95 boundary from an overview-page claim into a sourced neighbour note.
  • Retrieve at least two non-US national personnel-action regimes and one collective-agreement-governed regime so the accepted personnel-action typology and time-limited-form constraints can be generalized or explicitly partitioned by jurisdiction.
  • Machine-parse the incident-management assignment-list forms and retrieve the ILO employment-relationship recommendation full instrument text; both were cited from landing pages or unparsed PDFs and currently support only form identity and stated purpose.
  • Resolve the two deferred residues from rejected Grok findings: the planned-versus-actual clock as a third temporal axis distinct from effective-versus-record time, and evidence-artifact integrity hashing plus an explicit record-quality claim on the assignment record.
  • Compensation, pay rate, bill rate and benefit determination for the assignment; referenced only as an engagement-level concern.
  • Cost allocation, chargeback and inter-company recharge arising from an assignment.
  • Collective agreement coverage, bargaining unit membership and consultation procedure detail.
  • Performance objectives, appraisal outcomes and succession candidate pools linked to an assignment.
  • Immigration and posting-of-workers formalities beyond a permission validity date, including social security coordination certificates.
  • Demand forecasting, vacancy management and the matching or ranking algorithms that select an assignee.
  • Capability, model version and evaluation history of a non-human agent assignee; only the accountability link is modelled.
  • Health surveillance and reasonable-adjustment records that condition an assignment; treated as external evidence pointers only.
  • Field-level detail of the incident assignment-list artifact: the FEMA PDFs could not be machine-parsed, so only the form identity and stated purpose are relied upon.
  • Sector-specific duty and rest regimes are referenced structurally but no single regime's limits are asserted.
  • ISO 30400:2022 HR terminology is paywalled and was not retrieved; job, position and assignment terms from that standard are not claimed.
  • HR Open Standards position-assignment schemas were not retrieved as public technical text.
  • IEC 62264 object-model attributes for personnel class assignment remain behind the ISA and IEC paywall; only the public ISA-95 overview was used.
  • ILO Recommendation No. 198 full instrument text did not load from NORMLEX in this run; only the official landing page is cited.
  • Military permanent-change-of-station and assignment-order systems were not fetched.
  • Shift roster, cost-center accounting splits and compensation as a function of occupancy lack primary support here.
  • National labour-dispatch and agency-worker regimes beyond the host-versus-employer distinction are not specified.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-org-016-work-assignment/spec.yaml, ver-cy/world-models/card-supplements/wm-org-016-work-assignment.json