Team

Team instance identifier assignment

A team instance normally has no authoritative external register. SCIM supplies a server-assigned immutable id plus a client-supplied externalId; FHIR CareTeam and Group both carry 0..* business identifiers; GLEIF/ISO 17442 covers legal entities only. Identity therefore resolves in priority order: authoritative master-system identifier (HRIS org-unit key or IdP group id), then a governed IRI in the adopting Dimension's namespace, then a Dimension-minted UUID or ULID. Names and dates are never identifiers.

1. Which system of record is authoritative for this team's identifier, and what is the key? identity
2. If no master-system key exists, which governed IRI or Dimension-minted UUID/ULID is assigned, and by whom? identity
3. Which alternate business identifiers must be carried, and which are merely correlational? interoperability
4. When two records are found to describe the same team, which survives and how is the loser tombstoned? exception

Boundary against organization, group and position

FHIR states that Organization is a formally recognized entity while Group is an undifferentiated collection lacking formal legal recognition, and that CareTeam participants are differentiated individuals. W3C org separates FormalOrganization, OrganizationalUnit and OrganizationalCollaboration. HR Open publishes no Team noun at all. Each instance must therefore declare which of these it actually is, or be rejected as a team.

1. Is this collective an internal unit of one formal organization, a cross-organization collaboration, or a rule-defined cohort? classification
2. Is membership enumerated by identified participants or defined by characteristics? composition
3. Does the team have any separate legal recognition, and if not, which legal entity bears its obligations? authority
4. What disqualifies this record from being a team under this model? validation

Names, slugs and descriptions

Human-readable names, alternative labels, generated slugs or mail nicknames, and optional descriptions that distinguish like teams without serving as identity.

1. What is the preferred human-readable name of the team, and in which language or locale is it expressed? identity
2. What alternative names, generated slugs, mail nicknames or notations exist, and which system derives them from the preferred name? identity
3. What description or comment distinguishes this team from similarly named teams, such as red versus green trauma teams? definition
4. Who is authorized to change the team name, description or profile picture? authority

Containing and managing organization

Most workplace teams are units of one FormalOrganization or Microsoft tenant. FHIR separately records managingOrganization as the organization responsible for the care team. GitHub teams exist only inside an organization.

1. Which Organization instance contains this team, and is the team a unit with meaning only inside that organization? relationship
2. Which organization is responsible for managing the team, if that is different from the containing organization? ownership
3. Which tenant, directory or provisioning domain hosts the team record? identity
4. Must every member already belong to the containing organization, as GitHub requires, or may outsiders participate? constraint

Team type and category

FHIR CareTeam carries category 0..* and Group carries a required type from a closed value set; org:classification allows an organization-specific scheme; schema.org offers department and subOrganization as publication projections. Classification is multi-valued and scheme-qualified, never a single free-text label.

1. Which controlled classification schemes apply, and what is the code in each? classification
2. Is the team standing, time-boxed or incident-activated, and what evidence supports that? classification
3. Does the team qualify as a publicly presented department with its own URL, logo or hours? interoperability

Capability typing and tier

FEMA types a team by minimum capability into Type 1-4, where each tier fixes an overall function, minimum personnel with qualification codes, equipment and communications, plus composition and ordering specifications. This is a type-level artifact with its own identifier and version, distinct from the team instance that claims to meet it.

1. Against which published typing definition and version does this team claim a tier? evidence
2. Which capability tier is claimed, and what verified evidence supports the claim? quality
3. Where does the current composition fall short of the claimed tier, and what compensating measure applies? constraint
4. What must a requester agree before this team can be deployed or engaged? process

Team charter and mandate

OSHA requires an employer to prepare and maintain a written statement establishing the existence of the brigade, its basic organizational structure, the type, amount and frequency of training, the expected number of members and the functions to be performed. W3C org supplies org:purpose, FHIR supplies CareTeam.reason, FEMA supplies overall function, and the Scrum Guide supplies the pattern of a single shared objective. The charter is the authoritative statement of scope and is versioned.

