Resolve
No production tasks are declared, so crew and load-in cannot be scheduled.
Declare production tasks in Vendor Pack with duration, phase and responsible vendor.
Logistics & crew
The room has to be built before it can be beautiful.
This surface reads the production declarations you already made. It computes crew load, shared-access collisions and expected arrivals; a missing crew count or dock stays missing instead of becoming a house assumption.
The answer
Fail closedNo production tasks are declared, so crew and load-in cannot be scheduled.
- What causes it
- Not established yet.
- What changes it
- Declare production tasks in Vendor Pack with duration, phase and responsible vendor.
Inputs, assumptions and working
Read from the Vendor Pack declarations and the Event Project. Load-in starts at a time nobody has set, so calls show as offsets.
Crew-hours count only the tasks with a declared crew: 0 hours known, 0 tasks with no crew count. A missing count stays missing; it is not filled with a house assumption.
A collision is two declared calls on the same access point at the same time. Vendor capacity is never inferred.
Peak declared crew
—
Known crew-hours
—
Expected arrival lines
0
Access collisions
0
Operational gaps
What still costs somebody a phone call
Crew calls
Who is on the floor, and when
No schedulable production tasks are declared yet.
Venue access evidence
What the building has actually told you
No venue access evidence is carried into this event yet.
Arrival register
What has to reach the building
No arrival-bearing rental or own-stock lines are on the Event Project yet.