{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/3447a43a929d4b14850f88a7a55bf5c1\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/3447a43a929d4b14850f88a7a55bf5c1-402386089dadd5c0.gif","duration":393.088,"title":"Daily Ops Breakdown","description":"This Loom explains the new Daily Ops report and how to use it to understand what happened in the venue versus what was scheduled. It covers scheduling variance, staffing hours with flags for clock-in delays over five minutes and minute-level variance, and totals at the bottom to show differences from the plan (for example, 33.5 hours scheduled versus 32.7 worked). It also reviews training and maintenance signals including completed training modules, overdue timed resets dating back to April (noting Aiden has several), and hint message activity between hosts and game masters. Additional sections track timed and untimed resets, reset errors, tasks and expired or incomplete items, room utilization by slot fill percentage (for example 88 percent versus 25 percent), config changes, and test games."}