1. Is there a written constituting statement, who approved it, and when did it take effect? authority
2. What is the team's purpose and the specific functions it is expected to perform? definition
3. Is any element of the charter mandated by law, regulation or contract rather than chosen? requirement
4. What objective is the team accountable for, over what period, and how is attainment judged? measurement
5. When must the charter be reviewed or revalidated, and what triggers an out-of-cycle review? lifecycle

Decision rights, ownership and reporting line

W3C org gives headOf, reportsTo, unitOf and hasPost; FHIR gives CareTeam.managingOrganization 0..* and Group.managingEntity; FEMA requires delegated authorities to be agreed before deployment; the Scrum Guide assigns distinct accountabilities within a single team. NIST separation of duties and least privilege constrain which decision rights may be concentrated in one holder.

1. Which single party is accountable for the team's outcomes, and through which post is that held? ownership
2. Which organizations manage or co-manage the team, and how are conflicts between them resolved? authority
3. Which decisions may the team make autonomously, which need approval, and up to what threshold? authority
4. Which combinations of decision rights must not be held by the same person? security
5. Where does the team sit in the reporting structure, and is that line solid or matrixed? relationship

Membership assignment record

W3C org expresses membership as an n-ary org:Membership with memberDuring so that duration, remuneration and contract references can be attached; FHIR CareTeam.participant carries role, member, onBehalfOf and coverage; FHIR Group.member carries period and an inactive flag; schema.org OrganizationRole carries roleName with startDate and endDate; SCIM requires membership changes to be applied via the Group resource. Membership is a first-class dated record, never a mutable array of names.

1. For each member, when did participation start and when did or will it end? temporal
2. Which system is authoritative for writing membership, and how are conflicting writes from HR and IdP reconciled? authority
3. Is a departed member marked inactive with a closed period or removed from the record entirely? state
4. How are backdated or corrected memberships recorded without losing the prior assertion? provenance

In-team role and position binding

org:Post is a reusable position held by an agent via holds/heldBy; HR Open OrganizationChart models units, positions and incumbents; CareTeam.participant.role types the participation itself. The in-team role is the binding, and is distinct from the position definition owned by WM-ORG-004 and from the occupation code owned by ESCO/ISCO-08.

1. Does this member occupy a defined position, or hold only a team-scoped role with no position behind it? composition
2. Which governed occupation code describes the work performed, and under which classification version? classification
3. May one member hold several roles in the same team at once, and how is that recorded? constraint
4. Which role carries leadership of the team, and is it the same as the accountable owner? authority

External and non-human participants

CareTeam.participant.onBehalfOf lets a participant act for another organization; Group.type admits practitioner, device and organization members; SCIM supports nested groups; org:OrganizationalCollaboration covers teams spanning organizations; PROV distinguishes Person, Organization and SoftwareAgent. Contractors, partner-org members, nested sub-teams and software or robotic agents must be representable without pretending they are employees.

1. On whose behalf does each external participant act, and under which contract? relationship
2. Are any participants software agents, devices or robots, and who is the responsible human principal? ownership
3. Does the team contain nested sub-teams, and is that permitted by the governing method or policy? composition
4. What data may an external participant see, and what is withheld? access

Parent-child and team-of-teams

GitHub allows one parent team and many children; child teams inherit parent permissions; listed members of a parent include child members but those members are not direct parent members. Secret teams cannot nest. Scrum forbids sub-teams and instead splits oversized teams into multiple teams sharing a Product Goal. SCIM Groups may nest Groups. FHIR CareTeam may have another CareTeam as a participant.

1. What is the parent team, if any, and does this team have exactly one parent as in GitHub or an open unit hierarchy as in ORG? relationship
2. Which child teams exist, and do their members count as inherited members of this team for listing, mentions or permissions? composition
3. Is nesting forbidden because this is a Scrum Team, a secret team, or another profile that rejects sub-teams? constraint
4. When size or complexity requires change, should the team split into sibling teams sharing a goal rather than adding a child team? decision

