Team demand analysis
Stage 2 · Analysis
The operator jobs behind Team searches
Interpret observed language, identify required evidence, and preserve record authority before proposing Tools.
- 1
Maintain the Kitchen roster
Record the people who work in this Kitchen, link a member to a User when invited, and preserve member identity independently from account identity.
A named Team member may exist before login. Team membership does not itself create a User, App membership or Workspace access.
Owner: KitchenTeamMember with User and AppUser boundaries
- 2
Assign Kitchen responsibility
Record Kitchen role and Station responsibility without treating a label as verified competence or access authority.
Role, Station assignment, skill evidence and permission are separate facts.
Owner: Kitchen Team and Stations
- 3
Know who is trained for the work
Record reviewed Station competence, required training, completion evidence, certification issuer and expiry.
A note or uploaded file does not automatically prove competence. Every claim needs type, source, reviewer and effective dates.
Owner: Kitchen Team evidence composed with Stations and Food Safety
- 4
Hand operational context to the next Team
Record unresolved work, exceptions and acknowledgements for a Kitchen-local shift or service.
Handover links to Orders, Mise, Inventory, Food Safety and other owners; it does not duplicate their records or become generic task storage.
Owner: Team handover referencing owning capability records
Record map
Evidence the capability owns, references, or derives
kitchen.team.member
Kitchen Team member
Owner: Team
Team owns the Kitchen-local named member and keeps it distinct from User identity, App membership and access.
- member identity and optional User link
- Kitchen role and status
- permissions and audit stamps
kitchen.team.competence-evidence
Competence and training evidence
Owner: Team
Reviewed, dated evidence remains separate from roles, permissions and unverified uploaded material.
- member and requirement
- evidence source and reviewer
- effective and expiry dates
- review status
kitchen.team.handover
Shift handover
Owner: Team
Handover owns its time-bound envelope and references unresolved records without copying them.
- period and author
- recipient scope
- linked operational records
- notes and acknowledgement
Required record questions
What must Team make knowable?
- Which selected Kitchen owns this Team member row?
- Is this a named member, linked User, AppUser or authorized operator—and which relationships actually exist?
- Which Kitchen role and Station assignments are recorded, and when are they effective?
- What evidence supports each competence, training or certification claim?
- Who reviewed the evidence, when does it expire, and what remains unknown?
- Which handover period, author, recipients and acknowledgements apply?
- Which linked operational record owns each handover issue?
- Does any field incorrectly introduce payroll, scheduling, generic HR or access authority?