Team Requirement Intelligence · under development
Team Requirement Intelligence: role and headcount proposals, never people selection.
A Production needs the right roles across the right windows, but software cannot infer safe or lawful staffing from an equipment list. Operations360 is developing review candidates that keep workload assumptions, evidence gaps and human responsibility visible.
Current evidence state Under development: Crew requirement, availability and evidence foundations have been verified in staging; Team recommendation and optimisation are not generally available.
The operator problem: role demand is often reconstructed too late
Crew needs can be scattered across quotations, equipment packages, venue calls and experienced coordinators' memory. The same Production may require preparation, loading, travel, setup, operation, strike and return work with different skills and windows. A review candidate must expose its workload assumptions and never turn a role estimate into a person assignment.
What the current evidence supports
Crew evidence foundations
Tenant-scoped Crew requirements, availability windows, invitation states, attendance, skill/certification evidence and bounded recommendation evidence have staging acceptance.
Role and headcount candidates
Team Requirement Intelligence is being developed to propose Production roles, quantities and windows with assumptions and missing inputs for planner review.
Future Team Optimisation
Future Team Optimisation may explore allocation choices only after workload, eligibility, travel, fairness, permissions and review policies are accepted. It is roadmap direction, not current capability.
Evidence inputs
Approved Production scope
Current department requirements, venue, schedule, setup/show/strike windows, work locations and change history.
Workload evidence
Recorded equipment/package volume, preparation and loading tasks, operating positions, hand-offs and external-service responsibility.
Role policy
Tenant-approved role definitions, required skills or certifications, supervision, rest/travel constraints and privacy-safe operational rules.
Known uncertainty
Missing workload, venue, travel, safety, legal, competence or availability evidence remains a review question rather than an inferred answer.
Bounded outputs
Role and headcount proposal
The candidate may name required role types, quantities and operating windows, with its source scope and assumptions.
Planner questions
Unresolved workload, supervision, competence, travel, rest, safety and legal adequacy are surfaced for responsible review.
Team Optimisation
Ranking, selecting or optimising people and allocations is explicitly outside this milestone and remains future roadmap direction.
Worked Production examples
Sound rental
A Sound Production needs role demand before names
An approved scope records prep, load-in, setup, rehearsal, show, strike and return windows, but no reviewed staffing requirement exists.
- 01Read the approved Production scope and current operating windows.
- 02Prepare role and headcount candidates from tenant-approved role definitions and recorded workload assumptions.
- 03Expose missing supervision, competence, travel, rest, safety and legal inputs.
- 04Ask the authorised planner to revise or approve the requirement.
- 05Leave every person unselected and uncontacted.
Bounded outcome The under-development candidate separates role demand from individual availability, competence, invitation and assignment decisions.
Lighting · LED/video · staging · front of house
A multi-zone event preserves departmental responsibility
Several departments share venue windows but require different approved roles, work areas and responsible leads.
- 01Keep each role requirement linked to its department, zone and time window.
- 02Show shared loading, access and hand-off dependencies without merging roles.
- 03Prepare headcount candidates and unresolved reviewer questions.
- 04Require departmental and Operations review before any invitation workflow.
Bounded outcome One Production coordinates the demand while qualified planners retain discipline-specific staffing judgement.
Team review before invitation or assignment
Under development This review sequence describes the intended evidence contract; it is not a generally available autonomous workflow.
- 01Confirm the current Production scope, workload, locations and operating windows.
- 02Apply only tenant-approved role definitions and recorded requirement policies.
- 03Show role/headcount candidates, assumptions, gaps and excluded decisions.
- 04Require qualified review of competence, supervision, safety, legal adequacy, rest and travel.
- 05Let an authorised planner approve or revise role demand.
- 06Use separate governed availability, invitation and assignment workflows for people.
Team and people boundary
- A proposal cannot establish legal or safe staffing adequacy.
- A proposal cannot prove a person's competence, qualification, availability or willingness.
- A proposal cannot rank, select, contact, invite, assign or replace people.
- A proposal cannot optimise allocations, travel, fairness, cost or workload.
- Future Team Optimisation is roadmap direction only and requires separate evidence, privacy, policy and approval gates.
Frequently asked questions
Is Team Requirement Intelligence generally available?
No. The role/headcount recommender is under development. Crew foundations have been verified in staging, while Team Optimisation remains planned.
Will it choose or contact Crew?
No. It cannot rank, select, contact, invite, assign or replace people. Separate authorised workflows retain those decisions.
Does a proposal prove the team is safe or legally adequate?
No. Qualified reviewers must decide legal and safe adequacy, competence, supervision, rest, travel and discipline-specific responsibility.
What is Future Team Optimisation?
It is roadmap direction only. Any later optimisation would require governed evidence, eligibility, privacy, fairness, travel, workload and human-approval contracts.
Evaluate the operating model before the roadmap.
Use the current rental workflow and evidence guidance to assess fit. These requirement-intelligence pages do not promise general availability.
Review the Production lifecycleReview AI and approval boundaries