Invitation, synchronization and dynamic rules

Membership may be pending invitation, locked to an identity-provider group, or computed from a dynamic membership rule. Local writes may be forbidden while synchronization is active.

1. Which invitations to join the team are pending, who invited them, and when were the invitations created? event
2. Is membership synchronized from an identity-provider group, and does that block local add or remove operations? interoperability
3. Is membership computed from a directory rule, and is processing on or paused? process
4. Who may add or remove members when local writes are allowed: organization owner, team maintainer, team owner or another role? authority

Posts, positions and assignments

A Post exists independently of the incumbent and is the join to WM-ORG-004. A team may have posts even when vacant. Assignment of a holder is a time-qualified hold relation, not identity of the post.

1. Which posts or positions exist on this team, including vacant posts that currently have no holder? composition
2. Who currently holds each post, and may a post be held by more than one person at once? relationship
3. What is the assignment interval for each holder, with RFC 3339 start and end? temporal
4. Is the agent a member of the team ex officio because they hold a post, rather than by personal appointment? relationship

Allocation and capacity

CareTeam.participant.coverage expresses when a participant is available to the team; ISO 30414 reports workforce availability and productivity at organizational level; HR Open ships Timecard and Compensation domains that hold the underlying worker-level time data. Allocation is a property of the membership, expressed as a fraction or a schedule, and is the only defensible basis for team capacity.

1. What share of each member's working time is committed to this team, and over which period? measurement
2. Which other teams hold competing claims on the same member, and does the total exceed 1.0 FTE? constraint
3. During which hours and days is the team required to be staffed? temporal
4. Is reported capacity a planned commitment or an observed actual, and from which record? evidence

Minimum composition and staffing constraints

FEMA fixes minimum personnel and equipment per tier with qualification codes per position; OSHA requires the expected number of members to be stated and bars unfit members from interior structural firefighting absent a physician's certification; the Scrum Guide caps a Scrum Team at typically ten or fewer and forbids sub-teams. These are constraint profiles attached to the team, and they conflict with one another, so the applicable profile must be declared.

1. What is the minimum viable composition by role, and what happens when it is not met? constraint
2. Which constraint profile applies, and is it legally binding, contractual or methodological? requirement
3. Are there maximum size or nesting limits, and what evidence supports them? constraint
4. Are there fitness, medical or physical prerequisites for any role in this team? requirement

Competence coverage

ESCO links each occupation to essential and optional knowledge, skills and competences with governed URIs built over ISCO-08; FEMA publishes skillsets that can be assembled into Position Task Books; ISO 30414 reports a skills and capabilities area; the Scrum Guide requires cross-functionality, meaning the team holds all skills needed to create value. Coverage is a set relation between required competences and those actually held by active members.

1. Which competences does the team's mandate require, expressed in which governed vocabulary? requirement
2. Which required competences are held by only one active member or by none? quality
3. What evidence supports each claimed competence, and who assessed it? evidence
4. Can the team complete its expected functions without external hand-off, and if not, where does it depend on others? composition

Qualification currency and credentials

FEMA publishes job titles with position qualifications and Position Task Books, and its typing definitions carry per-position qualification codes; OSHA requires training before duty, at least annually for all brigade members and at least quarterly for interior structural firefighters, plus physician certification where fitness is in doubt. A credential held is not a credential current, and expiry must be modelled explicitly.

1. Which licences, certifications or task-book completions are required for each role in this team? requirement
2. When does each held credential expire, and what recurrence keeps it current? temporal
3. Which members are currently lapsed, and are they suspended from the affected duties? state
4. How is a credential verified against the issuing authority rather than self-asserted? validation

Team status lifecycle

FHIR CareTeam.status is proposed, active, suspended, inactive or entered-in-error, and Group carries a modifier active flag. The entered-in-error value matters: it separates a team that ended from a team that never should have been recorded, which is an erasure-relevant distinction that a simple active boolean cannot express.

1. What is the team's current status and since when? state
2. Which status transitions are permitted, and who may authorise each? lifecycle
3. How is an erroneously created team distinguished from one that ended normally? exception
4. What does suspension mean operationally for memberships, access and obligations? process

Effective dating and time semantics

RFC 3339 requires a full date, a full time with seconds and an explicit offset or Z, and reserves -00:00 for an unknown local offset. SCIM meta separates created from lastModified; PROV separates startedAtTime and endedAtTime on activities from generation of records. Event time (when the team changed) must be recorded separately from observation time (when the system learned of it).

1. For each assertion, when did the fact become true and when was it recorded? temporal
2. Is the local UTC offset known for each timestamp, or must -00:00 be used? temporal
3. How are open-ended and future-dated periods represented and queried as-of an instant? temporal
4. What timestamp precision is required, and where is a date alone acceptable? constraint

Formation and dissolution

schema.org supplies foundingDate and dissolutionDate; org:ChangeEvent records organizational change with resultedFrom links; FEMA's ordering specifications frame mobilization and demobilization preconditions. Formation and dissolution are events with their own authority, evidence and downstream obligations, not merely the endpoints of an interval.

1. Who authorised the team's formation and on what instrument? authority
2. What condition triggers dissolution, and is it time-based, objective-based or discretionary? lifecycle
3. On dissolution, where do open obligations, artifacts and members go? process
4. What entitlements must be revoked on dissolution, and within what window? security

Merge, split and transfer events

org:ChangeEvent explicitly links originalOrganization to resultingOrganization so that reorganizations are traceable; PROV wasDerivedFrom carries the same lineage semantics for records; ISO 30414 adds guidance on when multi-unit entities consolidate or report separately, which determines whether merged teams keep separate metric histories.

1. Which predecessor teams produced this team, and which successors did it produce? provenance
2. Does the team retain its identifier through the change, or is a new identity minted? identity
3. Are historical metrics and memberships consolidated, split or left with the predecessor? decision
4. When a team moves to a different parent unit, what changes and what must not? relationship

Interfaces, dependencies and collaborations

org:linkedTo relates organizations engaged in unspecified relationships and org:OrganizationalCollaboration models teams drawn from several organizations; CareTeam.telecom provides a central contact route for the team as a whole rather than for individuals. Dependencies between teams are typed edges with direction, criticality and an agreed interface.

1. Which other teams does this team depend on, and which depend on it? relationship
2. Through what agreed interface and service expectation does each dependency operate? process
3. What is the authoritative contact route for the team as a whole, distinct from any individual? interoperability
4. Is the team part of a wider standing collaboration, and who convenes it? composition

Site footprint and time coverage

org:Site with basedAt, hasSite, hasPrimarySite, hasRegisteredSite and siteAddress locates organizational activity; schema.org supplies location. Because RFC 3339 requires explicit offsets, a distributed team's coverage must be expressed with offsets or a named time zone, not local wall-clock text.

1. Which site is primary for the team, and which secondary sites are in use? spatial
2. How is the team distributed across sites, jurisdictions and time zones? spatial
3. Which obligations change because members sit in different jurisdictions? requirement
4. Are there hours in the required coverage window with no staffed member? validation

Team-level metrics binding

ISO 30414:2025 sets 11 human capital areas with 14 baseline required metrics, requires organizations to state their materiality interpretation, gives guidance on when multi-unit entities consolidate rather than report separately, and strengthens data governance and digital tagging. This model binds metrics to a team, a definition and an observation window; it does not restate formulae, and it must record that team-level granularity can breach both materiality and data minimisation.

1. Which metric definition and version is being reported, and who owns it? measurement
2. Over what window is each value measured, and at what instant was it computed? temporal
3. Is the value reported at team level, consolidated upward, or suppressed for materiality or re-identification risk? decision
4. How are values restated after a merge, split or definition change? quality

Evidence quality and health, safety and workload duties

PROV-O attributes every assertion to an agent through an activity, with qualifiedAssociation carrying hadRole and hadPlan; ISO 30414 moves human capital reporting toward auditable requirements and covers health, safety and wellbeing. OSHA imposes concrete recurring duties: training before duty, at least annually for all members and at least quarterly for interior structural firefighting, plus physician certification where a known condition is present.

1. Which agent asserted each team fact, acting on whose behalf and under what plan? provenance
2. Is each value system-derived, self-reported or audited, and what is its known error? quality
3. Which recurring health, safety or training duties attach to this team, and are they current? requirement
4. What workload or exposure limits apply, and how are breaches detected and escalated? constraint
5. What would an auditor need to reconstruct a reported team fact end to end? validation

Record provenance and artifact integrity

SCIM meta carries created, lastModified, location and a version usable for optimistic concurrency; PROV-O supplies wasGeneratedBy, wasAttributedTo and wasDerivedFrom; FEMA publishes each definition with a version, original release date and last-updated date. Every artifact in this aggregate carries an integrity value and a supersession link rather than being edited in place.

1. Which system generated each record, and from which upstream record was it derived? provenance
2. How is concurrent modification detected and rejected? validation
3. What integrity value proves an artifact has not changed since issue? evidence
4. When a record is corrected, how is the superseded version preserved and located? provenance

Access scope, privacy and retention

The European Commission states the GDPR principles of purpose limitation, data minimisation, accuracy, storage limitation for the shortest time possible, integrity and confidentiality, and accountability, and notes longer retention is possible for archiving or research with safeguards such as anonymisation. NIST SP 800-53 Access Control and Personnel Security families govern provisioning, least privilege and revocation on transfer or termination. FHIR assigns CareTeam the Patient security category and Group the Business category, showing that team records inherit sensitivity from their members.

1. What is the default visibility of the team record, and which elements are more restricted? access
2. For what declared purpose is each personal element held, and what use is out of scope? privacy
3. How long is each class of team record retained, and what starts the clock? retention
4. On erasure or objection, which elements are deleted, which anonymised and which must be kept? exception
5. When a membership ends, within what window are entitlements revoked and how is that evidenced? security

Visibility, privacy and sensitivity

GitHub contrasts visible and secret teams, with API values secret and closed; secret teams cannot nest and still leak their name if @mentioned. Microsoft visibility defaults to Public and classification must match a tenant-preconfigured sensitivity label. People outside the organization cannot view GitHub teams.

1. What is the visibility or privacy class of the team, and which vocabulary is in use: GitHub secret or closed, GitHub visible or secret, or Microsoft Public or Private? access
2. What sensitivity or business-data classification applies, and does it match a preconfigured directory label? security
3. Who can discover, view or @mention the team, and does a mention of a secret team reveal its name? access
4. What privacy duty applies when distributing membership lists across provisioning domains, as SCIM warns? privacy

Entitlements and member capabilities

Teams hold permissions on resources such as repositories, inherit child-team access from parents, and expose member, guest and messaging capability settings. Entitlements are relationships to resources, not the team itself.

1. Which resources can the team access, at what permission level, and are those entitlements inherited by child teams? access
2. What may ordinary members create, update or delete inside the team, such as channels, apps, tabs or connectors? access
3. What may guests do, and how does that differ from member and owner capabilities? access
4. What exception grants a person or child team broader access than the team default, and who authorized it? exception

External mappings and conformance claims

A team can project to org:OrganizationalUnit or org:OrganizationalCollaboration, to a SCIM Group, to a FHIR CareTeam or Group, to schema.org Organization with OrganizationRole, and to HR Open OrganizationChart units and positions. None of these is lossless: SCIM lacks mandate and lifecycle, FHIR CareTeam is subject-scoped, HR Open ships no Team noun at all, and FHIR Group deliberately denotes an undifferentiated collection. Conformance must be claimed per profile with evidence, never asserted globally.

1. Which external profiles must this team be projected into, and at which versions? interoperability
2. Which fields are lost or distorted in each projection, and how is the loss disclosed? quality
3. What evidence supports a conformance claim against a given profile? evidence
4. Can a projection be reimported without losing identity or membership history? validation